# Branching scenario storyboard template

Use this planning pack before you film, animate, or build the scenario. Keep the route map, scene cards, route ledger, and coverage audit linked with stable IDs.

This is a manual planning template. It is not an automatic Interakly import file.

## ID convention

- `S01`: Scene
- `C01`: Choice Moment inside a Scene
- `R01`: Route
- `J01`: documented rejoin point
- `O01`: Outcome
- `K01`: required knowledge or coverage item
- `V01`: variable or state value, only when state-based routing is necessary

Write the exact learner-facing option or a faithful short label on every Route. Avoid labels such as “Route A” that do not explain the trigger.

## 1. Decision brief

- **Working title:**
- **Version:**
- **Owner:**
- **Subject-matter expert:**
- **Reviewer:**
- **Audience:**
- **Prerequisite knowledge:**
- **Learner role:**
- **Job performance to practise:**
- **Critical decision in one sentence:**
- **Evidence available when the learner decides:**
- **Stakes and believable consequence:**
- **Success definition:**
- **Failure definition:**
- **Purpose: practice, coaching, or assessment:**
- **Mandatory shared foundation:**
- **Expected runtime:**
- **Maintained devices and viewing surfaces:**
- **Media and source constraints:**
- **Accessibility requirements:**
- **Approval date:**
- **Revision owner:**

### Performance statement

Given [context and available evidence], the learner will [visible decision or action] to [quality standard or result].

## 2. Route map

Create a node for every Scene and Outcome. Place each Choice Moment inside its Scene. Label each connection with its Route ID and faithful trigger wording.

### Map inventory

| ID | Type | Title or faithful label | Owner | Status |
| --- | --- | --- | --- | --- |
| S01 | Scene |  |  | Draft |
| C01 @ S01 | Choice Moment |  |  | Draft |
| R01 | Route |  |  | Draft |
| O01 | Outcome |  |  | Draft |

## 3. Scene card

Duplicate this card for every produced Scene.

- **Scene ID:**
- **Title:**
- **Objective contribution:**
- **Incoming facts and state:**
- **What the learner sees:**
- **What the learner hears:**
- **What the learner must notice:**
- **Script or dialogue:**
- **Media asset and duration:**
- **Choice ID and timestamp:**
- **Exact option wording:**
- **Immediate consequence for each option:**
- **Explanatory feedback or later debrief:**
- **Outgoing Route IDs:**
- **Captions and transcript:**
- **Non-pointer interaction requirement:**
- **Production owner:**
- **Status:**
- **Approval notes:**

## 4. Route ledger

Use one row for every transition. The ledger is the connection authority. If route copy changes, update the learner-facing option and this row together.

| Route ID | Source Scene and Choice | Exact trigger or option | Destination | Immediate consequence | State carried forward | Why this branch exists | Rejoin permitted | Evidence or score | QA status |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| R01 | S01, C01 |  |  |  |  |  | No |  | Untested |

## 5. Coverage audit

Replace the example path headings with every reachable learner walk. A blank cell should be investigated before production.

| Required element | Path P01 | Path P02 | Path P03 | Owner or evidence |
| --- | --- | --- | --- | --- |
| Mandatory shared foundation |  |  |  |  |
| Learning objective 1 |  |  |  |  |
| Learning objective 2 |  |  |  |  |
| Critical decision |  |  |  |  |
| Explanatory feedback |  |  |  |  |
| Required policy or reference |  |  |  |  |
| Accessible alternative |  |  |  |  |
| Outcome meaning |  |  |  |  |
| Desktop route test |  |  |  |  |
| Phone route test |  |  |  |  |
| Embed route test |  |  |  |  |
| Resume and replay test |  |  |  |  |

## Rejoin-equivalence test

Before routes rejoin, compare their state. Record **equal**, **irrelevant to what follows**, or **still different**.

| State dimension | Route 1 | Route 2 | Result |
| --- | --- | --- | --- |
| Required facts |  |  |  |
| Relationship, trust, urgency, or risk |  |  |  |
| Resources and available actions |  |  |  |
| Rules and permissions |  |  |  |
| Meaning of the next assessed decision |  |  |  |

If a difference still affects the next decision, keep the routes separate or represent the state explicitly.

## Route and production budget

These numbers answer different questions. Do not use “number of branches” as a substitute for all of them.

| Measure | Planned | Approved | Produced | Tested |
| --- | ---: | ---: | ---: | ---: |
| Distinct Scenes |  |  |  |  |
| Choice Moments |  |  |  |  |
| Learner-facing options |  |  |  |  |
| Routes to wire |  |  |  |  |
| Outcomes |  |  |  |  |
| Reachable learner walks |  |  |  |  |
| Video minutes |  |  |  |  |
| Media assets |  |  |  |  |
| Caption and transcript files |  |  |  |  |
| Review passes |  |  |  |  |

## Text-only prototype review

Walk every route before media production. Ask one subject-matter expert and one person unfamiliar with the design to test it.

| Walk ID | Route sequence | Tester | Did the decision feel fair? | Was the consequence clear? | Missing context or contradiction | Result |
| --- | --- | --- | --- | --- | --- | --- |
| P01 |  |  |  |  |  | Untested |

## Production handoff

- [ ] The decision brief has an approved owner and version.
- [ ] Every Scene, Choice Moment, Route, rejoin, and Outcome has a stable ID.
- [ ] Every exact option matches the Scene card and route ledger.
- [ ] Every branch has a learning reason that another route does not already provide.
- [ ] Every rejoin passes the equivalence test.
- [ ] Mandatory content appears on every route that needs it.
- [ ] Route, Scene, Outcome, and reachable-walk counts reconcile.
- [ ] Scripts, source media, captions, transcripts, and alternatives have owners.
- [ ] Every reachable walk has a named QA test.
- [ ] The complete plan has been reviewed on the smallest maintained viewing surface.
- [ ] The team understands that the storyboard must be translated manually into the authoring tool.

Created by Interakly Learn. You may copy and adapt this template for your own projects.