AI Features
Check a script for continuity issues
Continuity checking scans your script for inconsistencies between scenes — a time of day that does not follow from the scene before it, a set named two different ways, an INT/EXT that does not match the action, or a malformed heading. It flags each one as a warning you can jump to, apply, or ignore, and builds a timeline analysis of your story days. This article explains how the check works and how to read its results. For the click-by-click steps, see Continuity warnings.
How continuity checking works
The check combines a fast deterministic engine with AI:
- A deterministic engine resolves each scene’s story day and time of day and flags time-of-day sequence problems and heading-notation errors. This part is objective.
- An AI pass reads scene headings and a little body text to flag INT/EXT mismatches, inconsistent set names, and day/night contradictions (a heading time of day that its own action contradicts), using the engine’s timeline as context. This part is interpretive and can occasionally produce a false positive.
Both feed a single list of warnings. The engine also produces the timeline shown in the Analysis tab. Continuity checking runs as a background job and uses credits at 1 credit = 1 scene processed, charged only when the run succeeds.
Run a check
To run a continuity check, open the continuity popover from the script viewer’s footer, then select Run Continuity Check. Progress shows in the popover as the job runs. To check only part of the script, turn on Scene range and pick the From and To scenes before running.
[SCREENSHOT: The continuity popover with the Run Continuity Check button and the Scene range toggle]
Re-running replaces the current warnings but keeps any you have ignored, so your dismissals never reappear. For the full procedure, see Continuity warnings.
Read the results
The popover has two tabs: Warnings and Analysis.
Warnings tab
The Warnings tab lists every active issue. Each warning shows:
- The scene number, which you select to jump to that scene.
- A category label (see the reference below).
- A description of what is wrong.
- A suggested fix, where one applies — shown next to a lightbulb, often as a
current value → suggested valuehint.
For each warning you can:
- Select Apply to accept the suggested heading fix and mark the warning resolved. Apply appears only when the warning carries a suggested value.
- Select Ignore to dismiss the warning as a false positive.
- Select the Completed checkbox to mark that you have handled it by hand.
To clear everything at once, select Ignore all warnings at the bottom of the tab.
Analysis tab
The Analysis tab is a timeline overview from the deterministic engine. It shows the Total Script Days the script spans, then one row per scene with the scene number, its assigned story day, its resolved time of day, and a confidence dot. These story-day assignments are useful for scheduling, because they tell you which scenes happen on the same story day.
[SCREENSHOT: The Analysis tab showing Total Script Days and a per-scene list with story day, time of day, and confidence dots]
The confidence dot shows how sure the engine is about a scene’s day resolution: green for high, amber for medium, and red for low. The color always appears with the word “high,” “medium,” or “low” in the legend and tooltip, so it never carries meaning alone.
Reference
Warning categories
The check flags five categories of issue:
| Category label | What it catches | Source |
|---|---|---|
| INT/EXT mismatch | The scene’s INT/EXT does not match the action or its set. | AI |
| Set name | The same set is referred to inconsistently across scenes. | AI |
| Day/night | A scene’s heading time of day contradicts its own action (e.g. a DAY scene described with moonlight or darkness). | AI |
| Time of day | The time of day does not follow logically from the previous scene. | Engine |
| Notation | A scene heading is malformed or uses incorrect notation. | Engine |
Warning severity
Each warning carries a severity of error, warning, or info.
Tips
- Run a check after each new revision. New drafts often introduce timing or naming inconsistencies.
- Treat engine-flagged issues (time of day, notation) as objective. Treat AI-flagged issues (INT/EXT mismatch, set name) as interpretive — confirm them before acting.
- Do not dismiss warnings too quickly. A time-of-day warning can reveal a genuine script error the writer needs to fix.