Stage and performance
Make a cue sheet from an approved running order
Build the sheet only from an approved running order, since cues written against an unsettled order need rework. Give each cue a number, an observable trigger, one action and one operator, then confirm each cue with the person who runs it.
Event or show: [ ] Running order version and date approved: [ ] Cue caller: [ ] Cue number: [ ] Position in running order: [ ] Trigger, stated so it can be seen or heard: [ ] Action: [ ] Operator: [ ] Backup operator: [ ] Trigger is ambiguous: [yes or no, and why] Rehearsed with the team: [yes or no, date] Confirmed by operator: [ ] Cues still unrehearsed: [ ] Sheet revision and date: [ ]
Triggers that cause missed cues
A trigger such as "when the scene feels finished" depends on judgment, and two operators may read it differently. Prefer something observable: a spoken line, a visible movement, a count or a call from a named person. Check that each cue has one owner, since a cue shared between operators can be missed by both. Flag any cue the team has not run together, because a cue that reads well on paper may fail against real timing.
Check whether each trigger can be seen, heard or called by the assigned operator. For an unclear trigger, suggest a candidate only if the supplied running order supports it, and label it for caller and operator confirmation. Otherwise ask for the missing detail. List cues without an operator or rehearsal status.
Run it with the operators
Give each operator their section and ask them to correct any trigger they cannot reliably catch. Run the sequence at least once with everyone at their stations and record which cues were confirmed. Decide who calls cues and who may change the sheet. Date each revision so no one works from an old copy.