What is Book Series Bible?
A book series bible is a maintained reference document that tracks continuity across multiple books, including characters, chronology, world rules, locations, organizations, unresolved threads, terminology, and promises that future installments must respect.
What good book series bible looks like
A useful series bible stores only facts that affect continuity or future decisions, separates confirmed canon from ideas, records where each fact first appears, and is updated during drafting and revision so later books do not rely on memory alone.
- Character records with names, ages/time markers, relationships, physical facts that matter, arcs, secrets, and status by book.
- Chronology and event timeline with dates or relative sequence.
- World/location/system rules plus exceptions and source chapter.
- Open threads, planted clues, promises, unresolved relationships, and canon-versus-idea status.
A practical structure to follow
Use these elements as a decision checklist, not as a rigid formula. The exact wording should still fit the reader, context, and purpose.
- Character records with names, ages/time markers, relationships, physical facts that matter, arcs, secrets, and status by book.
- Chronology and event timeline with dates or relative sequence.
- World/location/system rules plus exceptions and source chapter.
- Open threads, planted clues, promises, unresolved relationships, and canon-versus-idea status.
How to write book series bible step by step
- 1Choose categories based on the kind of continuity your series actually needs.
- 2Record source location for important facts so they can be verified in the manuscript.
- 3Mark entries as canon, draft-only, possible, or retired.
- 4Track changes by book rather than overwriting history.
- 5Add open threads when planted and close them when paid off.
- 6Audit the bible before outlining each new installment and after final copy edits.
8 Book Series Bible examples
Read the examples for structure and choices rather than copying surface wording. Notice what stays consistent and what changes with audience or purpose.
Character record: Mara Vale — Book 1 age 34; allergic to shellfish established ch. 6; estranged brother Tomas; becomes archive director at end of Book 2.
Timeline: Book 2 begins eleven months after the courthouse fire, not “about a year” if later dates depend on the anniversary.
World rule: Map boundaries become physical only when drawn with imperial ink; exception introduced Book 2 ch. 19.
Open thread: Who mailed the blank key? Planted Book 1 ch. 3; referenced Book 2 ch. 7; planned payoff Book 3.
Location: North Archive has one public entrance and a service tunnel sealed in Book 1; reopening it in Book 4 requires an explicit event.
Terminology: Organization officially “Office of Civic Records”; characters use “Records Office” informally.
Book Series Bible templates
Replace every bracketed field with situation-specific information. A template is a starting structure, not finished copy.
Character entry: Name [x] | aliases [x] | first appearance [book/chapter] | fixed facts [x] | relationships by book [x] | unresolved threads [x].
Canon entry: Fact [x] | status [canon/draft/idea] | source [book/chapter] | implications [x] | later changes [x].
Timeline row: Date/relative point [x] | event [x] | characters [x] | source [x] | dependency [x].
Common mistakes to avoid
- Turning the bible into an encyclopedia of facts that never affect writing.
- Mixing brainstorm ideas with published canon without labels.
- Changing a character fact without noting which books already establish the old version.
- Tracking plot events but not promises, secrets, or unresolved relationship dynamics.
Final revision checklist
- Does the opening make the purpose clear quickly?
- Is every important claim, detail, or example doing a distinct job?
- Could a reader misunderstand any pronoun, transition, time reference, or instruction?
- Is the tone appropriate for the relationship and situation?
- Can you remove repetition without removing necessary context?
- If the writing contains factual claims, names, dates, quotations, or citations, have you verified them independently?
Questions about Book Series Bible
What is Book Series Bible?
A book series bible is a maintained reference document that tracks continuity across multiple books, including characters, chronology, world rules, locations, organizations, unresolved threads, terminology, and promises that future installments must respect.
What makes Book Series Bible effective?
A useful series bible stores only facts that affect continuity or future decisions, separates confirmed canon from ideas, records where each fact first appears, and is updated during drafting and revision so later books do not rely on memory alone.
How do I write Book Series Bible?
Start with the purpose and reader, then work through the structure in order. Draft for meaning first, check the examples for pattern, and do a final revision for clarity, accuracy, tone, and unnecessary repetition.
What should I avoid when writing Book Series Bible?
Turning the bible into an encyclopedia of facts that never affect writing. Mixing brainstorm ideas with published canon without labels. Changing a character fact without noting which books already establish the old version.
Does every statement about Book Series Bible need a recent source?
No. Freshness should match the claim type. Current policies, prices, roles, platform behavior, research findings, market conditions, and other changeable facts need current verification. Stable grammar, primary literary texts, manuscript canon, durable craft principles, and original illustrative examples may not need a recent citation at all. First classify the material as fact, interpretation, recommendation, convention, or original example; then use the strongest source and recency standard appropriate to that category, while preserving attribution and uncertainty where they matter.
When should I use a first-party or primary source instead of a secondary source for Book Series Bible?
Use the first-party or primary source when the exact fact, quotation, current requirement, project/manuscript detail, policy, metric, or source text controls the conclusion. Use a strong secondary source when the job is synthesis, explanation, field-level context, or orientation and the secondary source is appropriate to that job. If a reader could act on the claim, if sources disagree, or if wording depends on an exact passage, number, rule, or current status, escalate to the controlling source of truth and record the source, version/date, and locator before publication.
Should Book Series Bible show one “last updated” date or track verification at the claim level?
Use a page-level revision date for editorial history, but do not let it imply that every statement was reverified on that date. Changeable facts, quotations, policies, project facts, market data, provider capabilities, and other consequential claims should carry a source record with their own last-verified date or version and a specific recheck trigger. Stable editorial synthesis and original instructional examples can use the page revision/version record instead. When a material correction, retraction, or recommendation change affects what the reader should believe or do, retain the prior record and disclose what changed and why.
How do I know whether a claim or source on a Book Series Bible guide is stale, corrected, or still active?
Do not infer status from the page-wide update date. Check the controlling source or project record, the exact version/date last verified, and the trigger that could make the item changeable. Keep it active when the source still controls the exact claim; mark review due when a trigger has fired but the conclusion is not yet disproved; mark stale when the old version no longer controls; and use corrected, retracted, withdrawn, or superseded when the editorial history requires it. The correction level should match reader impact: cosmetic edits are not the same as a material factual correction or a critical source failure.