The agenda says “demo at 9:10,” but nobody knows who starts the slides or whether the presenter is ready. Put the planned time, the start condition, the person calling the transition, and the execution role beside each segment. A guest-facing agenda does not supply those backstage instructions.
Use this original fictional thirty-minute presentation to build the crew version. All roles and timing rules are illustrative; no event, crew acknowledgement, or live cue has occurred. The actual date, time zone, venue, and assigned people remain blank.
Open the complete example · Download the full HTML source
- C01 — Welcome, 9:00-9:10 a.m. Host delivers the welcome. In this exercise, the designated caller gives the start instruction after the crew confirms the agreed readiness checks.
- C02 — Demo, 9:10-9:25 a.m. Presenter demonstrates the supplied material. The slide operator changes to the opening demo slide on the caller's instruction after presenter readiness is confirmed.
- C03 — Questions, 9:25-9:30 a.m. Moderator takes questions after the demo ends and the caller gives the transition instruction.
The three durations are ten, fifteen, and five minutes: thirty minutes in total. The exercise fixes the planned finish at 9:30 a.m. Write that finish constraint beside the sequence so a delayed middle segment has a visible consequence.
Describe the instruction the crew needs
Simon Fraser University's day-of planning guide describes a detailed program schedule as a chronological sequence of event tasks and includes production details and staff responsibilities. Use that planning context to collect your actual arrangements; the three cues here are an authored example, not a university operating procedure.
Give a cue a stable ID so a changed title does not break the crew's reference. Separate the role authorizing a transition from the role performing it. For a real show, confirm who fills those roles, the communication channel, and what the agreed instruction means. Do not assume every team uses the same calling vocabulary.
Treat the planned clock time and permission to proceed as separate fields. A time in a document does not confirm that a presenter is ready or operate the equipment. Keep readiness and actual execution in the crew's real communication process.
Work a delay through the remaining segments
Suppose the demo begins at 9:12 instead of 9:10 in a separate timing scenario. Keeping its fifteen minutes moves its end to 9:27. Keeping five minutes for questions then moves the finish to 9:32, two minutes past the supplied finish constraint.
Show that conflict instead of silently shrinking questions to three minutes. The person with actual authority must choose among the available changes. Record the chosen revision and communicate it through the real crew channel before treating it as the working sequence.
Keep the original planned times visible beside the proposal. Calling the revised scenario “actual” would imply observations the exercise does not contain. If someone later records real execution times, give those their own fields and source.
Copy a crew-sheet request
Create one complete HTML event run-of-show review sheet.
Event/date/time zone and confirmed finish constraint: [SUPPLY]
Segments with IDs, planned starts/ends and durations: [PASTE]
Caller, execution roles and actual assigned people: [SUPPLY]
Readiness checks, cue wording and communication channel: [SUPPLY]
Confirmed equipment/material references: [SUPPLY]
Change authority and crew revision process: [SUPPLY]
Separate planned times, start conditions and actual observations.
Retain original timing beside any supplied delay scenario. Calculate
the downstream finish and identify conflicts; do not silently shorten
segments, invent approval or mark a cue executed. Include a blank cue
record. Use readable labeled records, local styles and no external
assets, notifications, equipment control, storage or fake GO buttons.
Return the complete HTML and unresolved staffing/timing questions.
The attendee event itinerary helps guests move between activities and rooms; it explicitly keeps internal cues separate. Maintain both copies from the accepted event plan. Finish by having each responsible crew member explain their next instruction, then resolve the timing conflict and issue the accepted crew revision through the organizer's actual process.