Building a Story Bible That Survives a Series
A single book has a memory you can hold in your head. A six-book series does not. The story bible is the discipline that keeps Book 1's eye color, Book 3's broken promise, and Book 5's payoff agreeing with each other, long after you've forgotten you wrote them.
A story bible is the structured, single source of truth for everything your series knows about itself: every character, place, faction, item, and event, plus the rules and relationships that bind them. In StoryHelm this record is called the Canon, and across a multi-book series it becomes the Series Atlas: one continuity shared by every book you write.
Why a series needs more than notes
Most authors start a series with the best of intentions: a Scrivener folder, a spreadsheet of names, a notebook with a hand-drawn map. It works fine for Book 1. By Book 3, the notes have drifted out of sync with the manuscripts. A character who died in chapter nine of Book 2 sends a letter in Book 4. A coastal kingdom quietly becomes landlocked. The notebook says one thing; the prose says another; the reader catches both.
The problem is not discipline. A story bible maintained by hand is a copy of the truth, and a copy drifts the moment you stop updating it. The version that matters is the one in your manuscripts, so the bible has to stay tethered to what you actually wrote, not to what you remember writing.
That tether is the whole idea behind a story bible that builds itself. Instead of you transcribing facts into a reference document, the reference document is read back out of the prose: characters, places, and events extracted from the text, organized into Canon, and re-checked every time you revise. Change a fact in chapter twelve and the bible updates with it, instead of preserving the old version you forgot to correct.
When the bible assembles itself, StoryHelm reads and extracts what already exists in your manuscript into structured Canon. It does not draft characters, invent backstory, or generate prose. You write the series; StoryHelm keeps it consistent.
Read the cluster
Five pieces: what a story bible is, how it differs from a series bible, a template you can fill in by hand, and the two ways StoryHelm builds one for you, from raw notes or from a finished manuscript.
What Is a Story Bible? (And Why Yours Should Build Itself)
The classic story bible is a binder you maintain by hand, and abandon by Book 3. We break down the four jobs a story bible actually has to do (remember, organize, cross-reference, and catch contradictions) and why a hand-kept binder fails at the last one. Then we show the modern alternative: a Canon that is extracted from your prose and re-verified on every revision, so it stays current as the book changes.
Read articleStory Bible vs Series Bible
The two terms get used interchangeably, but the distinction matters once you have more than one book. A story bible governs the canon of a single work. A series bible governs the canon shared across every book: the rules, timelines, and entities that must stay consistent from Book 1 to the finale. This piece draws the line clearly, with examples of facts that live in each.
Read articleSeries Bible Template
A ready-to-use, genre-neutral series bible template covering characters, places, factions, items, events, magic/tech rules, and a master timeline. These are the same five entity types StoryHelm tracks. Use it to seed your canon by hand, or as a checklist for what a complete series bible should contain before Book 2.
Read articleFrom Notes to Canon (Story Elements)
You already have the raw material: a paragraph naming the three rival houses, a line that says iron breaks the binding spell, a list of who holds the harbor in which year. Story Elements reads those unstructured notes and extracts the people, places, factions, items, and events into structured Canon entities you can review and confirm. No prose is generated; your notes are simply organized into the bible's schema.
Read articleHow to Turn a Manuscript Into a Story Bible: Automatically
Upload a finished book and StoryHelm reads the whole manuscript, extracts every named entity and event, and assembles a structured Canon you can browse, correct, and carry into the next book. The book becomes its own reference document.
Extraction is grounded in the text. Every entity in your Canon traces back to the passages it came from, so a drifted trait can be shown to you as the two sentences that disagree. Rather than assert the mismatch, StoryHelm hands you both lines and lets you decide which is canon.
Later book: “She turned, and her grey eyes were the color of the harbor at dawn.”
Story bible vs series bible: what lives where
| Fact about your world | Story bible (one book) | Series bible (Series Atlas) |
|---|---|---|
| A character's eye color, scar, and speech tics | Yes: stable within the book | Yes: must match across every book |
| A one-scene innkeeper who never returns | Yes | Optional: only if reused later |
| The rules of your magic / technology system | Often implicit | Yes: readers notice when the rules bend |
| The master chronology of dated events | Local timeline | Yes: one timeline spanning all books |
| A promise planted in Book 1, paid off in Book 5 | No: out of scope | Yes: the payoff has to survive the whole series |
| Faction allegiances that shift between books | Snapshot | Yes: tracked as evolving relationships |
In StoryHelm, a per-book story bible is your Canon for that project; the Series Atlas is the shared canon that all books in the series draw from and must agree with.
What a series-grade story bible contains
The five entities
- Characters: traits, arcs, relationships
- Places: geography, ownership, state changes
- Factions: allegiances, hierarchies
- Items: provenance, who holds them when
- Events: what happened, in what order
What links them together
- A master timeline across all books
- World rules (magic, tech, society)
- Relationships between entities
- Aliases & name variants, reconciled
- Setups & their payoffs, threaded
What keeps it accurate
- Every fact cited to a passage
- Re-verified on every revision
- Contradictions surfaced, not buried
- Shared by all books, owned by you
- Editable: never auto-overwritten
Write in StoryHelm's editor or import your finished books, and it reads your bible across the whole series. Two systems do the work.
The structured single source of truth for one book (characters, places, factions, items, events), extracted from your manuscript or your notes, each entity traceable to the passages it came from.
The shared Canon and continuity across the whole series, so a fact established in Book 1 still holds in Book 6, and the Coherence Guardian flags the moment a revision breaks it.
Built on 41 analysis passes across 7 workflows, powered by Claude. You write the story; StoryHelm makes sure it holds together.
Look up a term while you read
Every concept in this guide has a plain-language entry in our glossary, the Continuity Encyclopedia. Definitions, examples, and how each one shows up in StoryHelm.
Turn your finished books into a bible that catches its own drift.
Bring in book one or all six. StoryHelm reads the prose, extracts every character, place, and event into a Canon that re-verifies itself on every revision, and points to the exact book and chapter where a fact stops agreeing. That is the slip a reader leaves a one-star review over, found before your box set ships, not after.
Get the free Self-Audit