Story Bible vs. Continuity Tracker: What’s the Difference?

A story bible gives writers a central place to keep character descriptions, worldbuilding notes, place names, timelines, and the rules of a fictional world. When a writer forgets what color eyes a protagonist has, which faction controls a city, or whether magic requires a spoken incantation, the story bible holds the answer.

That kind of reference is useful. Many long manuscripts also need a second kind of record: what is true at a specific point in the story. A story bible might tell you that Elena and Marcus are uneasy allies. It may not tell you whether they still distrust each other in chapter 15, after the rescue scene and the confession.

What a story bible records

A story bible records stable facts about the world: the layout of the capital city, the name of the ruling faction, the rules of the magic system, the protagonist’s backstory, and the geography of the continent. These facts usually exist outside a single scene. The city existed before page one. The magic system has rules before any character explains them.

Story bibles are especially useful for fantasy, science fiction, historical fiction, and long series. They help writers keep names, rules, histories, geography, and recurring details consistent across a large project.

Common story bible tools include Notion, World Anvil, Campfire, and organized folders of documents. Most of these tools use a wiki-like structure: pages for characters, places, factions, events, and concepts, with links between related entries.

Where a story bible starts to struggle

A story bible gets harder to use when the thing being tracked changes across the manuscript.

Imagine a story bible page for Elena and Marcus. During planning, the entry says they are uneasy allies who distrust each other. In chapter 11, Elena reveals a confidence. Marcus comes through in a crisis. By chapter 15, they rely on each other in a way they did not at the start.

If the story bible still says “uneasy allies,” the entry may describe the beginning of the book but not the middle. If it is updated to “trusted allies,” the old state disappears. When the writer returns to that page in chapter 25, the entry may no longer show when the relationship changed or what was true before the change.

The same problem appears with character knowledge, physical state, emotional state, political control, and unresolved secrets. These details change through the story. A single current-version wiki page can hide the path from one state to the next.

Why this matters during revision

Revision makes the problem more obvious. Moving a chapter, cutting a subplot, adding a scene, or changing the timing of a reveal can shift what is true downstream.

If Elena’s moment of trust with Marcus moves two chapters later, the following scenes may need to change. Dialogue that once made sense may now sound too familiar, too cold, or too informed. The story bible can still describe the characters and the world, but it may not show whether the trust existed before or after the moved scene.

This is why major revision can feel unmanageable even when the prose is working. The writer has lost track of the story’s state at each point in the manuscript and has to reread to reconstruct it.

What a continuity tracker records

A continuity tracker records changes at the scenes where they happen. Instead of keeping one character page that tries to describe every version of Marcus, the writer records scene-level notes: what changed in this scene, what Marcus now knows, what he still misunderstands, and how his relationship with Elena stands after the scene.

Those notes can be read from any later point in the manuscript. If the writer opens chapter 22 and asks, “What is true about Marcus here?” the answer comes from the notes attached to the scenes before chapter 22.

A story bible records the world. A continuity tracker records the changing state of the story as the manuscript moves from scene to scene.

Which one does the project need?

Many long projects need both. The balance depends on where the complexity lives.

Heavy worldbuilding, stable facts: a story bible is the better starting point. If the project depends on magic rules, geography, history, factions, invented languages, or background lore, the writer needs a clear reference for those facts.

Character-driven stories with shifting dynamics: a continuity tracker becomes more useful. Mysteries, thrillers, family dramas, literary fiction, and relationship-heavy stories often depend on what characters know, what they hide, how they feel, and how relationships change over time.

Long series with both kinds of complexity: separate the two records. Use the story bible for stable facts about the world. Use the continuity tracker for what is currently true in book two, book three, or book four. Mixing both jobs into one giant database often creates entries that are half reference page and half revision log.

A simple way to sort the notes

Here is the practical distinction:

• “Elena is a forensic archivist who grew up in the northern territories” belongs in a story bible. It is a stable fact.
• “Elena does not know that Marcus was involved in her father’s disappearance” belongs in a continuity tracker. It is true at a specific point and may change later.
• “The city of Vethara has three districts and a contested harbor” belongs in a story bible.
• “As of chapter 18, Faction A holds the harbor and Faction B has retreated to the second district” belongs in a continuity tracker.

If the note describes what exists, put it in the story bible. If the note describes what is true right now, attach it to the point in the manuscript where it becomes true.