How to build a story bible for a finished book

6 min read · Updated October 23, 2026

To build a story bible for a book you've already written, read it back in a few focused passes rather than one slow, exhaustive one. Pull out the details most likely to cause errors first (names, physical descriptions, ages, deaths, the timeline), note the chapter for every fact, and fill in the rest later as you need it.

Most writers do this at one of two moments: right before a sequel, when book two has to agree with book one, or before a major revision, when moving scenes around can break dates and reveals. Either way, the goal isn't a perfect encyclopedia. It's a reference you can trust for the next book.

AI can do a lot of the extraction for you, as long as you review what it finds. There's a section on that below.

Why build one after the fact?

A sequel is written against a fixed text. Readers have the first book; you can't quietly change it. Every detail you get wrong in book two is a contradiction they can point to. A bible built from the finished text records what you actually wrote, which is often different from what you remember writing.

A revision has the opposite problem. Things can still change, but every change ripples. If you move the burning of Thornwatch a week later, which other scenes depended on that date? The bible tells you.

Before you start

Gather what you have:

• The final text. Use the published or final edited version, not an earlier draft. Canon is what the reader read.
• Your old notes, outlines and synopses. Useful as a map, but don't trust them. Plans drift.
• Any style sheet from your copyeditor. If your book was copyedited, the style sheet already has spellings and many key facts.
• Reader questions and reviews. If readers have asked "wasn't she dead?" you know where to look.

Then decide on a structure. A story bible template with a Source column on every table is a good start.

Pass one: names and a chapter map

Skim the whole book quickly and build two lists.

A chapter map. For each chapter: its number, title if any, POV character, and roughly when it happens in story time. For The Ashen Crown:

A name list. Every named character, place, group, object and invented term, with the chapter where it first appears and every alternate name. Don't describe anything yet. Just get the names down, spelled exactly as in the text.

This pass is fast and gives you the skeleton everything else hangs on.

Pass two: the high-risk details

Now go back with a narrow focus. Look only for the facts readers most often catch:

1. Physical descriptions. Eyes, hair, height, scars. Record the exact wording and chapter.
2. Ages and birth dates. Any stated age, birth year, or "she was ten when..." line.
3. Deaths and injuries. Who dies, when, where. Who's wounded, and how badly.
4. Dates and durations. "Three days later," "the following spring," travel times.
5. Family relationships. Who's whose parent, sibling, spouse.

Write each one as a single fact with its source. Don't reconcile yet; if chapter two says green eyes and a later chapter says grey, record both. Conflicts you find now are exactly what the bible is for.

Pass three: the timeline

With dates and durations collected, put events in order. Include backstory: births, old wars, the founding of houses, anything the text mentions that happened before page one.

Then check the arithmetic. In the sample series, Kael is described as nineteen on the night Thornwatch burns in 412 AS, but chapter three says he was born in 388. Both lines came from the same book. Laid out on a timeline, the problem is obvious: he'd be twenty-four.

Check, too, that no one is in two places at once and no one acts after their death. For more on this, see how to build a story bible timeline.

Pass four: rules, relationships and secrets

Last, the slower material:

• Rules of the world. How the magic, technology or society works, and especially what it costs or can't do.
• Relationships and loyalties, and when they change.
• Secrets and reveals. What's true, what the reader has been told, and what's still hidden. If you're writing a sequel, mark which secrets book one revealed and which are still owed.
• Open threads. Promises and mysteries the next book has to address.

What can wait

You don't need everything before you start the sequel. Leave these until a scene needs them:

• Minor characters who appear once
• Descriptions of places you won't revisit
• Voice notes for characters who won't return

Add them when you write the scene that uses them.

Using AI to speed it up

Extraction is the kind of task AI tools like ChatGPT and Claude are good at: reading a chapter and listing every named person, place, physical detail, date and relationship. A few rules make it reliable:

• Work one chapter at a time. Long inputs produce vaguer output. One chapter per request keeps the source clear.
• Ask for quotes. Every fact should come with the exact words from the text. A quote is how you check the AI didn't invent it.
• Ask it to separate explicit from inferred. "Her green eyes" is explicit. "She's probably in her twenties" is inferred. Treat inferences as notes, not canon.
• Give it your existing names. Paste your name list first and tell it to use those names exactly, so it doesn't create "Sir Kael" as a separate person from Kael Varn.
• Review everything. AI tools misread, merge characters, and sometimes make up details. You're the authority on your book.

If you have synopses or back-cover copy for earlier books, you can also ask an AI for a rough starter bible from those, then confirm the details against the text. For a longer look at the workflow, see using AI to build a story bible.

Check what you've built

Once the bible has the high-risk details and a timeline, run a check:

1. Look for conflicting values. Same character, same detail, two different answers.
2. Check ages against birth dates.
3. Check deaths against later appearances.
4. Check that no one is in two places on the same day.
5. Look for duplicates. The same person entered twice under different names.

Decide each conflict. Some are mistakes to note (you can't fix a published book, but you can avoid repeating the error). Some are real changes that need a date range. Some are deliberate mysteries; note them as such.

Then keep it going

The hard part is done. From here, the bible grows with the next book: a short update after each writing session, a source on every fact, and a check before each revision. For the habits that keep a series bible useful over many books, see keeping a series consistent.