Cue

Almost everything that changes during a performance changes on a cue: light, sound, video, automation, flown scenery, followspots, and the entrances a stage manager calls. Each cue binds together a trigger (a line, a beat, a movement, a clock), a target (the state or event to reach), a timing (how fast, in what shape), and a responsibility (which desk or hands execute it). Numbered and stacked in sequence, cues are the score of the performance’s technical life.

A work of any complexity runs to hundreds of them, distributed across departments and held together partly by files and partly by craft: the operator’s feel for a fade, the caller’s timing, the corrections a run accumulates that never make it back into paperwork. That unwritten margin is why cue documentation is a discipline rather than a printout — the printed stack describes the machine’s part; the behavior lives in the ensemble of machine and crew.

Documented well — stacks with their logic, timings as performed, interactions between departments, the reasons behind the oddities — a cue record lets a work be remounted or toured without its original crew, and gives researchers the closest substitute for having stood at the desk. Undocumented, the behavior ends the day the crew disperses.