5 MIN READ
Last-minute event running-order changes: who decides and how does the crew find out?
PUBLISHED
Author: Wojciech Chowaniec
From a request to an agreed instruction: approve changes, identify superseded plans and confirm that the affected crew understands.

A running-order change is ready to implement when the team knows who approved it, what it replaces and which affected people have acknowledged the new instruction. Editing a file or posting in a group chat is not enough. Agree a short decision process before the event begins.
An extra speech, a moved film or a different award sequence can look like a small correction. For the crew, it may mean a different entrance, screen asset, microphone, lighting state or dinner-service transition. Consider the surrounding sequence rather than treating the change as an edit to a single field.
Separate a request from an approved instruction
The person raising a change should explain what is needed and why. They do not have to prescribe the solution. If a speaker will arrive late, the immediate issue is their availability. Moving the speech, swapping items or using an agreed fallback are options to assess.
Do not let the request reach the host, playback operator and stage team as three separate instructions. Identify someone who receives it and brings the proposal to a shared decision. That person can make clear that an option is still under consideration before the crew treats it as the new plan.
Name the people and the scope of their decisions
Before the event, agree who approves programme or content changes for the organiser, who considers their effect on the running order and who confirms that they can be delivered. Job titles vary. What matters is that these functions have named people and an agreed deputy for this event.
Programme approval does not confirm that the technical team or performers are ready. Equally, preparing a file does not mean its content has been signed off. Bring these confirmations together with the person coordinating the change, who can then communicate one agreed version.
On a smaller event, one person may cover several functions. They still need information from those affected. A change to the dinner transition, for example, needs agreement with the person responsible for meal service, not only the host.
Check the item before the change and the one after it
Walk through a short sequence for every proposal: what is ending, what happens next and how the event returns to the rest of the programme. This exposes dependencies hidden by a programme item’s title.
- Are the people needed for the new sequence ready and informed?
- Does the host have the correct introduction, names and closing information?
- Do screens, sound and lighting refer to the same moment?
- Must anything be placed on or removed from the stage?
- What happens to guest operations, catering and other event spaces?
- Which previous instruction is being superseded?
Not every change needs a meeting of the entire production team. It needs answers from the people affected. If an essential condition cannot be confirmed, leave the proposal unresolved or use an agreed fallback. Do not communicate an assumption as a finished decision.
Record the difference, not just a new file version
Identify the running-order item and describe the revised sequence. Moving a film does not necessarily move its introduction, title card and the next speaker’s entrance with it. Decide explicitly what remains, what changes and what is omitted.

A short record of the difference, the decision time and the approver is useful alongside the current document version. Identify superseded instructions too, so the new plan does not compete with an earlier printout or a file still open at an operator’s position.
Once the event is running, do not expect everyone to study a whole document again. Explain the scope and location of the correction concisely, then keep the record in the agreed source. The process must work for people who are currently managing the stage, operating equipment or looking after guests.
An acknowledgement closes the loop
Sending a message confirms that it was sent, not that it was understood. The leads responsible for affected areas should acknowledge the instruction. For a more complex change, ask them to repeat the key part of their scope: the entrance, the asset or the instruction being replaced.
Agree the channel used for decisions and who collects acknowledgements. A lead can brief their own team rather than drawing everyone into one conversation. If a necessary person cannot be reached, report the missing confirmation. Earlier activity in a group chat does not prove that they have read the change.
Approving a change and giving the start cue are separate actions. A revised sequence does not automatically start a film or send someone on stage. Live execution cues should still come from the person designated to lead that sequence.
A working model: moving a film before the awards
This is a planning example, not a MOVYTZA case study. Imagine that someone needed for an awards sequence is not ready. A proposal is made to play first a film originally scheduled after the awards.
Check more than whether the film is loaded. Does its opening assume the awards have already happened? What changes in the host’s introduction? Who confirms that the people needed after playback will be ready? The stage team needs to know which entrance has been deferred, while operators need to understand when the revised sequence takes effect.
If the film only makes sense after the awards, having the file available does not justify the swap. Return to other prepared options. The aim is a workable sequence that makes sense to the audience, rather than filling screen time with whatever asset is available.
A short change record for the crew
Adapt this working template to the team’s agreed process:
- Running-order item and reason for the request: …
- Proposed sequence and the instruction it replaces: …
- Effects on adjacent items, people and assets: …
- Programme approver and confirmation that delivery is possible: …
- Person communicating the decision and intended recipients: …
- Document version, effective point and acknowledgements received: …
- Open conditions or the agreed fallback: …
The record helps close a decision. It does not replace the running order or production agreements, but makes the distinction between a proposal and a usable instruction clear.
The corporate gala run-of-show template provides a starting document. In event directing, connect that document with one practical agreement: the crew should know which decision applies and who will give the cue to execute it.