An event crisis plan is a prepared set of decisions that spells out who's in charge and what happens the moment something goes seriously wrong — an equipment failure, a medical incident, a sudden change in weather. It isn't a list of every disaster imaginable; it's a clear division of roles and fast first steps for the situations that can realistically happen at your event. Without one, the first thing a team has to figure out mid-crisis is who's even allowed to decide — and that's exactly the time a real crisis doesn't leave you.
What a crisis plan is and why corporate events need one
A crisis plan assigns a named person and a defined response to each foreseeable situation — not a vague instruction to "stay calm." Its purpose isn't to prevent every problem, because that's not realistic at any event; it's to shrink the gap between something happening and the team acting on it. A small internal meeting might need a one-page version. A conference with hundreds of guests or a public event needs a more detailed document with clear escalation steps.
Companies tend to underinvest in this because most events run without a serious incident. That's exactly why, when something does happen, neither the experience nor the preparation is there — and improvising under pressure produces worse decisions than the same team would make calmly in advance.
What situations a crisis plan typically needs to cover
Most incidents fall into technical, medical, organizational, and safety categories, and they share one trait: they demand a fast decision with no time for a long discussion. The table below outlines common scenarios and who should own the first response.
| Type | Example | First responder | |---|---|---| | Technical | Sound, projection, or power failure | Technical production team | | Medical | A guest collapses, an injury, an allergic reaction | Person with first-aid training, plus emergency services contact | | Organizational | A key speaker running late, a supplier cancelling | Event manager | | Safety | Entry breach, conflict between guests | Security staff or a designated coordinator | | External | Sudden weather change at an outdoor event | Event manager, working from a pre-agreed backup plan |
Not every situation carries the same weight. A technical failure usually needs a few minutes and some improvisation with the running order. A medical or safety incident needs the programme paused immediately and a defined procedure — not something worked out on the spot.
Who on the team should have the authority to act
Authority should sit with one named person who can decide without waiting for approval — usually the lead event manager or on-site production coordinator. If a decision has to wait on someone who isn't physically there, the plan stops being useful. That person needs a short contact list at hand — technical crew, medical services, venue management, security — and clarity on which situations they resolve themselves versus which ones need company leadership or the client looped in immediately.
It's just as important to name a backup for the case where the crisis directly involves the lead decision-maker — a medical issue affecting the coordinator themselves, for instance. A plan with no backup only works in the scenario where nothing unusual happens to the person running it, which is rarely how a real crisis unfolds.
How to actually build a crisis plan
Building one starts with identifying the risks specific to that event, not copying a generic template. An outdoor event carries different risks than a gala dinner in a hotel ballroom; a conference with international speakers carries different risks than an internal team day. A workable process looks like this:
- Walk through the event's running order and flag the highest-risk moments — guest arrival, transitions between spaces, technically demanding segments.
- Assign a concrete response and a named owner to each risk.
- Prepare a contact list that every production team member carries, not just one person.
- Brief the full team on the plan in person before the event, not just by email.
- After the event, review what actually happened and what the plan didn't cover.
A plan that's written up and never walked through with the team out loud has a low chance of working the moment it's actually needed.
How to test the plan before it's needed for real
A crisis plan that only exists on paper can still be tested without an actual crisis — through a short tabletop exercise where the team walks through a handful of realistic scenarios and says out loud what they'd do in the moment. This usually takes thirty to sixty minutes and surfaces gaps a written document can't show — two people who each assume the other owns a decision, or a venue contact known to only one person who might not even be on site that day.
For recurring event formats — an annual conference, a yearly sports day — it's worth repeating the tabletop exercise before every edition, not just once when the plan is first written. The team changes, venues change, and a plan that worked last year may not cover the risks of this year's format.
What to do right after an incident
The first priority is stabilizing the situation, not immediately assigning blame or managing outward communication. Only once the situation is under control does it make sense to decide whether and how the programme continues, and to tell guests what's happening in a clear, calm way. Slow or unclear communication toward guests usually does more damage than the incident itself.
After the event, a short written record is worth the time — what happened, how the team responded, what should change next time. That record becomes the starting point for updating the crisis plan before the next event.
Where to start
A crisis plan doesn't need to be built from scratch for every event — a basic structure the team adapts to each specific occasion is enough. If you're planning a corporate event or conference and want a crisis scenario thought through in advance, take a look at our corporate events service or reach out through our contact form — a crisis plan is a standard part of how we produce any larger event.