Continuity Checker for Fiction Writers

A continuity checker reads a manuscript, extracts candidate facts — character details, locations, events, world rules — and looks for passages that may conflict with them. In PlotLens, extraction builds a Story Bible from your prose and checks run on demand. Upload .docx, .pdf, .epub, .fountain, or .fdx directly in the web app; Companion watching is a separate integration path. Results can appear in the editor, a Spot Check, or a Word/PDF findings report. PlotLens analyzes rather than drafts your prose, and it shows exact source text only when it can re-read a clean span.

Spell checkers catch typos. Grammar tools catch syntax errors. PlotLens focuses on narrative continuity — factual relationships across passages that require more context than a sentence-level language check.

The three kinds of continuity errors that ship

The errors that show up in published fiction are usually one of three shapes, and they’re all invisible to spell- and grammar-checkers because they’re not language errors — they’re fact errors.

The first is detail drift. A character’s eye color, the spelling of a town’s name, a scar described on the left cheek in chapter four and the right cheek in chapter eleven, a horse named in dialogue but never again. These slip past every human reader who isn’t holding a spreadsheet because no human can hold the whole text in working memory.

The second is timeline contradiction. The story says it’s been three weeks since a key event, but the actual chronology of the chapters that follow only accounts for ten days. A character travels from city A to city B in a day in book one and three days in book two without explanation. Two scenes that were supposed to be simultaneous reference each other as having already happened.

The third is state contradiction — usually about what a character knows. A character references a secret they haven’t been told yet. A character claims not to know something the story already showed them learning. A character forgets a fact that’s important to a later scene. These are the hardest to catch by hand because they require simulating each character’s epistemic state at every point in the narrative.

PlotLens can surface review leads across all three. Detail drift draws on extracted entities and their provenance. Event questions draw on the events PlotLens has found, while the current timeline view groups those events by document rather than asserting a definitive story chronology. State questions use the belief-vs-fact model when enough evidence is available. Coverage and accuracy depend on what the manuscript states and what extraction found.

Your Story Bible is the set of facts your story has established — what readers call canon.

How PlotLens actually validates continuity

The flow is simple to describe: add material, run a check, and review the possible conflicts PlotLens found against the Story Bible it derived. When a clean span is available, a finding can include exact source text so you can compare the new passage with the earlier evidence. Decide what to do: revise the manuscript, update the facts you rely on, or mark the finding as not a problem when the difference is deliberate.

What’s behind the simple flow:

• The Story Bible can be derived from your manuscript. The checker compares new prose against extracted facts from earlier material, with sentence-level provenance when a clean span is available. You can review and supplement those facts rather than treating extraction as complete.
• Entity resolution helps with messy names. Aliases, nicknames, titles, and dialogue references can be linked to the same character, but ambiguous identities still need review.
• The validator can distinguish evidence types. Narration, dialogue, and character belief provide different kinds of evidence. That separation helps reduce false alarms around lies and mistaken beliefs; it does not make every classification certain.
• Events remain source-bound. PlotLens can extract event and time references for review. The current timeline view presents events within each document; it does not claim to solve the manuscript’s complete story chronology.

Where it fits in a working writer’s day

A novelist working through a third draft can use PlotLens as a pass between “the writing is done” and “send to the editor.” Run extraction, check the material that matters, and treat every flag as a decision: revise, retcon, or deliberate. By the end of the read-through, you have a documented set of reviewed questions — not a guarantee that no continuity error remains.

A screenwriter on a feature uses the same pattern at the table-read stage. Validation runs against every scene in the script, with screenplay-aware parsing (scene headings, character cues, action lines, dialogue all treated as distinct evidence types). Possible continuity conflicts become review questions before production decisions lock them into costly reshoots.

A writers’ room on a serialized show runs the checker after every script draft. The shared Story Bible can surface when episode 405 appears to conflict with a reveal from episode 207. The room decides whether to revise or retcon, updates the facts it relies on, and checks later scripts against that reviewed state.

If you’re tired of finding the eye-color drift in the reader review, the free tier covers a single project so you can run the validator on a manuscript you’ve already finished. Prefer to organize facts manually first? Use the ungated Story Bible facts-and-rules template in your browser. Editors can see the editor review workflow. Compare PlotLens to Sudowrite for the analysis-vs-generation framing or to Novelcrafter for the closest tool that pitches a similar workflow.