Checklist: audit your manuscript's continuity before you submit

What is a continuity pass and when should you run it?

A continuity pass is a systematic read of the manuscript to verify that attributes, names, dates, relationships, places and objects stay coherent from first page to last. Run it after structural edits and before line editing, beta readers or submission: at that point the text is stable and mistakes are still cheap to fix.

Order matters. Audit continuity before you reshuffle chapters and you'll have to do it all again; audit after the line edit and every fix reopens polished prose. And don't try to watch all eight dimensions at once — attention is serial. Work the checklist section by section, one dimension per pass, the same way you'd approach character consistency in general.

1. Physical attributes and age arithmetic

The first thing readers notice: eyes that change colour, a scar that migrates to the other cheek.

• Eyes, hair, skin: search (Ctrl+F) for "eyes", "gaze", "hair" and check every hit against the character's sheet. The single highest-yield search on this list.
• Scars, tattoos, marks: search "scar", "tattoo", "birthmark". Verify which side of the body each mark sits on — and that it never appears before the scene where it's acquired.
• Wounds and injuries: search "arm", "hand", "limp", "bandage". The wound in the left arm that later aches in the right is a classic.
• Age arithmetic: search "years old" and "birthday". If she was 34 in spring and the novel spans two years with an on-page birthday, the sums have to work.
• Relative physicality: who is taller than whom, who is left-handed. Established once, contradicted in the chapter-20 fight scene.

2. Names and spelling variants

• Spellings and accents: search each name in its plausible variants ("Elizabeth"/"Elisabeth", "Katharine"/"Katherine") and, for accented names, without the accent. Spellcheck won't protect proper nouns.
• Nicknames and pet names: list who calls whom what. If only Grandma says "Charlie-boy", the antagonist shouldn't suddenly say it too.
• Surnames: search them one by one; they're written least often and mutate most.
• Renamed minor characters: characters rebaptised mid-draft leave traces. Search the old name if you remember changing it — and if you don't remember, search both.

3. Timeline and chronology

The base tactic is a day ledger: a chapter → story-day table, built from the text's own markers.

• Days of the week: search "Monday", "Tuesday"… and "weekend". If the dinner-party Friday sits three "the next day"s after the accident's Monday, something is off.
• Declared jumps: search "the next day", "a week later", "two months", "that same night" and add them up in the ledger.
• Travel: do the journeys fit the time you give them? A six-hour drive can't fit inside one hour of plot.
• Pregnancies, seasons, holidays: a pregnancy runs about 40 weeks; Christmas doesn't fall in a northern-hemisphere August. Search "pregnant", "Christmas", "summer", "snow" and square the calendar.
• Ages against dates: cross this ledger with the arithmetic from section 1.

4. Knowledge state: who knows what, and when

The reveal audit. This is the hardest dimension to check with searches, because the error usually lives in a reaction, not a word.

• Secret inventory: list every secret or twist and pin down the exact scene where it's revealed, and to whom.
• Backward leaks: search each secret's key terms ("fire", "will", "sister") in the chapters before the reveal. Nobody should allude to it or react as if they already know.
• Witnesses: note who is present at each reveal. Anyone who learned it "second-hand" needs a plausible chain of transmission.
• Forward amnesia: the inverse error: someone who already knows acting surprised three chapters later.
• Deliberate exceptions: an unreliable narrator or a lying character breaks these rules on purpose. Mark it as intentional in your notes so you don't "fix" it by accident.

5. Relationship state, chapter by chapter

• A per-chapter map: for every pair of characters that matters, note their state per chapter: together, estranged, enemies, reconciled. Scenes must honour the state in force.
• Gestures and intimacy: the physical closeness and trust in each scene must match that chapter's state — not the previous draft's.
• Register shifts: how formally characters address each other is relationship state too. In Spanish, the move from usted to tú is a full-blown relationship event — see register in fiction; in English, watch the shift from "Mr Alvarez" to "Diego", and any unmotivated shift back.
• Terms of address: search "darling", "love", "sir", "Doctor". Address should evolve with the relationship, never contradict it.

6. Places and geography

• Floors and storeys: search "floor", "storey", "stairs", "attic". The two-storey house that grows a third is one of the errors readers cite most.
• Interior layout: the kitchen on the right of the hallway stays on the right; the bedroom window always faces the same courtyard. Sketch a quick floor plan if the house matters.
• Distances and journeys: "ten minutes on foot" in chapter 4 can't become "across town" in chapter 18. Cross-check with section 3.
• Place names: search every invented street, neighbourhood or town in its possible spellings, exactly like the names in section 2.

7. Objects: the Chekhov audit

If a rifle hangs on the wall in act one, it must fire in act three — and in between, it can't teleport.

• Inventory: list the objects with narrative weight (the letter, the ring, the key, the gun) and search each one. Reconstruct its life: appearance → use → fate.
• Vanishings: the object introduced with ceremony that's never mentioned again. Decide: it fires, or it's cut.
• Bilocations: the letter left in the drawer that turns up in a handbag three scenes later. Every move needs a scene, or at least a line.
• Physical state: broken/mended, full/empty, lost/found. The phone with a dead battery can't receive the call that resolves the climax.

8. Voice and register per character

• Verbal tics: search every catchphrase you've assigned and confirm only its owner uses it. A shared tic dissolves two voices into one.
• Language level: the character who'd never say "notwithstanding" doesn't say it in chapter 22 because you were writing formal that day. Reread their dialogue alone, in sequence.
• Swearing: who curses, how much, and with what. Search the strong ones and verify the speaker.
• Dialect and other languages: an accent, a regional variety or borrowed words assigned to one character must hold in every scene — or evolve for a reason the story tells.

How long does a manual continuity pass really take?

Honestly: a long time. Auditing isn't pleasure reading; with the checklist in hand you move at roughly 3,000–5,000 words per hour. For a 100,000-word manuscript that's 20–35 hours of audit reading alone, plus the search passes for each section and the day ledger. In practice: one to two weeks of real work.

And a single pass won't catch everything, because you can't watch eight dimensions at once. That's why the checklist is ordered: sections 1–2 are cheap searches worth doing first; chronology and knowledge state demand slow reading; voice demands rereading each character's dialogue in sequence. Budget separate passes — or accept that the only pass will be partial.

Tooling: from the big-bang pass to continuous checking

Everything above works in any editor with Ctrl+F. What genuinely makes it cheaper is keeping a story bible up to date: if eye colours, dates and each relationship's state live in one place, every check is a lookup instead of an excavation. Without a bible, half your audit time goes into reconstructing the canon you're about to audit.

The alternative to the big final pass is not accruing the debt at all: checking continuously. That's the approach behind Journzy, an AI writing studio that reads your manuscript against your story bible as you write and flags the contradiction the moment it appears — the eyes that change colour, the intimacy that doesn't match the chapter's relationship state, the register that slips back for no reason. The AI watches and suggests; it never writes your text, and every flag can be dismissed with "It's intentional", because unreliable narrators and deliberate breaks are your call. It's in private beta, with an invite waitlist. The checklist above still stands — it's exactly what a system like that checks for you at every sentence.