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

In my personal writing projects, I usually start by creating two documents. One has the working title of my manuscript. The second has the same title with “(Notes)” added to the end.

In my longest unfinished draft, the notes document contains around 20,000 words of organized, categorized, and color-coded lore. It includes characters, relationships, history, cultures, world rules, and whatever else I decided I needed while writing.

It can be tedious scrolling through that behemoth of a document, searching for some bit of worldbuilding I remember recording but that has long since slipped out of my working memory. Still, the document does its job. It gives me somewhere to put details I might need again.

My process is probably familiar to plenty of writers. There are countless guides and videos explaining how different authors approach worldbuilding, when they begin planning, and how much they develop before drafting prose. My own process is a mixture of learning from other writers and stumbling through the details as the manuscript demands them.

But in one of my unpublished drafts, I ran into a problem that my normal notes document was not especially good at solving.

The story was tightly bound to its characters’ history. A major event initially occurred four years before the manuscript began. Then I moved it to two years in the past. Later, it became just shy of three years, or sometimes vaguely “more than two years ago.”

One of the main character’s daughters had been born after that event. As the timeline shifted, so did her possible age.

The latest version of my notes could tell me when the event was now supposed to have happened. What the notes could not easily tell me was every place in the manuscript that still depended on an earlier version of the timeline.

A character might say that the girl was almost three years old. Another scene might refer to something her mother did shortly after the birth. Dialogue between characters might imply that four years of history had passed between them, even though the revised timeline now allowed less than three.

Eventually, I lost track of which version the manuscript actually supported.

I still plan to return to that story someday. Maybe some of you are reading this article in a future where I have finally published it.

Story Bibles Describe the Project’s Reference Model

My notes documents were effectively story bibles.

A story bible is a place to record information about the people, places, systems, history, and terminology of a writing project. It is usually organized around the things that exist in the story and the relatively stable information attached to them.

For example, I might create notes about a holiday celebrated twice a year on a distant, world-spanning city inhabited by trillions of people.

I could record the customs, foods, festivals, and traditions that distinguish the two seasonal versions of the holiday. I might decide whether local governments recognize it as mandatory paid leave, whether it is usually celebrated with family or romantic partners, or whether different cultures within the city approach it differently.

A character page might contain physical details such as hair, eyes, height, build, and common clothing. It could also include her birthday, family connections, hobbies, background, beliefs, and general outlook on the world.

Those details may be developed before drafting begins, or they may be added gradually as the manuscript creates a need for them.

This kind of reference information answers questions like:

• What is this?
• Who is this person?
• How does this part of the world work?
• What history or background do I need to remember?

A story bible is very good at answering those questions.

Where Story Bibles Become Awkward

The problem begins when the thing being described changes over the course of the manuscript.

A character page may say that Elena distrusts Nathan. That may be true at the beginning of the novel.

Later, Nathan protects her during an attack. Elena begins to reconsider her opinion of him. Several chapters after that, she chooses to trust him with something important. Then she discovers that he lied about part of their shared history.

What should Elena’s character page say?

If it says she distrusts Nathan, it describes the beginning of the story but not the middle.

If I update it to say that she trusts him, the page no longer describes her earlier state.

I could record every stage of the relationship on the same page, but the character reference gradually becomes a chronological history. It is no longer only answering who Elena is. It is also trying to explain what she believed at several different points in the manuscript.

That is not necessarily wrong. A story bible can contain changing information.

The awkwardness is that the page is now being asked to answer two different questions:

What is generally true about Elena?

What is true about Elena at the scene I am currently writing?

The second question depends on time and position in the manuscript.

Continuity Tracking Describes What Is True Here

The distinction I find useful is not really between two kinds of software. It is between two kinds of information.

A story bible often holds reference information about the project.

Continuity tracking preserves information whose answer changes depending on where you are in the story.

That might include:

• What Ethan knows about his girlfriend’s history before an argument
• How much fuel remains in Nathan’s beat-up Hyundai after a road trip
• Which districts have been evacuated before a volcanic eruption
• Whether Betty knows that Ethan hid her mail
• How old a child must be during a particular conversation
• Who possesses an important object at the end of a scene
• Whether two characters have repaired their relationship yet
• What condition a damaged location is currently in

These questions do not have one answer for the entire manuscript.

Their answers change as events happen.

That is what I mean by continuity tracking. It is a way of preserving meaningful state changes at the point in the manuscript where they occur.

If Elena learns that Nathan lied in scene 14, that knowledge becomes part of her state from scene 14 forward. It should not influence her behavior in scene 8. It should influence how she interprets him in scene 18.

The important part is not simply recording that Elena eventually discovers the lie. It is preserving when that discovery becomes true for her.

One Story Element Can Need Both

The same character, place, object, or system may need both reference information and time-bound state.

A character page can explain who Elena is, where she came from, what she looks like, and what she generally values.

Continuity notes can preserve what Elena knows, believes, possesses, or feels at different points in the manuscript.

A story bible can describe a city’s geography, history, government, and culture.

Continuity tracking can record that one district is evacuated in chapter 12, the harbor is captured in chapter 18, and the eastern bridge collapses in chapter 23.

A reference page can explain how a starship normally functions.

Continuity notes can record its remaining fuel, current damage, disabled systems, and whether repairs have been completed yet.

The information can live in separate tools or in the same one. The difference is the job the information is being asked to perform.

If I expect a note to answer “What is this?”, it is probably reference information.

If I expect it to answer “What is true here?”, it probably needs some connection to narrative position.

Why the Difference Matters During Revision

The timeline problem in my unfinished novel was not simply that I changed a fact.

Changing the date of the historical event affected every scene that relied on how much time had passed since it occurred.

The story bible could preserve the newest version:

The event happened just under three years ago.

But that did not automatically identify every line of dialogue, character age, anniversary, memory, relationship, or sequence of events that still depended on the four-year version.

This is where continuity becomes more than a collection of static facts.

Much of a narrative consists of changes accumulating through time. Characters grow. Relationships develop. Places are damaged. Objects are lost and recovered. Earlier events restrict what can happen later.

When revision moves one of those events, the effects can spread through the manuscript.

Suppose Elena originally began trusting Nathan in chapter 11. Several later conversations were written with that trust already established.

During revision, the scene that earns her trust moves to chapter 19.

Her general character page may still correctly say that she eventually trusts him. But scenes 12 through 18 now happen before the change.

She may speak too openly. She may share information she no longer has a reason to share. Nathan may rely on a level of trust that the revised manuscript has not yet earned.

The broad description is not necessarily wrong. The timing is.

How Scriptri Fits

Scriptri is being developed to connect reference information with the manuscript’s changing state.

An entity such as a character, location, object, faction, or concept can have descriptive information attached to it. It can also have notes connected to the scenes where something changes.

If Elena discovers a secret in scene 14, I can record that change against both Elena and the scene where she learns it.

Scriptri’s At This Point view can then bring forward the relevant notes established through the place in the manuscript I am currently working.

That does not make timeline revision automatic. Moving a historical event still requires judgment about which parts of the manuscript depend on it.

But scene-bound information gives me anchors. Instead of searching through a 20,000-word notes document and trying to remember which version of the story each paragraph describes, I can connect important changes to the manuscript itself.

Scriptri currently supports both descriptive information and scene-bound notes, although its strongest tools are still focused on changing story state. Broader worldbuilding and lore features are continuing to develop.

The goal is not to replace story bibles or force all writing information into one undifferentiated system.

A character page should be able to explain who the character is.

The continuity record should be able to show what has happened to them.

The Difference Is Time

A story bible helps answer:

What is true about this story world?

Continuity tracking helps answer:

What is true at this point in the story?

Some projects can keep both kinds of information in the same document without much difficulty. Other manuscripts become complicated enough that reference information and changing state begin to compete with each other.

That is the gap that led me to build Scriptri.

The story bible tells me about the thing.

Continuity tracking tells me what has happened to the thing by the time it gets here.