Using Scrivener for Continuity: What It Does Well and Where It Falls Short

Scrivener is one of the strongest manuscript management tools available to fiction writers. Its binder, corkboard, outliner, document notes, custom metadata, and scene-level structure make it a natural fit for long novels, scripts, and series.

It also gives writers several places to store continuity notes: document notes, synopsis cards, labels, keywords, metadata fields, and research files. The hard part is turning those separate notes into an answer to a scene-specific question: what is true at this point in the story?

Scrivener can remain the main drafting tool. A continuity tracker can sit beside it and track the state that changes from scene to scene: what characters know, what relationships have shifted, what objects moved, and which facts need to stay true later.

What Scrivener does well

Scrivener’s project tree maps well to manuscript structure. A folder can hold a chapter. Documents inside it can hold scenes. That setup lets writers see the shape of the manuscript, move scenes without copying and pasting, and split or merge material as the draft changes.

Scrivener also gives writers useful supporting tools:

• Document notes are free-text notes attached to a specific scene. Writers use them for revision reminders, scene intentions, loose ideas, and continuity details.
• Custom metadata lets writers add fields to scenes, such as POV, location, timeline, draft status, or subplot.
• Synopsis cards give each scene a short summary that can be viewed on the corkboard or in the outliner.
• The research folder keeps reference material, images, web archives, and planning documents in the same project as the manuscript.
• Collections let writers group or filter scenes by search results, status, POV, or other criteria.

Those features are useful for organizing a manuscript. They can also support some continuity work, especially when a writer already has a strong note-taking habit.

Where continuity gets hard

Scrivener usually attaches information to individual documents. A note about scene 14 lives in scene 14. You can search for it, open it, or review it in context, but Scrivener is not designed to gather those notes into a running answer to a question like: “What does Marcus know at the start of chapter 22?”

Custom metadata has the same limit. A writer can create a “Character State” field for each scene, but checking a character’s state across the whole manuscript still means scanning documents and rebuilding the answer by hand.

A synopsis card summarizes what happens in a scene. A continuity note records what changes because of the scene. Those are related jobs, but they are not the same job. A synopsis might say, “Elena confronts Marcus in the library.” A continuity note might say, “Elena now knows Marcus lied about his location. She decides not to reveal that she knows.” The second note helps you write the next scene.

Common Scrivener continuity workarounds

Scrivener writers often build their own continuity systems. These can work, but each one gets harder to maintain as the manuscript grows or changes shape.

The character sheet document. Some writers keep one research document for each major character. That works well for stable information: age, appearance, background, family, personality, and role in the story. It gets messier when the same page also tries to track what the character knows in chapter 5, chapter 18, and chapter 32.

The running continuity document. Some writers keep a long log: “After scene 14, Elena knows X. After scene 17, Marcus discovers Y.” This can work for a stable draft. It becomes fragile when scenes move, merge, or disappear during revision.

Keywords as tags. Scrivener keywords can mark which characters, places, or subplots appear in a scene. That helps with filtering. It does not tell you what a character knows, feels, believes, or carries into that scene.

Spreadsheets alongside Scrivener. Many writers eventually create a spreadsheet for character state, scene by scene. This works, but it creates a second system that must stay in sync with the manuscript. Any restructure in Scrivener usually means a matching cleanup pass in the spreadsheet.

A two-tool workflow

Scrivener and a continuity tracker can handle different parts of the job:

• Scrivener handles drafting, scene order, manuscript structure, research, compile, and export.
• A continuity tracker handles changing story state: character knowledge, relationship shifts, physical state, faction changes, continuity flags, and the question “what is true here?”

The practical problem is sync. If the manuscript lives in Scrivener and the continuity record lives somewhere else, the continuity tool needs a way to import and refresh the scene structure without turning every revision into duplicate data entry.

Scrivener import and refresh in Scriptri

Scriptri can import zipped Scrivener projects directly. Create a zipped backup of the Scrivener project (File → Back Up → Back Up To…, with “Back up as zip file” selected), then import that zip into Scriptri. Scriptri brings in the scene structure, titles, and text so the continuity record can start from the existing draft.

After import, associate the relevant characters, places, objects, factions, or concepts with each scene. Then add continuity notes for what changes in that scene: what a character learns, what a relationship becomes, what object moves, what location changes, or what open question needs to be flagged.

When the Scrivener project changes, export a new zipped backup and use Scriptri’s refresh flow. Scriptri compares the new upload against the scenes previously imported from Scrivener. It shows which items appear changed, new, unchanged, or missing, then lets you choose what to import or replace.

In the current beta, refresh is conservative. Replacing a scene updates the manuscript text while preserving the Scriptri scene record and its existing continuity notes. Refreshed scenes should be reviewed before relying on their carried-forward context, because the manuscript text may have changed enough that the scene’s entity associations or notes need cleanup. Scriptri does not write back to Scrivener, and it does not automatically delete scenes that are missing from a later Scrivener upload.

What this looks like during revision

Say you are revising a mystery novel. In Scrivener, you move two second-act scenes earlier and add a new confrontation scene. Then you export a zipped backup and refresh the project in Scriptri.

Scriptri shows which imported Scrivener documents changed, which ones are new, which ones are unchanged, and which ones are missing from the latest upload. After choosing which scenes to refresh, you review the refreshed scenes, update entity associations if needed, and use the “At This Point” panel to check whether the characters still have the right carried-forward context.

If the restructure changed what a character should know at that point, update the relevant note. The review happens against visible scene context instead of memory alone.

Does Scrivener replace a continuity tracker?

Scrivener is a manuscript management tool. It is excellent at holding scenes, drafts, notes, research, metadata, and structure. A continuity tracker has a narrower job: gather scene-level notes into a usable view of what is true at a specific point in the story.

For many writers, the cleanest split is simple. Scrivener is where the manuscript lives. The continuity tracker is where changing story state gets recorded and checked.