Writers · problem and fix
How to catch continuity errors in a novel manuscript on Mac: a revision routine
To catch continuity errors in a novel manuscript, write down every fact a reader will track, then check each revised chapter against that list. Most errors come from revision itself. A change in one scene can quietly break a detail somewhere else. This page covers what the errors cost, why they happen, and a routine you can run with tools you already own. It ends with an honest note on where Lazur fits.
The short answer
- Write a fact list first: names, ages, eye color, dates, and who knows what.
- After each revision, check the changed chapter, then search for every fact it touches.
- Research on proofreading suggests you miss more errors in your own text. Change how you read.
- Scrivener snapshots help you compare versions, but they are not full backups.
- Lazur reads only what is on screen while you hold ⌥ ⌘, so use it on one passage at a time.
What continuity errors across revised chapters costs you
Hours spent rereading
A continuity pass means rereading whole chapters with a list open beside you. No study I found measures how many hours that takes. The Authors Guild survey measures income, not hours, so it cannot price the work. Time one chapter yourself, then multiply that time by the chapters you revised.
Income that depends on the book
The Authors Guild survey put median book income at $2,000 before tax, and $15,000 for full-time traditionally published trade authors. Those figures come through Publishers Weekly, not the Authors Guild report itself. A book that loses readers can earn less. I did not find data that links continuity errors to sales.
Trust with readers and reviewers
A reader who spots a detail that contradicts an earlier scene may stop trusting the rest of the book. Reviews can say so in public. I did not find research that measures how often this happens. Treat it as a craft cost you can control, not a number you can quote.
Errors that reach print
Panko's compilation of proofreading studies shows that people catch fewer errors in their own text. In the 1993 Daneman and Stainton study, own-text detection was 59% at 20 minutes, against 76% for others' text. That study tested spelling and word errors, not story facts. It still suggests a fresh reader is worth having.
Why it happens
A change in one place does not reach the others
Revision edits a scene, not the whole book. When you move a funeral from one day to another, the chapter that mentions the funeral keeps the old day. Nothing in your word processor links those two sentences. Each change creates a new chance for a mismatch.
Your memory fills in the gaps
You remember what you meant to write, not always what you actually wrote. Your eye reads the sentence you intended. That is one reason proofreading research finds lower detection rates in your own text. Panko's compilation puts the gap at 59% against 76% at 20 minutes, for word errors.
The facts live in your head, not on the page
If the eye color exists only in your memory, every chapter gets checked from memory. Memory is exactly what fails after a long revision. A written fact list gives you something to check against, instead of something to guess at.
Drafting ahead of revision
Many writers draft later chapters before they finish revising earlier ones. The later chapter then depends on a version of the early chapter that changes again. Each rewrite of the early chapter can break the later one. Keep the fact list current so the later chapter has a fixed reference.
Scenes moved around in the outline
When you rearrange scenes, the order of events can change without any sentence changing. In Scrivener, dragging a corkboard card also reorders the Binder document. A scene that now happens before another can invalidate a fact that depended on the old order. Check the timeline after each move.
Duplicate copies of a chapter
Many writers keep a draft, a revised draft, and a final copy in different folders. You fix the mistake in one copy, and the copy that goes to a reader keeps the old detail. Keep one current file, and archive the old copies in a separate folder.
How to fix it
These work with or without any app.
Write a fact list before the next revision
Make a table with four columns: Fact, First seen, Repeated in, and Status. Fill in only the facts a reader could check. Start with names, ages, dates, and places. Update the list after every revision, not at the end of the book. That habit keeps the list useful.
Save a copy before every change
Keep the chapter as it stood before you touched it. In Scrivener, press ⌘5 for a snapshot, or ⌃⌘5 for a titled snapshot that names the revision. In Pages, Word, or Google Docs, duplicate the file or the chapter section before you edit. Then you can compare the change and undo a bad fix.
Log each change in one line
Write the fact, the old version, and the new version. For example: detective's eye color, brown to green, opening chapter. This takes a minute. It gives you a checklist for the search step, so you do not rely on memory for what you changed.
Search for the fact, not just the name
Search each changed fact across the whole book with ⌘F. Search for the old word and its synonyms. Search for names and nicknames, times like midnight and dawn, and objects. Read each hit in context, because a hit is not always an error. Some hits are fine. Some are the error you were hunting.
Read in a different format
Print the changed chapter, or change the font and the zoom. Read with the fact list on paper beside you. A new format can make your attention land on different words. That helps when you have read the same draft many times.
Add a timeline column for time and season
Add columns to the fact list for the day, the time of day, and the season. Read them top to bottom. A jump in the season or a missing day shows you the problem quickly. This matters most for novels that cover weeks or months of story time.
Mark intended changes
Add a column called Intended. Write yes for differences the reader should notice. That keeps your next pass from fixing a deliberate lie or a mystery clue. The list then tells you which mismatches are bugs and which are part of the plot.
Get a second reader with the list
Give a beta reader or critique partner the fact list and ask them to flag mismatches. They read for story, so they will miss some facts. Treat their notes as one check among several, not as the final word on the book.
Use a voice helper for one passage at a time
Lazur can point at a name on the screen you have open and explain what a passage says about time. Hold ⌥ ⌘ and ask. It works on what is visible, so use it after you have chosen the passage, not as the whole check.
Revision is where continuity breaks. You move a funeral from one day to another to fit a new subplot. Then a chapter that mentions the funeral still says the old day. Nothing crashes. The book just disagrees with itself, and a reader notices before you do.
What continuity errors cost you
Nobody I could find has measured the cost of continuity errors. I searched for surveys on how often they show up in revised fiction, and for studies on the hours they take to fix. I found none. So the figures below describe your working situation, not the errors themselves.
140,300
writers and authors held jobs in 2025, across many writing fields
BLS Occupational Outlook Handbook: Writers and Authors$15,000
median book income for full-time traditionally published trade authors, Authors Guild survey
Publishers Weekly: Author incomes post small gains59% own vs 76% others
word errors caught at 20 minutes, own text versus others' text (proofreading study, not story facts)
Errors in Proofreading (Panko)Time is the first cost. A continuity pass means reading the whole book again, slowly, with a list open next to it. The Authors Guild income survey does not measure hours spent writing or revising, so it cannot price that work for you. The Bureau of Labor Statistics does not track revision time either. What it does show is how the job is structured. Most writers are self-employed, so the draft often reaches a reader with no staff editor checking it first.
Money is the second cost. The Authors Guild survey, as reported by Publishers Weekly, found a median book income of $2,000 before tax across 5,699 published authors who responded. For full-time traditionally published trade authors, the median was $15,000. A reader who spots a broken detail may leave a harsh review. I did not find data on how often that happens, so treat it as a risk, not a measured cost.
- Hours rereading whole chapters to find one changed fact
- Trust, when a reader spots a detail that contradicts an earlier scene
- Editing time, when an agent or editor catches the error before you do
- Rewrites that spread, when a fix in one chapter breaks two more
Why your own eyes miss errors
Proofreading research points the same way. Panko compiles a 1993 study by Daneman and Stainton. At 20 minutes, readers caught 59% of word errors in their own text. In other people's text, they caught 76%. At two weeks, the numbers were 68% and 83%. Replication is mixed, and these tests used spelling and word errors, not story facts. It may still match your own experience. You read what you meant to write.
Build a fact list before you touch a chapter
A fact list is a plain document. Keep it in Pages, Word, Google Docs, or Notion. Each row names one fact, the chapter where it first appears, and each later chapter that repeats it. Write facts the way a reader sees them. Eye color. Age at the time of the trial. The car model in the chase. The day of the storm.
Track these kinds of facts first:
- Names and spellings, including nicknames, titles, and place names
- Ages, birthdays, and how old each character is in each scene
- Recurring physical details, such as scars, height, jewelry, and clothes
- Dates, days of the week, and the time of day for each scene
- Distances, room layouts, and which door opens which way
- Who knows what, and the chapter where each character learned it
Keep the list short at first. Add a row when you notice a fact a reader could check. A short list you finish is more useful than a long one you abandon. Mark intended changes too, which I cover below.
A revision routine that catches errors chapter by chapter
- Freeze the draft. Save a copy or a snapshot of each chapter before you change it.
- Log each change in one line: the fact, the old version, and the new version.
- Read the changed chapter with the fact list open beside it. Stop at every name, number, and date.
- Search the whole book for each changed fact. Use ⌘F in Pages, Word, or Google Docs.
- Search for synonyms too. Old wording often survives in dialogue and tags.
- Update the fact list, then read the chapters that share the same characters.
Here is a worked example. Your detective has brown eyes in the opening chapter. You decide she should have green eyes. You change the description and search for brown. You find one more mention in a later flashback. Then you search for dark, because a late chapter says her dark eyes narrowed. The search for brown missed it. Search for the fact, and search for its synonyms.
Use snapshots and the corkboard in Scrivener
If you draft in Scrivener for Mac, two tools help with this routine. ⌘5 takes a snapshot of the selected document. ⌃⌘5 takes a titled snapshot. You can also reach snapshots through Documents > Snapshot, or open the Snapshots pane from the camera icon in the Inspector. A snapshot saves one document at one moment, so you can look back or restore parts of it. Literature and Latte covers comparing and restoring snapshots in a separate article, so read that before you need it.
The corkboard helps you see order. Each index card is a file in the Binder and an item in the Outliner. Dragging cards reorders the Binder documents. In freeform Corkboard mode, Commit saves the layout to the Corkboard, Binder, and Outliner. Moving a scene card can move the timeline too, so check the chapters on either side of every move.
The Scrivener release notes list 3.5.2, released 18 December 2025, as the latest version I checked. Menu names can change between releases, so confirm them in your copy before you follow a path.
Get a second reader for the facts
A beta reader or critique partner reads for story, not for your fact list. Give them the list and ask them to flag every place the text and the list disagree. Expect them to miss things too. Their notes are a second check, not a final one. Ask which chapters felt confusing about time, since confusion about time often points to a timeline problem.
Where Lazur helps, and where it does not
Lazur is a voice assistant for the Mac. Hold ⌥ ⌘ to ask about anything on screen, and Lazur answers out loud. Ask where something is, and Lazur draws a circle and a label around it. It looks at the screen only while you hold the shortcut. Treat it as a second reader for the passage in front of you, not as a checker for the whole book.
Two uses fit well. Ask where a name appears on the screen you have open, one spot at a time. Or ask it to explain what a passage says about the timeline. It works on what you show it, so you still need the fact list, the search, and your own reading. Lazur does not click buttons or edit files for you.
Hold fn to dictate clean, formatted text at the cursor in any app. This helps when you log a change while the chapter is still open. Add character names to the personal dictionary, so dictation spells them the way your fact list does. Snippets can hold a standard row format you reuse.
Manuscripts are private work, so check the facts about data. Lazur listens and looks at the screen only while you hold the shortcut. Audio and the screenshot go to AI providers to answer, and they are not stored. Content is never used to train AI models. If your manuscript sits under a publisher contract or a confidentiality term, read those terms before you share any text with an AI tool.
Edge cases that trip up careful writers
Some errors hide from search. A character who is a few days away in one chapter and last week in another is hard to find by keyword. Weather and seasons drift the same way. Build a timeline before you rely on search alone.
- Weather and season: rain in one scene, drought in the next
- Time of day across parallel scenes that happen at once
- Objects that move, such as a letter in one hand and then in a drawer
- Names changed late in drafting, so old names survive in dialogue tags
- Ages that shift when a flashback is added or cut
For these, make a timeline row for each scene. Put the day, the time of day, and the season in separate columns. Read the columns from top to bottom. A gap or a jump shows you the error faster than rereading the whole chapter.
Mark intended changes so you do not fix them by mistake
Some differences are the point. A character lies about her age, and the reader is meant to catch the lie later. If you do not mark that, your next pass may fix the lie. Add a column called Intended to your fact list. Write yes, and note the chapter where the reader should notice. That row tells you to leave it alone.
| Fact | First seen | Repeated in | Status |
|---|---|---|---|
| Detective's eye color: green | Opening chapter | Late flashback, dialogue tag | Checked after revision |
| Storm date | Flood chapter | Epilogue news clip | Open: epilogue still says the old day |
| Car model in the chase | Chase chapter | Garage scene | Open: not checked yet |
| Sister's age: intended lie | Family dinner | Hospital scene | Intended: reader should catch it later |
Mistakes people make with continuity
- Fixing the chapter you are in and skipping the chapters that repeat the fact
- Trusting memory when a search takes a few seconds
- Editing one copy of a chapter while the export uses another
- Building a fact list so detailed that you stop updating it
- Treating a snapshot as the same thing as a full backup
- Reading the same draft in the same font and missing the same mistakes
Change how you read the draft
Fresh eyes help, and so does a different format. Print the chapter and read it with a pen. Change the font or the zoom. Keep the fact list on paper beside you. A new format can make your attention land on different words, which helps when you have read the same draft many times.
What to do next
Pick one chapter this week and build only its facts. Run the routine on that chapter and the chapters that share its characters. Then decide whether the list saves you time. Start with the facts that repeat across chapters, because one-time details rarely cause trouble.
If you want a voice helper while you work, try Lazur on one passage first at the download page. The trial needs no credit card. Read the pricing page before you commit. If you write in Pages or Word, the Pages guide for writers and the Word guide for writers cover setup for long drafts.
Faster with Lazur
Where Lazur helps with continuity errors across revised chapters
Hold ⌥ ⌘ and say what you want. Lazur sees your Word window. Lazur draws a circle and a label around the button or menu you need.
- 1
Hold ⌥⌘ and talk
- 2
Lazur draws a circle and a label around the button or menu you need.
- 3
You stay in Word. Nothing to copy into a chat window.
More things to say in Word
- “Where does this screen mention her eye color?”
- “What does this passage say about the timing of the storm?”
- “Hold fn and dictate a fact list row”
- “Draft a fact list row from my notes”
- “Walk me through turning on Track Changes”
- “Remind me to check the fact list tomorrow morning”
Free for 3 days, then $18/month. Download for Mac
You say“Where in this scene does she mention the blue car?”
Lazur · points at itLazur draws a circle and a label around the matching sentence on screen. It covers only the visible scene.
What writers say to Lazur for this
Each one is a single hold of ⌥ ⌘.
“Where does this screen mention her eye color?”
Lazur circles the spot on screen and adds a label, so you can check the wording yourself.
Points at it
“What does this passage say about the timing of the storm?”
Lazur answers out loud about what is on screen while you hold ⌥ ⌘. It covers the visible passage only.
Explains what's on screen
“Hold fn and dictate a fact list row”
Hold fn to dictate clean, formatted text at the cursor in any app. Personal dictionary entries keep names spelled correctly.
Types what you say
“Draft a fact list row from my notes”
Lazur drafts and types text. Check every row against the book yourself, because Lazur sees only what is on screen.
Drafts it
“Walk me through turning on Track Changes”
Lazur guides you one click at a time and waits for each click. It does not click for you.
Walks you through it
“Remind me to check the fact list tomorrow morning”
Timers, Apple Reminders, and Calendar events work by voice, so you can schedule each revision pass.
Handles the small stuff
A plan you can start this week
- Morning
Write the fact list
Open one table in Notion, Pages, Word, or Google Docs. List the facts a reader will track in the chapters you plan to revise. Keep it to facts you can actually check.
- Before
Save and log the change
Snapshot or copy the chapter first. Write one line for each change: the fact, the old version, and the new version. Then start the edit.
- Pass one
Read the changed chapter
Read with the fact list beside you. Stop at every name, date, object, and time reference. Mark each mismatch in the margin without fixing it yet.
- Pass two
Search every changed fact
Use ⌘F across the whole book for each changed fact and its synonyms. Fix each real mismatch, then update the matching fact list row.
- Week
Get a second reader
Send the fact list and the revised chapters to a critique partner. Ask them to flag mismatches and confusing timing. Keep their notes separate from your own.
- Close
Review and archive
Check the Intended column. Archive old copies in one folder and keep one current file. Note which step took longest so the next pass goes faster.
Questions people ask
Can Lazur find every continuity error in my manuscript?
No. Lazur looks at the screen only while you hold ⌥ ⌘, so it works on the passage in front of you. Use a fact list and a search for each changed fact to cover the whole book.
Is a continuity error the same as a typo?
No. A typo is a spelling or word mistake. A continuity error is a story fact that disagrees with another part of the book, such as an eye color or a date. Typo checks will not find that kind of mismatch. You need the fact list for it.
Do Scrivener snapshots count as backups?
No. A snapshot saves one document at one moment. Literature and Latte says snapshots are not full project backups. Keep your regular backups running too.
Does Word or Pages have a built-in continuity checker?
I did not verify a built-in continuity checker in Word or Pages, so plan on a manual pass with a fact list and search. Check the help menu in your copy for current features.
How long does a continuity pass take?
No study I found measures it. Time one chapter yourself, then estimate the rest of the book from that number.
Should I use AI to check my manuscript?
You can use it as a second reader for one passage at a time. Check every flag against the book yourself. Lazur sends audio and screenshots to AI providers to answer, and they are not stored. Content is never used to train AI models.
What if my manuscript is under a contract or NDA?
Read the contract and any confidentiality terms before you share text with an AI tool or a reader. Your publisher or agent sets the rules for that text, so follow them first.
Sources
- Writers and Authors, Occupational Outlook Handbook · U.S. Bureau of Labor Statistics · checked 2026-11-07
- Author incomes post small gains (Authors Guild survey coverage) · Publishers Weekly · checked 2026-11-07
- Errors in Proofreading · Raymond R. Panko (University of Hawaii) · checked 2026-11-07
- Organize Your Scrivener Project with the Corkboard · Literature & Latte · checked 2026-11-07
- Use Snapshots in Scrivener to Save Versions of Your Projects · Literature & Latte · checked 2026-11-07
- Scrivener Release Notes · Literature & Latte · checked 2026-11-07
Fix continuity errors across revised chapters with Lazur, free for 3 days
Hold a key and ask. Lazur sees your screen, points at the button and talks you through it, in any Mac app. No credit card.