All posts

Guides

How to Keep Track of NPCs in Your Campaign

Learn how to keep track of NPCs in your campaign: what to record for each one, how to capture improvised NPCs, and how to keep secret NPCs hidden from players.

By Mythical AtlasLast updated

Your players just asked about "that dwarf at the bridge" from four sessions ago, and you have no idea what you named him. Every Game Master hits this. The fix for how to keep track of NPCs in your campaign is simple: keep one searchable NPC list, write a short entry for every named character the moment they appear, and keep the secret parts somewhere players can't see.

That's the whole system. The rest of this guide covers what to write in each entry, how to handle NPCs you invent on the spot, how to keep a villain's true motives hidden, and a short routine that keeps the list current. It works in a notebook, a spreadsheet or a campaign manager, for D&D, Pathfinder or any other system.

Why NPC tracking breaks down

Most campaigns don't lose NPCs because the GM is disorganized. They lose them because the cast grows faster than anyone expects. A single town visit can produce a shopkeeper, a guard captain, a suspicious priest and three people you made up because the party asked a question. Multiply that by twenty sessions and you have dozens of names scattered across session notes, sticky notes and a group chat.

Two problems follow. You contradict yourself (the blacksmith was a woman last month, now he's a man), and your players lose interest in NPCs because they can't remember who anyone is. Both are easy to fix once every NPC has one home.

What to record for each NPC

Keep entries short. A long entry you never finish is worse than three lines you write right away. For most characters, this is plenty:

FieldExample
Name and a one-line hookBrannoc, the one-eyed ferryman who overcharges
Where they areFerry crossing south of Millbrook
What they wantEnough coin to buy back his family's boat
How they talk or actGravelly voice, calls everyone "friend"
What the party knowsTook them across the river and hinted at smugglers
Last seenSession 6

Two fields do most of the work. What they want lets you improvise their reaction to anything the party does. What the party knows keeps you from accidentally revealing something the characters never learned.

For important NPCs, add a few more lines:

  • Relationships: who they're allied with, who they owe, who they hate.
  • Secrets: what they're hiding and what it would take for the party to find out.
  • Stats: a stat block or a borrowed one ("use a veteran") if there's any chance of a fight.
  • Changes: a running list of what has happened to them ("lost his boat in session 9").

The "last seen" or "changes" line matters more than it looks. NPCs feel alive when they remember the party and when the world has moved on since the last visit.

Make names stick at the table

Tracking only helps if players can connect a name to a person. A few habits make that easier:

  • Use the name more than once. Have the NPC introduce themselves, then have someone else refer to them by name.
  • Pick names that are easy to say. Short, plain names are easier to remember than long invented ones.
  • Give one memorable detail. A scar, a catchphrase or an odd job does more than a full description.
  • Let players look things up. If the party can check a shared NPC list themselves, they'll stop asking you, and they'll engage with NPCs more.

Keep player-facing and GM-only details apart

This is the part a single document usually gets wrong. Your NPC list really has two audiences. Players need the public version: name, where they met, what they were told. You need the full version: real motives, hidden allegiances, the stat block for when things go wrong.

If both versions live in the same shared file, you'll either leak a secret or stop sharing the list at all. Split them. Common approaches:

  • A player-facing list plus a private GM file, with the same names in both.
  • One tool that lets you mark individual entries, or parts of them, as hidden.
  • Keeping the secret NPCs (the cult leader in disguise, the patron who's secretly the villain) entirely out of the shared list until they're revealed.

When an NPC's secret comes out in play, move what the party learned into the public version that night.

How to track improvised NPCs

Improvised NPCs cause most of the mess, because you create them without a plan. Two tricks help.

Keep a name list ready. Prepare a short list of names, a few personality quirks and a few occupations before the session. When the party asks the stable hand's name, read the next one off the list and cross it out. You'll never reuse a name by accident.

Capture during play, tidy up after. Mid-session, write only the name and three or four words ("Tamsin, stable hand, nervous, saw the thief"). After the session, decide which improvised NPCs earned a real entry. If the party talked to them for more than a minute, or showed any interest, they get one. If not, leave them on the scrap list. Lots of great recurring characters start as a throwaway answer to a question.

Session recaps help here too. A recap that names who the party met doubles as a checklist of NPCs to add. Our guide to writing a session recap covers what to include.

Tracking NPCs in Mythical Atlas

If you'd rather not juggle a public list and a private file, Mythical Atlas puts NPCs in the campaign's Glossary. Here's how it maps onto the system above.

One entry per NPC. Create a Creature entry with the NPC category, a Markdown description (good for the "what they want" and "what the party knows" fields) and an optional image. Creature entries can also hold a stat block, from Armor Class and Hit Points to actions and spellcasting, so the fight-ready version is in the same place.

Tags for finding people. Add tags like quest-giver, friendly, hostile or the name of a town. Players and the GM can search names and descriptions and filter by category or tag, so "who did we meet in Millbrook?" becomes a quick filter.

Private entries for secret NPCs. Mark an entry as private and only the GM can see it. That suits the disguised villain, the boss you're still preparing, or an NPC the party hasn't met yet. When they're revealed, turn off the toggle and the entry appears for players. Players can read public entries but can't edit them, so your list stays tidy.

Rollable tables for improvised NPCs. The Codex lets you build your own tables and roll a random row with one click. Its "NPCs on the Fly" starter template gives you a head start on names and quirks, and you can import your own lists from a CSV file. Mark rows as used so later rolls skip names you've already handed out, and link a row to a Glossary creature once that NPC gets a full entry. Codex tables are private unless you choose to share them.

A note on Notes. The Notes page is handy for a player-run NPC directory, since players can write shared notes about who they've met. But every campaign member can read every note, including personal ones, so keep NPC secrets out of Notes and in private Glossary entries instead.

A five-minute NPC routine

Right after each session:

  1. Add an entry for every named NPC the party spent real time with.
  2. Update "what the party knows" and "last seen" for anyone they met again.
  3. Reveal any NPC whose secret came out, or move the new details into the public version.
  4. Cross off the improvised names you used.

Before the next session:

  1. Re-read the entries for NPCs the party is likely to meet.
  2. Ask what each important NPC has been doing since the party last saw them.
  3. Refresh your list of spare names.

Start with the next session

You don't need to go back and catalogue every NPC from past sessions. Start with the next game, add entries as characters show up, and backfill the old ones only when the party asks about them. For a wider view of keeping quests, recaps, rules and NPCs together, see how to organize a D&D campaign.