• Home
  • Blog
  • Gallery
  • Pricing
  • Home
  • Blog
  • Gallery
  • Pricing
Start creating

Create.Play.

Creator blog

Home/Blog/Interactive Film Workflow

How an interactive film workflow moves from script to shooting: production unit cards

A finished script is not yet shoot-ready. A production unit card hands shared footage, route differences, prop states and open questions to named owners, with checkable evidence for release or return.

D
DramaFork Editorial TeamInteractive storytelling and AI production
2026.10.13Estimated reading time: 14 min
Original text-free cinematic editorial illustration: a script sits beside a clapperboard, prop bag and route-colored scene cards. A producer groups shoot-ready material into one package while an unresolved card remains outside.
Article contents
Creator blog
  1. 01Introduction
  2. 021. Divide content into independently checkable units
  3. 032. Record requirements and proof on the unit card
  4. 043. Complete playback, then check sharing boundaries
  5. 054. Resolve open issues through shoot-readiness criteria
  6. 065. Accept preparation evidence; recheck changes
Back to article top

Introduction

In an interactive film workflow, shoot readiness depends on whether the receiving team can use the same materials to identify what to film, what can be shared, how branch differences appear and what remains unresolved. A finalized script is an input; the output is a production-unit package with versions, acceptance evidence and owners. Do not release the affected unit while an unresolved issue could change story causality or required images.

This article covers the interface between script and shooting preparation, not shooting order. The Silent Recording Room is an original fictional teaching example, not a real user case, tested achievement or product feature. Its cards and criteria are example designs.

1. Divide content into independently checkable units

In a recording room, investigator Xu Ning finds a recorder and can “Play the recording” or “Ask the administrator directly.” After playback she hears a cough and asks whether the administrator was there last night; asking directly leaves her knowing only that someone moved the equipment. The administrator then retrieves a key on both routes, but her knowledge differs.

“Find recorder, choose, talk, get key” does not tell the camera team how much coverage to prepare, and actors may carry post-recording suspicion into the other route. Start with five candidate units: discovery, playback, direct question, post-listening follow-up and key retrieval. Then check whether the last can actually be shared.

A production unit is a set of requirements that can state its own entry, exit and required filming content. It may contain several shots and is not a scene, route or take. Overlarge units hide differences in dialogue; overfine ones turn every gesture into separate approval and lose complete actions during handoff.

The writer supplies at least script version, relevant pages, choice conditions and next-passage continuity requirements. Production checks consistent references. Dialogue from draft 3 with route connections from draft 2 must return for version alignment, not be patched by verbal explanations on set.

2. Record requirements and proof on the unit card

Actors, location and props identify resources but not how to judge readiness once they arrive. Copy the fields below, fill one card per unit and label attachments with its ID.

Field Required content
Identity and source Unit ID, revision, script version and pages
Applicable conditions Incoming routes and what the character already knows
Entry and exit Character positions, object states and outgoing information
Shared content and differences Reusable content, separately filmed content and prohibited uses
Required coverage Actions, dialogue, reactions and necessary sounds
Preparation evidence Storyboards, prop references, sound plan and attachment locations
Open issues Issue, impact scope, owner and closure deadline
Acceptance decision Release or return, basis, confirmer and date

Required coverage states narrative needs, such as clearly seeing Xu Ning press play herself. The director and cinematographer decide close-up or continuous medium shot. This checks omissions without making the card dictate composition.

At handoff, the writer confirms causality and information, the director expression, and camera, sound and props leads feasibility; production consolidates blockers. One person may cover several roles in a small team, but identify each confirmation rather than replace evidence with one blanket signature.

3. Complete playback, then check sharing boundaries

Fill “Rec2, revision 1”: script draft 3 page 2; viewers selected playback and Xu Ning has not heard the cough; entry, recorder stopped and right hand hovering over the button; exit, playback ended, hand withdrawn and cough known. Connect to post-listening follow-up, not direct question.

Require three things: identifiable button press, a usable reaction at the cough and a final turn toward the administrator. The sound plan uses an on-set cue for performance, replaced by the final recording in post. Set cue timing, content and recording arrangements before shooting. “Sound in post” alone leaves actors guessing when to react.

Prop attachments show button positions before and after playback. If the prepared recorder cannot hold the pressed state, withhold release. Use a suitable prop or rewrite the action as press-and-spring-back and revise the storyboard. Recheck exit conditions for either approach rather than swap a visually similar machine.

For key retrieval, a detail shot of the administrator reaching to open a drawer can be a shared candidate only without route-specific dialogue or Xu Ning’s differing reaction. Film her alert post-recording close-up separately. Define sharing with action and composition limits, not “universal ending.”

If the director wants tension in a continuous two-shot, film two complete versions instead. Sharing details or separate footage depends on whether the expression plan can conceal differences; the card records that choice as requirements.

4. Resolve open issues through shoot-readiness criteria

This example has three criteria. Narrative closure: every entry has a valid premise and exits connect to named next passages. Clear expression: required information has an image or sound plan instead of improvised critical evidence. Supported execution: owners confirm people, prop states and technical preparation, with findable attachments.

Unresolved cough identity affects Xu Ning’s question and the administrator’s reaction, so return it to writer and director. Unresolved placement after a spoken line belongs to director and sound lead. Neither earns release through “decide on set.”

Cup color can be nonblocking only if confirmed not to carry a clue, not constrained by existing adjoining footage and irrelevant to composition. Name the prop owner and latest decision time. If color identifies a suspect, the same issue becomes blocking. Judge size by impact.

A shoot-ready scene requires every planned unit to pass. If only discovery passes, release that explicit scope and keep unresolved units outside the package; partial approval is not whole-scene approval.

5. Accept preparation evidence; recheck changes

The package contains a unit index, released cards, matching script extracts, expression plans and state references, plus unreleased-unit list. The index specifies active revisions and lets anyone find attachments by ID. “Everyone read the script” does not replace this handoff.

Acceptance does not establish usable footage. After filming, separately check performance, continuity and coverage. Current evidence is unambiguous critical requirements and supported preparation, not a promised finished-film effect.

If the cough is removed just before shooting, pause Rec2 and post-listening follow-up releases, list affected dialogue, reactions and sound attachments, then revise and reconfirm. Discovery may retain its decision if it does not reference that information; unrelated content need not all be redone.

The card suits this small branching scene. Complex action, special filming conditions or more technical dependencies need additional preparation. Scheduling receives clearly scoped, version-consistent released requirements; deciding what comes first and how to group sets remains scheduling’s task.

Explore product capabilities Play interactive stories

Continue reading

Browse more articles
Original cinematic editorial illustration without text: fine glowing lines connect a replaced film segment to affected branches, subtitle cards and language markers. A reviewing editor selects a few checks while unaffected routes remain in shadow.
Interactive Film Workflow2026.10.13 · 14 min

Change regression in an interactive film workflow: An impact card for minimum retesting

After replacing a shot, trace its users and dependent judgments before creating checks with entry conditions and expected results. A change-impact card defines the handoff scope, evidence and return conditions.

Cover of the blog article “How to Shoot a Scene with Four Branches: Continuity, Script Supervision, and Shooting Order”
Production practice2026.08.29 · 13 min

How to Shoot a Scene with Four Branches: Continuity, Script Supervision, and Shooting Order

The biggest risk in a scene with four branches is not the dialogue, but mismatches between entry states, pauses before choices, and exit actions. On set, shoot it as a shared core with several state variants, using a branch board, continuity photos, and exit checks to safeguard each route, rather than shooting the entire scene four times in succession.

Original cinematic editorial illustration: a writer passes a paper branch map across a studio worktable to a director and an interaction designer. Entry, player-action, and exit symbols mark the nodes, with fine lines connecting the routes and no readable text.
Interactive Film Workflow2026.10.13 · 19 min

An interactive film workflow for handing off branch maps: define entry, actions, and exit with node contracts

A branch map shows where the story goes; a node contract explains what makes each step possible. Use a reusable handoff card to give producers, directors, and implementers the information available to players, action feedback, state changes, acceptance evidence, and responsibility for corrections.

From a story to a playable world.

Create interactive narrative games with DramaFork: connect scripts, characters, shots, and choices into a playable first version.

Product

  • Pricing
  • Credits guide
  • Capabilities
  • Workflow
  • Examples
  • FAQ

Explore

  • Playable gallery
  • Creator blog
  • Creator partnership

Legal

  • Privacy
  • Terms
  • Cookies
© 2026 DramaFork/DramaFork · Interactive narrative games
Press Enter to send, or drag away and release.