A D&D NPC tracker for continuity: who they are, what they know, and what was promised

What a D&D NPC tracker is actually for

A D&D NPC tracker can do two different jobs, and most templates only do the first. One is prep: an NPC you are writing before the session, with a stat block, a personality and a secret. The other is continuity: keeping a character the same person across twenty sessions after the table has met them, argued with them, nicknamed them and made them promises.

There is a good free sheet for the first job. The NPC Tracker on D&D Beyond's Tracking Sheets page is one of nine sheets in its free Basic Rules, and its fields — listed with their source in the table below — are built around an NPC you author: a stat block, alignment, personality, appearance, a secret. If what you need is somewhere to design an NPC before game night, download that one and you are done.

This page is for the second job. What breaks continuity is rarely a stat block. It is the barkeep you improvised in session three coming back with a different voice, the favour the party was promised and you forgot, the merchant who mentions a secret only the party knew, the guard captain the party humiliated in session nine who is somehow friendly again by session twelve. None of that fits on a prep sheet, because none of it existed until the table made it happen.

So this tracker records what the table touched rather than what you designed: the names the party actually uses, when the NPC was first and last seen, the voice, what they want, what they know, what was promised in both directions, how they feel about the party now, and the thread they are still holding.

The DM's NPC tracker template (copy this)

One card per NPC who matters. It is plain text, so it pastes cleanly into a notes app, a shared doc or a spreadsheet cell, and it fits on an index card if you write small. Keep every line short enough to read in the two seconds before the NPC opens their mouth.

The last block is a change log, and it is the part most templates leave out. When an NPC's attitude or situation changes, do not overwrite the old value — add a line with the session number. Twelve sessions from now, why the guard captain hates the party is exactly the question someone will ask.

NPC TRACKER
NAME: _________________________________________
ALSO CALLED: __________________________________
  (what the party actually says - search for these)
WHO, IN ONE LINE: _____________________________

FIRST SEEN: session ___   where: _______________
LAST SEEN:  session ___   last words to the party:
  "____________________________________________"

VOICE: pitch ____________  pace ____________
       tic ___________  habit _______________
WANTS: _______________________________________
KNOWS: (what they know that matters)
  ____________________________________________
DOES NOT KNOW: (so they never act on it)
  ____________________________________________

THEY PROMISED THE PARTY: ______________________
THE PARTY PROMISED THEM: ______________________
ATTITUDE TO THE PARTY: hostile / wary / neutral / warm / loyal
  because: _______________________ (session ___)
OPEN THREAD: _________________________________

CHANGES (add a line - never overwrite)
  session ___: ________________________________
  session ___: ________________________________

A filled-in example: one NPC, three sessions in

Here is the card for a harbormaster the party has met three times. Every line is a handle rather than a description: enough to pick her back up mid-scene, not a character study.

Notice which lines did the work. ALSO CALLED is how you find her again, because by session nine nobody at the table said Sera Vell; they said the nervous one. DOES NOT KNOW stops her acting on a secret she never learned, one of the easiest ways for a long-running NPC to get quietly broken. And the change log explains her attitude, which the attitude line on its own never does.

NPC TRACKER
NAME: Sera Vell
ALSO CALLED: the harbormaster, "the nervous one"
WHO, IN ONE LINE: Greyport harbormaster, owes the Ash Guild

FIRST SEEN: session 3   where: Greyport docks
LAST SEEN:  session 9   last words to the party:
  "Then you never saw the manifest. Understood?"

VOICE: pitch high  pace clipped
       tic never finishes a sentence
       habit taps the counter when she is lying
WANTS: her Ash Guild debt cleared before winter
KNOWS: the Marrow shipment was not grain
DOES NOT KNOW: the party has the second manifest

THEY PROMISED THE PARTY: a berth for the Gull, no questions
THE PARTY PROMISED THEM: keep her name out of it
ATTITUDE TO THE PARTY: wary
  because: they lied to her about the cargo (session 6)
OPEN THREAD: who paid her to lie in session 9?

CHANGES
  session 3: warm - party paid the berth fee in full
  session 6: wary - caught the party lying about cargo
  session 9: lied about the manifest (tapping the counter)

When an NPC earns a card

Not every name gets one. A tracker with a card for every innkeeper you ever voiced is a tracker you stop opening, so use a promotion rule instead of good intentions.

• During play, write only the name and a two-word tag, the moment you say the name out loud — an N line on the in-session notes sheet, or a blank index card behind the screen. The other fields are cheap to rebuild after the game. The name is not.
• After the session, give a card to anyone who spoke to the party twice, made or received a promise, or knows something the party wants. Everyone else goes on the one-line roster further down.
• Every time a carded NPC appears, update LAST SEEN and their last words, and add a CHANGES line if anything moved. That is thirty seconds per NPC in your post-game notes.
• When an NPC dies, leaves or is resolved, close the card rather than deleting it. Dead NPCs have relatives, and players remember exactly who they still owe.

What each line on the sheet is protecting you from

Every field is there to stop one specific continuity failure. If a line does not match a failure your campaign actually has, delete it — a shorter card you keep up beats a complete one you abandon.

• ALSO CALLED: parties rename NPCs constantly, and a tracker you can only search by the name you gave them fails the first time you need it mid-scene.
• FIRST and LAST SEEN: a session number is the index into everything else — your notes, your recap, the recording if there is one. Without it, finding the scene means rereading the campaign.
• VOICE: the hardest thing to recover after a gap and the most obvious when it slips. The campaign memory guide explains why the mechanical handles reload and a word like mysterious does not.
• KNOWS and DOES NOT KNOW: an NPC acting on information they could not have reads to players as the DM cheating, and it is exactly the kind of slip they notice.
• Promises in both directions: the load-bearing beams of a campaign. The party will remember what they were promised long after you have forgotten offering it.
• ATTITUDE with a reason: hostile tells you nothing about how to open the next scene. Hostile because the party burned his warehouse does.
• OPEN THREAD: the hook this NPC is still holding. Reading down these lines before a session is half your prep.

A one-page NPC tracker sheet for everyone who does not need a card

Most NPCs get a line, not a card. This roster holds a few dozen of them on one page: enough to stay consistent about a shopkeeper's name and mood without pretending they need a backstory. Promote anyone who starts to matter.

Sort it by last seen before you prep. The names at the bottom are the ones the players have forgotten, and one of them turning up again is a cheap way to make the world feel like it kept moving without the party. The session prep checklist has a names step and a loose-threads step, and this sheet is where both come from.

NPC ROSTER - one line per NPC. Promote to a card when
they start to matter. Sort by last seen before you prep.

NAME (also called) | who | seen first-last | attitude | thread

Merrin | barkeep, owes Ash Guild | s3-s9 | warm | -
Pell ("Pockets") | fence, Lower Ward | s5 | wary | wants map
______________ | _______________ | _____ | _____ | ______
______________ | _______________ | _____ | _____ | ______
______________ | _______________ | _____ | _____ | ______
______________ | _______________ | _____ | _____ | ______

Keeping an NPC tracker online: a notes app, a spreadsheet or a shoebox

The template is app-agnostic on purpose, and the right home for it is the one you will actually open on a Tuesday night. Three shapes work, and nothing stops you using two at once.

• A notes app, one note per NPC. Paste the card, title the note with the NPC's canonical name, and leave the ALSO CALLED line in the body so search finds the nickname too. This is the best home for cards.
• A spreadsheet for the roster. One row per NPC and one column per field, and you can sort by last seen or filter to the open threads in a second — the one thing a spreadsheet does better than any notes app.
• Index cards at a physical table. You can spread tonight's NPCs in front of you and hand a card to the player who keeps talking to that NPC. Type up the ones that matter after the game, or the shoebox becomes an archive nobody searches.

Should the tracker live in a dedicated NPC tracker app?

If you are shopping for an NPC tracker app, the worldbuilding tools are built for authoring NPCs before play, and for a GM who designs their cast in advance they beat any plain-text card. World Anvil, Kanka and LegendKeeper each have a comparison here that says where they are the better pick, and Obsidian and Notion cover the build-it-yourself route. Whichever you choose, the card above pastes into it unchanged.

The honest test is the same for every option: can you find an NPC by the nickname the party uses, in under ten seconds, while the table waits? Search matters far more than structure. A messy document you can search beats a beautiful app you stop updating by session six.

If you are a player keeping an NPC tracker

Players need this sheet too, and the card works with three edits. You cannot see what an NPC secretly knows, so KNOWS becomes WHAT THEY TOLD US, and DOES NOT KNOW becomes WHAT WE HAVE NOT TOLD THEM, which matters more than most parties realise. Add DO WE TRUST THEM, with the session that settled it. Drop VOICE unless you enjoy it.

One roster the whole party can edit beats five private ones that disagree. The player note-taking guide covers the rest of what is worth writing down from the other side of the screen.

The version that fills itself in, and what it cannot fill

If your table records its sessions, most of this card already exists — it is just scattered across four hours of audio. A transcript makes it searchable: FIRST SEEN and LAST SEEN become a search for the name, and an NPC's last words become a quote you can find instead of a line you had to remember to write down. The recording guide covers getting audio worth searching, and the consent guide covers asking your table first.

Tools built for tabletop go a step further and fill the card in from the recording — the AI note-taker guide compares them; DM Scribe, which publishes this guide, is one.

Be clear about what no transcript can fill. A transcript is text, so the VOICE line stays on your card, and ours carry no speaker labels, so a quote tells you what was said rather than who said it. The DOES NOT KNOW line, whatever an NPC wants but never said, and every secret you never spoke aloud are on no recording, because they only ever existed in your head. And if your table does not record — some should not, starting with any table where someone is uncomfortable being recorded — this template is the whole system, and it costs nothing.