Skip to content

Learn › Series Continuity › Encyclopedia › What Is a Story Bible?

Definitional Guide

What Is a Story Bible? (And Why Yours Should Build Itself)

Every series author keeps one, whether they admit it or not. The question is whether it keeps up with the manuscript, or quietly falls a book behind.

SO

By Scott Ohlund, Founder · Updated October 7, 2026 · 9 min read · Series Continuity

A story bible is the single, structured reference that records everything true about a work of fiction, its characters, places, factions, items, timeline, and the rules of its world, so that every chapter and every book stays consistent with what came before. For a series, it is the source of truth a continuity check is measured against.

In StoryHelm this living reference is called your Canon, and your Series Atlas gathers every book's Canon in one place.

Start one today: the free Series Bible Template (PDF).

What a story bible contains

A story bible is not a folder of notes or a pile of character interviews. It is a set of records, one per thing the reader is expected to remember, that a future chapter can be checked against. At minimum, a working bible tracks these layers:

C

CharactersNames and the spellings of them, eye and hair color, age across the timeline, scars and tells, relationships, allegiances, what they know and when they learned it, and how they speak.
P

PlacesGeography, distances and travel times, the layout of recurring settings, climate and season, and which locations are accessible to whom.
F

Factions & organizationsHouses, guilds, governments, families, their hierarchies, rivalries, founding events, and who currently leads them.
I

Items & artifactsHeirlooms, weapons, keys, letters, and anything with abilities or history, including who holds it now and how it changes hands.
E

Events & timelineThe chronological spine: when each event happened, in what order, how much time passed between scenes, and how those dates line up across books.
R

World rulesThe laws of the world the reader is asked to trust, magic costs, technology limits, social customs, and the consequences when a character breaks them.

The discipline is not in writing these down once. It is in keeping each record true to the latest draft, so that when you write Chapter 40 you can answer a simple question, does this contradict anything I have already promised the reader?

Story bible vs. series bible

The two terms get used interchangeably, and for a standalone novel there is no difference. The distinction matters the moment you write book two.

	Story bible	Series bible
Scope	One book. Everything true within a single manuscript.	The whole series. One shared record every book draws from and must not contradict.
Timeline	The events of this book, in order.	A continuous chronology stitched across every installment, including gaps between books.
Hardest job	Internal consistency, chapter to chapter.	Cross-book consistency, plus tracking what each character knew at the start of each book.
Fails when	A detail changes mid-manuscript and isn't reconciled.	A book-1 fact is quietly overwritten in book 4, and no single document caught the drift.
In StoryHelm	Your Canon for one project.	Your Series Atlas, every book's Canon in one place, with a cross-book check on character details and the dates two fully read books give the same event.

A series bible is a story bible that refuses to forget. Its real work is not the first book's facts, but the load of everything that has accumulated by the time the reader reaches the finale.

Why hand-maintained bibles break at book 3

Here is the uncomfortable part. The spreadsheet works beautifully for book one. It usually survives book two. By book three, for almost every series author, it has quietly stopped being true.

The contrarian thesis

A hand-maintained story bible is a second manuscript, written in parallel with the first, with none of the momentum and all of the discipline. The two drift apart not because authors are careless, but because the bible is updated by memory and the manuscript is updated by inspiration, and inspiration always wins.

The failure is structural, not personal. Three forces compound with every book:

Volume outruns memory. A trilogy can run to several hundred thousand words and hundreds of named entities. No author re-reads book one before drafting book three. The bible becomes the only record, and the only record is now out of date.

Edits skip the bible. You change a character's eye color in a revision pass, or move a scene three days earlier to fix pacing. The manuscript updates instantly. The bible updates only if you remember to open a second file and find the right row, which, mid-flow, you do not.

The bible is never checked. A spreadsheet is a place to look things up. It never looks back at you. Nothing in a static document notices that Chapter 31 says the manor burned down and Chapter 38 has a character walking its halls.

So the bible silently rots, and the contradictions it was meant to prevent ship to readers anyway. Here is an illustrative drift a hand-kept bible would never flag, because nobody re-read both chapters side by side:

Book 1, Ch. 7: Maren had her mother's gray eyes, the only thing of hers the fire had left him.

Book 3, Ch. 22: He would know those deep brown eyes anywhere, the same as the day he first carried her from the wreckage.

Two true-feeling sentences, written months apart. The bible said gray. Nobody opened it. That single unchecked row is where a series quietly loses a reader's trust.

How a bible can build itself from the manuscript

Watch the shortIf you must remember to update your bible, it's failing

If the problem is that the bible and the manuscript are maintained separately, the fix is to stop maintaining them separately. The bible should be derived from the writing, not kept alongside it. The manuscript is the source of truth; the bible is what you get when something reads the manuscript and structures what it finds.

That inverts the work. Instead of you transcribing facts into a second document, the document is generated from the words you already wrote, and re-generated every time the draft is read again. Practically, a self-building bible does four things:

1

Extracts entities from the proseIt reads the manuscript and pulls out the characters, places, factions, items, and events, with a few lines from the book that mention each one. You review; you don't transcribe.

2

Builds the records as structured factsGray eyes, the burned manor, the three-day journey, each becomes a recorded detail attached to its entity, kept with the book it came from.

3

Updates itself each time the draft is readRevise a scene and run a new read, and the records move with the prose, while any detail you entered or confirmed stays put. Each read brings the bible back in line with the latest words.

4

Checks new chapters against itselfBecause the facts are on record, a later chapter that says "brown eyes" can be measured against the established "gray," and the contradiction surfaced before the reader ever sees it.

Note what this does not do. It writes no sentence of your book, names no character, and decides no plot point. It reads the words you already wrote and gives them back as a structure you can trust, and check the next chapter against.

How StoryHelm checks this

StoryHelm builds your Canon directly from the manuscript. It reads the prose you wrote and structures it into characters, places, factions, items, and events, each entry linked to a few sentences from your book that mention it. In a Full read, the Coherence Guardian checks every chapter against that Canon and flags trait, timeline, and other contradictions within the book before they reach a reader. Save a scene in StoryHelm's Scene Editor and a quick check also looks it over for misspelled names. The Canon grows with each read of your book instead of falling a book behind it.

Related terms

Each of these has a full entry in the continuity encyclopedia.

Canon: The structured single source of truth for one project: characters, places, factions, items, and events, built from the manuscript.
Series Atlas: Every book's Canon gathered in one place, the series-bible form of a story bible, with a cross-book check on character details and the dates two fully read books give the same event.
Coherence Guardian: Continuity checks that flag trait, timeline, place, and other contradictions within a book against its Canon each time you run a Full read.
Continuity: The property of a series staying true to its own established facts, chapter to chapter and book to book.
Story Elements: The process of scanning raw notes you paste in for names and suggesting each as an entry, with the sentence it came from, for you to approve one by one.
World Rules: The internal laws of a fictional world, magic costs, technology limits, social customs, that the reader is asked to trust.

Keep reading

Canon & Story Bible

Series Bible Software That Builds From Your Books

A canon for each book, gathered in the Series Atlas and exportable as PDF, DOCX or Markdown.

Series Continuity

The complete guide to keeping a multi-book series true to its own facts, chapter to chapter and book to book.

Continuity Encyclopedia

Full entries for Canon, Series Atlas, Coherence Guardian, and every term in the continuity vocabulary.

What Is a Continuity Error?

The kinds of contradictions that break a reader's trust, and why they slip past a hand-kept bible.

How to Keep a Series Consistent

A practical workflow for catching drift before it reaches readers, across every book in the series.

Stop Maintaining Two Manuscripts

Get the story bible that builds itself from your prose.

Bring in your manuscript and StoryHelm reads it, structures its characters, places, and rules into your Canon, and links each entry to sentences in your book that mention it. No second file to keep true, no row to forget. Because the bible is built from the words you wrote, each read brings it up to date, and gray eyes that turn brown can be flagged here, not in a one-star review after the box set ships.

Get the free Self-Audit

Free 12-check PDF with your welcome email · Founding seat included · It never writes your prose