Practical framework / 5 MIN READ
Track continuity across a filmed instructional sequence
Record the state of the task between shots so an edit does not imply that an essential action happened without being shown or explained.
AI-assisted research and analysis for the SNS Creative Fieldbook
Sources checked 2026-11-06
Instructional continuity includes more than matching appearances. The object, settings and demonstrated result must remain logically consistent as separate takes become one explanation.
What you will leave with: Leave with a continuity record that connects each shot to the task state the viewer needs to understand.
Use this when
- A demonstration is filmed out of sequence.
- Close-ups come from different takes than the wide shot.
- An edit makes a process appear to skip a necessary step.
This focuses on state and continuity in filmed instruction, not general B-roll planning, procedural safety certification or permission to conceal a failed demonstration.
Map the task states before filming
List the important condition before and after each demonstrated action. For a simple craft example, that might include which pieces are attached and which tool is in use. For software, it may include the selected document, settings and saved state. Identify changes that cannot be reset easily and plan their recording order carefully. Keep the authoritative procedure separate from the shooting order. The editor should know what the viewer must understand even when production records the final result first. If a step is omitted for time, plan an honest explanation rather than relying on a visual jump to hide it.
Record continuity with usable identifiers
ScreenSkills describes script-supervision records that connect action, dialogue and production details across shots. Use a proportionate version for the instructional sequence: identify the scene, take and relevant task state, and capture reference images when authorized. Record changes that affect meaning rather than every decorative detail equally. Make the notes findable alongside the footage. A photograph of the setup is most useful when it is tied to the correct take and explains what must match. Do not rely solely on the demonstrator remembering the exact state several hours or days later.
Check transitions before leaving the setup
Compare the end of one shot with the start of the next planned shot. Check object orientation, settings, quantities and any action that changes what the viewer believes is happening. If a close-up needs a reset, confirm that the reset does not create an impossible intermediate state. Capture an appropriate transition or explanation where needed. Raise continuity issues while the setup still exists, but do not repeat unsafe or destructive actions just to obtain a match. The production lead and subject expert should decide on a truthful alternative when a step cannot be recreated responsibly.
Review the assembled instruction for missing logic
Watch a rough edit with someone who knows the task and someone who did not see the filming. Ask each to describe the sequence and identify anything they had to infer. A seamless-looking cut can still conceal a necessary operation, while a clearly signposted time jump may be entirely honest. Verify that the final result belongs to the demonstrated conditions rather than a different preparation. Keep continuity notes available for revisions and pickups. If footage cannot support the intended explanation, revise the explanation or reshoot appropriately instead of using editing to imply evidence the team did not capture.
Make the reasoning concrete.
A hypothetical studio films a paper-model assembly demonstration with wide shots and close-ups recorded separately.
Appearance-only match
Opening: The editor matches hand position but uses a close-up where an extra tab has already been secured.
Hypothesis: The cut looks smooth.
Risk: The viewer cannot understand how the model reached its new state and may miss an essential action.
Task-state continuity
Opening: The team records the state for each take and checks that the assembled sequence accounts for every required attachment.
Hypothesis: The explanation remains reproducible and truthful.
Risk: Some transitions may need a brief spoken explanation or a new shot.
The editor adds a captured intermediate step and rejects a result shot that belonged to a differently prepared model.
Take the questions into your next brief.
Use these prompts in your own notes. Nothing is submitted from this page.
States
What must be true before and after each action?
Records
Which take and reference image document that state?
Transitions
Does the next shot start from a compatible condition?
Omissions
Which time jumps or skipped actions need explicit explanation?
Edit
Can a fresh viewer explain the complete process without inventing a step?
Watch for the wrong conclusion.
- Tracking appearance while ignoring task state.
- Combining takes with incompatible settings.
- Using a result from a different preparation without disclosure.
- Discovering missing transitions only after dismantling the setup.
Your next action
Choose one filmed process and annotate the before-and-after state of each shot before approving its rough edit.
Sources & scope
The framework, examples and suggested checks are original editorial synthesis. Hypothetical examples are not measured results. Source checking is not an independent audit or a guarantee of business outcomes. No named human reviewer is claimed.
- ScreenSkills: Script supervisor →Primary publisher guidance · Supports: Supports continuity breakdowns and written or photographic records connecting action, dialogue and production details. The instructional-state checks here are original synthesis, not a complete training course in script supervision.