How to keep a series bible that actually helps you write
Published on may 12, 2026
Ask ten series authors for their story bible and you'll get two beautiful wikis, three abandoned spreadsheets, four piles of sticky notes, and one person who says it's all in their head. The pattern is consistent: bibles that try to record everything get abandoned, and bibles that record the right things get used.
The failure mode is always the same. You set up the wiki in a burst of organizational optimism, spend a weekend cataloguing eye colors and birthdays, and then the actual writing starts. Every hour spent updating the bible is an hour not spent on the book — so the bible falls behind, and a bible that's behind is worse than no bible, because you can no longer tell which entries to trust.
Record decisions, not descriptions
The useful unit of a series bible isn't a character profile — it's a decision. 'Mara can't swim' matters because you decided it in book one and someone will drown in book three. Descriptions you can re-derive from the text; decisions you have to remember, because breaking one breaks a promise to your reader.
A good test: write the entry as a constraint, not a fact. 'The wards fail at sunset' constrains every night scene you will ever write in that world. 'The tavern has oak beams' constrains nothing, and the moment it matters, you'll check the original scene anyway. Constraints go in the bible. Furniture stays in the book.
A bible entry earns its place when forgetting it would cost you a rewrite.
Structure for retrieval, not for completeness
Organize by the question you'll ask, not the category the fact belongs to. Mid-scene, you never ask 'what are all the properties of the magic system?' You ask 'can Edda light this fire without being detected?' Entries that answer questions get read; taxonomies get admired once and never opened again.
This is also why dates beat prose. 'Winter, year 3: the border closes' can be scanned in a second from a timeline. The same fact buried in a paragraph about geopolitics is functionally lost. When in doubt, make it a list with dates.
Let the book maintain it
The reason most bibles die is that maintenance competes with writing. This is exactly what we built Story Memory to fix: Fable extracts the decisions from your chapters as you write them, and the bible stays current because the book itself is the source of truth.
Whether you use Fable or a notebook, the principle holds: track what you promised, when you promised it, and what it constrains. Skip the eye colors — unless someone's going to drown over them.
