When something goes wrong during an event: a calm playbook

Things go wrong at events. A vendor arrives late, a microphone fails, a guest feels unwell, the power flickers. No amount of planning removes the possibility. What planning can do is shrink the consequences, by making sure the team knows what to do when the moment comes.

The following playbook is general by design. Each situation is different, and serious emergencies should always follow local safety rules and the guidance of emergency services. But the underlying approach, which is to pause, assess, decide, communicate and follow up, applies widely.

Step one: pause and breathe

The first few seconds shape everything that follows. A manager who reacts instantly, with raised voice and quick movements, signals alarm to everyone nearby. A manager who takes a breath, steps slightly aside and looks at the situation signals control.

This is not about slowness. It is about making sure the first action is a good one. If someone is in danger, act immediately. If not, a moment of thought is almost always worth it.

Step two: assess

Ask a few simple questions. What exactly has happened? Is anyone at risk? Is the problem growing, stable or fixed already? Who is affected, and do they know? What is the next event in the schedule, and how much time is there?

Separate what you know from what you suspect. Early information is often incomplete, so avoid acting on assumptions when a quick check will do.

Step three: decide and assign

Once you understand the situation, choose a course of action and give it to a specific person. Vague requests such as "someone should look at the speaker" lead to confusion. A clear assignment, such as asking a named team member to check the speaker and report back in two minutes, leads to action.

• Prioritize safety first, then guest experience, then schedule, then convenience.
• Choose the simplest fix that works, even if it is not elegant.
• Have a backup in mind in case the first fix fails.
• Keep your own hands free for coordinating, rather than getting absorbed in the repair.

Step four: communicate

Silence breeds worry. Staff need to know what is happening and what is expected of them. The client may need to hear about it, calmly and briefly, before they hear about it from someone else.

When speaking to a client, lead with what you are doing about it. Describe the issue in a sentence, state the plan and offer a time when you will update them. Avoid over-explaining, and avoid blaming vendors or colleagues in front of guests.

With guests, the right level of communication depends on how visible the problem is. Many issues can be solved quietly with no announcement. If guests must be told, keep the tone matter-of-fact and warm.

Step five: protect the experience

A problem rarely needs to become the guests' problem. Think about how to keep the rest of the event running while the issue is resolved. If the sound system fails, can the program shift to a segment that does not need it? If service is delayed, can bar staff keep guests comfortable in the meantime?

Small gestures help. A complimentary drink, a quick apology or a personal check-in can turn a frustrating moment into one where the guest feels cared for.

Common situations worth rehearsing

It helps to walk the team through a handful of scenarios in advance. Talking through them, even for a few minutes, builds the reflexes that matter.

• A guest becomes ill or is injured.
• A piece of equipment fails mid-program.
• A vendor does not show up or arrives well behind schedule.
• A disagreement arises between guests, or a guest becomes disruptive.
• A sudden change in weather affects an outdoor portion of the event.
• A power or building system issue interrupts service.

For each one, decide who is in charge, who is notified, and what the first three actions are. Write the answers down and keep them where staff can find them.

Step six: follow up and learn

After the event, take time to review what happened. What was the root cause? Which parts of the response worked? What would make the next occurrence smaller or easier to handle?

Share the lessons with the team without assigning blame. A team that can discuss mistakes openly will catch more of them in the future. Update checklists, contact lists and training notes so the improvements stick.

Calm is not a personality trait. It is a practice, built from preparation and repeated until it becomes habit. When the unexpected arrives, the team that has rehearsed will look like it has done this a hundred times. That is exactly the point.