A series bible gives you one reliable place to track characters, relationships, worldbuilding rules, chronology, naming choices, unresolved threads, and installment summaries. This guide includes a practical series bible template, a maintenance workflow, and review checkpoints that can help prevent continuity errors as your fiction expands.
Overview
A series bible is a working reference document for a connected set of books. It is not a substitute for your manuscript, outline, or scene list. Instead, it records the details you need to preserve across drafts and installments: what happened, when it happened, who knows about it, which rules apply, and what remains unresolved.
The most useful bible is neither the longest nor the most decorative. It is the one you can update quickly and consult without hesitation. A simple document with clear headings may serve a short trilogy better than a complex database. A large fantasy, science-fiction, mystery, or romance series may benefit from linked notes, tables, or a spreadsheet. Choose a format that reduces friction rather than creating another project to manage.
Use the bible as a continuity control center at three stages:
- During drafting: record new facts as you establish them, especially facts that could affect later books.
- During revision: compare the manuscript against the bible and resolve contradictions before copy editing.
- Before publication: verify names, dates, ages, locations, series order, open threads, and details repeated in marketing copy.
A separate fiction editing style sheet can hold spelling, capitalization, punctuation, and voice decisions. Your series bible should focus primarily on story continuity and the fictional world.
What to track
Start with the sections that protect the story from the errors you are most likely to make. You can add detail as the series grows.
1. Series overview
Write a short description of the series premise, genre, intended reading order, and central conflict. Add a one- or two-sentence summary for each planned or published installment. Keep this section brief enough to scan before outlining a new book.
Useful fields include:
- Series title and working title variations
- Planned number of installments, if known
- Publication or story order, with any difference clearly marked
- Point of view and tense conventions
- Core promises to the reader, such as a mystery structure, romantic arc, or escalating political conflict
- One-paragraph summary of each installment
2. Character records
Create one record for every recurring or continuity-critical character. Include information that can change or cause mistakes, not only broad personality traits.
- Full name, aliases, titles, pronunciation, and naming conventions
- Age, birthday, physical details, and distinguishing features
- Occupation, skills, education, resources, and limitations
- Important relationships and how those relationships change
- Private goal, public goal, fear, belief, and internal contradiction
- Major turning points by installment
- What the character knows, suspects, believes incorrectly, or is hiding
- Current status, location, injuries, possessions, and unresolved commitments
Track character knowledge separately from objective truth. A character may believe an event happened one way while the reader knows otherwise. That distinction is especially important in mysteries, thrillers, unreliable-narrator fiction, and stories built around secrets.
3. Relationships and character arcs
A relationship table can reveal continuity problems that individual character notes hide. Record the relationship at the beginning and end of each installment, along with the event that changes it.
For each major relationship, note the current status, shared history, source of tension, mutual obligation, and next pressure point. For character arcs, list the starting belief, key tests, choices, consequences, and ending belief. If an arc continues into another book, state what has changed and what deliberately remains unresolved.
4. Locations and recurring objects
Give each significant location a stable record. Include geography, access points, distances, climate, sensory details, ownership, security, and changes caused by earlier events. A floor plan or simple route sketch can be more useful than several paragraphs when characters move through a building.
Track recurring objects in the same way. Record who owns an item, where it is, what it looks like, what it can and cannot do, and when it changes hands. This prevents a weapon, letter, heirloom, evidence item, or magical object from appearing in two places at once.
5. Worldbuilding rules
Separate established rules from possibilities you have not yet committed to. For each rule, record its limits, cost, exceptions, origin, and the consequences of breaking it. Avoid using vague notes such as magic works differently here. Write the operational version: who can use it, under what conditions, with what risk, and what other characters understand about it.
Genre-specific records may include:
- Fantasy and science fiction: technology, magic, species, governments, economies, travel, language, calendars, and resource limits.
- Mystery and thriller: crime timeline, evidence chain, alibis, investigative discoveries, false leads, and what each suspect knows.
- Romance: attraction milestones, emotional turning points, relationship status, external obstacles, and the commitments required by the ending.
- Historical fiction: period-specific institutions, customs, transportation, communication, vocabulary, and deliberate departures from the historical record.
- Contemporary fiction: technology, public events, school or workplace calendars, travel times, and references that may date the story.
6. Chronology and continuity log
Build a master timeline independent of the order in which scenes appear. Include dates, approximate times, locations, character ages, travel duration, and overlapping events. Mark uncertain dates instead of silently guessing them.
A useful timeline row might contain: date or story day, event, point-of-view character, location, participants, evidence in the manuscript, and continuity notes. Add a separate list of fixed facts, flexible facts, and contradictions awaiting a decision.
7. Open threads and installment summaries
Record every promise you expect to answer, complicate, or intentionally leave open. For each thread, note where it begins, its current status, planned resolution, responsible characters, and the book in which you expect to address it. Label threads as open, resolved, revised, abandoned, or intentionally ambiguous.
At the end of each installment summary, add a short continuity handoff: where each major character is, what they want next, what they know, and which immediate problem carries forward.
Copyable series bible template
SERIES OVERVIEW Premise: Genre and reader expectations: Reading order: Point of view and tense: Installment summaries: CHARACTER RECORD Name and aliases: Age and birthday: Appearance and distinguishing details: Role and resources: Goal: Fear or false belief: Important relationships: What this character knows: Arc by installment: Current status and location: RELATIONSHIP RECORD Characters: Starting relationship: Shared history: Current tension: Turning points: End state by installment: LOCATION OR OBJECT RECORD Name: Description: Owner or controlling party: Rules, limits, or access: First appearance: Current status: Changes across installments: WORLD RULE Rule or convention: Who knows it: Limits and cost: Exceptions: Consequences: Related scenes: MASTER TIMELINE Date or story day | Event | Location | Characters | Continuity note OPEN THREAD Thread: Introduced in: Current status: Who is affected: Planned resolution or question: Target installment: INSTALLMENT HANDOFF Book and draft status: Major events: Character locations: New facts established: Unresolved threads: Facts to verify before next book:
Cadence and checkpoints
Do not wait until the final book is complete to update the bible. A lightweight recurring workflow is more reliable than a large continuity audit performed from memory.
During drafting
Keep a temporary capture note beside your manuscript. Add details that may matter later: a new birthday, a changed route, an object’s location, a newly established rule, or a character who has learned a secret. Review that capture note at the end of each writing session or chapter group and transfer only confirmed facts into the main bible.
Mark uncertain information with a visible label such as TBD, provisional, or needs verification. This prevents an accidental guess from becoming canon.
At the end of a scene or chapter
Ask four quick questions: What changed? Who knows about it? Where is every important character now? Which resource, object, promise, or injury must carry forward? Answering these questions takes less time than reconstructing the same information months later.
At the end of an installment
Run a continuity pass before starting the next book. Update the master timeline, character statuses, relationship arcs, locations, objects, rules, and open threads. Then write the installment handoff in plain language. This handoff becomes the first reference document for the next outline.
Before a reader-facing revision
Compare the bible with the manuscript rather than treating the bible as automatically correct. The manuscript may contain an intentional change that was never recorded. Once you decide which version is authoritative, update the bible and any affected scenes.
For a broader revision process, use the manuscript revision roadmap. Continuity checking works best after major structural decisions but before final proofreading and production formatting.
How to interpret changes
A changed detail is not automatically an error. Treat each discrepancy as a decision point. First identify whether it affects plot logic, character motivation, reader understanding, or only surface consistency. A changed eye color may require a search and replace. A changed date of a crime may alter the entire mystery solution.
Use a simple priority system:
- Critical: the change breaks causality, reveals an impossible action, contradicts a major rule, or makes a character’s knowledge unclear.
- Important: the change affects a recurring relationship, location, object, timeline, or character arc.
- Minor: the change concerns a small descriptive detail that does not affect the story’s logic but should remain consistent for polish.
- Intentional: the apparent contradiction is a planned reveal, unreliable account, retcon, or unresolved ambiguity. Explain it in the bible so it does not look accidental during the next review.
When revising a detail, search for every dependent reference. A changed character age can affect school years, birthdays, memories, marriage dates, and the ages of relatives. A changed location can affect travel time, weather, scene order, and who could plausibly arrive first. Record these dependencies in a decision log.
Keep version history when possible, particularly if you collaborate with a co-writer, editor, or sensitivity reader. A dated decision log can answer why a detail changed without forcing you to reread several drafts. If you use a writing app, spreadsheet, notes system, or shared document, prioritize reliable search, clear headings, and easy export over advanced features.
When to revisit
Revisit the series bible at least at these checkpoints:
- When you begin outlining a new installment, spin-off, prequel, or companion story
- After completing a first draft or making a major structural change
- Before sending a manuscript to beta readers or an editor
- After receiving feedback that identifies confusion about timing, motivation, names, or world rules
- Before final proofing, publication, or preparing a revised edition
- When a previously published book is corrected or republished
- On a monthly or quarterly review schedule while a series is active
Use a recurring review to check the facts most likely to drift: character ages, names and titles, injuries, relationship status, travel routes, seasonal details, technology, open mysteries, and the order of revelations. If you publish companion content, also compare the bible with your book description, newsletter copy, retailer metadata, and launch materials. The book description checklist and book metadata checklist can help you keep reader-facing information aligned with the final story.
To put the system into practice, create the document now with the template above. Populate only the facts already established, add a decision log, and schedule a short review at the end of your next writing week. Before beginning the next installment, update the character handoffs and master timeline first. That small habit turns the series bible from a static archive into a practical continuity tool you can trust.