Continuity editing is the pass that exists because drafting and consistency-checking are different jobs your brain can't do at once. While you're writing, your attention is pointed forward — the next scene, the next line, the momentum of the story. Continuity is a sideways question, about whether this moment agrees with a hundred other moments scattered across the whole work, and you can't hold that whole map in view while also generating new prose. So the contradictions accumulate silently in the draft, and someone has to go back and hunt them down. That hunt is continuity editing.
It's the enforcement arm of canon management: the systematic search for the places where the story stopped agreeing with itself. Done by vibes — reading through and hoping something jumps out — it catches the obvious and misses the subtle, which is exactly the wrong ratio, because the subtle errors are the ones that survive to publication. This guide is about running a continuity pass as a real process, with categories and a reference, so the errors surface on your desk instead of in a reader's review.
Make it a separate pass with one job
The first principle of continuity editing is that it deserves its own pass, uncontaminated by other kinds of editing. When you try to fix continuity, prose, and structure in the same read-through, continuity loses, because it's the least immediately visible of the three — a clunky sentence announces itself, a buried contradiction doesn't. A dedicated pass, where the only question you're asking is 'does this contradict anything established,' gives the subtle errors a chance to surface instead of being crowded out by more obvious concerns.
That narrow focus is what makes the pass effective. Reading specifically for consistency puts your attention on exactly the details drafting glossed over — the ages, the timelines, the established rules, the physical particulars — rather than on the story you already know by heart. It's a different mode of reading, closer to auditing than to enjoying, and it works precisely because it refuses to be about anything but agreement with canon.
Check against the record, not your memory
The fatal flaw in most self-editing for continuity is that it checks the manuscript against the author's memory — and the author's memory is the exact thing that failed to keep canon straight in the first place. If you 'remember' a character's history wrong, you'll read right past the scene that contradicts the real history, because it matches your mistaken recollection. The only reliable check is against an external source of truth: your story bible, holding what's actually established, verified detail by detail.
This turns continuity editing from an act of recall into an act of comparison, which is far more trustworthy. You look up what the canon says a character knows at this point in the timeline, then check whether the scene honors it. You confirm what a world rule actually permits, then check whether the plot quietly breaks it. The specific categories where this comparison pays off most — timeline, character consistency, world rules, spatial detail — are the ones we enumerate in common continuity errors, and each is worth its own focused sweep.
Threads deserve special attention in this pass, because a dropped or contradicted plot thread is a continuity error that spans the whole book rather than a single scene. Checking that every setup pays off, every promise is kept, and no thread quietly changes its own history is continuity editing at the structural level — the through-line we cover in managing subplots and threads.
Surface contradictions instead of stumbling on them
The hardest continuity errors to catch by hand are the relational ones — where no single sentence is wrong, but two facts far apart in the manuscript can't both be true. A rule established in chapter two and an event in chapter thirty that violates it are each fine in isolation; the contradiction only exists in their relationship, and no linear read-through reliably holds both in mind at the same moment. This is why even careful manual passes miss things, and why continuity is ultimately a scale problem.
The answer at scale is to actively stress-test the world rather than hope to notice — to check the whole web of facts against itself and surface the conflicts, instead of relying on a reader's eye to trip over them one at a time. Being able to scan a body of canon for contradictions turns the subtle, relational errors from lucky catches into systematic ones. This is the capability at the heart of what CanonBoard's conflict detection is built to do, and the reason canon management treats continuity as infrastructure you build rather than diligence you perform.
However you run it, the goal of continuity editing is the same: to be the one who finds the contradiction. Every error caught in your pass is one that never reaches a reader, never breaks the spell, never becomes the plot hole a review is built around. It's unglamorous work, and it's the difference between a world that feels authored with full control and one that feels like it slipped its author's grip.
Frequently asked questions
- What is continuity editing?
- Continuity editing is a dedicated pass whose only job is to make the story consistent with itself — checking that facts, timelines, character traits, and world rules established in one place still hold everywhere else. It's distinct from developmental editing (which is about story and structure) and line editing (which is about prose). Continuity editing asks a narrower, ruthless question of every detail: does this contradict anything the story has already established? It's the practical act of enforcing canon across a whole manuscript.
- How do I check my own work for continuity errors?
- Separate the pass from the writing, and check against a source of truth rather than your memory. Trying to catch continuity errors while drafting fails because the drafting brain is focused forward, not sideways at everything already established. Instead, run a dedicated pass where you verify specific categories — timeline, character traits, established rules, physical details — against your story bible, not against what you think you remember. The errors live in the gap between what you wrote and what you recall writing, so the check has to reference the record, not the recollection.
CanonBoard scans your whole world and tells you where it disagrees with itself.
Start free