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.
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 a series-wide one is your Series Atlas.
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:
-
CCharactersNames 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.
-
PPlacesGeography, distances and travel times, the layout of recurring settings, climate and season, and which locations are accessible to whom.
-
FFactions & organizationsHouses, guilds, governments, families, their hierarchies, rivalries, founding events, and who currently leads them.
-
IItems & artifactsHeirlooms, weapons, keys, letters, and anything with abilities or history, including who holds it now and how it changes hands.
-
EEvents & timelineThe chronological spine: when each event happened, in what order, how much time passed between scenes, and how those dates line up across books.
-
RWorld 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 canon 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, shared canon and continuity across the whole series. |
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.
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:
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:
Two true-feeling sentences, written months apart. The bible said grey. 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
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 you write more. Practically, a self-building bible does four things:
Note what this does not do. It writes no sentence, 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.
StoryHelm builds your Canon directly from the manuscript. Its Braindump reads the prose you wrote and structures it into characters, places, factions, items, and events, each fact tied back to the line that established it. As you draft, the Coherence Guardian measures new chapters against that Canon and flags name, trait, and timeline contradictions before they reach a reader. The Canon grows with your writing 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
- A shared Canon and continuity layer spanning every book in a series, the series-bible form of a story bible.
- Coherence Guardian
- Live continuity checks that flag name, trait, and timeline contradictions against the Canon as you write.
- Continuity
- The property of a series staying true to its own established facts, chapter to chapter and book to book.
- Braindump
- The process of turning raw notes and prose into structured Canon entities automatically.
- World Rules
- The internal laws of a fictional world, magic costs, technology limits, social customs, that the reader is asked to trust.
Keep reading
Series Continuity
The complete guide to keeping a multi-book series true to its own facts, chapter to chapter and book to book.
ReadContinuity Encyclopedia
Full entries for Canon, Series Atlas, Coherence Guardian, and every term in the continuity vocabulary.
ReadWhat Is a Continuity Error?
The kinds of contradictions that break a reader's trust, and why they slip past a hand-kept bible.
ReadHow to Keep a Series Consistent
A practical workflow for catching drift before it reaches readers, across every book in the series.
Read