How to keep continuity in a long novel

Why does continuity slip in a long novel?

Nobody loses track of a heroine’s hair color on purpose. It happens because a novel gets written over months or years, in hundreds of sittings, by a person whose memory is busy with harder things: the shape of the second act, the line of dialogue that won’t sit right, the subplot that might have to go. Chapter 2 was written last spring. Chapter 19 was written at midnight last Tuesday. The two have never met.

Revision makes it worse, not better. You cut the scene where Oren loses his ship and forget that chapter 14 still mentions the loss. You rename a city and miss three of the forty mentions.

Readers, meanwhile, are very good at noticing. They read your book in a week, so details you set down a year apart sit side by side in their heads. The goal of any continuity process is simple to state: give your memory the same advantage the reader’s has.

What kinds of continuity errors are there?

Most slips fall into a handful of families. Knowing which one you’re hunting makes the hunt faster.

Some of these are pure memory problems (attributes, names). Some are arithmetic (timeline). Lifecycle errors are the most embarrassing, because they’re the easiest for a reader to spot. Dead is a yes-or-no question.

How do you check continuity by hand?

Writers and editors kept long books straight for a long time before software came along. The old tools still work.

Keep a style sheet

Copyeditors keep a style sheet for every book: how names are spelled, which words are capitalized, how numbers are written, and a running list of character details. Start your own on day one. Keep it as a plain list, alphabetical by name, with a chapter number beside every entry. The chapter number is what turns a memory into evidence.

Keep a story bible, if it helps

A story bible is a bigger reference: characters, places, history, and the rules of the world. It earns its keep for series, shared worlds, and anything with a magic system. Keep it lean; it exists to serve the draft. (There’s more on that in Do you need a story bible?)

Make a scene list

One line per scene: chapter, point-of-view character, where it happens, when it happens, and who’s present. Timeline errors show up here, because you can see the days side by side. Add a column for who is alive.

Run search passes

Before a draft goes out, search for every name, alias, and plausible misspelling. Search for colors near character names. Search for “the next morning” and “that night” and check each one against your scene list. It’s tedious, and it works.

Ask beta readers specific questions

Beta readers catch what you can no longer see, but “Any continuity problems?” mostly gets a shrug. Ask instead: “Did anything about timing or travel feel off?” “Did anyone seem to know something they shouldn’t?” “Did you ever lose track of who was in the room?”

When should you check for continuity errors?

Not while you’re drafting, if checking slows you down. A first draft’s job is to exist, and stopping every paragraph to confirm an eye color is a reliable way to lose a scene. Plenty of writers keep a running “verify later” note and push on.

The best moments to check are at the seams of the work:

• After a draft. Build or update the style sheet from what the pages actually say, not what you remember them saying.
• After cutting or moving scenes. Recheck the scene list and every reference to what you cut. Moving scenes is the riskiest edit of all; a reordered book can quietly put a funeral before a death.
• Before it goes out. Run your search passes before the manuscript reaches beta readers, an editor, or an agent.

What does it mean to settle a fact as canon?

All of those methods share one move: deciding that a detail is fixed, and writing it down somewhere other than the manuscript. That’s what canon means here. Not “everything in the book,” but the details you’ve decided are true.

The difference matters. A draft is full of details nobody has decided yet. Mira’s hair might be auburn only because you needed an adjective at one in the morning. Settling it is a separate act: “Yes. Auburn. That’s her.” Once a detail is settled, a later page that disagrees is a question worth asking. Before it’s settled, it’s just a draft being a draft.

A tool can only help once you’ve made that move. In Asten’s canon, a fact is an entity, a property, and a value (Mira · hair · auburn) with a status. Only confirmed facts produce hard contradictions, so half-formed ideas don’t start arguing with you. A fact can also carry a valid-from and a valid-to, which is how you record a change, like a dye job or a promotion, rather than a mistake. And when you change your mind about the record, you mark the old fact contested or deprecated, and it stops arguing.

What does a continuity check look like in practice?

Take the two classic slips from our running example.

Mira’s hair

In chapter 2 you settled Mira’s hair as auburn. Seventeen chapters and several months later, you write:

She pushed her black hair out of her eyes and looked down at the harbor.Chapter 19, draft

Asten’s compiler weighs the page against the record and marks it in red:

The mark doesn’t fix anything. It names the rule, the sentence, and the settled fact, and leaves you the choice. Keep my sentence if chapter 19 is right and you’ll revisit chapter 2. Retire “auburn” if black is the new truth. Add an event if Mira dyed her hair and the story should show it. Or suppress the mark with a reason; the suppression is saved with the project, so it won’t come back on the next pass.

Captain Oren’s death

Oren dies in chapter 9, and you settled it. In chapter 14, a scene beat has him on the quay, giving orders.

Maybe chapter 14 is a memory and should read like one. Maybe someone else gives the order. Maybe Oren isn’t as dead as everyone thinks, and that’s the twist, in which case you silence the rule for him and move on. The attribute check is always on. The lifecycle check lives in the Lifecycle method pack, which is on by default and can be turned off.

What can’t a continuity checker catch?

Be wary of any tool that promises to catch everything. Asten doesn’t. It reads only plain attributes from your prose, such as hair color, age, or whether someone is alive, and only when a name is in the same sentence; a pronoun on its own is not weighed, and what it reads is never stored as a fact. Travel checks work only along routes you declare with a travel time. Name drift is still partly a job for your search passes, though Asten flags names that aren’t in the cast and names that are easy to confuse, and giving an entity its aliases means “the Captain” and Oren are recorded as the same person.

And no checker can tell you whether a contradiction is a mistake, a lie a character tells, or a clue you planted. That judgment is the writing. A good process (a style sheet, a scene list, a handful of settled facts, and something to do the comparing) just makes sure you get to exercise it before your readers do.