Your Story Bible: What Goes In It
A few months into a novel, no one remembers the eye colour of a minor character who appeared in chapter 3, or what year the backstory is set in. The story bible is where these things are written down once, so you don't reinvent them differently every time.
What it is
It's a single document — a file, a notebook, a panel in your writing app — that gathers the fixed facts of the story: the ones that, once decided, shouldn't change without a reason. It isn't your idea journal or your outline: it's the archive of what the text has already established.
The practical difference: the outline says what will happen, the bible says what the world it happens in is made of.
The sheets it holds
Five sections cover almost every need.
| Section | What it records | Most useful field |
|---|---|---|
| Characters | looks, age, voice, relationships, what they want | "truth and lie" for the arc |
| Places | geography, mood, who lives there, distances | a mental map of the moves |
| Objects | weapons, letters, inheritances, anything recurring | who has it now |
| Timeline | dates, relative ages, order of events | how many years before is the backstory |
| World rules | magic, technology, laws, customs | the limits, not just the powers |
For realist fiction, "world rules" become continuity of detail: what job a character has, what car they drive, the name of the bar downstairs.
What NOT to put in it
- Ideas still open. If you haven't decided how the antagonist dies, don't write it in the bible: keep it in your notes. The bible records the decided, not the possible.
- Whole paragraphs of backstory. A character doesn't need three pages of childhood: they need the wound, the lie, two or three concrete facts. The rest you find by writing.
- Copies of the text. The bible isn't where you retype scenes: it's where you note that in that scene the character got the scar on their wrist.
A too-detailed bible doesn't get updated, and a bible that isn't updated is worse than none: you trust a false fact.
How to keep it current
The rule that works: update it at the end of every writing session, not during. Five minutes where you skim what you wrote and ask: did I introduce a character? a place? did I give a date, an age, a physical detail? If so, you add it.
Updating it mid-writing breaks the flow; not updating it at all means finding two versions of the same fact at chapter 20. The right moment is when you've stopped writing but still remember what you decided.
Why it pays to have it from the start
Someone who starts the bible halfway through spends a day combing the written chapters to recover the facts. Someone who keeps it from chapter one builds it five minutes at a time without noticing. The cost is the same; it only changes whether you pay it spread out or all at once.
Frequently asked questions
Is it useful for a standalone novel, not a series?
Yes. The internal consistency of a 90,000-word novel written over a year is already a memory problem. Series add another: consistency between volumes. But the first exists for a single book too.
A file, a notebook, or a dedicated tool?
Whichever you actually open. A notebook is handy but not searchable; a text file is searchable but goes messy; a panel inside the editor keeps the sheets next to the text and fills in without switching windows. The key is that there's only one: two bibles that diverge are the problem you meant to avoid.
How much time does keeping it take?
Once running, five minutes per session. The first fill-in of a main character can take half an hour, but that's time taken away from future rewriting, not added to it.
What if I no longer like a choice in the bible?
You change it, but knowingly: you update the sheet and note on a list the points in the already-written text to fix. The danger isn't changing your mind, it's changing it and forgetting half the old occurrences.
Should the story bible go to the editor or the translator?
Yes, it's one of its best uses. A translator who has the list of proper names, their pronunciations and the world rules makes far fewer continuity errors. The same goes for a careful beta reader.