Lighting cue

A cue connects an event in the show to a lighting response. The event might be a spoken phrase, a musical moment, a presenter reaching a position or an instruction from the show caller. The response could change brightness, color, position, beam shape or several attributes together.

Many cues are stored in a lighting console and recalled in a planned sequence. A cue can contain a complete look or only selected changes, depending on the console and programming approach. Tracking systems may allow values to continue from earlier cues until they are changed, so the visible result depends on more than the current cue label.

Timing describes how the change unfolds. An immediate switch, a gentle fade and a delayed movement create different impressions even when the final fixture settings match. Different attributes may need separate timing so that, for example, a visible color change happens differently from a concealed repositioning.

Cues organize attention. A presentation look can make a speaker readable, a transition can redirect the audience toward an entrance and a performance sequence can reinforce musical structure. The strongest cue is not necessarily the most noticeable one. Often it simply makes the next action feel clear and inevitable.

For the crew, cues provide a repeatable framework. Lighting, sound, video and stage management can discuss the same moment using an agreed reference. That reference is especially valuable when an event contains similar segments, changing presenters or several versions of a running order.

Repeatability does not mean ignoring live conditions. A delayed entrance or extended speech may require the operator to wait, hold a look or take an agreed alternative. Cue design should therefore separate the intended creative result from the trigger method. A technically correct sequence can still feel wrong if it advances before the stage action is ready.

Start with the purpose of the moment, then define the lighting state and how it should arrive. Avoid programming by cue number alone. A useful label describes the action clearly enough that an operator can recognize it during rehearsal, including after the running order changes.

Programming also requires attention to what is not supposed to change. A new stage color should not accidentally remove essential facial light. A reset should not expose moving fixtures sweeping through the audience. Review the transition from the preceding state, not only the final picture.

Triggering may be manual, linked to timecode or connected to another control system. Each method has different dependencies. Test recovery after a pause or restart, and agree which person can authorize a departure from the normal sequence. Automated timing should support the event rather than force live action to chase it.

A conference in Abu Dhabi opens with a video, followed by a host walking to a lectern. The lighting team prepares a subdued audience state, a video look and a host presentation look. The key challenge is the handover between recorded content and a live entrance.

1. The team defines the intended appearance of each stage of the opening before storing console cues.
2. The video and lighting operators agree how the end of playback will be identified.
3. The host rehearses the entrance so the lighting team can confirm coverage and transition timing.
4. The show caller rehearses the standby and execution calls using the current cue references.
5. The team tests a delayed entrance and agrees which look should remain active while waiting.

During rehearsal, the host takes longer than expected to reach the lectern. The team changes the trigger for the final presentation look rather than simply shortening every fade. That adjustment respects the action while preserving the visual intention of the opening.

If a followspot is involved, its operator receives a coordinated instruction describing the pickup and handover. The console cue and the human-operated action can share a show reference without pretending they are the same technical process.

• Testing only the final state overlooks distracting movements and brightness changes during the transition.
• Using unclear labels makes similar presentation moments difficult to distinguish under pressure.
• Changing cue numbers without updating the show documents creates conflicting references between departments.
• Relying on automatic timing for unpredictable live action can advance the lighting before the stage is ready.
• Editing a tracked value without reviewing later cues can produce unintended changes elsewhere in the sequence.

Keep working versions identifiable and maintain the console's appropriate backup process. After a substantial edit, rehearse the surrounding sequence rather than checking the revised cue in isolation. The incoming state, transition and following action all influence whether the change works.

A lighting cue is not a substitute for emergency lighting or a venue safety procedure. Decorative blackouts and dramatic effects must be coordinated so essential access and safety systems remain appropriate. The show team should know the agreed response to interruptions without relying on an improvised console action.