How to Build a Story Bible
Somewhere around chapter six, you stop being able to remember what colour you made the inn, or which brother is older. A story bible is where the answers live — the single record your book agrees with itself against.
What a story bible is
A story bible is a living reference for everything in your story that has to stay consistent: who your people are, where things happen, what the rules are. It isn't your outline — that's the plot — and it isn't your notes. It's the canon: the authoritative version of each fact, the thing you check when memory fails. For a standalone novel it keeps four hundred pages in register. For a series, it's the difference between one coherent world and several that happen to share a title.
What goes in it
Keep it to what actually recurs. A bible that tries to hold everything gets abandoned; one that holds the persistent facts gets used. The core entries:
- Characters. The largest section. Name and any aliases (a nickname, a title, a false identity), defining physical traits, age, relationships, and the one-line arc. Aliases matter more than they seem — half of continuity trouble is one person referred to three ways.
- Locations. The places that reappear — a house, a town, a ship — with the details you'll need to describe them the same way twice.
- Factions and organizations. Families, companies, courts, crews. Who's allied with whom, and who runs what.
- Objects. The significant items — a weapon, a letter, an heirloom — that a reader will track and that you must not lose or duplicate.
- World rules. In fantasy and science fiction, the limits of the magic or the technology. Write them down and obey them; a broken rule costs a reader's trust faster than any other error.
- Timeline. A chronology of events, real and invented, so ages add up and "three days later" survives arithmetic.
How to structure it
Group by entry type, and give each entry a short summary plus whatever custom fields your story actually needs — a novel about sailors needs a "rank" field; a legal thriller needs "jurisdiction." Don't inherit someone else's template wholesale. The right structure is the smallest one that answers the questions you keep asking yourself.
Whatever holds it — a document, a wiki, a dedicated tool — the non-negotiable rule is that there is exactly one of it. The moment facts live in two places, they disagree.
How to keep it from going stale
A story bible dies when the draft moves on without it. Three habits keep it alive:
- Update as you write. When you invent a fact, record it then — not "later." Later is where the second, contradictory version comes from.
- Check before you invent. When you're about to state a detail you might have set before, look. Ten seconds in the bible saves a continuity pass later.
- Reconcile after revision. When a rewrite changes a fact, change the bible in the same sitting, or the two drift apart for good.
When to build it
There's no wrong time, but most writers don't build a bible up front — they grow one. You start a few chapters in, when the world outgrows memory, and you back-fill the facts you've already set. The organic bible is often the honest one: it records the story you're actually writing, not the one you planned.
The story bible in Skarvia
Skarvia calls it the Codex, and it's built into each project. Characters, locations, factions, items, and notes — each with aliases, a summary, and your own custom fields. It can populate itself from your draft, so you're not typing what you already wrote, and every name in the manuscript gets an inline card you can hover to see who they are without leaving the page. A series shares one Codex across every book or episode, so the world stays single. Best of all, the Codex feeds the continuity editor: the canon you record becomes the standard your draft is checked against. Skarvia keeps the bible; the story stays yours.