Once a learning scenario branches, each route has its own history. A character may have received a clarification in one version but not another. If the next scene assumes both conversations happened, the learner faces an incoherent situation. Create a branch record before filming so every continuation follows from information actually available on that route.
Record state as well as scene order
A diagram showing arrows between video clips is a useful start, but it does not explain the content carried along those arrows. For each branch, note what was said, what was agreed, what remains unknown and any visible object that changed. Those notes let the writer and editor check the logic rather than relying on memory.
Give branches stable identifiers that do not depend on the eventual filenames. A scene may be renamed during production without changing its place in the exercise. Keep the content map separate from the delivery platform's implementation, and have the appropriate learning or technical owner confirm that implementation.
In a hypothetical scenario, a coordinator can clarify whether a draft is for discussion or for formal issue. One branch establishes that it is for discussion; another proceeds without that clarification. The later response should reflect the information obtained on the chosen route. It should not accuse the second viewer of ignoring an answer that only appeared in the first branch.
Film shared scenes only when their assumptions match
Reusing a continuation can reduce the amount of footage, but the shared scene must be valid for every route that reaches it. Check pronouns, references to earlier statements and visible document status. A line such as as we agreed earlier may work in only one branch even when the room and performers look identical.
If routes reconverge, decide what information has genuinely become common by that point. A short recap can establish shared ground, provided it does not pretend that earlier choices were identical. Otherwise, record separate continuation lines. The production saving from a shared clip is not worthwhile if it erases the consequence the exercise was designed to explore.
Use a continuity sheet during the shoot. Before each take, tell performers which route they are in and what their characters know. Shooting out of story order is manageable when that context is explicit. It is risky to assume the actors will infer it from a numbered script page.
Review complete routes rather than isolated clips
A subject reviewer may approve every clip and still miss a broken connection. Assemble or simulate each permitted route and review it from beginning to end. Check that the viewer receives the necessary information, that consequences follow the selected response and that the feedback refers to the route actually taken.
Keep a route-level issue log. An error may belong to a transition or choice label rather than to a single video. The finished resource should preserve a coherent account for every learner path, not merely a folder of individually plausible scenes.
Discuss the production brief
Review Live Images services and ask about suitability for the filmed elements you need. Agree who owns the subject matter and any specialist review before booking.
Editorial basis
Original production-planning guidance with hypothetical examples. This article does not establish employment, safety, legal or assessment requirements. Search intent is an editorial hypothesis, not measured demand. AI-assisted unpublished draft.