What a story bible is, and is not
A story bible records what is true. An outline records what happens. Confusing the two is the most common reason both become unusable.
You read an outline from start to finish. You do not read a story bible at all: you look things up in it. That difference should shape how you build it. An outline is sequential and narrative. A bible is referential and flat, organized so that a specific question ("what color were her eyes in chapter two", "how long does the crossing take", "is it Kaelin or Kaelen") can be answered in under fifteen seconds.
It is also not a worldbuilding project. A story bible describes the world of the book you are writing, not the world entire. If an entry does not have a plausible chance of appearing on the page or constraining something that does, it belongs in a notebook you keep for pleasure (which is a fine thing to keep, but it is not this thing).
The fifteen second test. Pick any fact in your story and try to look it up in your bible. If it takes longer than about fifteen seconds to find, the bible is organized wrong. The purpose of a story bible is to stop you scrolling back through 60,000 words to check a detail, so any question that is slower to answer in the bible than in the manuscript means the bible has stopped doing its job.
When to start one
Later than most writers do. The instinct is to build the bible first, before drafting, and it is almost always a mistake. Worldbuilding before you have written any of your narrative produces beautifully detailed material for a book that doesn't even exist yet. At this fragile stage, the draft is what needs your attention, not the bible.
Two reliable triggers to consider. The first trigger is around 10,000 words, by which point you have invented enough that some of the details may have started to slip. The second trigger is the first time you have to scroll back through the draft to check a detail. That scroll is the bible announcing that it is needed. Start it that day, and seed it with the things you were looking for on that first pass.
The exception to this rule is secondary-world fantasy and science fiction with hard constraints, where the rules genuinely need to be settled before you can write a coherent scene. Even then, keep the pre-draft version to a page or two of rules, and let everything else accumulate as you write.
The six sections that matter
Most story bibles, whatever their genre, come down to six sections. Anything beyond these tends to be optional and personal.
1. Cast
One entry per named character. Full name and its exact spelling, role in the story, and the handful of physical and verbal details you will need to repeat: the things a reader would notice twice. Resist writing full biographies here. Deep character work belongs in a character profile. The cast list is for continuity, and its job is to stop you from doing something silly, like giving someone two different sisters.
2. Places
Each location that appears more than once: its name, what it looks and sounds and smells like, who hails from there, and how it sits in relation to other places. Distances and travel times are worth recording explicitly if they'll be relevant to your narrative, because they are the most frequently contradicted facts in any draft with a journey in it.
3. Rules
The constraints of your world. How the magic or technology system works and, more importantly, what it can NOT do. What makes the magic or technology fail? Who holds power and by what mechanism? What does the social order punish? Every genre has rules, including realist fiction, where the rules are simply the ones we live under and in that case the section can be short.
Write the limits before the capabilities. A magic system defined by what it can do produces stories where the magic solves everything. A system defined by what it costs produces much deeper, richer stories.
4. Timeline
A dated sequence of events, covering both what happens on the page and the backstory behind it. This is the section writers skip and then rebuild painfully in revision. Ages, intervals, seasons, how long ago the war was, etc.: these contradict each other constantly and are noticed by readers immediately.
5. Style sheet
Spellings, capitalization, invented terms, and formatting decisions. Is it "the Council" or "the council". Do you italicize the invented language. Is it grey or gray. A copy editor will eventually ask you for exactly this document, and building it as you go costs nothing, while rebuilding it later costs a weekend (or more).
6. Open questions
Perhaps the most underrated section. A running list of what you have deliberately not decided: whether the brother survives, what the inscription actually says, how the border is policed, and on and on. Writing these down turns unresolved things into decisions you make intentionally, rather than contradictions you discover during a revision.
A story bible template you can copy
Below is the starting skeleton for a story bible. Copy it, delete what your book does not need, and expect it to look quite different by the end of your draft.
STORY BIBLE: [Title] Last updated: [date] -------------------------------------------- 1. CAST -------------------------------------------- [Full name] ([preferred name]) Role: Age / born: Appearance (repeatable details only): Voice (speech habits, what they never say): Relationships: First appears: -------------------------------------------- 2. PLACES -------------------------------------------- [Place name] What it is: Sensory detail (sight, sound, smell): Distance / travel time to [other place]: Who is usually there: First appears: -------------------------------------------- 3. RULES -------------------------------------------- System / institution: How it works: What it CANNOT do: What it costs to use: Who is excluded from it: Known exceptions: -------------------------------------------- 4. TIMELINE -------------------------------------------- BACKSTORY [year / relative date] - [event] ON THE PAGE [day / chapter] - [event] - [who is present] -------------------------------------------- 5. STYLE SHEET -------------------------------------------- Spellings and invented terms: Capitalization decisions: Numbers, dates, measurements: Formatting (italics, dialect, chapter headings): Point of view and tense: -------------------------------------------- 6. OPEN QUESTIONS -------------------------------------------- [ ] [Question] - blocking / not blocking - decide by [chapter]
What to leave out
A story bible fails far more often from bloat than from being too thin. Four things are usually worth cutting.
Anything you have not written yet. Record facts once they are on the page. Speculative entries for chapters you have not reached become obsolete and, worse, they make you feel obliged to use material that no longer fits.
Detail that never surfaces. The full genealogy of a house that appears in one scene is a pleasure, not an easy-to-find story bible reference. There is nothing wrong with it, and it's fun to create. But, keep it somewhere else.
Duplicates of the manuscript. Do not paste passages of prose into the bible. Note the fact and where it appears, then let the manuscript hold the words. Some tools will let you link passages to keep things interconnected, which is an easy way to withstand this temptation.
Your outline. Keep them separate. The moment the bible starts describing sequence, it stops being a clean reference and starts being a second (worse) outline.
Keeping it current
Every story bible decays. The question is only how fast, and the answer depends almost entirely on friction.
Update in the same session, not in a separate pass. When you invent a name mid-scene, add it within the minute. Writers who plan a weekly bible-updating session almost never hold it, and after three missed weeks the document is untrustworthy, which means it is also worthless: an unreliable reference is worse than none, because you check it, believe it, and are wrong.
Keep it beside the draft. Friction is the whole battle. A bible in the same project as the manuscript gets updated. One in a different app, or file, or a notebook in a drawer, often does not.
Let it be ugly. Fragments, lowercase, half-sentences, they're all invited to the party. The bible is a tool and no one else will read it. Time spent formatting it is time not spent writing.
Prune once, at the end of the draft. When you finish, spend an hour deleting entries that never mattered and correcting the ones the draft changed. That is the version you carry into revision, and into book two (or three, or four).
A note on the last five percent. No bible is ever complete, and chasing completeness is how writers end up with an immaculate reference document and no novel. If it answers the questions you actually ask, it is finished enough.
Story bibles for a series
Everything above scales to multiple books in a series, but two things change once multiple books exist.
First, the bible splits. You end up with a series-level document holding what is true across all books (the world, the rules, the long timeline, the cast who recur) and a per-book document holding what is true only within one (this book's locations, its minor cast, its immediate chronology). Without the split, book three's bible carries the accumulated weight of everything and becomes too slow to use.
Second, the timeline stops being optional. Across a series, the errors readers catch are almost entirely temporal: someone is the wrong age, a season is wrong, an event is remembered as being five years ago in one book and eight years ago in another. A dated series timeline is the single highest-value page in a multi-book bible.
If you are heading toward a series, the series planning guide covers how the arcs and the bible relate.