Common Continuity Errors in Fiction (and How to Catch Each One)

Continuity errors in writing fall into five recognizable types. That’s genuinely good news, because a vague fear of “contradicting myself somewhere in 100,000 words” is paralyzing, while a checklist of five specific failure modes is something you can actually hunt for. Here is each type, a real example of how it slips in, and a concrete way to catch it before a reader does.

1. Attribute errors

The most famous kind: a fixed detail about a person, place, or object changes without cause. Elena’s eyes are grey in chapter 3 and green in chapter 31. A cottage has a red door early and a blue one later. A minor character is “Tomas” in one scene and “Thomas” in the next.

Why it slips in: you remember the feel of a character, not the spec sheet. Months into a draft, the specifics wobble because your memory stored an impression, not a value.

How to catch it: keep attributes as short factual pairs (eyes: grey, door: red), not buried in prose paragraphs, and check them wherever the entity appears. The trick is knowing where it appears, which is why an appearance log (or a tool that builds one from @mentions) turns “reread the book” into “check four chapters.”

2. Timeline errors

Events referenced out of order, or durations that don’t add up. A character mentions the siege two chapters before the siege happens. A pregnancy lasts fourteen months. “Three days later” lands the characters on the same weekday they started.

Why it slips in: reading order and story chronology drift apart. Flashbacks, parallel plots, and revisions that reorder chapters all separate “when the reader encounters a scene” from “when it happens in the story.”

How to catch it: give each chapter a story-time index separate from its position in the manuscript, and track elapsed time explicitly. Once scenes are ordered by story time, a reference to an event that hasn’t happened yet becomes visible instead of hidden.

3. Rule errors

Your world establishes how it works, then quietly breaks its own law when the plot needs it to. Magic requires moonlight, but someone casts at noon. Faster-than-light travel is impossible, except in the one scene where the rescue depends on it. A currency, a technology, a social taboo: any established constraint the story later violates.

Why it slips in: rules are promises to the reader, and under drafting pressure a promise is easy to bend for a scene that needs to work. Readers of fantasy and science fiction are unusually unforgiving here, because the rules are half the pleasure.

How to catch it: write your world’s hard rules down as explicit constraints, not lore, and re-read any scene that touches magic, technology, or law against them. A hard magic system especially needs its costs and limits recorded as checkable facts. (More on the underlying system in how to track continuity in a novel.)

4. Relationship errors

Who knows whom, who knows what, and who stands where. Two characters the text later treats as strangers are established as siblings. A character acts on information they were never told. A rivalry resolves and then reappears unresolved.

Why it slips in: relationships are the least visible facts in a manuscript. An eye color sits in one sentence, but “Elena doesn’t yet know her brother is the traitor” is spread across the whole book and lives mostly in your head. Prose notes capture this worst of all.

How to catch it: map relationships as their own layer (Elena serves the Order, the Relic is held in the Citadel, Marcus knows the secret as of chapter 9), and track the flow of information deliberately. “Who knows what, and since when” is the single most useful question to ask before a reveal.

5. State errors

Facts that were true, until they weren’t. A character killed in chapter 12 has dialogue in chapter 15. A destroyed bridge is crossed later. A stolen object is back in its owner’s hands with no explanation.

Why it slips in: a static fact sheet can only say a fact “is” true. It can’t represent “was true until chapter 12,” so when you revise, the change point gets lost, and the dead speak.

How to catch it: record when a fact changes, not just what it is. status: alive to dead (chapter 12) makes “speaks in chapter 15” checkably wrong and “speaks in chapter 9” correctly fine. State over time is the difference between a checklist and a system, and it’s the error type most tools can’t handle at all.

Why these survive all the way to print

Notice the common thread: every one of these hides in the gap between a fact and its contradiction, a gap usually measured in dozens of chapters. Human memory is worst at exactly that distance, and the standard tools (a spreadsheet, a re-read, a beta reader) all require you to already suspect the specific error to find it. The mistakes that reach print are the ones nobody suspected, in the scenes everyone was sure about.

Catching them without rereading the whole book

You can hunt all five types by hand: structured facts kept short, a story-time index, an explicit rules list, a relationship map, and change points recorded against story time. That’s the manual system, and it works. The tedious part is the cross-referencing, which is mechanical and therefore automatable. For a survey of what does the automating, from spreadsheets to AI, see the best tools to catch continuity errors, and for what AI can and can’t reliably flag, can AI catch plot holes and continuity errors?

This is the exact problem StoryGuard was built for: your world is a structured graph, your chapters link to it as you write, entity state is tracked against story time, and an AI scan reads both together and flags all five error types with the offending sentence highlighted. However you catch them, the goal is the same. Name the five, check for each, and stop letting the contradictions you never suspected be the ones your readers find first.