Campaign Continuity

How to Keep a Long Campaign Consistent

A campaign that runs for years accumulates hundreds of facts — half of them improvised at the table — and no memory holds it all. Here's how to keep a long campaign from quietly contradicting itself: capture what you invent live, keep one source of truth, and check new canon against the old.

CanonBoard EditorialJuly 9, 202610 min read

A one-shot never has a continuity problem. A campaign that runs for three years has almost nothing but continuity problems, because it accumulates canon the way a river accumulates silt — session after session, hundreds of names and rulings and promises, and a large share of them invented on the spot and never written anywhere. The northern pass you closed in session 8, the god you said answers on the third prayer, the NPC you killed and then, forgetting, had walk into a scene in session 40. No memory holds a campaign that size, and memory is exactly what most game masters are relying on.

Keeping a long campaign consistent is therefore not a matter of prepping harder — it's a matter of capturing what you invent and checking what you add. This is the tabletop face of a problem every long-form story shares, the one we cover in how to track continuity across a series; at the table, run live and improvised, it just arrives faster and hurts sooner. Here's how to keep a years-long campaign making sense.

Capture what you improvise, the moment it's canon

The single highest-value habit in a long campaign is writing down the things you make up at the table, as they happen. Nearly every campaign contradiction traces back to un-captured improvisation: a fact that became canon the moment you said it aloud, but that only ever lived in your memory of that night. Months later, with that memory faded, a new ruling walks straight into it. The prep rarely contradicts itself — the improvisation does, because it was never recorded.

So treat the table as a source of canon equal to your prep, and give improvised facts the same home. When you name the tavern-keeper, close the pass, or rule on the god, that fact should land in your world document, not just in the session's echo. This doesn't have to break the flow — a quick capture between beats, cleaned up after — but it has to happen, because a decision you don't record is a contradiction you've scheduled for later. We go deeper on making on-the-fly canon durable in player-driven canon and improvisation.

Keep one source of truth, not a pile of session notes

Campaigns tend to scatter their canon: a prep doc, a stack of session notes, a wiki started with enthusiasm and abandoned by session 15, and the game master's memory holding it all together. Every scattered store is a place for the world to drift, because each contains a slightly different version of what's true, and no one of them is authoritative. When the players ask what's canon, you want one answer, from one place.

That means consolidating the world — prepped and improvised, NPCs and factions and rulings and timeline — into a single living document everyone's decisions flow into and get checked against. The value isn't tidiness; it's trust. A campaign with one source of truth is one you can extend confidently, because you can actually find what's already established before you add to it. This is the same principle that keeps any long series coherent, covered in how to track continuity across a series, and it's what turns a three-year campaign from a memory you're anxiously guarding into a world you can look up.

Check new canon against the old before it reaches the table

The contradictions that hurt most are the ones nobody catches until a player does — the dead NPC who reappears, the rule that quietly reversed, the age that doesn't add up across two sessions. They hide because the conflicting facts sit dozens of sessions apart, and no game master reads a three-year campaign with both nights open at once. The catch has to happen when you add the new fact, not when the table trips over the old one.

So build a habit of checking: before a new NPC, ruling, or reveal goes live, hold it against what's already established and make sure it fits. Past a certain size this is more than a memory can do reliably, which is why the ability to actively surface contradictions across an entire campaign — rather than hope you remember — is what separates a world that deepens over years from one that slowly stops making sense. The specific failure modes to hunt for are the same across all long-form storytelling, catalogued in common continuity errors. Catch them at the point of writing, and a long campaign gets richer instead of more contradictory the longer it runs.

Frequently asked questions

Why do long campaigns start contradicting themselves?
Because most of a campaign's canon is improvised at the table and never written down. You name an NPC, make a ruling, or promise a fact in the moment, and it's binding — but it lives only in your memory of that session, and months later a new decision contradicts it. The breaks almost never come from the prep; they come from the un-captured improvisation piling up until no one can remember what's true. The fix is capturing live canon, not planning harder.
How do I track canon across dozens of sessions?
Keep one source of truth for the whole campaign, and route everything into it — prepped and improvised alike. When you invent a fact at the table, it should land in the same place as your prep, not in a separate memory. Then, before new material reaches the table, check it against what's already established. A campaign you can actually search, with every canonized fact in one place, beats a stack of session notes you have to re-read to trust.
What should I do when I realize I've contradicted my own canon?
Decide which version is canon, make it consistent going forward, and — if the players noticed — fold the discrepancy into the story rather than pretending it didn't happen. A contradiction the table caught can often become a plot hook: someone lied, memory was altered, the record was forged. What you can't do is leave both versions floating, because the next decision that touches them will only deepen the tangle. Pick one, update the source of truth, and move on.
Stop discovering continuity breaks in the table read.

CanonBoard scans your whole world and tells you where it disagrees with itself.

Start free
Share