TL;DR
Continuity errors fall into a few families: names, appearance, time, place, objects, knowledge and rules. Record each fact where it first appears, read the draft in separate passes for each family, and decide on purpose which version stays when two disagree.
A continuity error is a detail in a novel that contradicts another detail somewhere else in it: a name spelled two ways, an eye colour that changes between chapters, a year that turns out to be fourteen months long, or a character who acts on a secret before anyone has told them. The common ones fall into seven families, and each family can be caught with its own short check. Even careful authors make them. Arthur Conan Doyle did, famously, with the wound of Dr. Watson.
A classic case
In A Study in Scarlet, Watson tells us how he was hurt at the Battle of Maiwand: "I was struck on the shoulder by a Jezail bullet, which shattered the bone and grazed the subclavian artery." In The Sign of the Four, he is "nursing my wounded leg. I had a Jezail bullet through it some time before." Both passages are on Project Gutenberg. Wikipedia's article on Watson records the result in a note: his wound "was contradictorily located in his leg and his shoulder, depending on the story."
Nobody stopped reading Sherlock Holmes because of it. But the case teaches two things. Errors across a long series are normal, and a detail that matters to a character's body is the kind a reader will remember.
The seven families of continuity error
| Family | What goes wrong | Example (ours) |
|---|---|---|
| Names | A name or spelling changes | Brannock is Brannoch in chapter nine |
| Appearance | A physical detail changes | A scar on the left hand is on the right in chapter twenty |
| Time | Dates, ages, seasons or days do not add up | The festival is on a Tuesday and the next day is a Thursday |
| Place | A route, distance or layout changes | The harbour is downhill from the inn, then uphill |
| Objects | Something is lost, found or duplicated | The key left in the river is in her pocket on the next page |
| Knowledge | A character knows what they should not | He names the thief before he has seen the letter |
| Rules | A power, law or custom is bent | A spell that needed a spoken word is cast in silence |
Scroll horizontally to see all columns. Arrow keys work when the table is focused.
Jericho Writers' guide to copyediting names three of these directly. A copyeditor, it says, will notice if a character's eye colours change from a glacial blue in the first chapter to a muddy brown in the thirtieth, will check the timeline "calendar in hand", and will catch the character called Brain instead of Brian for most of the manuscript. Its list of what a copyeditor checks includes continuity of place and character names, continuity of character and setting cosmetics, and discrepancies in the timeline.
Rules deserve special attention in fantasy and science fiction. Brandon Sanderson says of J.K. Rowling's Harry Potter books that she adds new rules as she goes, sometimes running into contradictions and conveniently forgetting abilities the characters had earlier. He says the lapses are not important to the story and that each single book is generally cohesive. That is a useful reminder: some contradictions matter more than others.
Why they happen
Most continuity errors come from three causes.
- Writing over a long time. You wrote chapter three in January and chapter thirty in October. Memory does not hold that many details.
- Revising. You change a fact in one scene and miss the three that depended on it. Tolkien did this on purpose in The Hobbit: Wikipedia records that after he developed the One Ring in The Lord of the Rings, he revised the riddle-game scene for the second edition so that Gollum is aggressive and distraught instead of parting amicably with Bilbo. A deliberate change like that is still a continuity task, because everything that refers back to it must agree.
- Moving parts. Timelines, multiple points of view and magic add facts that interact.
How to catch them
Record facts where they first appear
Rochelle Melander, on Jane Friedman's site, recommends a story bible, a place to hold everything you plan and invent. She asks the kind of questions that cause errors: what colour and model of car did the protagonist drive in chapter one, how does she take her coffee, what was the name of the pet hamster she buried in chapter three? She adds that the bible can check continuity, because details that "may seem like meaningless details to us" can annoy readers. Who cares, she asks, if the protagonist takes her coffee black at the beginning of the book and with sugar at the end? Readers do. Her article opens with a line from L. Sprague de Camp: "In writing a series of stories about the same characters, plan the whole series in advance in some detail, to avoid contradictions and inconsistencies."
Melander also recommends the "good enough" bible, built quickly and expanded as needed, so that the bible never becomes more important than the book. de Camp wants the series planned in detail in advance, and Melander wants the lightest bible that works. Choose according to how long your series is. How to build a story bible and the story bible template give you a place to start.
Keep a timeline in days, not chapters
Write the story's calendar separately from its chapter order. For each event, note the day, the season and the age of anyone who matters. Jericho Writers' piece on story timelines says a timeline helps keep a story free of plot holes, and recommends deciding the ages of characters at the beginning and end. It cites Ian Rankin's Rebus novels, in which the characters age with the publication dates, and Rebus retires at 60 in the 2007 novel Exit Music.
Keep a knowledge log
For every secret, note who learns it, in which scene, and from whom. Check each scene where the character acts on it. This is the most common error in mysteries and the hardest to see by rereading, because the reader already knows.
Read in passes, one family at a time
Jericho Writers says a thorough self-edit begins with big-picture elements and moves to minor details, with at least three rounds of revisions and sometimes nine or ten. Make the last of them a continuity pass. Read only for one family each time: names, then appearance, then time. Search for each name and its variants, including spelling and nicknames.
Use outside readers
Ask beta readers a specific question: "Did anything contradict itself?" Then hire a copyeditor. Sandra Wendel, in an excerpt on Jane Friedman's site, lists checking that names of characters and places are spelled consistently among the tasks of a copy edit, and her example is Peterson in chapter one who may or may not be the Petersen in chapter six. A copyeditor is the last net, not the first.
When you find one
- Decide which version is right, on the basis of the story, not whichever you found first.
- Fix the other, and search for everything that depended on the version you changed.
- Record the fact in your sheet so it cannot drift again.
- If the contradiction is minor and the book is long, decide whether it matters. Sanderson's view of the Potter lapses is a reminder to spend effort where readers will notice.
For rules that bend, see how to create a magic system, and for tracking across books, how to write a series.
Frequently asked questions
What is a continuity error in a novel?
A detail that contradicts another detail in the same book or series: names, appearance, times, places, objects, what characters know, or the rules of the world.
What are common examples of continuity errors?
A character's eye colour changing, a timeline that does not add up, a lost object reappearing, a spell cast in a way the rules forbid, and a character who knows a secret too early. Dr. Watson's war wound moves from shoulder to leg between two Holmes stories.
How do I find continuity errors in my own manuscript?
Keep a fact sheet, a day-by-day timeline and a knowledge log, then read the draft once for each family of error. Ask beta readers directly, and consider a copyeditor.
Do readers really notice continuity errors?
Some do and some do not. Jericho Writers' copyediting guide treats them as serious enough that a copyeditor is hired to find them, and Sanderson notes that minor lapses may not hurt a story. Fix the ones about bodies, dates and rules first.
Can software catch continuity errors?
Yes, within its recorded data, supported rules and evidence. It cannot infer every contradiction from prose. Separate deterministic findings, uncertain timing and interpretive suggestions, then check the passage before revising.
Where Musael fits
Musael connects the manuscript to World records, with confirmed facts, beliefs, hypotheses and source passages kept distinct. Continuity checks inspect explicit recorded information and author-supplied rules; they do not infer every eye-color change or secret from arbitrary prose.
Plan → Revision reads saved passages by POV and plotline and keeps tasks beside the scenes to change. World → Checks → Revision tools follows explicit dependencies and compares author-recorded character acquisition and uses in story time. Unknown times stay uncertain; source status is shown separately. A flashback appearing later in the book is not automatically a later event.
AI review, when used under the current plan, is a separate interpretive aid. Inspect suggestions and approve changes deliberately. It cannot guarantee that every contradiction has been found, and deterministic checks do not silently rewrite prose. See how a continuity checker reads a manuscript for examples and limits.
Sources
- Arthur Conan Doyle, A Study in Scarlet, Project Gutenberg: gutenberg.org
- Arthur Conan Doyle, The Sign of the Four, Project Gutenberg: gutenberg.org
- Wikipedia, "Dr. Watson" and "The Hobbit": en.wikipedia.org, en.wikipedia.org
- Jericho Writers, "What Is Copyediting? A Complete Guide": jerichowriters.com
- Jericho Writers, "Story Timelines: How To Structure Your Narrative": jerichowriters.com
- Jericho Writers, "Questions To Ask Yourself When Self-Editing": jerichowriters.com
- Rochelle Melander, "The Story Bible: What It Is and Why You Need One", Jane Friedman: janefriedman.com
- Brandon Sanderson, "Sanderson's First Law": brandonsanderson.com
- Sandra Wendel, "The Differences Between Line Editing, Copy Editing, and Proofreading", Jane Friedman: janefriedman.com
