How to control last-minute event changes without confusing suppliers

Your venue changes the delivery entrance. You tell the production supplier, update the site plan and get on with everything else. Then the catering truck arrives at the old gate because its driver downloaded yesterday's instructions. Security has the new plan, but nobody told the person covering the early shift.

This is where last-minute event changes become expensive. Each person can be doing exactly what they were told, and the event still ends up with crews waiting, equipment in the wrong place and a delayed opening.

To control those changes, you need one person coordinating the revised instruction, a clear record of which version applies, and confirmation from the people who must act on it. Decide when the new arrangement starts, check that the connected tasks are ready, and replace the old instructions wherever people will still find them.

That doesn't mean every correction needs a meeting. It means a supplier shouldn't have to guess whether a message is an idea, an approved decision or an instruction to start work. Here's how to make that distinction hold up when the event is close and everyone's busy.

Separate a proposed change from an instruction

The first thing you want to do is make the status obvious. "Can we move catering to the side entrance?" asks for an assessment. "Catering deliveries now use the side entrance" instructs someone to change their behaviour. Those messages create very different jobs, even if they appear in the same conversation.

Label the request while you're checking it. Tell suppliers what you're considering, what information you need and whether the existing plan still applies. If the existing arrangement is unsafe or unavailable, explicitly state the temporary hold or alternative under your site procedures. Don't leave people following an instruction you already know they cannot use.

The Association for Project Management's change control guidance separates recording and evaluating a request from approving it, updating the plan and monitoring implementation. For your event, keep those distinctions visible in everyday messages. A supplier discussing feasibility hasn't necessarily received permission to begin.

When the change alters the work or price you've agreed, use the commercial approval process too. Our guide to event supplier scope changes covers that question. Here, we're concentrating on the next operational problem. Once you've made a decision, how do you get everyone working to it without creating conflicting instructions?

Put one person in charge of coordinating each change

Choose the person who will take the change through to a verified result. They collect the facts, involve the affected suppliers, arrange the decision and check that the instruction reaches the people doing the work. This could be your production manager, operations lead or you, depending on the event.

That person doesn't need authority over every technical or commercial decision. The venue may approve access arrangements while the responsible specialist checks equipment safety. What matters is that somebody knows which answers are still missing and follows them up. Otherwise, each supplier can believe another person is coordinating the whole thing.

Name a deputy and make the handover practical. If the coordinator is unavailable during doors, who has the current record and permission to take over? A name on a contact sheet helps only if that person knows what has already happened. Include unresolved questions and the next decision deadline when handing responsibility over.

Tell your own team how requests reach this person. A sponsor coordinator can explain what a sponsor needs without issuing separate instructions to stage crew. Ask suppliers to bring conflicting requests back through the named contact. They should be able to query an instruction without worrying that they're ignoring someone senior.

Write the difference people need to act on

Start with what changes compared with the current approved plan. "Updated logistics attached" makes every recipient search for the difference. "Catering deliveries move from the north gate to the service gate; delivery times stay the same" tells them what to check immediately.

Include the event date, the area affected, the person issuing the instruction and the plan version it replaces. Use locations people can identify onsite. If the venue calls it the service gate but your transport company calls it gate three, confirm they mean the same entrance before circulating another name.

Then describe the action for each affected team. Catering needs to redirect drivers. Security needs the correct gate coverage. The venue needs to confirm access. Your operations team may need to move a check-in point for suppliers. One general announcement won't explain those different responsibilities.

Keep unrelated instructions intact. If you're changing one delivery route, don't casually rewrite the entire supplier pack and introduce an unexplained change to unloading times. When a related detail must change, identify it explicitly. The point is to help people distinguish the decision from formatting edits, old discussion and suggestions nobody accepted.

Check who depends on the changed task

A change rarely stops with the supplier who requested it. Ask who needs the original task to happen, who shares its space and who acts immediately afterwards. That will usually identify more useful recipients than a list of everyone who attended the planning meeting.

Imagine the lighting supplier needs access later than planned. Ask whether sound can still test while that work happens, whether the venue can supervise access, and whether rehearsal can begin when promised. A new lighting completion time isn't workable merely because the lighting supplier accepts it. The connected sequence has to work as well.

For events in Great Britain, HSE's guidance on managing an event describes coordinating a safe phased programme of work and communicating it to the relevant parties. It also distinguishes overall coordination from taking responsibility for suppliers' individual technical work. Use competent people to assess their own work and the points where it connects with others.

Ask each affected lead a concrete question. What do you need before you can start, what will you deliver, and who needs to know when you're finished? Those answers help you identify the real condition for proceeding. "Everyone is aware" is much weaker than knowing the venue must release the loading area before a truck enters it.

Set the decision deadline before the delivery deadline

A delivery deadline tells you when something must be ready. A decision deadline tells you when you must choose for that outcome to remain possible. Mixing them up creates the familiar situation where everyone agrees on the plan just after it has become impossible to deliver.

Work backwards with the suppliers. If revised signs need printing, allow for approval, production, transport and installation. If a different entrance needs staff, check when the supervisor must brief them. Use their confirmed timings, rather than applying a standard buffer that has nothing to do with the work.

Write the latest decision time and what happens if it passes. Perhaps the original approved arrangement continues. Perhaps you use a simpler option already checked with the venue. Where neither is safe or available, the consequence might be delaying the affected activity. Name who makes that call and who receives it.

Don't silently extend the deadline because one person hasn't replied. Ask whether the option is still available and what the delay now changes. If the production slot has gone, an approval based on the old timing is no longer enough. You need a revised delivery assessment before treating the proposal as ready.

Make the fallback an instruction someone can use

A useful fallback describes what happens when the preferred change cannot proceed. "We'll sort it onsite" leaves every supplier making its own assumption. Decide the usable alternative while the people who understand the constraints can still discuss it.

For the delivery entrance example, the fallback might be a venue-approved holding arrangement while the access issue is resolved. It must identify the location, contact and release condition. Don't invent an overflow area simply because it looks empty on a map. The venue and responsible transport staff need to confirm that the arrangement is suitable.

Connect this decision with your event contingency plan. A late truck can affect setup, checks and doors. The person deciding whether to delay opening needs to know which essential tasks remain incomplete, rather than hearing only that the supplier is "nearly there".

Keep the fallback realistic for the remaining time. An alternative that requires equipment already dispatched elsewhere isn't available just because it worked at your previous event. Ask who has confirmed the people, access and resources it needs. If confirmation expires at a particular time, record that limit so the next person doesn't mistake an old possibility for a current option.

Publish a current plan people can identify

Choose a single location for the approved working documents and tell suppliers where it is. Use the system they can access reliably. A sophisticated workspace creates no benefit if half the onsite leads cannot open it from their phones.

Put a clear version and issue time on each document. Identify its event and purpose, especially when suppliers are working across several bookings. Names such as "final revised latest" become useless after another change. A numbered version with a visible issue time gives people something concrete to compare.

Maintain one approved version for each purpose. The site plan and running order can have different revision numbers because they are different documents. A short change record should identify which versions now apply together. Don't force a supplier to infer that a new schedule automatically replaces a separate access plan.

A live link helps you maintain the approved copy, but it doesn't update screenshots, downloads or paper. Tell recipients what changed and whether they need to replace those copies. Where documents must work offline, make downloading the current version part of the briefing. Check this before crews travel into an area with poor reception. Then ask who still has an older copy and arrange to replace it today.

Send the instruction to the person doing the job

Your supplier's account manager may have approved the new arrangement without briefing its onsite lead. The onsite lead may know, while the hired driver or relief crew still has the original email. Ask the supplier who must receive the revised instruction within its own team.

Keep a small distribution record for the change. Record the affected organisation, its named lead, the action required and the reply. You don't need to collect every crew member's personal details. You need to know which responsible lead has accepted the job of briefing them and how you'll check that happened.

For visiting vehicles, HSE's workplace transport guidance specifically addresses drivers knowing the site layout, route and unloading procedures. That is why sending a revised gate map to a commercial contact isn't the end of a route change. Check the information reaches the driver through the supplier's agreed arrangements.

Also include people arriving later. An afternoon security shift can undo a perfectly coordinated morning change if its briefing still describes the old entrance. Ask each lead whether the instruction covers subcontractors, replacement staff and shift handovers. Make that question part of distribution rather than waiting for someone to discover the omission onsite.

Ask for an answer that proves understanding

A delivered message tells you very little about what will happen. Even "received" may only mean someone has seen it. For an instruction with operational consequences, ask the responsible person to confirm the action, timing and anything preventing them from complying.

A useful reply might say, "Our drivers will use the service gate for all catering deliveries tomorrow. I've replaced the north gate map in their instructions. The first driver has confirmed the new route." You can see what the supplier believes the change requires and check it against your intention.

The US Agency for Healthcare Research and Quality describes a check-back in its TeamSTEPPS pocket guide. The receiver confirms the message, and the sender verifies that understanding. It's a healthcare communication method, not evidence about event outcomes. The useful practice you can adapt is asking someone to repeat the important instruction so you can correct a misunderstanding before they act.

Use this proportionately. You don't need elaborate replies to a corrected spelling. You do need clear confirmation for changed access, timings or work sequences. If a supplier replies with a different interpretation, resolve it directly and update the record. Don't count an ambiguous answer as completed communication.

Resolve conflicting updates before issuing another revision

Sometimes the confusion starts while you're still preparing the change. Production sends a revised access time, the venue sends a revised map and catering replies to yesterday's message. Each update may be reasonable on its own. The coordinator needs to establish whether they describe one arrangement that can actually happen.

Compare them with the current approved version. Identify which fact each person is changing and ask about the conflict directly. If the venue can release the service gate only after another booking leaves, a supplier's preferred arrival time doesn't change that constraint. Agree an arrival or holding arrangement the responsible people can support, then circulate the complete decision.

Avoid combining separate replies into an instruction nobody has reviewed. You might accidentally pair a new delivery time with an old unloading position. Send the affected leads the combined proposal and ask them to check their own part and its connections. Record any condition attached to their answer, especially where one supplier is relying on another to finish first.

A conditional reply needs follow-up. "We can do that if the area is clear" doesn't confirm the area will be clear. Ask who controls it and when that person will check. If nobody can confirm the condition, the proposed arrangement remains unresolved. Keep the affected task on its agreed hold or fallback rather than treating a qualified answer as full readiness.

There may also be a second request while the first change is being briefed. Pause long enough to assess whether it affects the instruction already issued. If it does, cancel or replace that instruction explicitly. Tell the recipients which actions should stop, which completed actions remain valid and what they should do while the next decision is checked. Don't let two coordinators issue competing revisions in different conversations.

When the wrong instruction has already reached a supplier, contact its lead through the fastest agreed route. Establish whether anyone has acted on it. Correct the action as well as the document, with the responsible specialists involved wherever necessary. A clean new file won't move equipment that somebody already installed in the wrong place.

Finally, tell the original sender what you corrected. That person may still be answering questions from the rejected version. Ask them to stop forwarding it and direct queries to the approved instruction. This closes a common route by which an old decision returns after everyone believes the change has been settled.

Decide when the revised arrangement becomes active

Approval and activation can happen at different times. You may approve a new entrance today but keep the current entrance operating until staff and signs are ready tomorrow. State the activation time or the condition that allows the new arrangement to begin.

Where several suppliers must switch together, name who releases the change. Before that release, check the required conditions with the responsible leads. For an access change, that might include venue permission, the new position being staffed, drivers being briefed and outdated signs being removed. The exact conditions depend on your event and the competent people managing the activity.

Be explicit about work already underway. If a truck is travelling on the old instructions, contact it through the supplier and agree how it will receive a safe revised direction. Don't assume a message to the whole group reaches someone driving. The change needs to cover the transition as well as future arrivals.

Avoid telling one supplier to start before the connecting supplier is ready. If the new location isn't available yet, "approved" cannot mean "move now". A short confirmation that the arrangement is active prevents that confusion. Record who issued it and when, so later arrivals can establish which instruction applies.

Remove old instructions without losing the record

You need to stop people using obsolete instructions while preserving the history of what happened. Keep the earlier version in an archive labelled as replaced. Remove it from the current working folder, pinned messages and printed briefing packs that crews will consult.

Check the places where instructions actually survive. A supplier may have copied your access paragraph into its own crew sheet. The venue may have printed a map for the gatehouse. Your team may have scheduled an email before the change was agreed. Replacing the central file won't correct those copies.

Ask the responsible lead to confirm which copies it replaced. Where a screenshot or printout cannot be withdrawn, issue a clear cancellation and replacement through the agreed channel. For important changes, check understanding directly with the people using those copies. Don't rely on the newer message simply appearing further down a busy conversation.

If the proposal is rejected, cancel any preparation based on it as well. A draft plan sent for assessment can still find its way into a crew pack. Mark it as rejected and confirm the approved arrangement. People should never have to choose between a rejected proposal that looks recent and an approved plan that looks older.

Work through a complete change before event day

Here's a fictional example. A paid evening event uses the north gate for supplier deliveries. The venue reports that this gate will be unavailable during setup. Your operations lead records the issue and asks affected suppliers to assess a proposed service gate route. Until the replacement is confirmed, arrivals need the venue's approved temporary instructions.

The caterer confirms the route works for its vehicles. Production identifies a clash with its unloading position. Security checks how it will cover the revised access. The venue and relevant leads agree a sequence that avoids the clash, and the operations lead records the required conditions before issuing the approved revision.

The new instruction identifies the service gate, the revised delivery sequence and the documents it replaces. Each supplier lead confirms its own action. The caterer briefs the drivers, production updates its crew sheet and security includes the gate position in the shift briefing. Your operations lead follows up any missing answers before the decision deadline.

Before activation, the responsible people confirm the route and staffing are ready. The authorised coordinator releases the revised arrangement. The person monitoring arrivals then checks the first deliveries against it. If a driver still has the north gate map, you correct that distribution failure before assuming all later deliveries have the right information.

Use a short, complete change message

You can communicate a straightforward revision in a short message if the decision has already been checked. Start with the approved action, then specify who needs to act and when. Link the current document rather than attaching several versions and asking people to find the right one.

For example, a fictional instruction could read, "Approved access change for Friday's event. Catering deliveries use the service gate from the venue's confirmed release. The linked access plan version four replaces version three. Catering lead, confirm drivers have the revised route. Security lead, confirm gate staff are briefed. Operations will issue the release after venue readiness is confirmed. Please report any obstacle before your agreed decision deadline."

Fill in the actual date, contact and deadline before sending. Where the change has a fixed activation time, include it. Where activation depends on readiness, explain who will confirm that condition. Don't use an example's wording to hide an unanswered question.

For a complex change, attach the checked detail and keep the message readable. Suppliers need enough information to execute their part without searching a long discussion. If the instruction requires substantial explanation, brief the relevant leads together, invite questions and send the agreed record afterwards. Written follow-up prevents a second argument over what the call decided.

Keep live changes short enough to manage

Once setup begins, people need an immediate account of the situation. Identify the affected area, what has happened, what must pause or continue, and who is coordinating the response. Route technical decisions to the responsible specialist and use the site's agreed communication procedures.

For a routine operational change, contact the relevant leads, confirm their understanding and record the instruction as soon as practicable. Read back important times and locations on a radio rather than assuming they were heard correctly. If the channel is busy or unclear, use the agreed alternative without leaving people guessing whether the first instruction still applies.

Changes to cues and programme timing also need to reach the person calling the show. Update the event run of show through its named owner. A revised supplier completion time should not quietly become an instruction to the stage manager through a separate conversation.

Keep emergency action under the event's emergency arrangements. Urgent protective action must not wait for routine document approval. Once the immediate situation allows, record what changed and tell the affected teams which instructions now apply. This helps you resume coordinated work instead of allowing temporary emergency directions to become an unexplained permanent plan.

Freeze optional changes without blocking necessary decisions

As the event gets close, set a point after which optional changes normally stop. The reason is practical. Crews need time to brief their teams, prepare equipment and carry out checks. Repeated preferences arriving after that point can disrupt work already underway.

State the exceptions in advance. Safety issues, an unavailable essential service or a condition that prevents delivery need assessment even after the freeze. Decide who can approve an exception and require the same checks of dependencies, communication and readiness. Calling something urgent doesn't remove those consequences.

If a sponsor requests a cosmetic change after the deadline, ask what it would displace. Will a crew stop essential setup? Will signs need replacing? Does the revised arrangement affect an attendee promise? You can decline the change when the remaining time cannot support it responsibly. Explain the available option rather than promising an upgrade suppliers cannot deliver.

A freeze also protects suppliers from contradictory requests within your own team. Tell sales, marketing and guest services how to submit a late request. They may have a legitimate need you haven't considered. They still need one decision that affected suppliers can follow, rather than separate approvals from whoever answers first.

Test the fallback communication and the restart

Your planned communication method may fail when you need it. Test whether the relevant people can use radios, open documents and reach the named contacts at the site. Agree how a supplier reports a problem if mobile reception disappears or its supervisor changes unexpectedly.

HSE's guidance on incidents and emergencies recommends testing communication systems and using exercises to validate emergency plans. It also addresses readiness before restarting after an incident. Those are specific safety planning responsibilities in Great Britain. Build your event's emergency arrangements with the venue and appropriate specialists, including the applicable local requirements.

For routine changes, rehearse one ordinary failure too. Ask what happens if a supplier does not acknowledge the revised loading time. Who calls the deputy, how is the affected task held safely, and when does the fallback apply? Work through the answer before everyone is occupied with setup.

Check restart instructions as carefully as the pause. Confirm who authorises work to resume and which conditions must be satisfied. If several teams stopped together, they may need a coordinated sequence to restart. "All sorted" doesn't explain which task can begin or whether the shared area is available again.

Close the change only after checking the result

A change is complete when the required action has happened and the people relying on it know the result. Ask for confirmation from the person responsible for delivery, then check the outcome where the consequence warrants it. A revised sign isn't finished because someone sent the artwork to a printer.

Record any remaining work with its owner. If the route has changed but one scheduled supplier email still contains the old map, distribution remains incomplete. If a supplier followed the right instruction but arrived at an unstaffed gate, investigate readiness and coordination rather than treating the email as proof the process worked.

Keep useful notes for the next event. Record where the conflicting instruction came from and change that part of your preparation. Perhaps subcontractors received an old briefing attachment, or a replacement supervisor missed the handover. "Communicate better" won't fix either problem without a specific change to how instructions reach those people.

For your next revision, start with the approved plan and ask the affected supplier leads to explain what their teams will do differently. Check their answers before releasing the change. That conversation is where you find out whether you have one workable plan or several versions people are about to follow.