How to create a story bible: complete guide and template

A story bible is the master document recording everything your manuscript must never contradict: character sheets, places, relationships and a timeline. To create one, open a sheet per character (physical traits, voice, register, want, wound, knowledge state), one per place, and one per relationship with its chapter-by-chapter evolution — then update it in the same session you write.

What is a story bible?

A story bible (also called a series bible or character bible) is your novel's external memory: the canonical record of the facts your text has established. It is not the outline — the outline says what will happen; the bible says what is already true. Diego's eye color, which floor Marta lives on, who knows Elena's secret and since which chapter: small facts, but each one is a promise to the reader.

The problem it solves is memory, not talent. In a forty-chapter, ensemble-cast novel nobody holds a thousand details in their head at once, and continuity errors never announce themselves: they slip in exactly where you stopped looking. A well-built bible turns that mental load into something you can consult — and even verify.

What should a story bible include?

Four blocks: characters, places, relationships and timeline. Most templates cover the first two and neglect the last two — which is precisely where the hardest-to-catch errors live.

Character sheets

• Stable physical traits: eyes, hair, scars, age when the story opens, features other characters mention.
• Voice: verbal tics, rhythm, vocabulary, what they would never say. Voice is the first thing to blur when a character spends ten chapters offstage.
• Register with each other character: who they are formal with, who they are familiar with, and since when. In Spanish fiction, the shift from usted to tú is a relationship event in its own right; if it slides backwards for no reason, readers notice.
• Want and wound: what they pursue, what hurts them, the story they tell themselves. This is what keeps their decisions from contradicting each other across acts.
• Knowledge state: what they know, what they don't, and in which chapter they learned each thing. The source of the classic “how do they know this if nobody told them?”.

Places

Every recurring setting deserves a sheet: internal geography (how many floors does the house have? does the bar have a street-facing window?), distances and travel times between locations, fixed sensory details, and which characters have been there. Readers draw surprisingly precise mental maps and object when the balcony switches walls.

Relationships — and how they evolve

This is the dimension almost every template leaves out: a relationship is not a label, it is a timeline. “Marta and Diego: lovers” is true in chapter 3 and false in chapter 12. If it only stores the current state, it cannot say what was true in the scene you're revising. Record each relationship as a sequence of states, with the chapter where it turns, what caused the turn, and who else knows.

Timeline

An internal calendar for the story: how many days each chapter spans, which date (even a relative one: “day 14”) each scene falls on, and the events that anchor everything else. Without it, pregnancies last eleven months and Fridays come twice a week.

Story bible template (copy it)

Copy these four sheets into your document or tool. Fill in only what the manuscript establishes; leave everything else blank until it exists on the page.

Character sheet

Place sheet

Relationship sheet (with evolution)

One sheet per pair of characters who interact. The evolution table is the part you cannot skip:

Timeline

When should you build it: before, during, or mid-manuscript?

Before writing: useful in moderation. Fill in only what you need to start — names, want, wound, initial register — and resist the urge to write the bible instead of the novel. A twenty-field sheet for a character who hasn't spoken yet is procrastination with a clear conscience.

While writing: the natural mode. You write the scene, and if Diego reveals a scar or Marta drops the formal address, you note it before closing the session. The golden rule: the bible documents what the text says, not what you planned for it to say. When they disagree, either fix the text or update the bible — never leave them in conflict.

With a manuscript already underway (retrofitting): the most common case, and the one most guides skip. Don't try to reconstruct it from memory: reread chapter by chapter with the sheets open and extract only facts the text asserts, each with its source chapter. Work in this order:

1. A fast pass per chapter: note every physical attribute, relationship change, revealed fact and time marker, with the chapter number next to it.
2. Open a separate contradiction log: whenever a new fact clashes with one already recorded, don't resolve it yet — log it and keep reading.
3. When you finish, resolve contradictions in batches: decide which version is canon, fix the manuscript, and leave the bible with a single truth.
4. From that day on, maintain the bible at the pace of the writing; retrofitting happens once, maintenance is forever.

The extraction pass takes several sessions and earns every one: it doubles as the best structural reread your book will get, and it sets up the continuity check before you submit the manuscript.

Why do story bibles rot (and how do you stop it)?

Every abandoned bible died of the same thing: updating it is a separate act from writing. You write with the novel open and the bible closed; the new fact stays in the chapter and never reaches the sheet. Three weeks later it is no longer reliable, and a bible you don't trust is worse than none — it gives false confidence.

• Update in the same session. Closing a writing session includes two minutes of bible work. No exceptions.
• Every fact carries its source chapter. “Brown eyes (ch. 2)” can be verified; “brown eyes” alone cannot.
• Record changes, not just states. When a relationship or a register shifts, log the chapter of the turn — don't overwrite the previous value.
• One sync pass per revision round. Whenever you rewrite chapters, revisit the affected sheets: rewrites are where most bibles break.

Where does software fit?

There are three tiers of tool, and it helps to know which one you're on. The first is the static document: a Word file, a Notion page, a notebook. It works — this whole template fits in one — but all the discipline falls on you, and it never warns you when the manuscript contradicts it. The second tier is structured tools: writing codices and wikis that organize linked sheets and, in several cases, feed them to a generating AI. Better lookup, same limitation: the bible gets read, not checked.

The third tier is a bible that is actively checked against the prose. That is Journzy's model: characters, places and relationships live in a knowledge graph with a per-chapter timeline, and the AI reads what you write against that graph and flags the contradiction as it happens — the eyes that change color, the formality that slides backwards, the character who knows something nobody has told them yet. It never writes or rewrites a sentence of yours, and every flag carries an “It's intentional” dismissal, because a deliberate break is a legitimate authorial choice. The bible stops being a document you maintain and becomes a contract that gets enforced.

Wherever you start, start: the template above works the same on paper as in a graph. And if any term trips you up — canon, retcon, point of view — the fiction writer's glossary covers them all.