What a series bible is, in plain words
A series bible is a single reference document that records every fact about your story world that has been settled on the page: who people are, where things are, what the rules are, when things happened, and what you have promised readers but not yet answered. It is a lookup tool, not a piece of writing. Nobody reads it for pleasure, including you.
The name comes from television, where many writers need to agree on the same facts. For a novelist it is the same idea at a smaller scale: the only other writer you need to agree with is yourself, eighteen months from now.
Why a series needs one
Readers of a series remember details you have forgotten. They remember that a character is left-handed, that a bridge was closed after a flood, that someone swore never to return to a town. Contradicting those facts by accident costs trust, and the contradiction often only appears when a reader writes in to point it out.
A single book can survive on memory and a search of the manuscript. A series cannot, because the facts are spread across several files, several drafts, and several years of your life. The bible collects them in one spot so the answer to 'what did I say about this?' takes thirty seconds, not an evening.
What to include, and what to skip
Start with five headings. Each holds facts, not prose.
Then be strict about what stays out. The test is whether you would have to look it up. If you will remember it without help, skip it.
One field deserves extra care: who knows what. In a series, a character may learn a secret in Book Two that another character in Book Four must not know yet. A single line per secret ('Odile knows the boat was moved; Dov does not') prevents a whole category of slips.
- Characters: name, role, the facts about them that appear on the page (age, appearance, history), and who knows what.
- Places: layout, distances, what is where, and any detail a reader could check.
- Rules: how anything unusual works, such as magic, technology, law or custom, including its limits.
- Timeline: dated events, and how much time passes between books.
- Open questions: mysteries you have raised, promises you have made, and answers you have not yet decided.
- Skip: backstory you will never use, chapter-by-chapter summaries (the manuscript already has them), and long descriptions that duplicate the text.
A simple structure that holds up
Write each entry as one line, followed by where it was established. Add a status: fixed means it is on the page and readers have seen it, planned means it is only in your head. That one distinction saves a lot of grief, because you can change a plan freely but a fixed fact is a promise.
Use the same shape for every entry: category, the fact, the status, and the book and chapter where it appears. Plain headings in one document are enough. You can add tables or links later if you feel the need, and most people never do.
A worked example: ten lines
Here are ten lines from the bible of an invented series, the Saltmarsh Ledger books, set in a tidal harbor town called Wren Quay. Notice how short each entry is.
- Character: Odile Fenn, harbor clerk, 34 in Book 1. Left-handed. Fixed (B1, ch. 2).
- Character: Tomas Fenn, her brother, drowned eleven years before Book 1. Body never found. Fixed (B1, ch. 5).
- Place: the Customs House on the quay; east wing closed since the flood. Fixed (B1, ch. 9).
- Place: Pellam Island, reachable on foot only near low tide, about two hours either side. Fixed (B1, ch. 12).
- Rule: the tide bell rings twice a day and no boat leaves harbor while it rings. Fixed (B1, ch. 3).
- Rule: letters sealed with green wax may be opened only by the person named. Planned, not yet shown.
- Timeline: the flood is Year 0. Book 1 opens in October of Year 11. Book 2 opens the following March.
- Timeline: Odile's mother died in the spring of Year 6. Fixed (B1, ch. 14).
- Open question: who moved Tomas's boat after the flood? Reveal planned for Book 3.
- Open question: what is kept in the locked room behind the ledger shelves? Undecided.
A contradiction caught: worked example
Here is what the bible does in practice. Suppose you are drafting Book Three of the Saltmarsh Ledger books and want Odile to remember her mother's funeral, in the summer. You open the bible and find: 'Odile's mother died in the spring of Year 6. Fixed (B1, ch. 14).' You change your scene to spring and keep going.
Without the line, you would have written summer, a reader would have noticed, and a correction would have followed in a later edition. Thirty seconds of lookup saved a mistake that is awkward to fix once a book is out.
The same entry also tells you something else. It is fixed, so you cannot quietly move it. If summer is better for the story, you now have a decision to make on purpose: change Book One, or change the scene. Either is fine. The point is that you chose.
Starting when Book One is half written
You do not need to begin with a blank template and imagine the whole world. Begin by reading your own draft and writing down facts as you meet them, one line each, in order. Treat it as an afternoon's job per half of a book, not a project.
Start with characters and the timeline, since those drift fastest. Places and rules can follow. When you find two passages that disagree, write both down with a question mark, decide which one wins, and fix the draft. You will probably find a handful of contradictions, which is normal and much better to discover now than after publication.
From then on, add facts as you write them. At the end of each chapter, spend two minutes adding any new fixed fact before you close the file.
Keeping it current without a second job
A bible fails when it feels like homework. Keep it light. Update it at the end of each writing session, only with new facts. When you change something in the draft, change the matching line the same day, because the one you forget will be the one that bites you in Book Three.
A routine that works: when you stop for the day, spend two minutes on a short note of any name you invented, any date you mentioned, any rule you showed. Add each as a line with its chapter number. That is all. You are not summarizing the chapter, only capturing the facts a future version of you will need.
Once per book, read the whole thing and delete lines you did not use. If the upkeep takes more than five minutes a session, you are recording too much.
If you would rather keep this inside your writing tool, SagaFold lets a series of up to twenty books share characters and facts through story notes linked to the passages where they appear, with a timeline that spans one book or the whole series. A shared document works just as well if it stays small.