How to Build a Series Bible That You Actually Keep Updated

Somewhere in book three, a reader emails to tell you that Maren's eyes were grey in book one and are green now. Then someone points out that the journey from the capital took two days in the first novel and a week in the third. Then you realise you have spelled your own invented city two different ways across four hundred pages.

Continuity errors are not a sign of carelessness. They are the predictable result of holding a quarter of a million words in your head across three or four years. Every long-running series writer hits this wall, and the tool that gets them past it is a series bible: a single reference document recording what is true in your world, so that you look things up instead of remembering them.

This guide covers what actually belongs in one, how to build it without stalling the writing, the specific entries that prevent the most common errors, how to retrofit one to a series already in progress, and how to keep it current when you are deep in a draft and least inclined to.

What a series bible is for

It is worth being precise, because the term gets used for two different things and only one of them is worth your time.

A series bible is a reference, not a plan. It records what you have already established and published, so that future books stay consistent with it. It is descriptive. Outlines, plot plans and future-book ideas are a different document with a different job, and mixing them is the main reason series bibles get abandoned: the moment the file contains speculation, you stop trusting it as a record of fact.

Keep them separate. The bible answers "what is true?" The plan answers "what happens next?" Only the first one needs to be authoritative.

The second thing to understand is that a bible earns its keep in three distinct ways, and only the first is obvious:

• Continuity. The stated reason. It prevents the grey-to-green eyes problem.
• Speed. The underrated reason. Not having to stop and search three manuscripts for a character's brother's name is worth more writing hours over a series than the bible costs to maintain.
• Delegation. The reason that matters commercially. A bible is what lets an editor, a proofreader, a cover designer, an audiobook narrator or a translator work on your series without asking you forty questions, and it is what makes a boxed set, a spin-off or a co-written entry possible at all.

What goes in it

The temptation is to record everything. Resist it: an exhaustive bible is one nobody updates. Record what you will need to look up, which in practice means anything a reader could catch you contradicting.

Characters

One entry per named character, however minor. Minor characters cause more errors than major ones, precisely because you do not remember them.

• Full name, spelling, and any nicknames or titles used, plus who uses which
• Age, and the book or date it applies to
• Physical description: the handful of details you actually put on the page
• Family and relationships, including who knows whom and how
• Occupation, skills, and anything established they cannot do
• Speech habits: characteristic phrases, dialect choices, level of formality
• First appearance, by book and chapter
• What they know and when they learned it. The single most valuable field in the entire document, and the one most often missing

That last item is the difference between a bible that prevents plot holes and one that only prevents cosmetic errors. Most serious continuity failures in a series are knowledge failures: a character acting on information they have not yet been given, or being surprised by something they were told two books ago.

Places

Names and spellings, geography and distances, travel times between them, notable locations within them, climate and seasons, and who lives where. If you have invented a map, the bible is where the canonical version lives.

Timeline

The most useful single page in the document. A chronological list of events with dates, covering both what happens on the page and what happened before the series began. Include character ages at each point, because age arithmetic across a multi-year series is where a great many errors hide.

Two practical tips. Record the in-world date of every chapter opening, even approximately. And note the gaps between books explicitly, since "two years later" in a blurb has to square with everyone's ages.

Rules of the world

For speculative fiction this is the section that matters most, but every genre has a version of it. What the magic can and cannot do, what it costs, who can use it. How the technology works and what its limits are. Which institutions hold power and how. For contemporary fiction: how the police procedure works in your jurisdiction, what the firm's internal hierarchy is, which details you have deliberately fictionalised.

The critical entries here are the limits. Readers forgive a magic system they do not fully understand; they do not forgive one that solves a problem in book three which it could not solve in book one.

Style sheet

Strictly a separate thing from the bible, and just as important. Invented words and their spellings, capitalisation conventions, whether your dragons are Dragons, how you render thoughts, your serial comma policy, numbers and dates, dialect spellings. This is the document your copyeditor will ask for first, and having one materially reduces what a copyedit costs.

Objects and plot devices

Anything that recurs: a weapon, a letter, an heirloom, a scar. Where it is now, who has seen it, what it does.

Building one without stalling the book

The failure mode here is real: authors decide to build a bible, spend three weeks on it, produce a beautiful document, and write nothing. A bible is infrastructure, and infrastructure should be built in the cheapest way that works.

Start it at the end of book one, not the start

Before you have written a book, you do not know which details will recur, so anything you record is speculation. After the first draft, you know exactly what you established. One focused pass through the finished manuscript produces a better bible in a day than three weeks of pre-planning.

Capture as you go, organise later

While drafting, keep a running note of every fact you invent: a name, a distance, a date, a rule. Do not stop to categorise it. A messy chronological list of established facts is genuinely useful; a beautifully organised document you stopped updating in chapter nine is not.

Keep it where the writing is

The single biggest predictor of whether a bible stays current is whether checking it requires leaving your manuscript. A bible in a different application, behind a different login, will be consulted for the first month and then quietly abandoned. Keep it in the same workspace as the book: a dedicated section, a set of notes attached to the project, or a document that opens beside the draft.

Write entries for your future self

"Maren, 34, grey eyes" is less useful than "Maren, 34 in book one (born 1189). Grey eyes, described twice: ch.2 and ch.19." Recording where something was established lets you verify it and, when you need to, retcon it deliberately rather than by accident.

Retrofitting a bible to a series in progress

Most authors come to this after two or three books are already out, which is harder but entirely doable in a couple of focused days. Work in this order.

• Pass one, names. Read each published book and list every proper noun: people, places, organisations, invented terms. Do not describe anything yet. This pass alone usually finds two or three spelling inconsistencies.
• Pass two, the timeline. Go chapter by chapter recording when each is set and what happens. This is the pass that finds the real problems.
• Pass three, descriptions. Fill in physical details, relationships and world rules, noting the chapter each came from.
• Pass four, contradictions. Now list everything that does not reconcile, and decide for each: correct it in a revised edition, or accept it as canon and write around it going forward.

Print books already sold cannot be changed, but ebooks can be updated at any time and print-on-demand interiors can be revised. Fixing a genuine error in a revised edition is normal and unremarkable. What you should not do is quietly change something a reader has already noticed and discussed, because that generates more attention than the error did.

Two shortcuts worth knowing. A full-text search across your manuscripts finds most spelling inconsistencies in minutes if you search for near-miss variants. And your most engaged readers frequently maintain wikis and continuity threads of their own, which are an excellent cross-check on your own work.

Where to keep it

There is no single right tool, but the trade-offs are consistent and worth understanding before you commit, because migrating a bible later is tedious enough that most people simply do not.

• A spreadsheet. Unbeatable for characters and timelines, because you can sort and filter. One tab per category. Weak for anything needing paragraphs, and unpleasant to read. Best if your series is character-heavy and your continuity problems are factual rather than conceptual.
• A single long document. The lowest-friction option and therefore the one most likely to stay current. Use headings and rely on search rather than structure. Gets unwieldy past roughly twenty thousand words, which for most series is book four or five.
• A personal wiki or linked-notes app. The most powerful, because entries link to each other the way your world does. Also the most likely to become a hobby that replaces writing. Choose this only if you already think in links.
• Notes attached to the manuscript. The highest-adherence option, because consulting it costs nothing and updating it happens where you already are. Less good for a global view, so it pairs well with a single summary document.

Two rules regardless of tool. Keep it in a plain, exportable format, because a bible locked inside an application you stop paying for is a bible you have lost. And keep exactly one canonical copy: the moment there are two, neither is trustworthy.

What changes by series type

The right bible for a trilogy is not the right bible for an eighteen-book cosy mystery series, and building the wrong one wastes effort in both directions.

A planned trilogy

You largely know the shape already, so the bible is mostly a timeline and a character sheet. Keep it light. The continuity window is short and you will hold most of it in your head. The highest-value entry is the record of what each character knows, since a trilogy usually turns on revelation.

A long-running series

This is where a bible stops being optional. With many books over many years, you will not remember minor characters, and readers who have read all of them will. Invest in the names list and the timeline above everything else, and version entries by book so character change is visible rather than flattened.

A shared world with standalones

Each book stands alone but the world persists. The world rules and the places sections carry the weight here, and the character sheets matter less. The thing to guard is the world's internal logic, because readers coming to book six first will judge it against book two if they read that next.

A co-written or ghostwritten series

The bible stops being a convenience and becomes the contract. Anyone writing in your world works from it, so it must be complete enough that a competent writer could produce a consistent book without asking you. Budget real time for this. It is also worth agreeing explicitly who may update the bible, because an unmanaged canon document with multiple editors drifts fast. Our guide to co-writing agreements covers the ownership side, which matters here: characters and worlds are assets, and who controls them should be in writing.

Keeping it current

A bible that is out of date is worse than none, because you will trust it. Three habits keep it honest.

Update at chapter end, not scene end. Stopping mid-scene to record a fact breaks the writing. Finishing a chapter and spending two minutes adding what it established does not.

Do a reconciliation pass after every draft. Between finishing a draft and sending it to an editor, read the bible against the manuscript. This is also an excellent structural check in its own right, because facts you invented and then quietly ignored are usually threads you meant to pull.

Version it by book. Note which entries were true as of which book. Characters change, and a bible that flattens a character's arc into one description loses the information you actually need.

A minimum viable bible

If the full version feels like too much, build this instead. It takes an afternoon and prevents most of what readers actually catch.

• A names list. Every proper noun with its canonical spelling.
• A one-line-per-character sheet. Name, age, relationship to the protagonist, one physical detail, first appearance.
• A timeline. One line per chapter: when it is set, what changes.
• A rules list. Five to ten lines on what your world does and does not permit.
• A style sheet. Invented words, capitalisation, and your house punctuation choices.

Five short documents. Everything else is refinement, and refinement can wait until you need it.

The short version

A series bible records what is true, not what you plan; keep the two documents separate or you will stop trusting the first. Start it after book one rather than before, when you know what actually recurs. The highest-value entries are the timeline and the record of what each character knows and when they learned it, because knowledge errors are the ones that break plots rather than just descriptions. Keep it beside the manuscript, update it at chapter ends, and note where each fact was established so you can verify it later. And if the full version feels like a project, build the five-document minimum in an afternoon instead, because an imperfect bible you keep current beats a thorough one you abandon.