The Story Bible Your Serial Actually Needs
Search for "story bible template" and you will find forty-question character sheets asking for your protagonist's eye color, favorite food, and zodiac sign. Fill one out and you will have a lovely document that prevents exactly none of the mistakes that actually embarrass serial writers in public.
Nobody has ever been caught in the comments over a forgotten eye color. Writers get caught when a character acts on information she never learned, when the knife planted in chapter 12 never reappears, when the hard magic rule from arc one bends silently in arc four. Those errors have nothing to do with favorite foods. They have to do with dependencies — facts that other facts rely on — and most templates do not track dependencies at all.
So here is a different kind of story bible: lean, built for serials, and organized around the question a working serialist actually asks mid-chapter, which is not "who is this character?" but "am I about to contradict something?"
The principle: track what can contradict you
A fact belongs in your bible in proportion to how likely it is to collide with a future chapter. Eye color almost never collides with anything. These five categories collide constantly, and they are the whole system.
1. Beliefs — with sources
The upgrade that changes everything: never record a bare fact about what a character knows. Record where they learned it.
Not: "Kira knows the guild is bankrupt." But: "Kira believes the guild is bankrupt — learned ch. 31, overheard Master Ellin."
The source does two jobs. First, it makes the belief checkable — before Kira acts on the bankruptcy, you can verify the learning scene still exists and still says what you think it says. Second, it lets you track false beliefs with the same machinery, because a belief with a source can be a lie with a source: "Dorn believes Kira fled the city — told to him, ch. 40, by Sera (false)." Serials run on dramatic irony, and dramatic irony is just the gap between the belief ledger and the truth. If you only write down truths, you cannot see the gap you are supposed to be exploiting.
2. Who knows what
The companion to beliefs: a plain log of information transfers. One line each — who learned what, in which chapter, from whom. Every reveal, confession, eavesdrop, letter, and lie gets a line.
This log is what saves you in a multi-POV serial, where the author is the only character who has read every scene. When chapter 70 needs someone to act on the treaty being fake, you do not squint at your memory. You check the log: has this specific character been told, on the page? No line, no knowledge — write the transfer scene or rewrite the action. It is a mechanical check, which is exactly why it works at chapter 70 when your memory does not.
3. Promises and payoffs
Every planted element — mysterious object, unexplained scar, prophecy, cliffhanger question, gun on the wall — is a small debt to the reader. Keep the ledger explicitly: what was planted, where, and what it seems to promise. When you pay one off, mark it with the chapter number. Skim the open entries before starting each new arc.
That skim is the entire defense against the dropped thread, and it takes five minutes. The alternative is a comment three months from now that begins "so are we just never finding out about..." — a sentence readers relish typing considerably more than you will enjoy reading.
4. World rules
Not the atlas. Not the deep lore. Just the rules — the statements your world treats as physics: magic has a cost and here it is, the dead stay dead, nothing moves faster than a horse, cultivation stage gates what a body can survive. One line per rule, plus the chapter where it was established, plus any exception you have allowed yourself — because the exceptions are what you will forget, and an exception you forgot making looks exactly like a plot hole to everyone else.
Power-system serials live and die here. Progression readers are, affectionately, auditors with reading lists. They will re-derive your system from first principles, and their favorite genre of comment is the one proving chapter 88 violates it.
5. Character state
The current, dated condition of everyone who matters: location, injuries, notable possessions, rank or level, standing grudges. State is the most volatile data in the story and the least recorded, which is how healed arms un-heal and drowned swords reappear. The fix is boring and effective — a "current state" block per major character, touched whenever their state changes, always stamped with a chapter number so you can tell fresh data from stale.
The template
Plain markdown; one file per project is genuinely enough to start. Copy it, replace the examples, and delete nothing else.
# Story Bible — [Serial Title]
## Characters
### [Name]
- One-line essence: [who they are when it matters]
- Wants: [driving goal] / Flaw: [the thing that costs them]
- CURRENT STATE (as of ch. __):
- Location:
- Condition/injuries:
- Notable possessions:
- Rank/level/standing:
- BELIEFS (with sources):
- Believes [X] — learned ch. __, from [source]
- Believes [Y] — told ch. __, by [person] (FALSE — truth is [Z])
## Who Knows What (information transfer log)
| Ch. | Who learned | What | From | True? |
|-----|-------------|------|------|-------|
| 12 | Kira | The guild is bankrupt | overheard Ellin | yes |
| 40 | Dorn | Kira fled the city | Sera | NO |
## Promises & Payoffs
| Planted ch. | The promise | Status | Paid off ch. |
|-------------|-------------|--------|--------------|
| 12 | The named knife with the sealed hilt | OPEN | — |
| 3 | Who burned the archive | PAID | 47 |
## World Rules
- [Rule] — established ch. __. Exceptions: [none / list them]
- Magic drains body heat; sustained casting causes hypothermia — est. ch. 2.
Exceptions: bonded pairs share the cost (est. ch. 19).
## Timeline
- Running calendar: story day count per chapter, one line each
- Ch. 41: Day 88–89. Tournament deadline: Day 109.
## Chapter Log
- Ch. __: [one line — what became true in this chapter]
Two habits keep it alive. Update at publish — the chapter log line and any state changes get written the day the chapter goes up, never "later," because "later" is how bibles rot into fiction about your fiction. And write sources always — a fact with a chapter number is checkable; a fact without one is a rumor with formatting.
When a spreadsheet is enough — and when it is not
Honesty about tooling: for a single-POV serial under roughly thirty or forty chapters on a relaxed schedule, the file above — as a markdown doc or a spreadsheet with these tabs — is genuinely all you need. The dataset is small enough to skim whole, and skimming whole is a real verification method. Do not let anyone upsell you past a problem you do not have.
The wall arrives with scale: multiple POVs, weekly deadlines, forty-plus chapters, a transfer log running to hundreds of rows. Past that point the bible keeps storing perfectly well — storage is what spreadsheets are for — but storing was never the hard part. The hard part is checking: reading this Friday's draft against every row and noticing that a character is acting on a transfer that never happened. A spreadsheet cannot read your draft. It will preserve the evidence of your contradiction beautifully, in sortable columns, without ever mentioning it. Checking at scale is the actual job, and it is the job we built PlotLoom for — it holds this same structure as real data, beliefs-with-sources and all, and reads each chapter against it before you publish, like a continuity editor who has actually memorized your archive.
But tool or no tool, the structure is the point. A bible that tracks dependencies — sourced beliefs, logged transfers, an honest promise ledger, dated state — will save you in a text file. A bible that tracks favorite foods will not save you in anything.
Start the file today. Chapter one of the log is short. That is the best thing about it.
When the checking outgrows the file, PlotLoom turns this template into living canon and runs the continuity check for you, every chapter. Join the waitlist.