Workflow

Two Kinds of Continuity Work: Tracking as You Go vs. Investigating Later

June 2026

When designing Scriptri, the starting assumption was that writers know what matters while a scene is being written.

Sometimes that is true.

A character learns a secret. A relationship changes. A weapon is introduced. A promise is made. A wound appears. The assumption was that the writer knows when a detail will matter later, so they record it immediately.

That is proactive continuity tracking: keeping the story’s state up to date as the manuscript grows.

But it turns out that is only half the work.

The other half happens later, often during revision, when a writer runs into a question they did not know they needed to track.

  • When did Elena’s sleeve become torn?
  • Which mug is this scene talking about?
  • Did Marcus already know about the ledger?
  • Was the North Annex locked before the confrontation?
  • Where was the blue key last seen?

These are not always details a writer can predict. They emerge after the manuscript has accumulated enough history to become difficult to hold in memory — even for details the author has explicitly recorded in their notes.

The problem becomes different: how do you find the details of a thread you need to track, but did not record, retroactively?

That is reactive continuity investigation.

Proactive tracking: record what changes

Proactive tracking is the clean version of continuity work.

After writing or revising a scene, the writer records what changed:

  • A character learns something.
  • A relationship shifts.
  • An object changes hands.
  • A location becomes important.
  • A clue is revealed.
  • A continuity concern needs review.

This works especially well for obvious state changes. If a detective discovers the killer’s motive in chapter 12, that belongs in the continuity record. From that point forward, the writer can check later scenes against that fact.

Proactive tracking turns a manuscript into a sequence of remembered story states — often states that are not explicitly stated in the scene itself. They may represent background information, inferred state, or continuity information the story relies on later.

But it has a limitation: it depends on the writer knowing what deserves a note.

Reactive investigation: recovering what became important later

Writers do not always know what will matter.

A background object becomes symbolic. A throwaway detail creates a contradiction. A character’s offhand comment suddenly affects the logic of a later reveal. A small physical description becomes important thirty scenes later.

At that point, the writer is no longer asking, “What should I record now?”

They are asking, “Where did this start?”

That is reactive investigation.

The writer has a question and needs to trace backward through the manuscript:

  • Search for possible references.
  • Decide which matches are relevant.
  • Separate similar objects or names.
  • Find the scene where the important fact first appeared.
  • Turn that discovery into structured memory so the same question does not have to be solved twice.

This kind of work is harder than ordinary search.

Search can find the word “mug.” It cannot tell you whether this is the same mug, a different mug, a metaphorical reference, or an irrelevant background object. The writer still has to judge the evidence.

This issue can compound when the details of an investigation fade into the background and then resurface later, forcing the author to repeat the same searches through their manuscript and notes again and again.

A good continuity tool should help the writer collect, classify, preserve, and categorize the answers to those questions.

Why both workflows matter

A continuity system that only supports proactive tracking can feel intimidating.

It asks the writer to predict the future importance of every detail. That is too much pressure. Writers should not have to maintain a perfect database while drafting. Stories are exploratory. Details become important at different times.

A continuity system that only supports reactive search has the opposite problem. It helps the writer find things later, but it does not preserve story state as the manuscript evolves. The same questions keep coming back because the answers are not carried forward.

The stronger model is both:

  • Track obvious changes as they happen.
  • Investigate unclear details when questions appear.
  • Convert discovered answers into reusable continuity records.

This turns continuity from a static note archive into a living story-state index.

Where Scriptri is headed

Before discussing features, a design principle worth naming: the goal is always that the writer remains the source of truth, but Scriptri helps uncover what has already been decided and reconcile conflicts as they appear.

Scriptri currently focuses on proactive tracking: scenes, entities, notes, At This Point, continuity flags, timeline events, and time queries. That is the foundation.

But the longer-term direction is broader. Scriptri should also help writers investigate continuity questions after the fact, and provide context-aware workspaces to answer questions as the world and story are built out.

The goal is to support a workflow like this:

  1. A writer notices a continuity question.
  2. They search across scenes, notes, entities, flags, and events.
  3. Scriptri surfaces possible evidence.
  4. The writer marks results as relevant, irrelevant, unclear, or a different object or entity.
  5. The writer converts the answer into a note, timeline event, location event, or resolved concern.
  6. Future scenes can use that answer instead of forcing another reread.

For example:

A writer asks, “When did Elena’s sleeve become torn?” They find the escape scene where it happened. They create a continuity note: “Elena’s sleeve is torn during the escape.” From then on, that detail is not just a search result — it is part of the story’s remembered state.

Continuity is not just remembering facts

Continuity is not only a checklist of names, dates, and props.

It is the changing truth of a story over time. What a character knows. What they believe. What they carry. What they have lost. What has been revealed. What remains unresolved. What the reader knows that the character does not. And hundreds of other questions like those.

Some of that can be tracked as the story is written.

Some of it has to be discovered later.

Scriptri is being built for both kinds of work: the notes you make as you go, and the investigations you need when the story has become too large to keep entirely in your head.

Scriptri is a continuity tracker for fiction writers

Associate characters, places, objects, and other entities with your scenes, write state-change notes as you draft, and use the “At This Point” panel to see what is true at any scene position. No account required, and your manuscript stays in your browser.

Try Scriptri free