The Story Bible Template That Keeps 300 Chapters Consistent

A story bible is the fix. It is not a worldbuilding hobby document. It is an operational file: the facts you have committed to, in one place, written so you can find them in ten seconds. Below is the template I use for novels and for serials that run into the hundreds of chapters, followed by notes on how to fill each section without turning it into a second book.

Principles before the template

Prose, not fragments. "Mara. 34. Archivist. Trust issues." is useless in a year and useless to an AI now. "Mara is thirty-four, has worked in the royal archive since she was nineteen, and has not trusted anyone with a key since her brother copied hers" tells the whole story. It costs twenty more words and saves you an hour of reconstruction.

Facts, not plans. The bible records what is true in the story so far. Plans live in the outline. Mixing them is how you end up with a bible that says the brother dies in chapter 30 when he in fact survived the rewrite.

One entry, one thing. Each character, place, faction and rule gets its own entry with its own heading. This matters for search, and it matters enormously if a tool is going to select entries to feed a model.

Date every change. A line at the bottom of each entry: "Updated ch. 41: now knows Mara is alive." When something contradicts, you can see which version is newer.

The template

Copy this into a new document. Replace the bracketed prompts. Delete what your project does not need.

# STORY BIBLE — [Title]
Last updated: [date] (through chapter [n])

## 1. Premise and promise
Premise (one sentence): [Protagonist] must [goal] before [pressure], but [obstacle]; if she fails, [stakes].
Genre and shelf: [e.g. secondary-world political fantasy, adult, single volume / 4-book series / ongoing serial]
The promise to the reader: [What feeling the ending must deliver. E.g. "justice that costs the hero her innocence."]
Central question: [The question the book asks and answers. E.g. "Can a forger tell the truth?"]
Themes we will not state aloud: [2–3 words each]

## 2. Characters
(One entry per named character who appears in more than one scene. Minor characters get one line under "Bit parts".)

### [Name] — [role in one phrase]
Age, body, one detail people notice first: 
What she wants (this book): 
What she needs (does not know it): 
Wound (the old thing that shaped the want): 
How she speaks: [sentence length, vocabulary, what she avoids saying, a sample line]
What she would never do: 
Relationships: [to each major character, one line, with the current state]
Facts committed so far: [eye colour, scars, allergies, skills, possessions, anything a reader could catch]
Arc so far: [two or three sentences, updated as you draft]
Updated: [chapter n]: [what changed]

### Bit parts
- [Name], [one line], first appears ch. [n]

## 3. World and rules
(One entry per system. The test: "Could a plot point depend on this?" If yes, it needs a rule.)

### [System, e.g. Magic / Technology / Law / Money / Religion]
How it works, in plain words: 
What it costs: 
What it cannot do (hard limits): 
Who controls or teaches it: 
Exceptions already established in the text (with chapter): 

### Places
#### [Place]
Where it is relative to other places, travel time: 
What it looks, sounds and smells like (three details): 
Who lives or works there: 
Scenes set here so far: ch. [n, n]

### Factions and institutions
#### [Faction]
What they want: 
Who leads: 
What they think of the protagonist: 
Resources and reach: 

## 4. Voice and style
Point of view and tense: 
Narrative distance: [e.g. close third, free indirect, no head-hopping within scenes]
Three paragraphs in the target voice (from the draft, the ones you are proudest of):
[paragraph]
[paragraph]
[paragraph]
Sentence rhythm notes: [e.g. "short declaratives under stress; long, comma-heavy in reflection"]
Vocabulary: [words this narrator would use / would never use]
Banned list: [phrases that keep creeping in: "a testament to", "couldn't help but", "let out a breath she didn't know she was holding"]
Dialogue conventions: [tags, dialect spelling, how profanity is handled]
Formatting conventions: [scene breaks, chapter headings, epigraphs, internal thought italics]

## 5. Timeline
(Chronological, dated in story-time. Include offstage events. Every entry has a chapter reference or "offstage".)
- [Year/Day 0]: [event] — offstage / backstory
- [Day 1]: [event] — ch. 1
- [Day 1, night]: [event] — ch. 2
...
Calendar notes: [season, moon, days of the week if they matter]
Ages at story start: [character: age]

## 6. Open questions
(Things you have not decided. Deciding them in the draft moves them to the section above.)
- [Question]. Leaning: [option]. Must decide by: ch. [n].

## 7. Chapter summaries
(One paragraph per chapter, written the day you finish it. What happened, what changed, what the reader now knows. This is the section that keeps 300 chapters consistent.)
- Ch. 1 — [POV] — [summary]. New facts: [list].
- Ch. 2 — ...

How to fill it without drowning

Section 1 is the one you write first and revise last

The premise and promise take an afternoon and will change twice. That is fine. What you are avoiding is the situation where, in chapter 25, you cannot remember what the ending is supposed to feel like and you write toward whatever feels good that day.

Section 2: write characters as people who talk

The "How she speaks" line does more for consistency than the whole physical description. Compare:

Ruiz speaks in short sentences and never asks a direct question; he states a fact and waits. Sample: "Your cousin was in Thursday."

versus

Ruiz: bartender, 50s, gruff.

The first version lets you (or a model) write him next year. The second produces a generic gruff bartender, which is not Ruiz.

"What she would never do" is your continuity guard against convenient plotting. If Mara would never leave a document unlocked, then the scene where she does one is a scene about her breaking, or it is a mistake.

I keep a separate character sheet template with the twelve questions that produce these entries fastest.

Section 3: rules are only rules if they cost something

The most common bible failure is a magic system described in loving detail with no line under "What it costs" or "What it cannot do." Plot points depend on limits, not on capabilities. If healing magic exists, the bible must say what it cannot heal, or every wound in the book is negotiable.

For places, three sensory details beat a paragraph of geography. Readers remember the smell of the archive; they do not remember its square footage. And "travel time" prevents the error where a journey takes four days in chapter 10 and an afternoon in chapter 50.

Section 4 is the section that makes AI output sound like you

If you draft with a model, the three sample paragraphs and the banned list are the highest-leverage thing in the file. Models imitate examples far better than they follow adjectives. "Write in a spare, literary voice" produces one thing; three actual paragraphs of your spare literary voice produce something much closer. I explain why in Keeping Your Voice When Writing With AI.

Even if you never touch AI, the banned list is worth keeping. Every writer has tics. Mine involve people's hands.

Section 5: the timeline is boring and non-negotiable

Nobody enjoys this section, and it catches more errors than any other. The failure it prevents: a pregnancy that lasts fourteen months, a letter that arrives before it is sent, a full moon on consecutive nights.

For serials, add a running "elapsed story-time" figure at each chapter. When you are 200 chapters in, "how long has it been since the tournament?" has a one-second answer.

Section 6 keeps you honest

Open questions are decisions you are deferring on purpose. Writing them down stops two things: the model (or your tired brain) from deciding them by accident, and you from forgetting you have not decided. The "must decide by" chapter turns it into a deadline.

Section 7 is the whole point for long work

Chapter summaries are where a 300-chapter serial lives or dies. One paragraph per chapter, written the same day. The "New facts" list is what gets copied up into sections 2 and 3.

Here is what it looks like for a serial:

Ch. 112 — Kael POV — Kael reaches the third floor of the tower and finds the guardian already dead; realises someone is ahead of him. Retrieves the lantern. Ends on the sound of footsteps above. New facts: lantern is warm to the touch; tower guardians can be killed by mundane weapons (contradicts ch. 40 assumption — resolved: ch. 40 guardian was a different class). Elapsed time: day 61.

That entry took ninety seconds. Finding the guardian rule by rereading chapters 40 through 112 would take an afternoon, and I would still have missed it.

Two versions: minimal and full

Not every project needs every section.

Using it with an AI tool

If you write in a tool with a built-in bible (SparkLore, Novelcrafter's Codex, Sudowrite's Story Bible), the sections above map onto its entry types. Two tips that hold regardless of tool:

1. Keep entries small and titled by the name people use. A tool that auto-detects which entries are relevant does it by matching names in your text. An entry titled "The Brother (Teo)" gets missed when the text says "Teo."
2. Put the style samples where the tool will send them every time. Some tools have a dedicated style or "voice" field; use it. If not, put the three paragraphs at the top of a "Style" entry marked always-include.

If you work in a chat window instead, the bible is what you paste. Paste the relevant entries, not the whole file. A 15,000-word bible in every request is expensive and, past a point, counterproductive; models weight the middle of long context less than the ends.

Try it in SparkLore

SparkLore's projects have a bible built to this shape: characters, world rules, places, style samples and chapter summaries, each as its own entry, injected into every generation. The chapter-summary step is automated, which is the one part of this template most writers stop doing by hand around chapter 30. If you want to see how a bible changes the output before you build one, the free AI character generator produces a character entry in the format above from a few lines of description, and you can paste it straight into your own document. Or start a project and fill section 1 tonight.