What Is Show Calling?

From the programme to the moment

The run of show says that an opening video follows the host’s welcome. Someone still needs to establish the moment when the video should begin.

The host may finish early, add another sentence or pause for applause. The playback operator needs a clear instruction, and the other teams involved need to understand what follows.

Show calling connects the agreed sequence to what is actually happening.

It does not mean announcing every action on a headset. It means identifying which actions need coordinated instruction, preparing the people responsible and communicating the agreed trigger clearly.

A time on the running order is not, by itself, an instruction to execute a cue.

What is a cue?

A cue identifies a production action and the point at which it should happen.

It might start a video, change a lighting state, introduce a sound effect or initiate an agreed stage transition. Some cues involve one department. Others bring several actions together.

The trigger may be a spoken phrase, a visible action, a confirmed readiness report or another agreed event. Some productions use timed or automated sequences.

The important questions are practical:

• What action is expected?
• Who performs it?
• What tells them to begin?
• What must already be ready?
• What happens if it cannot proceed?

A cue number can help identify an action, but the number alone does not explain its content or trigger.

Who calls the show?

Show calling may be assigned to a dedicated show caller, a stage manager or another appropriately prepared member of the production team.

In some theatre structures, a deputy stage manager performs the calling function. That is an example of a role arrangement, not a universal structure for live events.

The production should establish who gives coordinated cue instructions and how that responsibility relates to other roles.

A production manager may coordinate the wider production without calling its cues. A stage manager may coordinate performers and backstage readiness while a separate caller follows the programme. One person may combine responsibilities where the scope and workload make that workable.

Agree the function and authority, not just the title.

The working information

A caller needs current information that can be followed during delivery.

The run of show may provide the programme sequence, participants, timings and transitions. A calling script or coordinated cue sheets may provide more detailed triggers and departmental actions.

The documents should agree where they overlap. If the caller’s copy says one thing and the playback operator’s copy says another, both people may believe they are following the correct plan.

Useful working information can include:

• the current programme sequence;
• cue identities and triggers;
• relevant presenter or performer actions;
• content versions;
• readiness dependencies;
• communication routes;
• agreed procedures for changes or holds.

The production schedule provides the wider operational timeline. It does not replace the information needed to call individual programme actions.

Readiness before execution

An operator can have the correct cue prepared while another part of the transition remains unresolved.

The next presenter may not be ready. A microphone may not have reached its position. The stage team may still be completing an agreed movement.

The caller needs the readiness information relevant to the cue, communicated by the people responsible for those conditions.

Stage management can provide an important interface here: understanding stage activity and reporting when the relevant people and arrangements are ready.

A readiness report should describe a condition that has actually been checked. It should not become a polite assumption that another department has finished.

Clear instructions, agreed in advance

A production may use preparation calls, readiness acknowledgements and an execution instruction such as “go”. The wording and acknowledgement method should be agreed with the participating teams.

An instruction needs to identify the intended recipient or action clearly enough for that production. An ambiguous “go” can create a problem when several operators are listening for different actions.

Keep operational communication concise. Separate discussion from execution instructions so a question about a cue is not mistaken for permission to run it.

The caller’s instruction does not replace specialist checks, venue procedures or the authority of people responsible for safety-sensitive work. Those boundaries need to be explicit before delivery.

Rehearse the interfaces

Rehearsal gives the team an opportunity to test more than the individual production actions.

It can establish whether the caller recognises the trigger, whether the intended operator hears the instruction and whether the action fits what the presenter or performer is doing.

Consider the handover from a video to a live presenter. The relevant work may include the end of playback, a lighting change, microphone readiness and the presenter’s entrance.

Each action can work independently while the handover still feels confused.

Use rehearsal to clarify the sequence and dependencies. Record changes in the affected working documents rather than relying on everyone remembering a conversation.

When the programme changes

Live delivery can depart from the planned sequence. A segment may run long, a presenter may be delayed or a piece of content may need to be omitted.

The caller should work within the agreed decision structure. Permission to communicate cues does not automatically include permission to remove programme content or make every operational decision.

Establish who can approve a change and how the affected teams will receive it.

A revised instruction should make clear what happens next. If one action is skipped, check what other actions depended on it rather than assuming the remaining sequence is unaffected.

Holds and unresolved conditions

A production should agree how a concern is reported, who can hold an action and how a restart is authorised.

The appropriate arrangement depends on the work involved and the venue’s procedures. This article does not prescribe a universal stop or emergency protocol.

For ordinary programme coordination, make unresolved conditions visible. Do not translate “we have not confirmed this” into “it will probably be ready”.

Restart information matters too. The team needs to understand which cue comes next, what has already happened and which conditions need checking again.

Does every event need a separate show caller?

No.

A straightforward programme may be delivered effectively by an experienced team with explicit cue responsibilities. Some actions may run from agreed local triggers or prepared automated sequences.

A dedicated caller becomes more useful when several departments need coordinated timing, the programme changes frequently or important transitions depend on information from different people.

The requirement is sufficient cue coordination, not a particular staffing title.

The people delivering the programme should understand what happens next, who initiates it and what must be ready.