Script structure for judgment

What this lesson covers

1. 01

   Four beats

   Stake: Who, what they want, what is at risk.

   Choices: Three plausible moves.

   Consequence: What happens on the job.

   Teach: One sentence naming the rule or gap, with a link to the job aid.

2. 02

   The four beats on one refund

   Stake: a customer says their manager promised a full refund today, and they have no receipt. Choice: override now, refuse in one blunt line, or state the policy and offer verification. Consequence: the override creates an audit flag; the blunt refusal keeps the policy and loses the customer; verification applies the policy and keeps the relationship. Teach: "Exceptions above policy need verification or an authorised approver."

3. 03

   One screen per beat

   Stacking stake, choices, consequence, teach and a glossary on one screen raises load and breaks a sensible focus order. Four short screens are easier to caption, easier to review, and easier to fix one beat without redoing the scene.

4. 04

   How long should a scene be?

   Two numbers to design against. Before the first choice: aim for under 30 seconds of setup; every extra second is time the learner is not deciding. Consequence beats: 10 to 20 seconds, enough to show the effect, not a second story. If a scenario needs long setup because the situation is complex, split it: a short context screen the learner can read at their own pace, then the scene. Narration for setup should be at a natural pace; Guo and colleagues found engagement rose with more energetic delivery, which is about energy and removing pauses, not speaking faster than people can follow.

5. 05

   Script the four beats

   Write your scenario as four beats, one screen each, in both languages. Time the setup narration; cut it below 30 seconds.