# How should you order scenes for a complex procedure?

Author: AUTOVID Editorial Team
Published: 2026-11-21
Updated: 2026-11-21

![Abstract shapes show preparation and action, two alternative paths, and a merge into a final inspection with a magnifying glass.](https://autovid.net/blog-media/autovid_blog/images/generated-1795265933583-f565b40a15ae/1795265946699-blog-plan-complex-procedure-scene-order.webp)

Order a complex tutorial around prerequisites: first define the finished state, then arrange the scenes needed to reach it. Pair each action with a check that establishes readiness for the next step, and explain alternative paths separately before they rejoin. Use the order viewers can follow, rather than the order in which you recorded the footage.

For a document-export tutorial, completion might mean confirming that the recipient can open the file, rather than merely clicking Save. The workflow below is an editorial planning method using scene cards. Verify the actual requirements in the tool and environment you are demonstrating.

## Work backward from a verifiable end state

Scene order should establish the conditions needed for the next action. Describe the final result in one sentence, then ask what must already be ready immediately before it. For the export example, work backward through checking the output, exporting, choosing output settings, and preparing the source. Then arrange those steps in execution order.

Give each scene card a starting state, an action, and a visible result. If an operation could overwrite the original, place the backup step and warning before that operation. Not every click needs its own scene, but a click that changes the conditions for the next action should not disappear without explanation.

You can briefly preview the finished result at the beginning of the video. Clearly distinguish that preview from the steps viewers are about to perform, then restart the demonstration with preparation. Showing the outcome early must not imply that required preparation can be skipped.

## Follow each action with a check

An action scene should end with evidence that the viewer can proceed. Show the applied value after changing a setting, the created file after exporting, and the file contents when checking the result. Name the item being checked in the narration and make it identifiable on screen.

Do not rush a reading or comparison task with a sound cue or quick transition. During review, check whether the value can be read and distinguished from its previous state, then set the scene duration. Use the verification task to judge timing instead of assigning the same number of seconds to every step.

If you removed trial and error from the recording, compare the states on either side of the cut. When a selection or open window changes without explanation, restore the necessary action or state what preparation happened off screen. Removing elapsed time should not silently remove a required condition.

## Explain branch conditions and where paths rejoin

Alternative paths are not consecutive steps that every viewer must perform. Suppose a setup has one path requiring extra verification and another that does not. Before the split, explain how viewers identify their case. Restate who each demonstration applies to so viewers do not mistake both paths for a single sequence.

At the end of the alternatives, show the shared state required to rejoin the next scene. The illustration in this article is a conceptual map: preparation and action lead to a split, and the paths rejoin for a result check. When adapting it to a real procedure, write the selection condition at the split and the required state at the merge.

If a common failure prevents progress, explain the stopping condition and which preparation step to revisit near the relevant check. Move lengthy, uncommon exceptions into a supplemental section, but do not edit the main route as if a failed step had succeeded. Do not invent a recovery method you have not verified.

## Walk through the procedure using only the scene cards

Reviewing scene order means looking for hidden prerequisites between scenes. Give the script and cards to someone unfamiliar with the plan and ask them to follow the procedure from the real starting state. If reviewing alone, return after a break and reproduce it using only the information in your notes. Mark every point where you had to guess.

When preparing a long-form draft in AUTOVID, you can review chapter titles and summaries and request revisions to a selected chapter. Specify a missing condition, such as: ‘Explain how to copy the source before changing export settings, and add a result check after the action.’ A person must verify that the revised draft matches the actual procedure and that the materials used are cleared for use.

For the final review, follow the main route and each alternative separately, checking their starting states, stopping conditions, and shared rejoining state. Fewer scenes alone do not make a sequence complete. The sequence connects when the result of one scene gives viewers what they need to begin the next action.

[Learn more](https://autovid.net/de/features)
