What Continuity Errors Are
A continuity error is any contradiction or inconsistency within the world of your story. It occurs when a detail established in one part of the manuscript conflicts with a detail presented elsewhere. These errors break the internal logic of the narrative and, once noticed, are nearly impossible for a reader to un-see.
Why Continuity Matters
Continuity errors erode reader trust. Every novel is a contract between the writer and the reader: believe in this world, and it will reward you. When the details of that world contradict themselves, the contract cracks. The reader begins to question everything, and once they start reading with suspicion instead of immersion, the story has lost its hold.
For published authors, continuity errors are among the most frequently cited issues in reader reviews. They signal carelessness, and readers interpret them as a sign that the writer did not respect their own story enough to keep it straight. This is especially damaging in genres like mystery, fantasy, and science fiction where internal consistency is part of the genre's appeal.
Continuity also matters for the writer's own process. Unresolved contradictions in a manuscript often indicate deeper structural confusion. If you cannot keep track of when events happened, it may be because the timeline itself is not well constructed. Fixing continuity errors frequently leads to fixing plot logic along the way.
Common Continuity Pitfalls
Certain categories of continuity error are so common that experienced editors watch for them specifically. Being aware of these patterns helps you catch them during revision before a reader does.
- Season and weather drift: the story begins in October, three days pass in narrative time, and suddenly characters are wearing summer clothes. Track the calendar of your story explicitly.
- Character appearance shifts: hair color, eye color, height, and distinguishing marks are easy to forget between drafts. If a character is described as having brown eyes in chapter two, a reference to green eyes in chapter twenty will be noticed.
- Technology and setting anachronisms: a story set in 1995 should not have characters using smartphones. A rural village described as having no electricity should not have a scene lit by a desk lamp.
- Timeline compression and expansion: events that should take days are compressed into hours, or a single afternoon stretches across what feels like a week of activity. Readers have an intuitive sense of how long things take.
- Relationship inconsistencies: characters who have never met somehow know each other's names. A character references a conversation that happened in a scene they were not present for.
- Object tracking failures: a character sets down a briefcase in one scene and is carrying it in the next without picking it up. A weapon is lost in chapter five and used in chapter nine.
What Bookshaper Offers for Continuity
Bookshaper does not run an automated contradiction-detector over your prose. It tried one — a pass that read the whole manuscript looking for claims that contradicted each other — and retired it: telling a deliberate choice (a character introduced formally, then called by a nickname) apart from a genuine slip is a judgment call, not something a pattern can reproduce reliably, and the pass's false positives outnumbered its real catches.
What the app gives you instead is the reference material for the systematic passes above. The Timeline under Structure orders your chapters by the dates you set or adopt, so a chronology that has gone backward is something you see rather than something you have to reconstruct. Record Gaps compares the characters, places, and connections your prose establishes against your own cast, places and relationships and reports what you have not recorded yet. Lume, the in-app assistant, answers point questions about what you already established — what colour her eyes were in chapter three, who was at the funeral.
Neither replaces the manual passes described above. A timeline-only read and a character-detail read are still the reliable way to catch contradictions that matter; Bookshaper's job is to make the reference material for them easy to get to.
Fixing Continuity Errors
The most effective approach to fixing continuity errors is systematic rather than reactive. Rather than chasing individual errors as you spot them, dedicate a full revision pass specifically to continuity. This focused pass is faster and more thorough than trying to catch contradictions while also revising for prose quality, pacing, and character development.
- Build a continuity bible: create a reference document that tracks character physical descriptions, key dates and timeline markers, location details, and world-building rules. Update it as you revise.
- Do a timeline-only pass: read through the entire manuscript tracking nothing but time. Note every reference to days, dates, seasons, and elapsed time. Build a calendar of events and check it for impossible sequences.
- Do a character detail pass: for each major character, search the manuscript for every physical description and verify consistency. Check names, ages, relationships, and backstory references.
- Cross-reference locations: if a character travels between two places, verify that distance, travel time, and directional references are consistent across every mention.
- Read scenes in chronological order: if your manuscript uses flashbacks or non-linear structure, reorder the scenes mentally or physically and read them in timeline order. Contradictions that are hidden by narrative distance often become obvious when events are placed side by side.