Continuity errors readers actually notice

6 min read · Updated October 23, 2026

A continuity error is a detail that contradicts something your book has already established. Eyes that change color, a dead character at a dinner party, a three-day ride done overnight. Each is small. Readers notice them anyway, and in a series they notice more, because they've had years to reread.

The good news is that the errors readers catch fall into a short list of types. If you know the types, you can check for them deliberately instead of hoping to spot them on a read-through.

The errors readers notice most

Physical descriptions that change

Eye color, hair color, height, scars, tattoos, handedness, voice. These are stated once, early, and then repeated much later after the author has forgotten them.

In The Ashen Crown, Kael Varn has "green eyes" in book one, chapter two. In book two, chapter one, he has "grey eyes." Both lines read naturally. Only a side-by-side comparison shows the problem.

How to catch it: record every physical detail the first time you state it, with the chapter. Check your notes before describing a character who hasn't appeared for a while.

Characters who appear after they die

This one is easier to commit than it sounds, especially in long books, multiple-viewpoint novels and series. A character dies in a battle scene, then appears in a list of people at a council three chapters later because you copied the list from an earlier draft.

The Ashen Crown has this exact mistake. Lord Aldric dies holding the gate at Thornwatch on 3 Ashmoon, 412 AS. In book two, he attends the Council of Varrow in Frostmoon, 413.

The reverse also happens: a character taking part in events before they were born, usually in backstory or flashbacks.

How to catch it: record a death date for every character who dies, and check every scene they appear in after it.

Impossible travel

Once you've said how far apart two places are, every journey between them is fixed. Readers who like maps will check.

In the sample, Varrow is three days' ride from Thornwatch. Kael is at the vigil in Thornwatch on 5 Ashmoon, but a later chapter has him holding the Varrow walls from 4 to 6 Ashmoon. He's in two places at once.

How to catch it: note travel times for every route. Put each scene on a timeline with a place. Look for characters with overlapping stays in different places.

Ages that don't add up

Ages are arithmetic, and some readers will do it. If a character is "nineteen" in chapter one but was "born in the spring of 388" and the story is set in 412, they're about 24.

That's another planted error in The Ashen Crown. Similar traps: siblings whose age gap shifts, parents who would have been eleven when their child was born, and "ten years ago" that stays ten years ago in a sequel set two years later.

How to catch it: store birth years, not ages. When the text states an age, check it against the birth year and the current story date.

Names and spellings

A minor character's name spelled two ways, a town that gains or loses a letter, a nickname used before the character earned it. Readers are especially sharp about names in fantasy, where they're unfamiliar.

Duplicates are a related problem: the same character introduced twice under different names because you forgot you'd already named the innkeeper.

How to catch it: keep one list of every name, with aliases and titles. Search the manuscript for near-matches before final edits.

Who knows what

A character refers to a secret they haven't learned yet, or forgets something they found out two books ago. These are harder to spot because nothing on the page looks wrong in isolation.

How to catch it: for important secrets, record the chapter where each character learns them. Check scenes with those characters against it.

Rules that bend

Magic systems, technology limits, laws, the cost of something. If every use of Emberfire burns away a memory, a knight using it freely without consequence is an error, unless the book explains why.

How to catch it: write each rule down with its limits and costs. Check every scene where the rule comes up.

Objects that teleport

A sword left in one city turns up in another. A letter is burned and then read. A horse dies and then carries someone home.

How to catch it: for important objects, track who has them and where they are, with dates.

How to check continuity yourself

You can't keep an entire novel in your head. A system catches more than a careful reread.

1. Keep a bible as you draft. Record names, descriptions, dates, ages, deaths, travel times and rules. Note the chapter for each.
2. Do a dedicated continuity pass. Read only for facts, not for prose. It's slower than a normal read, and worth it.
3. Check by category. One pass for deaths, one for ages, one for travel. Focusing on one kind of error at a time catches far more.
4. Search, don't remember. When a character reappears, search the manuscript for their name and reread their last few appearances.
5. Read in story order if your book isn't linear. Flashbacks and multiple viewpoints hide errors that a chronological read exposes.

How editors check continuity

Professional editors use the same basic method you can use yourself.

• Copy editors usually keep a style sheet as they read: every name and its spelling, character descriptions, place names, dates, and style choices like how numbers are written. When something contradicts the sheet, they query it.
• Developmental editors look at larger logic: motivation, plot holes, whether events could happen in the order shown.
• Proofreaders catch some continuity slips, but their main job is the final text, and they're working fast.

Editors can only check against what they've read. On book four of a series, a copy editor may not have read books one to three. Giving them your series bible, or at least the relevant parts, saves them time and catches more errors. For the difference between these documents, see story bible vs. series bible vs. style sheet.

Not every inconsistency is a mistake

Sometimes the change is the story. An unreliable narrator misremembers. A curse turns eyes white. Two cultures date the same war differently. A character lies about their age.

Keep these, but record them as intentional. Note when the change happens and why. Otherwise you, a co-writer or an editor may "fix" the very thing you planned.

What to do when you find one

• Before publication: fix it in the text, then update your notes so the fix sticks.
• After publication: choose whether to correct it in a later edition, explain it in a future book, or simply pick one version and use it consistently from now on.
• Either way: record the decision. The second-worst continuity error is the original mistake. The worst is fixing it two different ways.