Guides · Choosing tools
Story bible vs novel continuity checker.
By Daniel Bentes · Published 28 July 2026
The short answer: a story bible is a record of what is true in your story; a continuity checker is a pass that reads your prose against such a record and reports the contradictions. One stores, the other reads. A bible nothing checks against drifts until it describes a book you are no longer writing, and a checker with no structured record has nothing to check against — which is exactly where continuity errors live.
Two definitions
One stores, the other reads.
A story bible is a record of what is true in your story — characters, places, rules, history — kept so you can look it up instead of remembering it. It is a reference. Its job is to be correct and to be findable.
A novel continuity checker reads your manuscript and reports where it contradicts itself. It is a process, not a document. Its job is to find the places your prose and your intentions have come apart.
They are not competitors and they are not the same thing, which is why "which should I use" is usually the wrong question. The useful question is what each fails at alone.
Side by side
What each one actually does.
| Story bible | Continuity checker | |
|---|---|---|
| What it is | A record of what is true | A pass that reads prose against a record |
| When you use it | Whenever you need to look something up | After drafting — per scene, or across the book |
| Catches a changed fact | Only if you look it up | Yes — that is the job |
| Catches a dropped setup | No — it holds facts, not obligations | Yes, if it tracks payoffs |
| Tells you what is true | Yes | No — it needs to be told |
| Degrades over time | Drifts from the manuscript unless maintained | Only as good as the record it reads |
| Fails alone by | Being correct about a book you did not write | Having nothing to check against |
The gap
Where continuity errors actually live.
A bible nothing reads drifts. You write chapter thirty, the entry still describes chapter four, and nobody compares them — the record is correct about a book you are no longer writing. A checker with no structured record has nothing to check against, so it falls back to reading your prose for internal plausibility, which is exactly the thing that fails at a hundred thousand words.
Continuity errors live in the space between the two. That is the honest argument for tools that do both, and it is also the honest limit: most products in this category are genuinely one or the other, and pretending otherwise on either side is how you pick the wrong one.
Choosing
Which you need first.
- Drafting something big and new — the bible first. There is nothing to check yet, and the record you build now is what makes checking possible later.
- Revising a finished draft — the checking first. The canon can be derived from the manuscript you already have; the errors cannot.
- Writing a series — both, and the bible has to be binding rather than advisory. See continuity across a book series.
- Working on a short novel with a small cast — honestly, neither, as software. A document and a careful reread will hold.
Loreon is deliberately both — see the story bible and the continuity checker — but the distinction above is worth understanding whichever tool you end up using, because it tells you what your current setup is not doing.
Limits
What neither one does.
- Neither knows your intent. A lying character and a continuity error look identical to both.
- Neither judges the writing. A perfectly consistent novel can be a bad one; continuity is a floor.
- Neither replaces a reader. The errors that matter most are often the ones a human notices and no record predicted.
Related: how to create a story bible, the continuity checklist, and how to maintain continuity in a novel.
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.