How to Build a Story Bible: The Complete Guide (with Template)

What a story bible actually is

A story bible — sometimes called a world bible, series bible, or show bible — is the reference document that records the canonical facts of your story world and keeps everyone working on it aligned. It is not the manuscript, the script, or the design doc. It is the layer underneath them: the agreed-upon truth that every page, episode, or quest is written against.

The distinction matters because the bible does a job no draft can do. A draft tells the story. The bible answers questions about the story: How old is this character in season three? What does magic cost in this world? Who knows the secret, and since when? When two writers disagree about a detail, the bible is what they check — and if it is vague, missing, or contradictory, the disagreement ends up on the page instead.

The best working definition is functional: a story bible is whatever you would need to hand a brand-new collaborator so they could write a scene that does not break your world. If that handoff would leave them guessing, your bible has a gap.

Why every serialized story needs one

A standalone short story can live entirely in one writer's head. A serialized world cannot. The moment your story spans multiple books, a full season, or a team of contributors, the number of facts that have to stay consistent outgrows any single memory — and the cost of a contradiction climbs from a quick fix to a published mistake.

Consider the math. A modest world might have forty characters, a dozen rules, and a hundred events. Every one of those facts can potentially conflict with another: a character who dies in book two appearing in book three, a magic system that costs a memory in chapter one and nothing in chapter twenty, a timeline where someone is born after their own child. There are thousands of pairs of facts that have to agree, and no person can hold thousands of pairs in their head at once.

This is why continuity errors are so common in long-running series and why they tend to surface at the worst possible time — in a table read, in editing, or in a one-star review three books deep. The break almost never happens because someone was careless. It happens because the world got too big to track informally, and the bible was a passive record that stored facts but never checked whether they still agreed.

The story bible template: core sections

Every story bible, regardless of medium, is built from the same handful of sections. You do not need all of them on day one, but you do need a slot for each so facts land in a predictable place. Copy this structure as your starting template:

1. Premise & logline. One or two paragraphs: what the story is, its central conflict, and its tone. This is the anchor everything else serves. If a later decision contradicts the premise, the premise usually wins.

2. Characters. One entry per significant character: name, role, age or timeframe, defining traits, relationships, arc, and current status (alive, where, knows what). This is the section that grows fastest and breaks most often, so keep each entry's facts atomic and dated.

3. World rules & systems. The non-negotiable mechanics of your world — how magic or technology works and what it costs, what is physically possible, social and political structures, economies. These are the rules every scene must obey; vague rules produce contradictory scenes.

4. Timeline & history. Events in chronological order, including backstory that predates the story. This is where you catch age, sequence, and cause-and-effect errors. A real timeline (not a paragraph of prose) makes those errors visible at a glance.

5. Locations & setting. The places that recur, their relationships to each other, travel times and distances, and the rules specific to each. Geography errors — a journey that takes a day in one chapter and a week in another — hide here.

6. Plot threads & arcs. The ongoing tensions, mysteries, and unresolved questions, with their current state and where each was last touched. This section is what keeps a thread from being dropped or accidentally resolved twice.

7. Lore & background. Static world context that colors everything but does not, by itself, carry open tension — myths, cultural detail, names, terminology. Keep this separate from timeline events so dated happenings do not get buried as flavor.

8. Style & canon notes. Naming conventions, spellings, tone guardrails, and the explicit rulings you have made ("yes, this exception is canon now, and here is why"). This is the section that prevents the same argument from being re-litigated every month.

How to build a story bible step by step

Start with the premise and the rules, not the characters. Most people begin with characters because they are the most fun, but characters are constrained by the world's rules — write the rules first and the characters have firm ground to stand on. Pin down the premise, then the three or four load-bearing rules your world cannot violate.

Next, lay out the timeline before you write a single character entry. Even a rough sequence of major events gives every later fact a place to anchor. When you add a character, you can immediately place their birth, their key moments, and their current status against that timeline — and catch sequence errors before they calcify.

Then populate characters, locations, and threads, keeping every fact atomic. "Maren is Toval's older sister and was twelve when their village burned" is three checkable facts, not one paragraph. Atomic facts are what let you — or a tool — later detect that a different scene makes Maren younger than Toval.

Finally, stress-test before you write the story. Read the whole bible against itself and look for pairs of facts that cannot both be true. This is the step almost everyone skips, and it is the step that actually prevents continuity errors. Doing it while the world is still notes — instead of after a season is written — is the difference between a one-line edit and a rewrite.

Keeping the bible alive (and honest)

A story bible fails in one of two ways: it goes out of date, or it grows past the point where anyone can verify it still holds together. Both failures come from treating the bible as passive storage — a place you write things down and hope they stay consistent.

The out-of-date failure is a process problem. The bible has to be the place decisions are made, not a transcription you update later if you remember. If a ruling happens in the room or in your head and only reaches the bible days later, the bible is always trailing the truth, and collaborators are reading an old copy. One shared source of truth that everyone edits directly removes this entire category of drift.

The grows-past-verification failure is the deeper one. Past a few dozen interacting facts, no human can confirm by hand that the whole world is still consistent — there are too many pairs to check. The only thing that scales is a bible that can read itself: a structure where each fact knows what it is (character, rule, event) and what it is allowed to touch, so the contradictions can be surfaced automatically instead of discovered by a reader.

Where CanonBoard fits

CanonBoard is a story bible built to argue back. Instead of a document, your world lives on an open canvas as connected, typed cards — characters, world rules, plot threads, lore, and a real timeline — so the structure of the world is legible to both your team and an engine that can hold the whole thing at once.

That structure is what makes the bible active rather than passive. CanonBoard scans the entire board on demand and surfaces continuity breaks with both sides quoted and the conflict named, so you fix contradictions while the world is still cheap to change. Smart Import can read an existing manuscript, script, or design doc and build the first draft of your bible automatically — characters, relationships, and a starting timeline — so you are not staring at a blank template.

The AI never writes your story; your voice is the product. It interviews, organizes, and tells you where the world disagrees with itself. Build the world, stress-test it, then go write it — against a bible you can actually trust.

Frequently asked questions

What is a story bible?

A story bible is the single authoritative reference for everything true about your fictional world — its characters, rules, history, timeline, and canon — that every scene, episode, or chapter is written against.

What should a story bible include?

Eight core sections: premise and logline, characters, world rules and systems, timeline and history, locations and setting, plot threads and arcs, lore and background, and style and canon notes.

How do you create a story bible?

Start with the premise and world rules, lay out a rough timeline, then populate characters, locations, and threads as atomic, dated facts — and stress-test the whole thing for contradictions before you start writing.

Do I need a story bible for a single standalone novel?

Not really. A standalone story can live in one writer's head. A bible earns its keep once the world spans multiple books, a full season, or a team, where the facts outgrow any single memory.