How to Keep Track of a Long-Running D&D Campaign

A recap answers “what happened last time?” A long campaign also needs “what changed six months ago, and what does that affect now?” Those questions cross sessions.

Archivist's August 19 research snapshot shows how quickly the world grows. Campaigns with at least ten logged sessions had median compendiums of 79 NPCs, 75 locations, 26 factions, and 43 items. At 50 or more sessions, those medians reached 209 NPCs, 184 locations, 61 factions, and 121 items.

No player should have to reread fifty chronological documents to find one alliance. The archive needs both a session view and an entity view.

1. Session record

Keep a concise recap, key decisions, consequences, discoveries, and next-session hooks. Preserve the transcript or raw notes as the source.

2. Campaign entities

Give recurring characters, locations, factions, and items one canonical page each. Update the page rather than creating “NPC name, session 14” and “NPC name, session 27” as separate facts.

3. Quest and promise log

Track status, owner, involved entities, last meaningful change, and the session where it changed. Include promises and debts, not only formal quests.

4. Timeline

Record events that change the world or explain cause and effect. A timeline is not another recap list; it is the campaign's chain of consequences.

1. Capture the session in Discord, on a phone, or in written notes.
2. Generate or write the recap.
3. Correct names, speakers, and mistaken certainty.
4. Approve changes to canonical entities and quests.
5. Separate GM-only details from the player record.
6. Publish the short catch-up before the next game.

This loop should update existing records before creating new ones. Duplicate entities are more damaging than a missing adjective because they split later searches across competing versions of the same person or place.

Fantasy names are hard for people and speech recognition. Store the canonical spelling, useful aliases, and the source that established it. When a correction occurs, fix the entity and the session record, then ensure future summaries retrieve the corrected version.

Use explicit uncertainty labels: confirmed, reported, player theory, and GM-only. A campaign system should never silently turn a rumor into canon.

An organized campaign is one that can answer questions under table pressure. Test it monthly:

• Who last controlled this location?
• What did we promise this faction?
• Which clues point to the current mystery?
• When did the party obtain this item?
• What does this player character know that the rest of the party does not?

If the answer requires searching several disconnected tools, tighten the linking or choose one canonical store. Archivist's campaign Q&A and MCP connector are built around this retrieval job.

A spreadsheet can track quests, a shared document can hold recaps, Notion can model linked databases, and Obsidian can keep a local Markdown graph. These approaches work when the group consistently performs the updates.

A purpose-built campaign-memory system is useful when capture and maintenance are the bottleneck. Compare the approaches in Best D&D Campaign Management Tools and start with the smallest system the table will actually keep current.

The compendium figures above are anonymized medians from active Archivist campaigns in an August 19, 2026 database snapshot. They describe a self-selected product population, not every D&D campaign. Session-count cohorts are nested: a 50-session campaign is also present in the 10-session cohort. Read the full definitions in The Data Behind D&D.