Corporate Event Cue Sheets: What Each Department Needs

Agenda times help teams anticipate the program, but a clock time is not always the right signal to act. A speaker may finish early or hold for applause. Pair each cue with an observable trigger, such as a specific spoken line or a caller’s instruction, instead of relying on the scheduled minute alone.

Include the segment, cue identifier, trigger, action and responsible department. Name the person authorized to call cues. Where an operator is expected to act independently, state that exception clearly. Otherwise, multiple people may interpret the same transition differently and start actions that were meant to occur together.

Audio needs to know which speaker or source becomes active, which playback item is involved and what ends the action. Distinguish music that stops on a caller’s instruction from music intended to continue beneath an introduction. Use speaker names and agreed source labels rather than vague directions such as next mic.

Video needs the exact asset reference, its intended destination and the state that follows it. A clip ending does not explain whether the screen should return to slides or a holding graphic. Lighting needs an agreed look label and transition instructions established with its operator. The cue sheet references those prepared looks; it should not invent technical settings.

Use shared cue identifiers so a call means the same thing to everyone. A coordinated transition can contain separate audio, video and lighting actions under one parent identifier, with clearly labeled sub-actions where timing differs. Department notes can add detail, but they should preserve the shared reference.

Avoid renumbering the entire show when a late cue is inserted. An agreed suffix system can preserve existing references and reduce confusion in printed copies. In a hypothetical awards transition, adding a holding slide should not silently change every cue number that follows it.

Assign one editor to maintain the master and label each published version with a revision identifier and issue time. Keep a short change log that names affected cues. Operators should be able to distinguish a working draft from the version currently authorized for rehearsal or show use.

After a significant revision, request acknowledgment from affected departments. Sending a file does not confirm that anyone has loaded or read it. During the live program, route necessary changes through the designated caller and record them in the master when practical, rather than creating competing instructions in private messages.

Read transitions aloud with department leads before rehearsal. Concentrate on moments where one action depends on another: playback before a walk-on, a lighting change after a screen transition, or a return from a remote segment. Define a fallback for a missing asset so operators are not forced to invent one live.