Building a story bible you’ll actually use

What to put in a story bible, how to organize it so answers take seconds to find, and how it keeps your drafts and AI-assisted chapters consistent.

6 min read
On this page

Somewhere around chapter twelve, many novelists stop to search their own manuscript for a fact: the color of a character’s eyes, the name of the bar, how many days have passed since the fire. A story bible is the document that answers those questions in seconds, so you can keep writing instead of searching.

It matters even more if you draft with AI. A model knows only what you give it. If the facts aren’t in front of it, it fills the gaps with plausible guesses, and plausible guesses are how a gray-eyed character ends up with brown eyes in chapter nine.

What a story bible is, and isn’t

A story bible is a reference of facts about your story: who, where, when, and how things work. It isn’t a place for prose, mood boards, or long backstories you’ll never use. The test for any entry: will I need to look this up while drafting or revising? If not, it doesn’t belong.

What to include

Characters

For each character who appears more than once:

  • Name: the exact spelling, any nicknames, and who uses which
  • Age and birthday, or at least the birth year
  • Physical details that appear on the page: eye color, height, scars, how they dress
  • Voice markers: speech habits, words they use, and words they never would
  • Relationships with each other character who matters
  • What they know, and when they learned it
  • Arc stage: where they are emotionally in each act

Places

  • Layout and distances, such as how long it takes to walk from the house to the harbor
  • Names of streets, shops, ships, and rooms
  • A few sensory details you’ll want to reuse consistently
  • Who lives or works where

Timeline

  • The date or day of the week for each chapter
  • Seasons, holidays, and weather that affect the plot
  • Ages at key events, so a character isn’t 34 in one chapter and 31 two years later
  • The backstory events that matter, with dates

Rules of the world

  • How the magic, technology, or institutions work, and what they cost
  • Limits: what can’t be done, and why
  • Money, laws, and customs that come up in the plot

Style sheet

  • Spelling choices, such as “OK” or “okay,” and “email” or “e-mail”
  • Capitalization of invented terms and titles
  • How you handle numbers, dialogue punctuation, and italics for thoughts or other languages
  • Point of view and tense rules, especially in books with several narrators

Open threads

  • Setups waiting for payoffs
  • Promises made to the reader
  • Mysteries, and who knows the answer

What to emphasize by genre

Every bible needs characters, places, and a timeline, but genres put weight in different places:

  • Mystery: a clue tracker showing where each clue appears, who has seen it, and which red herrings point where. Add a private, true timeline of the crime, separate from what the sleuth believes.
  • Fantasy and science fiction: rules, costs, and limits for magic or technology, plus names and spellings for places, peoples, and invented terms.
  • Romance: relationship milestones, such as the first meeting, the first kiss, and the big misunderstanding, so the emotional progression stays steady.
  • Thriller: a precise timeline, often down to the hour, with where each character is at each moment.
  • Historical fiction: period details you’ve verified, with their sources, so you don’t have to research the same fact twice.

Keep entries short and sourced

Write facts, not prose: one fact per line, with the chapter where each was established.

Mara Quinn. 38. Gray eyes (ch. 1). Left-handed (ch. 3). Calls her brother “Theo,” never “Theodore” (ch. 2). Doesn’t drink coffee; drinks strong black tea (ch. 4).

The chapter reference matters. When the bible and the manuscript disagree, you can go straight to the source and decide which version is right.

Organize for lookup

Speed is the point. Whatever tool you use, whether a single document with clear headings, a folder of short files, or a spreadsheet, keep these habits:

  • One entry per character, place, or rule
  • The same order of fields in every entry
  • A consistent arrangement: alphabetical, or grouped by role
  • A “last updated” note on each entry

If finding a fact takes longer than searching the manuscript, the bible won’t get used. Keep it open in a second window or on a second screen while you draft, so checking a fact costs a glance rather than a search.

Update it as you draft

A bible is only useful if it’s current. After each writing session, take five minutes:

  1. Add any new names, places, or terms
  2. Record any fact you invented on the page
  3. Note new setups and threads
  4. Mark the threads you’ve paid off

If you change a fact during revision, change it in the bible first, then search the manuscript for every place it appears.

Using a story bible with AI drafting

When you draft a scene with AI, don’t paste the whole bible. Give the model the entries that matter for that scene:

  • The characters present, with their voice markers
  • The location
  • Where the timeline stands, and what each character knows at this point
  • Any open threads the scene should touch, or must not resolve yet

Then check the draft against the bible. Models are good at sounding consistent and less reliable at staying consistent with facts they weren’t given. When a draft introduces a detail you want to keep, add it to the bible so the next scene knows about it. When a draft contradicts the bible, fix the draft and note the correction, because the same mistake tends to come back if the fact isn’t stated in the next prompt.

A bible keeps the facts straight; it doesn’t keep the prose sounding like you. Pair it with a voice sheet, as described in keeping your voice when you draft with AI.

Building a bible for a draft you’ve already written

If you’re starting a bible during revision, don’t try to fill every field at once. Read the manuscript with the bible open and record facts only as you meet them, chapter by chapter. Contradictions will surface as you go, which is useful in itself: each one is a continuity error you would otherwise have shipped. Mark them with both chapter references and resolve them after the read-through, so you aren’t rewriting in the middle of gathering facts.

Common problems

  • Bloat. Pages of backstory nobody checks. Move it to a separate notes file.
  • Contradictions. The bible says one thing and the manuscript another. Decide which wins, fix both, and note the chapter.
  • Abandonment. The bible stops being updated in act two. Keep the five-minute habit.
  • Starting too late. A bible built during revision works, but it means reading the whole draft to build it. Start with chapter one if you can.

Story bible checklist

  • Every recurring character has an entry with sourced details
  • Places include distances and names
  • A chapter-by-chapter timeline exists
  • World rules include limits and costs
  • A style sheet records spelling and formatting choices
  • Open threads are listed and kept current
  • The bible gets updated after every session

In AIBookWriter, the characters, outline, and story bible live alongside the manuscript, and importing an existing Word manuscript can fill in characters and a story bible with an optional AI pass. For a setting you haven’t built yet, the free World Builder drafts rules, places, factions, and conflicts you can trim into bible entries.

Tools for this article

Keep reading

AI writing6 min read

Keeping your voice when you draft with AI

How to keep your own voice when drafting with AI: write a voice sheet, choose a real writing sample, draft in small units, and revise for voice, not errors.

Write the book, not just the notes

AIBookWriter carries a book from first idea to finished files: plan it, write chapters in your own voice, get a whole-book review, then format and publish. The Free plan starts with 100 credits.

Start writing — it's free