What Is a Series Bible — and Why Your AI Editor Needs One

If you write a standalone novel, you can hold most of the important facts in your head. Character names, hair colours, the order of events, who knows what and when — it is all in a single document. You can check it yourself.

Write a series, and that calculation changes completely.

By book three, you have established hundreds of facts: a character's age in year one, a political system's rules, a magic system's limits, the exact phrasing of a prophecy, how long it takes to ride between two cities. Each new chapter you write has to be consistent with all of them — not just the facts you remember clearly, but the ones you committed to three years ago in a scene you have since forgotten.

This is what a series bible is for. And if you use AI tools to review your manuscripts, it is also why those tools need access to yours.

What is a series bible?

A series bible (sometimes called a story bible, world bible, or continuity document) is a living reference file that records every established fact in your fictional world.

It is not an outline. It is not a synopsis. It is not your notes-to-self. It is the canonical record of what is already true in your story — the facts that are now fixed, because a reader has seen them on the page.

The term comes from television. Showrunners use series bibles to keep writing rooms consistent across seasons and episodes. When you have twelve writers working on the same show, you need a shared ground truth. Fiction authors face the same problem when they work across multiple books over multiple years — just without the writing room.

What goes in a series bible?

There is no single standard format. What matters is that it captures the facts most likely to create continuity errors if forgotten or contradicted.

Most useful series bibles include:

Characters

Full names (including titles, nicknames, and name changes)
Ages at a fixed reference point, and how they change across books
Physical descriptions (height, eye colour, distinguishing features)
Abilities, skills, limitations — especially anything established as a hard rule
Relationships to other characters, and how those relationships evolve
Key backstory facts that have been revealed on the page

Timeline

A chronology of major events, anchored to whatever calendar system your world uses
How much time passes between chapters, and between books
Characters' ages at key events, cross-referenced with the character section

World-building

The rules of your magic system, technology, or unusual physics — especially the limits
Geography: distances, travel times, borders, place names
Political systems, factions, power structures
Languages, naming conventions, cultural rules that appear consistently

Canon events

Anything that has happened on the page that cannot be undone
Secrets that have been revealed (even if only to the reader)
Deaths, betrayals, alliances, promises

Terminology

Invented words and their precise meanings
Titles, ranks, proper nouns — especially ones that are easy to misspell inconsistently

Why continuity errors happen even to careful writers

The honest answer is that they happen because the human brain is not a database.

You remember the emotionally significant moments clearly. You remember the scenes you rewrote six times. What fades are the incidental facts — the detail you threw in on page 47 of book two that felt small at the time but now constrains what you can do in book four.

A reader who loved your series enough to read four books has a better memory of your world than you do. They notice when a character who lost three fingers in book one is described gripping a sword normally in book three. They notice when the journey that took twelve days in the first book takes four in the third. They notice the eye colour that changed.

These are not catastrophic failures. But they erode trust. The reader's relationship with your world depends on believing that the world is consistent — that the author is in control of it. Every error is a small signal that they are not.

A series bible does not prevent these errors by magic. It prevents them by giving you somewhere to look before you commit a new fact to the page.

How a series bible changes the revision process

Without a series bible, continuity checking is manual and unreliable. It means searching your own manuscripts for a character name, hoping you remember which book the relevant fact appeared in, cross-referencing across hundreds of thousands of words.

Most authors do not do this rigorously on every draft. There is not enough time, and human memory fills in gaps with what feels right rather than what is accurate.

With a series bible, the process becomes a reference task. You write a scene. You check the bible. You confirm or correct. It is still time-consuming, but it is bounded — you are checking against a single document rather than searching across an entire series.

The series bible also makes collaboration possible. If you work with a developmental editor, a writing assistant, or a continuity reader, the bible is what you hand them. It is the shared ground truth.

Why AI editorial tools need your series bible

This is where series bibles become critical for anyone using AI manuscript review tools.

General AI tools — large language models used directly — have no memory of your series. If you paste a chapter into ChatGPT and ask for feedback, the model has no idea that the character's name was spelled differently in book one, that the city was established as three days' ride from the capital, or that the magic system explicitly cannot do what your protagonist just did.

It will not catch those errors. It cannot. It has no access to your established canon.

AI editorial tools that offer series continuity checking work differently. They read your new chapter alongside your series bible, simultaneously, using both as context for the review. The continuity agent is not guessing about your world — it is checking your new chapter against the specific facts you have documented.

This is what Editorial Conductor's Series Continuity Keeper agent does. Aven, the continuity lead, reads your chapter and your bible together, looking for contradictions: an age that does not match the timeline, a place name spelled differently from how it appears in your established canon, a rule broken that your world has previously defined as unbreakable.

Without your bible, Aven has nothing to check against. The continuity pass becomes meaningless — it can only flag internal inconsistencies within the chapter itself, not contradictions with your established series facts. That is a significantly weaker check.

The quality of your continuity review is directly proportional to the quality of your series bible.

What makes a series bible useful (versus one that sits unused)

A series bible that is comprehensive but never maintained becomes a liability. It records what was true in draft one, and then diverges from what is true in the published books, creating its own source of confusion.

A few principles for keeping it useful:

Update it after every draft, not before. The bible records what is true on the published page, not what you intend to write. Update it after you finalise a book, not while you are drafting.

Be specific, not vague. "Elara has dark hair" is weak. "Elara has black hair, described in book one as 'the colour of a starless sky', cropped short after chapter 12 of book two following the Siege of Varath." is useful.

Record limits, not just facts. The limits of your systems — what your magic cannot do, what your technology has not achieved, what your political structure prevents — are often more important than the facts themselves. They are what constrains future plot.

Flag the things you are not sure about. If you cannot remember whether you established something as fact or only as rumour, note the uncertainty. That uncertainty is information.

Keep it in a format you can upload. For any AI continuity checking tool, you need your bible in a format the tool can read — typically a Word document or plain text file. A bible that lives in a dozen scattered notes apps is not useful here.

Do standalone novels need a series bible?

No. A standalone novel has all its facts in one document. The consistency check is manageable by a careful human reader.

But if you think there is any chance you will return to the world — a sequel, a prequel, a companion novel — start the bible when you finish the first book. It is much easier to build from fresh memory immediately after finishing than to reconstruct it years later when the series has grown.

Starting from nothing: a practical first pass

If you have a series in progress and no bible, here is the fastest way to build a first version:

Take your most recent completed manuscript.
Read through it with a document open beside it.
Every time you encounter an established fact — a character detail, a date, a place, a rule — add it to the document under the relevant category.
Do the same for each previous book, working backwards.
When you find contradictions between books, decide which version is canonical and note the discrepancy.

This will take time. A full series might take several days. But the resulting document is worth every hour — it is the foundation that makes all future books easier to write and easier to check.

Once you have it, keep it updated. Feed it to your AI editorial tools. Let the continuity agent read against it before you read against it yourself.

The series bible does not replace your judgment as a writer. It gives your judgment — and your AI tools — something solid to work with.