Continuity errors are contradictions between facts a novel itself establishes: blue eyes that turn brown, a Tuesday that happens twice, a sword left at the inn that turns up in a character's hand. Readers catch nine recurring kinds, from physical description and timeline math to series canon. The fix is a dedicated continuity pass after structural edits, built on a written record of every fact you invent.
They are small errors, but they are the kind readers love to point out in reviews, because spotting one feels like catching the author napping. Even the most famous authors have done it, which is reassuring and also a warning: if Conan Doyle could lose track of where Watson was shot, so can you.
Famous continuity slips (and what they teach)
These examples are all checkable in the text or in contemporary reporting.
Watson's wandering wound. In A Study in Scarlet (1887), Watson says he was "struck on the shoulder by a Jezail bullet" at the battle of Maiwand. Three years later, in The Sign of the Four, he sits "nursing my wounded leg," explaining that a Jezail bullet went through it. One war, one bullet, two body parts.
Watson's other first name. The title page of A Study in Scarlet presents the story as the reminiscences of John H. Watson. In "The Man with the Twisted Lip," Watson's own wife offers to send "James off to bed". It is the classic name slip: one wrong word, in a scene about something else.
The Goblet of Fire wand order. Salon reported in 2001 that early printings of Harry Potter and the Goblet of Fire had James Potter emerge from Voldemort's wand before Lily. Because the echoes of the dead emerge "in the reverse order in which they were killed," that contradicted the earlier books, in which Voldemort killed James first. In an email to fans that Salon quoted, Bloomsbury said the error was "spotted by our editorial team in July, and corrected in subsequent editions." This is a rules error: the scene's own magic dictated the order, and the order had to agree with what earlier books said about the deaths.
Tolkien's retrofit. Series-level canon can change after a book is published. In the first edition of The Hobbit, Gollum willingly bets his ring on the riddle game. Once the ring became the One Ring of The Lord of the Rings, Tolkien rewrote the chapter, and the revised text became the 1951 second edition; The Lord of the Rings then explains the original version as a lie Bilbo told under the ring's influence. Few authors get to rewrite book one, so for most series the lesson is to fix canon before book one goes out.
The pattern across all four is the same. None of these errors sits in a scene about the fact in question. The wound comes up in passing, the name in a domestic aside, the wand order in an action climax. Continuity errors live in the places you weren't looking.
The 9 kinds of continuity error readers catch
Examples below marked (illustrative) are invented to show the pattern.
1. Physical description drift
Eye color, hair, height, scars, tattoos, handedness, build, voice. These are set once, early, and then referenced from memory for 300 pages. (Illustrative: a love interest's "storm-gray eyes" in chapter 3 become "warm brown" in a kiss scene in chapter 22.) Handedness is a frequent offender in fight scenes, and injuries are worse: a broken wrist must stay broken, then heal at a believable pace, then leave whatever trace you said it would.
Prevent it: record every physical detail in a character entry the moment you write it, including details you invent mid-scene.
2. Timeline and age math
The most common kind in long novels, and the easiest for readers to check with a calculator. (Illustrative: a heroine is "twenty-six" in 2019, her backstory says she left home at eighteen "ten years ago," and the book opens in 2021.) Watch days of the week, how many "three days later"s add up across a section, school years, pregnancies, seasons and moon phases, and holidays that fall on fixed dates.
Prevent it: keep a dated timeline of scenes, even for a book that never states a date. If the book says "Thursday," the timeline should know which Thursday.
3. Geography and travel time
A journey that takes four days on the way out and an afternoon on the way back. A window that faces the sea in one chapter and the street in the next. A city whose districts move. (Illustrative: the inn is "a half-day's ride north" of the capital, but the army marches south to reach it.)
Prevent it: draw a rough map, even for a contemporary setting, and note travel times between key places by each mode of transport your characters use.
4. Object tracking
Who has the letter, the gun, the ring, the car keys? Objects get dropped in one scene and used in the next. (Illustrative: the detective leaves her phone in the patrol car, then takes a call in the warehouse.) Clothing and weather count too: a character who changes into a dress for the party shouldn't be reaching into her jeans pocket at the party.
Prevent it: list important objects with their last known location and holder, and check the list at every scene break where an object matters.
5. Names and spellings
Character names that change spelling (Katherine, Catherine, Kathryn), secondary characters whose names change outright, invented terms spelled two ways, and titles or ranks that shift. Watson's "James" is the famous version. (Illustrative: Sergeant Okafor in chapter 4 is Sergeant Okoro in chapter 17.)
Prevent it: keep one canonical spelling list, then search for each name and its likely variants. This is the one category where plain manuscript search catches almost everything.
6. Knowledge: who knows what, and when
A character acts on information they were never given, or forgets something they learned. (Illustrative: the brother is shocked to learn about the affair in chapter 20, but he overheard the phone call in chapter 11.) These are the hardest errors to spot by rereading because the scene reads naturally on its own. They often appear after revision, when you move a reveal earlier or later and forget the scenes that depended on it.
Prevent it: for each major secret or reveal, write down which characters know it and from which scene. Recheck the list every time you move a scene.
7. Rules of magic and technology
If casting a spell costs blood, it costs blood every time, including when the plot would rather it didn't. If the ship needs nine days to cross the system, it can't do it in two because the climax is due. The Goblet of Fire slip was this kind: the scene's own rule (the dead emerge in reverse order of their deaths) dictated what had to happen.
Prevent it: write each rule as a plain sentence with its costs and limits in your story bible, and list every scene where it is used.
8. Relationship state
Characters who fell out in chapter 9 chat warmly in chapter 12 with no reconciliation on the page. Someone who doesn't know their parent is alive mentions "my mother" in present tense. (Illustrative: the rivals call each other by first names before the scene where that change is supposed to land.) Relationship errors damage character arcs as well as facts, so readers feel them even when they can't name them.
Prevent it: track each key relationship's status and the scene that last changed it.
9. Series-level canon
Everything above, across books. A dead character reappears, a scar moves, a sister becomes a cousin, the magic system gains a convenient exception. Series readers reread, and they keep wikis. Tolkien had a second edition to fix The Hobbit; most authors don't.
Prevent it: treat your series bible as a deliverable for each book, finished and checked before the next draft starts. Our guide to keeping a book series consistent covers series bibles in detail.
Why you can't see your own continuity errors
You know your story too well. When you reread chapter 22, your memory supplies the correct eye color and your eye skims past the wrong one. Beta readers catch some errors because they read fresh, but they also read fast and for story, so they miss many.
That is why the fix is a record, not a reread. A fact written down at the moment of invention can be checked mechanically later; a fact held in memory can only be checked by noticing, and noticing is exactly what fails. If you don't yet keep one, start with our guide to building a story bible or copy our story bible template.
How to run a continuity pass
Do it after structural revision and before beta readers. Before that point, scenes are still moving and you will check things twice. After it, every fix you make is to the version people will read.
- Lock the structureFinish moving, merging and cutting scenes first. Continuity work on a scene you later delete is wasted.
- Build the fact recordOne story bible entry per character, place, object and world rule, plus a dated timeline of scenes.
- Timeline readRead only for time: dates, days of the week, ages, seasons, travel durations, pregnancies, injuries healing.
- Description and object readCheck every physical description and every important object's location against the record.
- Name and term searchSearch each proper noun and invented term, plus likely misspellings, and fix them to one canonical form.
- Knowledge and rules readFor each key reveal, list who knows it from that scene on; check every world-rule use against the stated rule.
Two practical notes. First, read for one category at a time. Trying to catch timeline, description and object errors in a single read means you catch none of them reliably. Second, when you find a contradiction, decide which version is canon before fixing anything. Sometimes the later version is better, which means changing the earlier scene and every reference between.
Spreadsheet, document, search or software?
Every method below works. The question is how much book you have to track and how much of the checking you want to do by hand.
For a standalone novel, a free combination usually suffices: a spreadsheet for the timeline, a document for characters and places, and manuscript search for names. The weakness of all three is that they only catch what you remember to compare. For long books and series, that is where dedicated story bible software earns its place: BlurbBio, for example, can detect the Story Bible from your manuscript on paid plans and check new chapters against it. Whatever flags a tool raises are candidates for you to judge, not verdicts.
The pre-beta and pre-publication checklist
Tick these off in two rounds. The first round makes the draft worth a beta reader's time; the second makes sure edits haven't introduced new contradictions. Your ticks are saved in this browser.
The second round matters more than writers expect. Edits are where many continuity errors are born: a scene moved to fix pacing, a reveal brought forward, a name changed at an editor's suggestion. The Goblet of Fire slip was caught by the publisher's editorial team and fixed in reprints, but by then the error was in readers' hands. Your last pass is the one that keeps it out of yours.
What to do this week
- Pick the category you're least sure about (for most writers, timeline or who-knows-what).
- Build that one section of your story bible from the manuscript as it stands.
- Do a single read for that category only, logging every contradiction.
- Fix, update the record, and move to the next category.
If you want a second pair of eyes on the mechanical part, BlurbBio's continuity checker does the comparison for you. Either way, the record is the real fix. Write the fact down once, and you never have to remember it again.