How to keep a long series consistent

5 min read · Updated October 23, 2026

A long series stays consistent when every established fact lives somewhere other than your memory, tagged with the book and chapter it came from. That place is a series bible. It doesn't have to be elaborate, but it has to be the thing you check before you write "her brown eyes" in book five.

Single novels get away with memory because you wrote the whole thing in a year or two. A series spans five or ten years, several drafts per book, edits you've forgotten and, often, readers who know the earlier books better than you do. The longer the series, the more a bible matters.

What drifts between books

Some details are almost guaranteed to slip. Watch these first:

• Physical descriptions. Eye color, hair, height, scars, which hand someone uses. In The Ashen Crown, Kael Varn has "green eyes" in book one and "grey eyes" in book two. Each sentence is fine alone. Together they're the kind of thing readers post about.
• Names and spellings. A minor character spelled "Selwyn" in book one and "Selwin" in book three. Nicknames that change. Titles that get promoted or forgotten.
• Ages and dates. Ages that don't advance with the years between books, or events "ten years ago" that stay ten years ago.
• Who is alive. A dead character turning up at a council in the sequel. The Ashen Crown does this on purpose: Lord Aldric dies in book one, chapter one, and attends the Council of Varrow in book two.
• Who knows what. A character acting on a secret they haven't learned yet, or forgetting one they learned two books ago.
• Rules. Magic costs, technology limits, laws, travel times. If Emberfire burns away a memory with every use in book one, a knight can't use it freely in book four without a reason.
• Possessions. The sword that was broken, the ring that was given away, the horse that died.
• Geography. Which way the river runs, how far the cities are, what's north of what.

Most of these are small. Readers forgive one or two. What erodes trust is a pattern, and patterns come from never writing things down.

Record where each fact came from

The single most useful habit in a series bible is noting the source of every fact: book, chapter and, ideally, the exact words.

Without the source column, you'd have to reread to find out which one is canon. With it, you can see that green came first and is already in print, so book two needs to change.

Do the same for facts that change on purpose. If a character goes blind, record the old eye description with an end date and the new one with a start date. Then a later "contradiction" is clearly intentional.

Revisiting books you've already published

Most series bibles start late, after book two or three, when the author realizes they can't remember the name of the innkeeper. That's normal. You don't need to reread everything at once.

• Start with what the next book needs. List the characters, places and items that appear in the book you're writing now. Pull their facts from the earlier books first.
• Fill in as you go. Every time you check a detail in an old book, add it to the bible. After a book or two, most of what matters is there.
• Use your own back matter. Synopses, blurbs and outlines are quick ways to seed the major facts before you get to the detail.

For a step-by-step method, see building a story bible for a finished book. If you want help from an AI chatbot with the extraction, see using ChatGPT or Claude for a story bible.

Spoilers in a series bible

A series bible is full of spoilers by design. That's fine when only you read it. It becomes a problem when you share it.

• Mark secrets. In The Ashen Crown, Brother Tolan set the fire at Thornwatch. That's revealed in book two. Keep it in the bible, but mark it so you know not to let it slip into a book-one appendix or a reader-facing glossary.
• Record when the reader learns each thing. The chapter where a fact is revealed isn't always the chapter it's true from. Mara's father dies in chapter one; a reader learns why in book two.
• Separate the author's bible from anything readers see. A wiki, glossary or "story so far" page should only include what a reader has reached.

Co-writers, editors and assistants

When two or more people work on a series, consistency problems double. Each person carries a slightly different version of the world in their head.

• Keep one bible. Separate notes always diverge. One shared source of truth, with everyone reading and writing to it, is the only setup that holds.
• Track who changed what. When a fact changes, you want to know who changed it and why. A change history also makes it safe to let others edit, because a mistake can be undone.
• Agree on attribute names. "Eye color," "eyes" and "eye colour" are three entries to a search. Settle on a short list of labels early.
• Decide what's canon. Brainstormed ideas, drafts and cut material should be marked so nobody writes them into a book by accident.

A routine that keeps a series consistent

The bible only helps if it's current. A light routine works better than an annual overhaul:

1. Before you draft a book, read the entries for every character and place you expect to use.
2. After each chapter, add new names and any physical details, ages, dates or rules you stated.
3. Before you send a book to your editor, run a continuity pass against the bible. Check deaths, ages, travel and anything with a number in it.
4. After publication, fix the bible to match what was printed, not what you meant. The printed book is canon.

When a mistake is already in print

It happens to every series. Your options:

• Fix it quietly in a later edition or ebook update, if your publishing setup allows.
• Make it canon. If Kael's eyes changed from green to grey, maybe Emberfire did it. Record the explanation in the bible so it stays consistent from here on.
• Leave it. Not every slip needs an in-world reason. Pick the version you'll use going forward, record it, and move on.

Whatever you choose, write it down. The worst outcome is fixing the same mistake in different ways in two different books.

For the errors readers spot most often, see continuity errors readers notice.