How to Catch Continuity Errors Before Your Editor Does
Most continuity errors are not careless. They happen because a story gets bigger than anyone's memory. By chapter twenty you are relying on what you think you wrote in chapter three, and what you think you wrote is a tidier version of the truth.
Where continuity errors come from
- An effect with no visible cause. A character knows something they were never told on the page.
- A cause that arrives late. A character reacts to news before the scene where they receive it.
- Threads that drift. A subplot goes quiet for forty pages and comes back with different facts.
- Edits that leave scars. You move a scene and forget what depended on it.
A method that works without any software
Put every scene on one line of a spreadsheet or a stack of index cards. For each scene, write down two things: what has to be true for this scene to work, and what it makes true for later scenes. Then read down the list and ask one question of every entry: where did the reader first learn this?
That single question catches most problems. It is slow by hand, and it gets slower with every revision, which is why most writers do it once, near the end, when fixes are most expensive.
Doing the same check on a plot grid
A plot grid makes the structure visible. Each plot is a column and each scene is a row, so you can see which threads are active in a scene and which have been silent for too long. Plot Forge adds cause-and-effect links on top: you draw an arrow from the scene that causes something to the scene that depends on it. When the order of events puts an effect before its cause, it is flagged on the grid.
The useful habit is to link as you plan, not at the end. A link takes seconds when the scene is fresh and much longer when you have to reconstruct why you wrote it.
A short checklist
- For each major reveal, can you point to the scene where the reader learns it?
- For each reaction, can you point to the scene that caused it?
- Does any thread disappear for more than a few chapters without a reason?
- After moving a scene, did you re-check everything that links to it?
None of this replaces a good editor. It means the editor spends time on your sentences and pacing instead of finding that Tuesday happens twice.