Guides · Revision
A novel continuity checklist.
By Daniel Bentes · Published 27 July 2026
The short answer: check at three scales, outward. At scene scale, while it is still warm — who is present, who knows what, what the weather and the injuries were. At chapter scale, whether elapsed time adds up and what canon just changed. At manuscript scale, the things only visible from above: every duration on one line, every setup marked paid or unpaid. A checklist you run at the wrong scale finds nothing.
First, a definition
What counts as a continuity error.
A continuity error is any place your manuscript states something that cannot be true alongside something else it states. That is a narrower test than "something feels wrong" and a wider one than "a fact changed" — a character acting on news nobody has told them is a continuity error, and so is a journey that takes two days in chapter four and a week in chapter nineteen.
The test matters because it tells you when to stop arguing. If two statements can both be true, it is not a continuity error, however awkward it reads. That is a craft problem, and it belongs on a different list.
The checklist
Three scales, in this order.
Work outward. Scene-scale errors are cheap to fix and expensive to leave, because later chapters get built on top of them. Manuscript-scale errors cannot be seen at all until the book is whole, so checking for them early is wasted effort.
Scale one — the scene you just wrote
Run this while the scene is still warm. It takes two minutes and it is the only pass you will ever do with the full context in your head.
- Is every character in this scene actually able to be here — not elsewhere, not unconscious, not dead?
- Does anyone act on information they have not been given on the page?
- Does the time of day, weather and season match the scene before it?
- Are physical details — injuries, clothing, what someone is carrying — carried forward from the last time we saw them?
- Does anything here contradict a rule you have established about how the world works?
Scale two — the chapter
Chapter scale is where scene-local decisions start to interact. Run it when a chapter is drafted, before you build the next one on it.
- Does elapsed time inside the chapter add up — and does it match what the chapter heading or the prose claims?
- Does every character who leaves the chapter end up somewhere the next chapter can reach?
- Has anyone's knowledge changed in this chapter? Write down what, and who now knows it.
- Did you introduce a new rule, place, or object? It is canon now — record it before you forget the version you meant.
- Did you plant anything? A setup you do not write down is a setup you will drop.
Scale three — the whole manuscript
This is the pass no amount of scene-level diligence substitutes for, because the errors it catches are only visible from above. Run it before a revision pass, before an editor sees it, and before a sequel locks the canon.
- Put every dated or datable event on one line. Contradictions in a timeline are arithmetic, and arithmetic does not survive being written down.
- List every setup and mark its payoff. Anything unmarked is a promise the book is not keeping.
- Take three or four load-bearing facts and grep the manuscript for every mention. Read them together, out of order.
- Check each major character's knowledge from first appearance to last, as a sequence.
- Read the first and last appearance of each significant character back to back. Drift shows up instantly at the ends.
Worked example
What the manuscript-scale pass catches.
Two passages, thirty pages apart, each unremarkable alone.
Chapter four
The ride to Vellhark took two days, and he arrived with the letter still sealed.
Chapter nineteen
"A week on that road," she said, "and by then the seal means nothing."
Neither passage is wrong on its own, and no scene-scale check would flag either. Only the manuscript-scale pass — every duration on one line — puts them next to each other. Then you decide: is the road slower in winter, is she exaggerating, or did you simply forget? All three are legitimate answers. Only the third is an error.
Where this stops working
What a checklist cannot do.
- It cannot read intent. A character who lies, an unreliable narrator, a deliberate contradiction planted for later — a checklist flags all three, and you dismiss all three.
- It is only as good as what you wrote down. Checking against memory is checking the thing that is failing. The checklist assumes a record.
- It does not scale linearly. At forty thousand words a spreadsheet is fine. At a hundred and forty thousand, across three volumes, the bookkeeping is the job.
- It says nothing about whether the book is good. Continuity is a floor, not a ceiling. A perfectly consistent novel can still be dull.
For the individual classes in more depth: character consistency, tracking what each character knows, timeline errors, and plot holes. For the underlying record, see how to create a story bible.
Loreon · The Writing Studio
Or let the software read it.
Everything above works with a spreadsheet and patience. Loreon does the same reading against a structured story bible and hands you the findings, with the passages cited.