How to Keep Track of NPCs in Your Campaign

Mid-session, a player asks: "Can we go back to that smith we met in session four — what was her name?" You stare at your notes. You know the smith exists. You can almost picture her shop. But the name is gone, and so is everything she said, every favor she owed the party, every secret you carefully planted. The session pauses. The illusion of a living world cracks.

This is the NPC tracking problem, and every DM hits it. The good news: it's entirely solvable with the right system. Not an elaborate one — a simple, sustainable one that takes minutes per session and pays off for years.

Why NPC Tracking Matters More Than You Think

NPCs are the connective tissue of a campaign. Players don't fall in love with worldbuilding lore — they fall in love with the gruff blacksmith who gave them a discount, the noble who betrayed them, the child they rescued from cultists. When you remember an NPC's details, you're not just being organized; you're honoring the player's emotional investment in your world.

The DMs who run great long campaigns aren't necessarily better improvisers. They're better at remembering. Their world feels coherent because every character introduced two months ago can resurface tomorrow with the same voice, the same motives, and the same unfinished business.

The Two Types of NPCs (And Why They Need Different Systems)

Throwaway NPCs

The shopkeeper, the random guard, the bartender at the inn the party will never visit again. These don't need a database entry — they need a name and a vibe, and that's it. You can generate them on the fly using a NPC generator or a simple random name list. If a throwaway NPC becomes important later (players latch onto them unexpectedly), promote them. Otherwise, they live and die in a single scene.

Recurring NPCs

The blacksmith the party returns to. The noble whose schemes drive the plot. The companion they've traveled with for ten sessions. These need real records — not just names, but relationships, secrets, and a history of every meaningful interaction with the party.

The mistake most DMs make is treating all NPCs the same. Either they over-document throwaways (wasting hours) or under-document recurring NPCs (losing campaign-critical details). Sort first, document second.

The NPC Profile Template

For every recurring NPC, capture these fields. Keep it scannable — you'll consult this mid-session.

• Name and aliases — including nicknames the players use
• Role and location — what they do, where they're usually found
• Three personality traits — enough to roleplay them consistently
• Voice/speech pattern — formal? terse? a verbal tic? — your anchor for dialogue
• Goal — what they're actively trying to achieve right now
• Secret — something they don't want others to know (or that the party doesn't know about them)
• Attitude toward the party — friendly, neutral, suspicious, hostile — and why
• Relationships — who else they're connected to in the world
• Last interaction — date and a one-line summary of what happened

That's nine fields. Most NPCs only need 4-5 of them. Don't fill in fields just because the template has them — empty fields are fine if the information doesn't exist yet.

The Session Workflow

Before the Session

Five minutes. Review the NPCs likely to appear. Refresh on their goals, their last interactions, and any promises or threats from previous sessions. This is the difference between "Oh right, what was she upset about?" and "She's still angry that you didn't deliver the package on time."

During the Session

Keep a scratchpad — paper, a sticky note, anything fast. When you improvise a new NPC, jot down the name immediately. You will forget it within 20 minutes if you don't. Note any promises the party makes, any deals struck, any threats issued. These become future hooks.

After the Session

Ten minutes. For each NPC who appeared, update their entry: what changed, what they learned, how their attitude shifted. For any improvised NPCs that mattered, create a proper entry. For ones that didn't, let them go.

NPC Tracking Tools: What Actually Works

Spreadsheets

The starter option. A Google Sheet with columns for name, location, role, status, and last seen works for short campaigns. The downside: spreadsheets don't represent relationships well. When NPC A is connected to NPC B, who's connected to faction C, who controls location D — a spreadsheet shows you four rows. It doesn't show you the web.

Notion / Obsidian

Step up from spreadsheets. Page-per-NPC with structured fields. Notion has database views (filter by location, sort by last interaction). Obsidian has wiki-style links between notes. Both work — both require manual setup that takes hours before you've documented your first NPC.

Dedicated Worldbuilding Tools

The best fit for serious campaigns. Tools like Anima's wiki with character entries let you create NPCs as typed entries with custom properties (role, location, attitude, voice) and visual relations to other characters, factions, and locations. When you click on an NPC, you see everyone they're connected to. When you click on a location, you see every NPC who lives there. The web of relationships becomes navigable.

The advantage isn't just storage — it's discoverability. With a relational system, you don't need to remember which NPC owes the party a favor. You filter by "owed favor: yes" and the answer appears.

Common NPC Tracking Mistakes

Tracking Too Much

You don't need an entry for every NPC. The market vendor the party bought apples from doesn't need a profile. Track NPCs who matter — recurring ones, ones with secrets, ones tied to plot threads. The rest can stay in the scratchpad and disappear.

Tracking Too Little

The opposite mistake: only writing down names. A name without context is useless three sessions later. At minimum, capture the location, the role, and one personality trait. That's enough to roleplay them again.

Not Updating After Sessions

The NPC tracking system that's only updated when you create new NPCs is half-functional. Updates after sessions are where the magic happens — recording changes in attitude, new information learned, and the consequences of player decisions. Without updates, your NPCs are frozen at their first appearance.

Ignoring Relationships

An NPC defined only by their own attributes is half the picture. Who do they know? Who do they hate? Who do they secretly work for? Relationships are where dramatic potential lives — and where most tracking systems fall down.

The "First Five" Principle

For any new recurring NPC, capture the first five things you know about them within 24 hours of their introduction. Just five. Name, role, voice, goal, and one quirk. That's enough to guarantee consistency the next time they appear, and it takes about two minutes.

The "first five" rule works because the friction is low. You're not committing to a 30-field profile — just five facts. Once those exist, you can expand the entry whenever the NPC reappears or whenever inspiration strikes. The hard part is starting; "first five" makes starting easy.

Connecting NPCs to Everything Else

The deepest level of NPC tracking isn't about NPCs in isolation — it's about how they connect to the rest of your world. The blacksmith isn't just a character; she's connected to her town, her guild, her rival, the noble who commissions her work, and the apprentice she's training. Each of those connections is a story waiting to happen.

When your worldbuilding notes are organized as a connected wiki, NPCs become entry points into the campaign. Click on the blacksmith, see everyone she knows, see the locations she's tied to, see the events she was part of. The web reveals stories you forgot you were telling.

NPC tracking sounds like administrative overhead. In practice, it's the foundation of every great long campaign. Set up a system that takes ten minutes per session, stick with it, and watch your world become unforgettable.