PolyzPolyz
All articles

How to Write a Series Bible That Keeps You Consistent

A practical guide to building a series bible: track characters, timelines, world rules, and continuity so book three never contradicts book one. What to record and how.

Polyz Team5 min read

Somewhere in book three, you'll write that a character has green eyes. A reader who's been with you since book one will email to inform you they were brown. They'll be right, and they'll be a little disappointed, and that small crack of "the author doesn't remember their own world" is exactly the kind of thing that erodes trust in a series. The bigger the project, the more of these landmines you plant for your future self.

A series bible is the reference document that defuses them. It's the single source of truth for your characters, timeline, and world rules, the thing you check before you contradict yourself. Writers who skip it spend book four rereading book one to find out whether the war happened before or after the coronation. Here's how to build one that actually keeps you consistent, without becoming a second job.

What a series bible is (and isn't)

A series bible is a living reference, not a polished document. Nobody reads it for pleasure. Its only job is to answer, fast, questions like: How old is she now? What color is the magic? Did they already meet? When did the king die?

It is not your outline, not your worldbuilding daydream, and not a place to write beautiful prose about your invented religion. The instant it becomes precious, you'll stop updating it, and an out-of-date bible is worse than none because you'll trust it and be wrong. Keep it ugly, keep it current, keep it searchable.

The four things worth tracking

You can record a thousand things. Most of them you'll never look up. Focus your energy on the categories that actually cause contradictions.

1. Characters

The most-checked section, because characters accumulate facts across books. For each significant character, track the things readers will catch:

  • Physical details: eye color, hair, scars, height, distinguishing marks.
  • Age and birthday, so you can do the math in later books.
  • Relationships: who they're related to, allied with, in love with, betrayed by.
  • Key backstory facts that are now canon.
  • Voice notes: how they speak, verbal tics, what they'd never say. This is what stops a character drifting out of their established voice between books.
  • Their state at the end of each book (alive, injured, where they are, what they know).

That last one matters more than people expect. A character's knowledge is continuity too. Forgetting that someone doesn't yet know the secret is a classic series error.

2. Timeline

The silent killer of series consistency. As soon as you have more than one book, events have to line up: ages, seasons, how long journeys take, what happened in what order. Keep a master chronology, ideally with dates or at least relative ordering, covering both the on-page events and the backstory that predates the series.

A timeline catches the errors that are nearly invisible while writing: a character who'd be sixty by the math but acts thirty, a journey that took two days in book one and two weeks in book two, a child born before their parents met. Spreadsheet, list, whatever. Just keep it.

3. World rules

If you've built a system, magic, technology, politics, economics, you've made promises, and readers hold you to them. The rules of your world are a contract: establish that magic costs the user something, and you can't quietly let the hero cast for free in the finale because it's convenient. That's the exact move that makes readers feel cheated.

Record:

  • How the system works and, crucially, its limits and costs. The limits are what create tension; track them religiously.
  • Geography: places, distances, what's where.
  • Politics and factions: who rules, who's at war, who hates whom.
  • Names and spellings. Your invented names will drift if you don't pin them down. Decide it's "Kaer Thorne" and not "Kaerthorne," then never wonder again.

This connects to the craft of worldbuilding without the info-dump: the bible is where all that worldbuilding lives so it doesn't all spill onto the page at once. You record everything privately, then reveal a sliver.

4. Loose threads and promises

The most forward-looking section, and the one that separates a planned series from a flailing one. Track the questions you've raised but not answered, the foreshadowing you've planted, the Chekhov's guns hanging on the wall. "Mentioned a missing brother in chapter two of book one, still unresolved." "Hinted the amulet has a second power, haven't paid it off."

Without this list, you'll either forget your own setups (leaving readers feeling cheated) or accidentally contradict them. With it, you have a menu of promises to pay off in later books, which is half of what makes a series feel deliberately constructed rather than improvised.

How to keep it usable

A series bible only works if you actually maintain it, and most die from neglect. A few habits that keep it alive:

  • Update as you write, not after. Establish a new fact, log it immediately. Telling yourself you'll "do the bible later" means you won't, and you'll spend the gap reconstructing canon from memory.
  • Make it searchable. You're going to look things up constantly. Whatever holds it should let you find "eye color" in two seconds. A document you have to scroll through is a document you'll skip.
  • Keep one source of truth. Not three half-updated versions in different files. The bible's whole value is that it's the place you trust.
  • Record the current state and the history. You need both what's true now and how it got that way, because flashbacks and revelations reach back into the past.

This is the unglamorous infrastructure of a long project, and it's also where the right tooling earns its keep. A bible scattered across notebooks and stray documents will rot. A story bible that lives beside your manuscript and updates as you write is the difference between a reference you trust and one you abandon by book two. When the same system feeds your AI writing coach, you also get continuity help on demand: you can ask "did this character know about the betrayal at this point?" and get an answer grounded in your actual books rather than a guess.

Start it on book one, even if you don't have a series yet

The cruel irony is that the writers who most need a bible, debut authors who don't yet know their book will become a series, are the least likely to keep one. Then the publisher wants three more and they're reverse-engineering canon from a manuscript they barely remember writing.

So start a lightweight bible from the first draft of the first book, even if it's just a running list of names, ages, and rules. It costs almost nothing while you're drafting and saves you enormous pain later. If the series never happens, you've lost a little tidy note-taking. If it does, you've saved your future self from the green-eyes email.

Consistency is invisible when you get it right and glaring when you get it wrong. A bible is how you make it invisible, book after book, so readers stay inside the world instead of catching you forgetting it.


Polyz keeps an auto-updating story bible beside your manuscript and an AI writing coach that answers continuity questions from your actual books. Start a free trial.

Try Polyz free for 7 days

Every feature, all three Claude models, a generous monthly quota. Card required to start. Cancel before day 7 and you owe nothing.