Continuity errors in your book: how to find and prevent them

Every book establishes facts: what people look like, what they are called, when things happen, who knows what, which rules hold in that world. Each fact becomes a small contract with the reader. A continuity error breaks that contract by accident — and without anyone noticing.

That does not mean nothing can change. A character can cut her hair, lose her faith, move town or change her name. That is development, and it works when the text shows the change. The error is the change nobody explained, because nobody noticed it happened.

These slips rarely come from a lack of talent. A novel takes months, sometimes years; you rewrite chapter 3 after finishing chapter 20, move scenes around, cut a minor character. The writer's memory cannot keep up with every draft — and the longer the book, the easier it is to lose the thread.

Almost every continuity error falls into one of six types. Knowing each one tells you what to look for in revision.

• Appearance and physical traits: Tainá has a scar on her chin in chapter 2 and a face "without a single mark" in chapter 11. Eye and hair color, height, tattoos, accent and even which hand someone writes with belong here.
• Names and spellings: the neighbor is Mr. Arlindo at the start and Mr. Orlando in the middle; Luíza becomes Luisa; someone uses a nickname before the scene where it is coined. The same goes for streets, companies, towns and pets.
• Timeline, ages and dates: the heroine is 32 in 2019 and 35 in 2021; a pregnancy lasts eleven months; the trip between two neighboring towns takes three days; it is Friday twice in the same week.
• A character who knows what they should not know yet: Joaquim mentions the letter that will only be found in the next chapter; the detective names the murder weapon before forensics arrive. This one shows up a lot after chapters are reordered.
• World and magic rules: if magic has a price, it cannot come free at the climax; if there is no phone signal in the mountains, the phone cannot ring there. Realism has rules too — bank opening hours, the distance between neighborhoods, the length of a flight.
• Objects and places: the knife was left in the kitchen and turns up in a pocket; the single-story house gains a cellar nobody mentioned; the car is red and then blue; someone who was sitting is standing without ever getting up.

No method catches every error, but four habits deal with most of them before the book reaches a reader.

1. Keep a story bible: a document or spreadsheet with every character, place and world rule, noting the chapter where each detail first appears. The chapter note is what makes the bible useful: when a doubt comes up, you go straight to the passage instead of rereading the book.
2. Close each chapter with a quick check: what did this chapter establish that is new — a trait, a name, a date, a rule? Update the bible right away. Five minutes now saves an afternoon of searching later.
3. Build a timeline separate from the chapter order: date (or "day 1", "day 2"), what happens, who is there and who learns what. The "who knows" column is the one that catches the character who knows too much.
4. Do focused read-throughs: instead of one general revision, reread the book looking for one thing only — just the timeline, just one character. Use the editor's search to follow a name from start to finish; different spellings jump out.

Beta readers help, but do not count on them for continuity: people reading for pleasure forgive and forget. If you want that help, ask for it explicitly: "note anything that seems to contradict something earlier".

Copy the list below and use it when you finish each chapter, or before you send the manuscript out to readers.

Chapter: ____
[ ] New physical traits noted in the bible (eyes, hair, scars, height)
[ ] Names and spellings checked against the bible (characters, places, nicknames)
[ ] Ages and dates match the timeline
[ ] Elapsed time is plausible (travel, pregnancies, seasons, days of the week)
[ ] Each character only knows what they have already found out on the page
[ ] World rules respected (magic, technology, distances, costs)
[ ] Objects are where they were left
[ ] Intentional changes recorded in the bible, with the reason
[ ] If I edited an earlier chapter: I checked every chapter after it

Linya's Continuity Engine does the cross-checking read that is exhausting to do by hand. When you ask for a check, it goes through the book's chapters and extracts the facts the text states: character traits, places, events, world rules. Each fact comes with the exact passage that supports it. Then every chapter is compared with what the earlier chapters have already established.

• Contradictions with evidence: each issue shows the earlier fact, with the original quote and a link to its chapter, the new passage that contradicts it, the severity (high, medium or low) and a suggested fix.
• Only what came before counts as established: chapter 12 is checked against chapters 1 to 11, never against what you wrote after it.
• Change is not an error: the check looks for direct contradictions and leaves aside changes the story explains, like a haircut, and differences in wording. What a character claims in dialogue is recorded as their testimony, not as the narrator's fact.
• Mistyped names: if your cast has a Joaquim and chapter 9 says "Joaqim", Linya points out the likely misspelling. The comparison runs against the names of the characters you have created for the book.
• Fixes with a preview: you see the proposed change before applying it to the text. If the difference is deliberate, mark it as intentional on the web, and it will not come back in later checks as long as that passage stays the same.
• An alert after you edit an earlier chapter: when you change a story fact (a name, someone's appearance, a date) in a chapter that has others after it, Linya lets you know that the later chapters may be affected, and one click checks them all. By default the alert comes after 10 minutes without saving. Rewording a sentence without changing the fact, or touching only the formatting, raises no alert.

The check runs when you ask for it: saving a chapter does not trigger anything. Chapters that have not changed reuse their saved result. When a name appears with no earlier history to compare against, Linya says so instead of giving you an empty "all clear". And it does not replace your own reading: it is a second check that neither tires nor forgets.

Is a continuity error the same as a plot hole?

Not quite. A plot hole is a flaw in the story's logic: the solution that does not hold up, the motive that does not add up. A continuity error is more concrete — a detail the book itself contradicts. Many plot holes start as continuity errors nobody fixed.

Should I check continuity while writing or only at the end?

Both, with different weight. While writing, the end-of-chapter check keeps the bible up to date. At the end, a focused read of the whole book catches what slipped through, especially after rewrites.

What if the character is lying or mistaken?

Then it is not an error, as long as the reader can tell at some point. Note in the bible what is true and what the character believes. In Linya, what a character claims in dialogue is recorded as their testimony, and on the web you can mark a difference as intentional.