How to Track Multiple NPCs and Factions During a Long-Running Story Campaign
For a long-running tabletop story campaign, track only the details that help you portray a character consistently or make a group’s next move matter. Keep a compact roster for recurring NPCs, a separate page for factions and their goals, and a brief session log that records changes. After each session, update those records from what actually happened, then choose a few developments to bring forward. This gives you continuity without requiring a complete simulation of every person and organization in the setting.
What should you track for each NPC?
Give each recurring NPC a short record with four useful fields: identity, desire, method, and current connection to the player characters. For example: “Mira Vale, bridge keeper; wants the old observatory reopened; solves problems by trading favors; trusts the party after they returned her map.” These details give you material to improvise what she says and does. The Blades in the Dark SRD similarly describes NPCs through a concrete desire and preferred method of action, while emphasizing that the GM responds to the players’ choices rather than needing to plan every event in advance. The Basics
Add a small “last seen” note when an NPC has been absent for a while: where the characters met them, what changed in their relationship, and any unresolved promise. Record observable facts rather than a full biography. If Mira’s family history, favorite food, and childhood rival have not affected play, they can stay off the working roster until there is a reason to use them.
Distinguish what is established in the campaign from what is still an idea. Mark confirmed facts plainly, and label unresolved possibilities as questions or options. This prevents a brainstormed possibility—such as Mira secretly knowing the observatory’s location—from becoming accidental canon before the table has chosen it.
How should NPCs and factions be organized?
Use one roster for people and one roster for groups. An NPC record focuses on an individual’s desire and behavior; a faction record focuses on a shared goal, resources or influence relevant to the story, key members, and relationships with other groups. A person can appear in both places: list Mira as an NPC, then note her role as the bridge keepers’ representative in that faction’s record.
Keep the faction list limited to groups that can affect the characters’ choices soon. A town council, traveling archive, or guild of mapmakers might matter if the party is dealing with them or their plans. A distant group with no current connection can remain in a setting reference rather than the active tracker. This is a practical way to keep the tool sized to the campaign rather than turning every named organization into ongoing bookkeeping.
For relationships, write the reason alongside the status: “The mapmakers cooperate with the council because the council protects their records.” Reasons are easier to update than a bare label like “allied.” When the characters break a promise or deliver something important, you can ask which connection would plausibly change and why. Some games provide formal faction ratings and procedures; Blades in the Dark, for example, has faction status values and rules for changing them based on crew actions. Treat those mechanics as game-specific rather than automatically importing them into another system. The Faction Game
How do you track what a faction is trying to do?
Give each active faction one immediate goal, a next step, and a visible sign of progress. For example: “Mapmakers’ Guild: recover the three survey plates; next step, ask the bridge keeper for access; sign of progress, a new route appears on public charts.” This turns a group from a static name into a source of possible scenes. Avoid vague goals such as “gain influence”: describe what would look different if the group succeeds.
For plans that take several sessions, a progress clock can help. Draw a circle divided into a few segments, name the obstacle or goal, and mark it only when an event in the fiction changes the situation. The official Blades in the Dark clock guidance says clocks are useful for complex or layered situations, and that a clock reflects the fictional progress rather than determining it. It also cautions that a simple obstacle may not need a clock at all. Progress Clocks
A clock for a fictional guild might be titled “Three survey plates recovered,” with segments for finding a lead, locating the first plate, and securing the rest. Those segment descriptions are an optional adaptation for your campaign, not a rule from Blades. If the players persuade the bridge keeper to help, that could advance the effort; if the plate is moved, the goal or clock may need to change. Don’t mark progress merely because time passed unless that is how your campaign handles faction activity. When a clock fills, decide what actually happens in the fiction and how the characters learn about it.
What do you update after each session?
Use a short repeatable review. First, list new facts the players established or discovered. Second, note promises, conflicts, gifts, or other actions that changed a relationship. Third, choose which active factions have a plausible next move because of those events. Fourth, write one way the result could become visible to the characters: a changed noticeboard, a new request from a contact, or a route newly marked on a map.
A concise session entry might read: “The party gave the copper survey plate to Mira. She promised to ask the guild for a meeting. The guild now has one plate; next session, a guild courier may bring a formal invitation.” Keep the session log chronological and the NPC or faction roster current. The log preserves how the change happened; the roster makes the current state easy to find.
Do not feel required to advance every group at every review. The Blades in the Dark downtime procedure explicitly has the GM focus on factions they are interested in at the moment, and says ignored factions can catch up later when they become relevant. That approach is useful as a general workload principle, though its specific downtime maneuvers and advancement rolls belong to that game. Downtime Activities in Play
How can you keep the tracker manageable?
Set a limit on what counts as active. One simple choice is to review only factions tied to the last session, the next likely session, or a major unresolved goal. Keep the rest archived. For NPCs, promote someone to the active roster when they recur, hold information the players need, or can change a current situation. Archive them when there is no foreseeable reason to prepare them; you can restore the record if they return.
Use plain language and short entries. “Wants the observatory open; asks the party to find its missing lens” is more useful at the table than a page of atmospheric prose if you need to decide quickly how that NPC responds. Add detail when play reveals it. A spreadsheet, notebook, shared document, or index cards can all work; choose the format that makes it easy for your group to find and revise information.
Keep the tracker as a support for play, not a promise that every plan must unfold. Player choices can change a goal, make a faction reconsider its approach, or remove a conflict from the campaign. If the facts change, update the entry and leave a short note in the log explaining why. The clocks guidance likewise treats the tracker as a reflection of the fictional situation, not a device that dictates it. Progress Clocks
What is a useful minimal template?
Copy this structure and fill only the fields that help your campaign:
NPC: Name and role; desire; preferred method; current relationship with the characters; last seen; open question or promise.
Faction: Name; shared goal; next step; current resources or influence that matter; allies and rivals with reasons; visible sign of progress; linked NPCs.
Session update: New facts; changed relationships; faction actions caused by events; information the players may encounter next time.
For a small campaign, this may fit on one page. For a sprawling campaign, keep one index of active records and separate pages for details. The useful test is simple: can you find what this person wants, what this group is doing, and what the characters changed without rereading the whole campaign history? If so, your tracker is doing its job.
How do you bring tracked developments back into play?
Turn updates into information the characters can encounter, then let them decide what to do with it. A faction may announce a public search, a familiar NPC may request a meeting, or a changed map may reveal that someone reached a location first. Treat those as scene invitations, not obligations. The group can follow the lead, ignore it, negotiate, or redirect the situation.
Before a session, choose only a few likely developments to introduce. If three factions each make a major move at once, the players may have trouble seeing which choices matter. A small number of clear changes can make the setting feel active while leaving room for unexpected decisions. When the players do something surprising, update the records afterward rather than forcing their action into an old plan.
The goal is a usable memory of the campaign: what recurring people want, what important groups are pursuing, and which choices have changed their paths. A compact roster, selective faction goals, and a brief post-session update provide that continuity while leaving the story open to the players.