The Errors That Ship, and How to Find Them

A contradiction ran through the central premise of my own novel across seven chapters. I wrote it, reread it, and did not see it. Neither did a careful human reader who went through the whole manuscript before I did.

Self editing continuity errors survive for a structural reason, not because anyone was careless. When you reread your own manuscript, you carry the intended version in memory, and that memory fills in what the page actually says. A human editor reading start to finish meets each chapter once, in order, and never holds the whole book in view at the same time. Self editing continuity errors are a structural result of reading your own work from memory instead of from the page.

This piece explains why that happens, walks through four real problems found in my own novel, The Emotion Collector: Awakening, before it went to print, and gives four manual checks you can run today with no tool and no cost. Nothing here is a verdict. Every manuscript has these. Maybe you’ve reread a scene for the tenth time, felt certain it was right, and had a beta reader catch what you couldn’t see at all.

Self editing continuity errors persist because two mechanisms work against you at once: memory overwrites what’s on the page, and linear reading never lets you compare chapter three with chapter nineteen at the same moment. The sections that follow walk through how that plays out in a real manuscript, what a whole-book comparison found in my own novel, The Emotion Collector: Awakening, and four manual checks you can run without any software.

Key Takeaways

• Memory overwrites the page: authors reread the version they meant to write, which is why self editing continuity errors persist through multiple passes.
• Linear reading has a blind spot: a chapter-by-chapter read cannot compare chapter three with chapter nineteen at the same moment.
• Four error types recur: contradicted premises, characters under two surnames, terms defined two ways, and ambiguous names that shift a character’s arc.
• Manual checks work: a name census, a date-anchored timeline, a glossary check, and out-of-order reading need no software.
• Errors found are errors fixed: everything described here in my own novel was corrected before printing.

Why Self Editing Continuity Errors Survive Every Read-Through

When you reread your own manuscript, you are not reading it cold. You supply the missing clause, the intended date, the name you meant to use, and the page and the memory blur together until they feel identical.

A second mechanism works against human editors too. Linear reading delivers a book in sequence, one chapter after another, so a contradiction between chapter four and chapter eleven requires holding both in working memory at once, which no reader manages reliably across ninety thousand words. That limit produces a specific and predictable result: contradictions survive longest exactly where the contradicting pages sit farthest apart. This is a structural gap, not negligence.

Be careful with the numbers people repeat here. The claims that editors catch roughly 80 percent of errors per pass, and that human accuracy tops out near 95 percent, appear across editing blogs and in discussions of Amy Einsohn’s The Copyeditor’s Handbook. I have not found an accessible primary study establishing either figure, so I won’t present them as settled fact.

You can test your own rate instead. Mark every correction you make on your next pass, count them, and see how many a second reader still finds afterward.

What a Whole-Manuscript Pass Found in My Own Novel

On The Emotion Collector: Awakening, a whole-manuscript comparison run through Perivane surfaced four things a careful human read-through had missed. All four were corrected before the book went to print. Nothing described here is a live defect in a book currently on sale.

The most serious was a central premise that contradicted itself across seven chapters. This wasn’t a slip in one line. The same idea was explained two incompatible ways, far enough apart that no linear reader ever held both versions at once. The error I was least able to see was the one I understood best, because I knew what I meant every time I read it.

Finding these was useful, not humiliating, and there’s no need to feel embarrassed when a check finds something you missed. The report format that surfaced them opens by saying it is here to help, not to judge, and that nothing in it is a verdict. That framing matters more than it might seem.

The Four Categories

The four findings map onto categories most manuscripts contain in some form.

• Contradicted premise: the same central idea explained two incompatible ways across seven chapters
• Split identity: a supporting character appearing under two different last names
• Double definition: one in-world program described with two different definitions
• Name ambiguity: an unclear reference that changed the weight of a major character’s arc

The Same Blind Spot in Fiction and Non-Fiction

Two full sample reports, published openly on Perivane, widen this beyond my own novel: one on Agatha Christie’s The Murder at the Vicarage, and one on J.C. Ryle’s Expository Thoughts on the Gospels: St. Matthew. Both are published, edited, respected books, which is the strongest argument that this problem is structural rather than personal.

In a detective novel, continuity pressure concentrates on who knew what and when, on the sequence of a single day, and on names and titles used inconsistently across a large cast. These are exactly the relations a linear read cannot hold in view at once.

Ryle’s commentary shows the parallel problem in expository writing. Consistency there means a term or doctrine carrying the same definition in chapter two and chapter twenty, and cross-references that point where they claim to point. Fiction and non-fiction fail in the same place: wherever meaning depends on two pages that are never read together.

The sample reports state findings and leave judgment to the author. Nothing in either one is a verdict, and that’s worth holding onto as you read your own work the same way.

Four Self Editing Continuity Errors Checks You Can Run Without Any Tool

These four passes target self editing continuity errors that linear reading structurally misses. Each needs nothing but your manuscript, a search function, and a notebook. Both sample reports published on Perivane show these same categories showing up in books that had already been professionally edited, which is a useful reminder that missing something here says nothing about your ability as a writer.

The glossary check catches definitions that drift. List every invented term, organization, program, ability, or piece of jargon. For each, write the definition as it appears at first use, then search every later occurrence and confirm the definition holds. This is the check that would have caught the double-definition error found in The Emotion Collector: Awakening.

Reading out of order weakens the memory effect that lets you read the intended version onto the page. Read chapters in reverse, or shuffled, or read only the scenes featuring one character in sequence. You might notice that a character’s eye color or hometown shifts between two chapters you never would have placed side by side otherwise. Breaking the expected order makes contradictions harder to smooth over automatically.

One common mistake is folding continuity into the final proofread. It competes with line-level attention and loses. Make it a separate pass, with a single question in mind. A second mistake is running these checks once, early. Continuity damage concentrates during heavy revision, when scenes move, merge, or vanish and their dependents are never re-checked.

The Name and Spelling Census

A census lists every proper noun in the manuscript and counts its variants.

• Build it: write down every character, place, organization, and title, with every spelling form you find
• Compare: flag any two entries that could be the same referent, including surnames used only once
• Resolve: decide the canonical form, then search and correct every instance

The Date-Anchored Timeline

Build the timeline only from explicit references in the text, never from what you remember planning.

• Extract: log every stated date, day name, season, age, time span, and clock reference with its page
• Sequence: place them in order and look for spans that cannot both be true
• Note gaps: unanchored stretches are where contradictions hide

What to Do When a Check Disagrees With Your Memory

The hardest moment is believing the error once you’ve found it. Your memory of the intended version is vivid and feels authoritative, which is exactly why it’s untrustworthy here.

One common pattern looks like this: a writer runs a name census, finds two surnames attached to the same character, the same split-identity pattern found in The Emotion Collector: Awakening, and insists for a moment that both are correct. Then they check the page and see there’s no way both were intended. That flash of resistance is normal, not a sign of sloppy editing. Most writers pass through it before they can act on what the check found.

The practical rule: the page wins. If the census shows two surnames, there are two surnames, regardless of which one you have been picturing for three years. A finding is a question about the page, not a judgment about the writer, and it’s okay to need a minute before you accept that.

Triage by consequence rather than by count. A premise that contradicts itself changes what the book means. A single misspelled place name does not. Fix both, but decide the order deliberately. For the ambiguous-name category, ask whether a first-time reader with no access to your intentions could resolve the reference. If not, it’s genuinely ambiguous even though it reads clearly to you.

Be honest about the labor involved. A name census, a date-anchored timeline, a glossary check, and an out-of-order read across a full novel amount to days of concentrated work, repeated after every substantial revision. That cost is the real reason these checks get skipped, more often than any lack of will. This is the task I built Perivane to do, and the two sample reports discussed above are published there in full, for anyone who wants to see what the findings actually look like on a real book.

If you’re building out a broader production process around this stage of the work, our book publishing checklist and our notes on Kindle Direct Publishing quality standards cover the steps that come before and after this one.

Why Manuscript Continuity Matters

Readers meet a book without your memory of it. Every gap you fill in automatically, they encounter as a gap. Continuity problems rarely sink a book on their own, but they cost trust at the exact moment a reader is deciding whether the author is in control. Finding four in my own novel confirmed that the checks worked.

Conclusion

Self editing continuity errors survive because memory overwrites the page and because linear reading never holds the whole manuscript at once. Both are structural. Neither is negligence, in your manuscript or anyone else’s.

In my own book, a whole-manuscript comparison found four things, including a premise contradicted across seven chapters, and all four were fixed before printing. The four manual checks described here, a name census, a date-anchored timeline, a glossary check, and out-of-order reading, are the practical answer. None require software. All require a separate pass and a specific question in mind, ideally before you move on to launch sequencing and the rest of the pre-publication work.

The register here is meant to help, not to judge. Nothing in this article is a verdict on anyone’s book, including mine. Pick one check, run it on your current manuscript this week, and count what it finds. Then decide whether the number surprised you.

Frequently Asked Questions

What are self editing continuity errors?

A self editing continuity error is a contradiction between two points in a manuscript, such as a changed name, date, or premise, that survives an author’s own read-throughs because both points feel consistent with what the writer remembers intending rather than what the page actually says.

Why do continuity errors survive multiple read-throughs?

They survive because two mechanisms work against the writer at once: memory overwrites the page, so authors reread the version they meant to write, and linear reading never lets anyone compare chapter three with chapter nineteen at the same moment, leaving contradictions between distant pages unnoticed.

How many errors do editors typically catch per pass?

Figures like “80 percent per pass” and “95 percent overall” circulate widely in editing discussions, including around Amy Einsohn’s The Copyeditor’s Handbook, but no accessible primary study supports either number. Treat them as folklore, and instead track your own correction rate across passes.

What types of continuity errors are most common in manuscripts?

Four categories recur across manuscripts: a contradicted premise explained two incompatible ways, a character appearing under two surnames, a term or program defined two different ways, and an ambiguous name reference that shifts how a character’s arc reads.

How can I check my manuscript for continuity errors without software?

Run four manual passes: a name and spelling census listing every proper noun and its variants, a date-anchored timeline built only from explicit text references, a glossary check confirming invented terms keep one definition, and an out-of-order read that breaks the memory effect hiding contradictions.

Is a continuity check the same as proofreading?

No. Proofreading focuses on line-level accuracy like spelling and punctuation, while a continuity check compares distant pages against each other for contradictions in names, dates, or definitions. Folding continuity checks into a final proofread causes them to compete for attention and lose, so they need a separate pass.

Part of the guide: The Long Push: What Keeps Selling After Launch Ends

Sources

• Amy Einsohn, The Copyeditor’s Handbook – University of California Press. The standard reference on editorial consistency checking
• Expository Thoughts on Matthew – Full text via the Christian Classics Ethereal Library
• Perivane – Sample Editorial Continuity Report, including the report this article describes