Continuity errors are the mistakes readers actually write reviews about. Not the prose, not the pacing: the character whose eyes changed colour, the journey that took four days and then one night, the fact somebody knew before they were told.
They happen because a book is longer than working memory, and a series is much longer. Here is what breaks, and what BookZeta gives you to stop it.
What actually breaks
In rough order of how often it happens:
Physical descriptions. Eye and hair colour, height, scars, age. Easy to prevent, and the most noticed.
Timeline. How much time has passed, what season it is, how old everyone is now, how long a journey takes. Slips badly when you write chapters out of order.
Geography. Distances, directions, what is next to what. If your map is only in your head, it moves.
Who knows what, and when. The worst category, because it is invisible while you write and obvious while reading. A character reacting to information they were never given is the error readers most often single out.
Rules of the world. What magic costs, what the technology can do, what is forbidden. Powers quietly expand across a long book and the tension drains out with them.
Minor characters. The innkeeper's name in chapter three. Readers remember. You will not.
Plot holes are a different problem
A continuity error is a contradiction. A plot hole is an absence: something that should have happened and did not, usually because a character had an obvious option and inexplicably ignored it.
Most plot holes have the same root cause. The plot needs a character to not do the sensible thing. They do not call for help, do not ask the obvious question, do not check the room.
There are only two honest fixes:
Remove the option. No signal, the person they would call is compromised, the door is already locked. Do this before the scene, not after, so it reads as circumstance rather than convenience.
Give them a reason not to take it. A reason grounded in who they are, established earlier. A character who refuses to ask for help must have refused to ask for help before, in a smaller way, where it cost them nothing.
What does not work is hoping the reader is going fast enough not to notice. In mystery and thriller particularly, they are reading for exactly this.
Where to keep the facts
The Series Bible, for anything shared. Characters, settings and entities live in the Series Bible as canonical records. This is the difference between checking a fact and remembering it.
The fields that carry the most continuity weight:
- Physical identity on a character. Fixed traits, written as facts. This is what keeps descriptions and generated portraits stable across books.
- Status. Alive, dead, missing. The guardrail that stops book three reintroducing someone book two killed.
- Relationships on entities. Who is allied with whom, what belongs to which faction. Worth filling in properly once your world has more than three moving parts.
- Environment and key elements on settings, so a place does not change character between the chapters that visit it.
Story notes, for the rest. The Notes panel in Writer Mode is private and never exports. It is the right home for a running timeline, a list of open plot threads, and the small facts that do not belong to a character or a place. Keep a "who knows what" list there for anything with a secret in it.
Casting, for per-book variation. Casting a Bible asset into a book creates a local copy you can edit for that story. Book three gets the scar and the new rank; the Bible keeps the canonical original. Versioning assets across books covers picking the right iteration, which matters for prequels.
The habit that prevents most of it
When something becomes true in a draft, record it that day. Not at the end of the chapter, not at the end of the book. The gap between inventing a fact and writing it down is where continuity errors are born.
Two more that pay off:
Tag characters with @ before generating. Tagged characters carry their profile into the AI assistant, so generated scenes work from the recorded facts rather than inventing new ones. Untagged characters drift, and the drift becomes canon once you accept it.
Keep the synopsis current. It is one of the main signals the assistant uses. A synopsis describing the book you planned rather than the book you wrote quietly degrades everything generated after the plot changed.
The continuity pass
Do this as its own pass, from a list, not by reading. Reading finds prose problems; only checking finds contradictions.
- Names and spellings. Every character, place and invented term. Search the manuscript for each.
- Descriptions. Check every physical detail against the Bible entry.
- Timeline. Build a date or day-count list for the whole book and check each chapter against it.
- Distances and travel. Every journey, against the same map.
- Knowledge. For each secret, note the chapter where each character learns it, then check no one acts on it earlier.
- World rules. List what magic or technology did in each scene. Look for the ones that grew.
If the book is part of a series, check against the Bible rather than against your memory of the earlier volumes.
Related
How to revise a novel puts this pass in the right place in the revision order, and how to write a book series covers the version of this problem that appears once you have more than one book.