How do I organise a D&D campaign and keep track of NPCs, factions and quests?

Why a chronological document stops working

A D&D campaign adds a handful of names every session. After ten or twelve sessions you are carrying thirty or forty NPCs, half a dozen factions with overlapping interests, a scatter of half-finished quests, and several locations whose details live in whichever session they first appeared in. One long document captures all of that faithfully and hides almost all of it when you need it.

The question at the table is never what happened in session 9. It is who this NPC owes money to, which faction currently holds the road the party wants to use, whether the party already promised to return a missing courier, or what actually happened three sessions ago versus what you planned to happen. A single timeline cannot answer any of those without search, scrolling, and the pause that breaks momentum.

Follow the campaign as it grows

If you are starting from scratch, begin with [how to start a D&D campaign](/answers/how-do-i-start-a-dnd-campaign). Use this page as the cast, places and open threads grow, then move into [how to prepare a D&D session](/answers/how-do-i-prepare-a-dnd-session) when you are ready to turn the current situation into flexible table prep.

Useful categories, and nothing else until you need it

Start with these. Add a category only when it makes retrieval easier than leaving those pages in an existing category.

• Characters and NPCs Promote a person when you expect to retrieve or update them independently: they are likely to matter again, affect a future choice, or connect to an open thread. A patron who spoke once can stay as a journal line until the party makes them important.
• Locations Towns, districts, dungeons, wilderness sites, the room where the macguffin was last seen. A location page records what is there now, not what you originally planned to put there.
• Factions Guilds, cults, houses, knightly orders and trading companies. Treat something as a faction when it can act as an organisation beyond one NPC's personal agenda: it has some shared identity or structure, members or agents, resources, and interests that can outlast an individual. A leader's goal may differ from the faction's.
• Quests and open threads Anything the party could still choose to do, learn, or resolve: missing couriers, unpaid debts, unanswered questions, threats that have not yet arrived. A thread stays open until the table closes it or the world does.
• Items and important objects The sword with a history, the sealed letter, the key the party has not identified yet. Not every piece of equipment, only objects that can change a future decision.
• Sessions and journal A dated log of what actually happened at the table. Do not rewrite old notes to match the current world; correct recording errors transparently and keep later reinterpretations separate. Use the journal as a historical fallback when the exact sequence or wording matters.
• Calendar and events Use this where time matters in your campaign: festivals, travel times, deadlines set by NPCs, seasonal changes. If time is loose at your table, a single timeline note on the relevant location or faction page is enough.

Keep world truth, knowledge, history and prep distinct

Track truth separately from knowledge about the truth. You do not need four separate storage systems: a status, label or linked note can make the distinction clear.

• World truth / GM truth What is actually true now: who rules the city, which inn burned down, or who is behind the false identity. Keep secrets and unrevealed relationships GM-only when needed. Update current state when it changes; preserve important transitions in dated events or session history, which answers how it became true.
• Party knowledge and claims Record what the characters have established separately from world truth. A rumour, lie, incomplete explanation, mistaken witness account, propaganda or theory belongs as a claim with its source and status, not as settled fact. Mark what is party-known, secret or safe to share, especially before showing or sharing notes.
• Session history What happened at the table, session by session: decisions made and outcomes taken. Current-state pages answer what is true now; the journal records how it became true and remains the fallback for exact history. Do not rewrite old notes to match later events.
• Prep Possibilities for future play: situations, encounters or dialogue you might use. Almost all of it will be abandoned, adapted or overtaken by player choices. Keep prep on pages you can delete without losing anything true about the world.

When prep mixes with current state, an NPC invented for one encounter becomes a permanent resident by accident, and a dropped plot still appears in every search. Deleting prep should not delete a world fact; changing current state should not erase the history of that change.

D&D continuity worth keeping

Do not duplicate the full character sheet. Track only character details that create campaign continuity, and only for the characters or developments where they matter.

• Character hooks and ties PC goals, unresolved backstory hooks, and relevant patrons, deities, oaths or faction ties that can bring the character back into the campaign.
• Changing assets and effects Important magic items and who currently holds them, plus lasting curses, boons or other campaign effects that may shape a future choice.
• Long-running projects and threats A stronghold, base or recurring downtime project; recurring villains and their current state; and milestone or level-related developments when your table uses them.

Track relationships, not just pages

A folder of NPC pages answers who someone is. It does not answer how they connect to the rest of the campaign, and those connections are usually the fact you are trying to find mid-session. A list headed allies on each character page duplicates the same relationship twice, so after a betrayal one page is already wrong.

Record relationships as single, directed links with a reason: who is connected to whom, in which direction, and why. One record, one place to edit, visible from either side. Innkeeper Mara works for the Silver Hart Inn, owes money to the Red Knives, knows Captain Venn, and is involved in the Missing Courier. Each of those is a separate link with its own direction, and changing one does not require editing four pages.

Start with the simplest label that still carries meaning: works for, owes money to, reports to, distrusts, or involved in. For relationships that matter to play, note whether they are current or ended, known or secret, and optionally when they began or changed. A relationship can be true for the GM while the party believes something else. You do not need this metadata on every link; use it when a change matters.

What deserves a page, and what can stay in the journal

Not everything the party meets needs a page. Promote something when you expect to retrieve or update it independently; these are useful signs it has earned that attention.

• It is likely to matter again The party is likely to return to the location, deal with the NPC, or make a decision involving the item. A single interaction alone is not a reason to maintain a page.
• It can change future decisions A debt, a promise, a piece of information withheld, a door left unopened. If forgetting it would make a later choice uninformed, it needs its own page.
• It is tied to an unresolved thread Someone is still waiting, still owed, still hunting, or still missing. The thread keeps the page alive.
• It is likely to recur A faction operating on the road the party travels, a town they will pass through again, an NPC the party clearly likes or distrusts. Recurrence is a prediction, so keep these pages short until the prediction pays off.
• Forgetting it would cause a continuity problem A killed NPC who reappears, a destroyed bridge the party tries to cross, a payment already made that gets demanded again. If getting it wrong would break trust in the world, record it where you will find it.

Minor colour that passes none of these tests can remain in the journal as a line of atmosphere. Promote it if the party later treats it as important. A short note added after play is cheaper than maintaining a page for eight sessions on the chance it might matter.

The table-ready view should be smaller than the archive

Your full campaign archive exists for retrieval between sessions. Bring a narrow, table-ready view: surface or reference canonical facts, and duplicate only the short prompts you need for speed.

• Current location Where the party is now, described in three or four lines you can read without interpreting. Who is there, what is immediately visible, what is likely to be asked about.
• Active NPCs Only people who may become relevant tonight. Keep the top of each page scannable enough to run the NPC cold: how they present, what they want, and the connection worth remembering. Put deeper history below it.
• Open threads The quests and loose ends that could be closed, advanced, or complicated this session. Not the whole backlog, just the few the party last touched or the world is about to push on.
• Immediate faction pressures What the relevant factions want right now, and the next concrete step they take if the party does nothing. One line per faction, visible consequences rather than abstract goals.
• Likely situations and complications Locations likely to be visited, plausible encounters or complications, and NPCs likely to act. Prepare what may become relevant, not a sequence the players are expected to trigger. Keep it disposable; promote only what becomes true.
• Quick rules references The two or three tables, conditions, or DCs you actually look up for this session. Not the whole rulebook, just the lines you know you will need.

Assembling this by hand each week is the part that quietly fails when life gets busy. Reference the few relevant facts and links on one session sheet rather than rebuilding the whole archive. After play, promote new facts back to their canonical pages.

Setting up or tidying a D&D campaign this week

Use this once to convert what you already have, then as a short pass after each session. The maintenance loop is: capture → promote → update → close → archive.

• Promote a person, place, faction, quest or item when you expect to retrieve or update it independently; leave one-off interactions in the journal until they matter again.
• Separate GM truth from party knowledge and unverified claims; mark GM-only, party-known and safe-to-share information where it matters.
• Keep current state on the relevant page and preserve important transitions as dated events or journal history.
• Use named relationship links; mark current or ended, known or secret, and dates only when the change matters to play.
• Keep prep separate from truth, and prepare likely situations rather than a sequence the players are expected to follow.
• Surface or reference tonight's canonical NPC, location, faction and thread facts on the run sheet; duplicate only quick prompts you need at the table.
• After play, capture what happened, promote what now matters, update current state and relationships, close resolved quests or promises, then archive or delete unused prep.