A solo author's story bible is a reference they keep for themselves. A team's story bible is infrastructure — the thing that decides whether five people are building one world or five overlapping ones. They look similar and they are not the same tool.
If you already know what goes into a story bible, this is the next question: how do you run one so a whole team actually shares it, instead of each person quietly keeping their own?
Why private bibles drift apart
The default failure is not having no bible — it is having several. One writer keeps notes in a doc, another in their head, a third in the margins of a script. Each is internally consistent and they disagree with each other, and because no two people ever read the same one, the disagreement stays invisible until it ships.
A shared bible exists to collapse those copies into one. Its first job is not completeness; it is singularity. There should be exactly one place the team agrees the truth lives, and everything else is a draft on the way into it.
Structure it for sharing, not just storing
A team bible has to be readable by people who did not write it. That means facts kept atomic and findable — "as of season two, she leads the council" rather than a paragraph only its author can parse — and a structure where anyone can locate a character, rule, or thread without asking the person who added it.
It also means the bible carries the kind of facts teams break on: not just who characters are, but what the world's rules cost, what the timeline asserts, and which threads are still open. The shared bible is where a contributor checks their work against the world before adding to it.
Permissions and history keep it trustworthy
For a shared bible to stay the source of truth, the team has to trust it — which means controlling who can change canon and recording every change. A wide group should be able to read and propose; a smaller group ratifies. Every change leaves a trail: what shifted, when, and by whom.
That history is what lets a team trace a contradiction back to the decision that caused it, and what lets a new contributor trust that the record reflects current canon rather than someone's unreviewed edit. A shared bible without permissions and history is just a faster way to overwrite each other.
Frequently asked questions
- What is a shared story bible?
- A shared story bible is one canonical record of a story world that an entire team reads from and writes to — as opposed to a solo author's private bible. Its job is to be the single source of truth so the team never works from conflicting copies.
- How is a team story bible different from a solo one?
- A solo bible mainly has to be complete. A team bible also has to be live, shared, permissioned, and traceable — current the moment canon changes, readable by everyone, editable by the right people, with a history of what changed and why.
- How do you keep a shared story bible from going stale?
- Make updating it part of the moment a decision is made, not a separate chore. When canon changes in a meeting or a draft, it should land in the shared bible the same day, in one place everyone already reads from.
CanonBoard scans your whole world and tells you where it disagrees with itself.
Start free