What Goes in a Series Bible (And What to Leave Out)

A series bible needs seven sections: characters (with aliases and relationships), locations, timeline, world rules, plot threads and reveals, per-character knowledge, and a retcon log. Everything else — aesthetic mood boards, unused backstory, research dumps — belongs somewhere, but not in the bible, because every page you add is a page you have to keep accurate across every future book.

That last clause is the whole game. A series bible isn’t judged by how complete it is on the day you build it; it’s judged by whether it’s still trustworthy in book four. Writers don’t abandon bibles because they’re lazy — they abandon them because the bible grew past what they could maintain, drifted out of date, and stopped being believable. So the design question isn’t “what could I record?” It’s “what can I afford to keep current?”

The seven sections that earn their maintenance cost

1. Characters — with aliases and relationships. The fact sheet everyone builds, plus the two fields everyone skips: every name a character is called in the text (nicknames, titles, how other characters refer to them in dialogue), and the relationship map as of each book. The relationship map, not just the relationships — who knows whom matters as much as who likes whom. The deeper treatment is in How to keep track of characters in a series.

2. Locations. Names, geography, travel times between them, and what’s been destroyed or changed. Travel times deserve their own line: “two days’ ride” in book one is a contract every later journey has to honor.

3. Timeline. Absolute dates if your story has them; relative ordering if it doesn’t. Include character ages at each major beat — age drift is one of the most-reported continuity errors in long series, partly because it requires arithmetic to catch.

4. World rules. Magic systems, technology limits, political structures, economics. Record the rule and the passage where it was established, because rules get established in dialogue, and dialogue is where you’ll later be tempted to bend them.

5. Plot threads and reveals. Every promise the text has made: the unexplained scar, the locked door, the prophecy at 40% volume. Series readers track these with terrifying accuracy. A thread list is also the cheapest defense against the saggy middle book — it’s an inventory of what’s still loaded.

6. Per-character knowledge. What each character knows, and as of when. This is the section almost no template includes and the one that powers everything readers love about series fiction: dramatic irony, slow reveals, secrets with timing. It’s also the hardest to maintain by hand, which is why it gets its own structural treatment in PlotLens.

7. The retcon log. When you deliberately change established canon — and across a long series you will — record what changed, when, and why. A retcon you logged is a decision; a retcon you didn’t is indistinguishable from an error, including to future-you.

What to leave out

Unused backstory. If it isn’t on the page yet, it isn’t canon yet — it’s a draft of canon. Keep it in your notes; promote it to the bible when the text commits to it. Bibles bloated with maybe-canon are the ones writers stop trusting, because they can’t remember which entries the reader has actually seen.

Research. Your folder of medieval metallurgy articles is valuable. It’s also not canon. The bible records what your story established about steel, not what’s true of steel.

Mood and aesthetics. Pinterest boards, playlists, character art — genuinely useful creative fuel, zero continuity value, and real maintenance noise when they’re interleaved with facts you need to verify under deadline.

The pattern: the bible is a record of commitments the text has made. Anything that isn’t a commitment dilutes it.

The maintenance rule that decides everything

Here’s the uncomfortable arithmetic. A trilogy with a mid-size cast generates roughly 2,000–4,000 discrete canonical facts — and every revision pass touches some of them. If your bible is hand-maintained, every revision creates silent drift between the manuscript and the record, and the drift compounds exactly when the series gets long enough to need the bible most. This decay curve is predictable enough that we wrote Why your story bible isn’t enough about it.

So adopt one rule before you build anything: decide, per section, whether it’s maintained by hand or derived from the manuscript. Sections 1–4 and 6 — the high-volume factual layers, including per-character knowledge — are exactly what tools can now extract from the prose automatically, with a citation for every fact, and re-derive after every revision so drift is structurally impossible. That’s the approach series bible software like PlotLens takes; section 6 especially, since per-character knowledge is the hardest section to maintain by hand and the one the belief-vs-fact model exists to derive. Sections 5 and 7 — threads and retcons — are editorial judgment, and they’re low-volume enough that hand-maintenance is genuinely fine.

Splitting the work this way turns the bible from a chore that loses to entropy into a small editorial habit plus an automated factual layer. The writers who keep shipping series tend to land on some version of that split, whatever tools they use.

If you want scaffolding to start from, the free character bible template covers section 1 in the structure described here. For the full series-scale picture — drafting cadence, multi-book arcs, and the infrastructure that decides whether book five ships — the pillar guide is Writing a Book Series: The Complete Guide.