How to rehearse an event emergency without a full live drill

Your emergency plan names the event manager, the security lead and the person who can stop the show. But have those people actually worked through a problem together? If everyone thinks someone else will make the announcement, you'll want to discover that before a paying audience arrives.

An event emergency tabletop exercise lets you rehearse those decisions without moving a real crowd or interrupting a live performance. You bring the people who would respond together, describe a realistic incident and ask them to explain what they would do using the current plan. Then you introduce new information and follow the response through the handoffs.

The useful result is a record of what worked, what nobody could answer and what needs changing before the event. A lively discussion alone doesn't give you that. You need someone recording the decisions, named people responsible for the fixes and a later check that those fixes work.

You also need to be honest about the limits. Discussing an evacuation cannot establish how quickly people can leave. Agreeing to use radios cannot prove the radios work across your site. A tabletop exercise helps you examine the plan and the people using it. Practical tests, competent assessment and any required drills still have their own jobs to do.

Decide what you want the exercise to answer

Start with a question your event team genuinely needs to resolve. Perhaps nobody has tested the connection between stopping admissions and stopping a performance. Perhaps your venue has changed its emergency arrangements, or your usual event manager won't be there this time. Those are useful reasons to rehearse.

"Are we ready for an emergency?" is too broad for one discussion. Try something you can observe instead. Can the duty team recognise when the agreed response is needed, contact the person authorised to decide and communicate that decision to the people who must act? Choose the particular response from your own assessed risks.

Great Britain's Health and Safety Executive identifies tabletop exercises as one way to test event emergency plans. It also says communication equipment should be tested before the event. Those are connected tasks, with different evidence behind them. Keep both on your preparation schedule.

Write the exercise objectives before writing the story. You might want participants to find the correct deputy, explain how a show stop reaches the performer and identify who updates staff at the entrance. If those are the objectives, your scenario needs to create those decisions without burying them under unrelated problems.

Keep the first exercise manageable. One well explored scenario will usually tell you more about an unclear handoff than a rapid tour through every emergency in the plan. You can schedule another exercise for a different risk once you've resolved the first set of findings.

If you still need the underlying plan, start with our event contingency plan guide. This exercise assumes the relevant arrangements already exist. Otherwise the meeting becomes a planning workshop, which can be useful, but won't show whether people can follow an agreed response.

The UK Resilience Academy's Exercising Best Practice Guidance starts exercise planning with a defined purpose and objectives, and treats exercises as part of wider preparation. It is guidance for resilience professionals, not a legal requirement imposed on every event organiser. You can use its planning approach while checking the specific duties and arrangements that apply to your event.

That distinction matters when someone asks whether the meeting makes the event compliant. Record what the exercise examined and the evidence it produced. Have the relevant responsible people assess their own requirements. A useful discussion can reveal missing work, but it cannot turn an unassessed arrangement into an approved one simply because everyone attended the same meeting.

Bring the people who would actually respond

Invite people because of the decisions or actions they would own during the incident. That may include the event duty manager, venue representative, security supervisor, production lead, admissions lead, medical provider and the person responsible for public communication. The exact group depends on your event and scenario.

Ask those people who else their response depends on. An event manager may authorise a show stop, while a stage manager contacts the performer and a sound operator handles the announcement. If you invite only the managers, the discussion can miss the point where their instruction becomes an action.

Include deputies where the plan relies on them. You don't need to remove the usual lead from every exercise, but you should find out what happens when they cannot answer. Check whether the deputy has the authority, information and access needed to act. Knowing their name isn't enough.

Coordinate involvement with relevant authorities and emergency services through your established arrangements. Don't assume attendance means they have approved your plan, or invent their response because a representative couldn't attend. Record that part as an assumption requiring confirmation. The exercise cannot commit another organisation to resources it hasn't agreed to provide.

Choose a facilitator who can keep the discussion on the objectives and challenge vague answers without taking over the response. Someone with appropriate event and exercise experience can help, especially when the scenario involves complex safety arrangements. The most senior person in the room isn't automatically the best facilitator.

Assign a separate recorder if you can. The facilitator needs to listen and ask the next useful question. The recorder needs to catch who decided what, which document they used and where the answer remained uncertain. Combining both jobs can leave you with a busy conversation and very little usable evidence afterwards.

Use the real event documents

Ask participants to bring the versions they expect to use on the day. That includes the emergency plan, relevant site plan, contact list and role instructions. Add the particular supplier or venue information needed for the scenario. You don't need to distribute every contract the business holds.

Put a date or version on the exercise pack and record which documents were used. If admissions is following an older site layout, that's already a finding. Don't quietly hand over the correct drawing and pretend everyone began with the same information. Find out how the wrong version remained in circulation.

Check that people can access their documents under the conditions you're discussing. A contact list in a shared folder may be convenient during the meeting. What happens if the scenario includes a connection failure? Identify the approved offline arrangements and arrange a separate access check where necessary. Don't solve the exercise by assuming everyone's personal phone has the file.

Use fictional personal information in exercise messages and records. You can test how staff would report a medical incident without circulating a real attendee's health details. Keep sensitive site and security information restricted to the people who need it, including after the session ends.

Prepare a short participant brief explaining the purpose, scope and boundaries. Say whether the exercise covers the period before doors, the live event or the return to normal operations. Tell participants what is simulated and what remains a real responsibility while they're in the meeting.

Agree how to stop the exercise if a real incident occurs. Use your organisation's established procedure and make it clear before starting. Keep normal emergency reporting available. Exercise paperwork and messages should be unmistakably labelled so someone outside the room cannot mistake a fictional report for a real warning.

Build a scenario around your event's risks

Use your risk assessment to choose the incident. Our event risk assessment template explains how to connect a hazard to the people exposed, the controls and the person responsible. Your exercise should examine whether the planned response still works when the relevant condition develops.

A realistic scenario needs enough context for people to decide. State the event phase, which areas are open, which teams are on duty and what information is confirmed. Describe what the reporting person can actually observe directly. A steward reporting an obstruction won't automatically know its cause, the duration or its effect on another part of the site.

Avoid writing a scenario that has only one acceptable sentence as its answer. You want to understand the team's reasoning, including what they need to verify. Sometimes the useful finding is that the plan doesn't distinguish between two conditions requiring different responses. Let participants identify that uncertainty instead of steering them towards your preferred wording.

Check the scenario with the relevant competent people before the session. A made up equipment limit or invented evacuation destination can lead the discussion into an unsafe assumption. Use the event's actual approved arrangements and technical advice, with fictional incident details clearly separated from them.

For weather scenarios, use the relevant local official weather service and your event's agreed procedures. The US National Weather Service's lightning guidance for organised outdoor activities illustrates why a plan needs clear decisions about stopping, suitable shelter and resuming. Its guidance doesn't supply a universal operating plan for every event or jurisdiction.

Make the scenario believable rather than spectacular. If your first rehearsal combines a power failure, a missing child, a major security incident and an unavailable venue, you may spend the meeting arguing about the story. A simpler incident can expose the same unclear authority much more effectively.

Prepare new information without scripting every answer

An exercise often develops through a series of new reports, sometimes called injects. These are the messages or changes the facilitator introduces to make participants reconsider what they know. Plain language works fine. You can simply call them scenario updates in the materials your team receives.

Each update should serve an objective. If you want to test deputy arrangements, make the normal decision maker unavailable. If you want to examine how teams share information, give one team a relevant report that the others haven't received. Don't add complications solely to keep the room entertained.

Prepare a facilitator copy showing when an update becomes relevant, which role receives it and what question it should help explore. You don't need to reveal that whole sequence to participants. They do need the opening situation, the exercise rules and the information their roles would reasonably have.

Leave room to follow their decisions. If participants identify a valid alternative within the plan, don't force them back towards the response you imagined. Ask how it would work, which checks it needs and who would confirm completion. If you cannot judge the answer, record it for specialist review rather than improvising a ruling.

CISA's tabletop exercise package documents include separate material for planners, facilitators, participants and evaluation. That separation is useful even for a small event team. Participants need a clear situation to respond to; the facilitator needs prompts; the recorder needs a way to capture what happens.

Have an agreed way to handle facts the scenario hasn't specified. The facilitator might supply a reasonable exercise assumption, consult the prepared notes or mark the question unresolved. Record whichever route you use. Otherwise a convenient answer invented during the discussion can quietly become something the team believes is already arranged.

Write a brief your team can use

Before you send the invitation, put the exercise details into a short working brief. Start with the event name, the event version being examined and the person responsible for the exercise. State the question in ordinary language. Everyone reading it should understand why their attendance matters and what they need to prepare.

Describe the boundaries next. For a session about a blocked route, specify which operating phase and area the discussion covers. Say that nobody will move attendees, activate alarms, call emergency services or send public messages as part of the simulation. Any separately agreed practical activity needs its own planning and control.

List the participants by their event roles and confirm who will attend for each organisation. Add the facilitator and recorder separately. Ask each participant to identify a substitute if they cannot attend, then decide whether that substitute can meaningfully take part. An unavailable essential decision maker may require changing the session rather than pressing ahead with an empty chair.

Name the documents participants need, where the current versions are held and how exercise findings will be recorded. Include the meeting arrangements and any access needs. For a remote session, check that everyone can see the same site plan and hear the discussion. A shared screen that participants cannot read creates a meeting problem before you've even begun examining the event response.

Finish the brief with what happens afterwards. State who reviews the findings, who assigns actions and how participants will receive revised instructions. Reserve the follow-up meeting or review point now. When the calendar already contains a decision about outstanding work, the report is less likely to disappear beneath the next production deadline.

Run the discussion as a sequence of decisions

Begin by checking everyone understands their role and the exercise boundaries. Then read the opening situation without adding hints about the intended response. Ask the role receiving the first report what they do next. Let them use the documents they would actually have.

Keep asking for the person, the message and the next action. "We'd tell security" leaves several questions unanswered. Which security role receives the report? What information goes with it? Who confirms they've received it? What does the reporting person do if nobody responds? Those details determine whether the handoff works.

Ask participants to distinguish facts from assumptions. A caller may report that an entrance is blocked. The team may assume another route remains usable. Have them explain who would confirm that route's condition and how the answer would reach the decision maker. An unverified alternative should remain unverified in the record.

Don't let the most confident speaker answer for everybody. Ask the admissions supervisor what their team would understand from the instruction, then ask the person sending it whether that matches what they intended. Differences often become visible only when both ends explain the same exchange.

You can pause to discuss a gap, then resume using an explicitly recorded assumption. That keeps one missing answer from consuming the whole session. It doesn't close the gap. Put the unresolved question on the action list and identify whether it prevents the relevant plan from being relied upon.

Keep exercise time separate from incident time. The team may take a long discussion to examine a decision that would need an immediate response in reality. Record that limitation. A quick answer around a table also cannot demonstrate a real response time, because nobody has performed the action under event conditions.

Work through a blocked route example

Here's a fictional scenario structure to adapt with your venue and safety advisers. It is a way to organise the discussion, not a proposed emergency procedure. The actual route decisions, staffing and response must come from the arrangements assessed for your event.

The event is operating and more ticket holders are still arriving. A steward reports that an incident has made a planned route unavailable. The report identifies the location using the current site plan, but the effect on nearby areas isn't yet confirmed. Start by asking who receives that report and what they need to establish.

Have the duty manager explain how the plan applies. Who assesses the affected area? Who has authority to change admissions or the programme? Which immediate actions can staff take under their existing instructions? The facilitator should record the answers and their sources, without inventing a safe substitute route.

Now introduce a relevant complication. The person normally responsible for the next decision is unavailable, and the deputy must take over. Ask the deputy to find the current information, state the authority they have and explain who needs to know they are acting. Record any missing access or conflicting instructions.

Next, the admissions lead reports that arriving buyers are still following old directions. Ask how the team communicates with those buyers and the staff receiving them. Any exercise wording must use the event's assessed alternative arrangements. If those arrangements haven't been confirmed, the exercise has found a planning problem that needs resolving.

Finally, provide a report that the original obstruction has been removed. Don't end the exercise there. Ask who checks the affected area, which other conditions must be satisfied and who authorises the next operational step. Removing one problem doesn't establish that every affected service and team is ready.

Examine the message at both ends

Public communication deserves its own attention during the exercise. Ask the responsible person to explain how an approved instruction reaches people already inside, people queuing and people still travelling. Different groups may need different actions, even when the underlying incident is the same.

Read proposed wording aloud in the room as a simulation, without broadcasting it. Can someone unfamiliar with the site understand where they should go or what they should do? Does the wording use the same location names as the signs and staff instructions? Ask a participant outside the communications role to explain what they understood.

Include accessible communication arrangements in the discussion. Who may miss an announcement, need another format or require assistance to follow an instruction? Involve people with relevant accessibility knowledge when planning and reviewing the exercise. Don't assume that adding a sentence about assistance proves the arrangements can deliver it.

Keep urgent onsite instructions separate from later booking information. An email about changed ticket arrangements cannot substitute for the communication needed to protect people at the venue. Conversely, a brief announcement during a disruption won't answer every buyer's question about the remainder of the programme or their booking afterwards.

Ask who updates the public event information and scheduled messages once a change is confirmed. An automated reminder telling buyers to arrive normally can conflict with a current instruction. The exercise should identify the person who checks those channels and the approval they need, rather than assuming someone in marketing will notice.

Test the return message too. When one team sends an instruction, what confirmation tells event control that the recipients understood and acted? A sent message and a completed action are different facts. Record both where they matter, and leave any missing confirmation visible for follow-up.

Record findings while you can still explain them

Write observations against the objectives you set at the start. "Communication needs improving" won't help the person assigned to fix it. Record the actual exchange, what was unclear and the effect on the next decision. Keep the wording factual so people can recognise the problem without arguing about a judgement of their performance.

For example, the admissions supervisor may have found an older contact list that named a manager who won't be onsite. The finding is the outdated list and the resulting unanswered handoff. The correction needs to address how approved contacts are issued and withdrawn, not simply tell that supervisor to be more careful.

Separate a plan problem from a knowledge problem. If the deputy's authority is missing from the plan, update the agreed arrangements. If the plan states it clearly but the deputy hasn't been briefed, training may be needed. Sometimes both are true. Ask the people involved before assigning a solution.

Give each agreed corrective action an owner, a due date and evidence required for closure. The evidence might be a revised role instruction followed by a repeat scenario, a confirmed supplier arrangement or a practical equipment test. Choose it according to the finding. A new document cannot prove an equipment repair works.

FEMA's exercise improvement planning resources connect exercise findings with corrective actions that are monitored and implemented. Apply that principle to your event records. You don't need an elaborate report, but you do need to know which actions remain open and what their consequences are.

Keep useful successes in the record as well. If a deputy found the plan, identified the right authority and passed a clear instruction, record the conditions that helped. You want to retain working arrangements when you revise the documents, especially when a later team inherits the event.

Consider a worked finding from the fictional blocked route exercise. The deputy correctly decides which role must assess the affected area, but the instruction names an entrance differently from the site plan. The receiving supervisor asks for clarification. Until that happens, the two people are discussing different locations without realising it.

The action should identify the inconsistent location names across the documents and staff instructions. Name the person responsible for agreeing the correct terms with the venue, then update the affected material through your normal document process. Close the action after the relevant people use the revised wording in a repeat exchange and demonstrate that they mean the same place.

That repeat exchange checks understanding. It still doesn't establish that the route is suitable, available or capable of handling the people who may need it. Keep those assessments and physical checks with the competent people responsible. Recording precisely what your follow-up proves prevents a sensible paperwork correction from becoming an unsupported claim about the whole emergency plan.

Follow up before calling the exercise complete

Ask participants for immediate observations before they leave. What surprised them? What information couldn't they find? Which assumption should the planning team check? Then reconcile those comments with the recorder's notes. Someone may remember a decision differently, and sorting that out early helps you avoid issuing a misleading action list.

Send the findings to the people who can resolve them, with sensitive details limited appropriately. A supplier may need only the action relevant to its service. A wider volunteer briefing may need the revised instruction without the full discussion of a hypothetical security problem. Decide who needs which information.

Arrange a review point before the affected arrangements must be ready. Work backwards from the actual delivery and assessment requirements. If a finding needs a venue change, supplier booking or additional training, the deadline must allow that work. Don't choose a convenient report date that leaves no time to correct anything.

Treat an unresolved issue according to its consequences. A safety problem can require changes to the plan, specialist assessment or an operational decision. It cannot be accepted simply because the action list has become inconvenient. Follow the event's established authority and escalation arrangements, and record what remains unresolved.

Repeat the part of the exercise affected by a change. If you clarified the deputy's authority, ask that deputy to work through the decision again using the revised instructions. If you changed a communication procedure, check the sender and receiver understand it. Book any necessary practical test separately and retain its result.

Our technical rehearsal guide covers joining production cues and equipment under rehearsal conditions. Coordinate the work where the same people are involved, but keep the evidence clear. A smooth programme rehearsal doesn't close every emergency planning action, and a useful emergency discussion doesn't demonstrate that the show equipment works.

Keep the exercise relevant as the event changes

An exercise describes one version of your event. If the site layout, audience arrangements, programme, supplier or key personnel change, check whether the conclusions still apply. A contact handoff tested with the original venue team needs revisiting when a different team takes responsibility.

Record the changes that require another review in the event planning process. That doesn't mean repeating the entire exercise whenever a minor detail moves. Ask which objective, response or assumption the change affects. Repeat the relevant discussion or test, with the people who now own the work.

Protect time for this before the final rush. A session held immediately before doors may reveal a problem you cannot resolve within the remaining time. Schedule early enough to make meaningful corrections, then check significant later changes. Your event's complexity and risk should determine the preparation required.

For a smaller paid event, the exercise may involve a compact team around the venue's established arrangements. You still need the right people and a record of what you found. A larger event may need several exercises addressing different teams or phases, with specialist support and coordination across organisations.

Don't convert attendance into a claim of readiness. A signed register establishes who participated. It doesn't prove every objective was met, every action was closed or every person working the event understands their responsibilities. Keep those statements separate when you brief the wider team or report to a client.

Choose the question your team is least comfortable answering, bring the current plan and ask the people who would act to work through it. Finish by assigning the unresolved work and deciding how you'll verify it. The next time you gather the team, start with what changed and whether it solved the problem you actually found.