How to Conduct a Tabletop Exercise for Better Emergency ...https://www.youtube.com/watch
4%
15 Tabletop Exercise Examples to Prepare for Emergency – Most Common Scenarioshttps://www.alert-software.com/blog/tabletop-exercise-examples-for-emergency-preparedness
4%
Nexight Insight: 9 Steps to Design a Powerful Tabletop Exercise | Nexight Grouphttps://nexightgroup.com/9-steps-to-design-a-powerful-tabletop-exercise/
3%
Tabletop Exercise Instructions For Planned Events and Unplanned Incidents/Emergencies: General Guidelines - FHWA Office of Operationshttps://ops.fhwa.dot.gov/publications/tabletopexercpe/index.htm
A good tabletop exercise (TTX) should feel real enough to expose gaps, but safe enough that people can experiment and fail without real-world consequences. FEMA’s HSEEP framework emphasizes four linked phases: design/development, conduct, evaluation, and improvement planning.
1. Start with 2–4 specific objectives
Don't start with “let's test our emergency plan.” Start with questions you genuinely need answered.
For example:
Can the team establish incident command and assign responsibilities within 15 minutes?
Can we maintain communications if our primary system fails?
Can we make and document an evacuation/shelter decision using the information available?
Can we notify employees, customers, families, regulators, or other stakeholders appropriately?
Can we transition from immediate response to recovery?
Make the objectives observable. FEMA recommends aligning objectives with the capabilities and critical tasks you want to evaluate.
2. Choose a scenario that is plausible—but uncomfortable
Use your organization's actual risk assessment, previous incidents, near misses, and known vulnerabilities.
Conducting a realistic and effective tabletop exercise (TTX) for your emergency response team comes down to careful planning, immersive pacing, and a robust after-action review. Follow this step-by-step framework to build and run your session:
Define Objectives and Scope : Establish clear, measurable goals for what you want to test (e.g., communication protocols, handoff procedures, or decision-making under time pressure). Keep the scope manageable within your allocated time frame.
Develop a Realistic Scenario : Build a crisis narrative tailored to your organization's actual risk profile (such as a cyberattack, active threat, or severe weather incident). Make sure it reflects current operational environments. For official guidance and templates, reference resources from .
Question: How do I conduct a realistic and effective tabletop exercise for our emergency response team?
Google AI Mode· Sep 21, 2026
Conducting a realistic and effective tabletop exercise (TTX) for your emergency response team comes down to careful planning, immersive pacing, and a strong post-game debrief. Here is a step-by-step framework to make it impactful:
Define Objectives and Scope : Establish 2 to 3 clear, measurable goals (e.g., testing communication protocols during an active cyber-incident or evaluating role handoffs during the first $30$ minutes of a facility evacuation). Keep the scope narrow enough to manage in a single session.
Develop a Realistic Scenario : Build a timeline based on credible local threats or realistic organizational vulnerabilities. Use a Master Scenario Events List (MSEL) to script injects—timed messages, phone calls, or simulated news alerts—that force participants to react and adapt.
Select the Right Participants : Include both the core emergency response team and key decision-makers. Assign a neutral facilitator to keep momentum going, a few evaluators to track decision points, and let players operate in their actual roles.
Establish the Ground Rules : Announce at the start that the exercise is a "safe space" for learning, not an audit or performance review. Use a "no-fault" policy so team members feel comfortable exposing operational gaps or communication breakdowns.
Question: How do I conduct a realistic and effective tabletop exercise for our emergency response team?
Question: How do I conduct a realistic and effective tabletop exercise for our emergency response team?
Google AI Mode· Sep 17, 2026
Conducting a realistic and effective tabletop exercise (TTX) for your emergency response team comes down to balancing pressure with psychological safety. Here is a step-by-step roadmap to run a scenario that actually moves the needle on your organization's preparedness.
Define Objectives : Establish clear, measurable goals (e.g., testing communication protocols during the first 30 minutes of an active incident or clarifying decision-making authority between the executive team and field leads).
Build a Realistic Scenario : Tailor the event to your actual geographic, operational, or cyber threats. Keep it grounded so participants don't spend time debating whether a completely impossible event could happen.
Appoint a Facilitator and Injectors : Designate a neutral facilitator to keep the pace moving and assign an "inject master" to drop unexpected updates (called injects)—such as a sudden media inquiry, a power failure, or conflicting data—via email, phone calls, or printed handouts.
Establish Ground Rules : Announce at the start that the exercise is a safe space for learning , not an audit or a test of individual competence. Emphasize that making mistakes during the TTX is a success because it highlights gaps before a real crisis hits.
Question: How do I conduct a realistic and effective tabletop exercise for our emergency response team?
Question: How do I conduct a realistic and effective tabletop exercise for our emergency response team?
Google AI Mode· Sep 13, 2026
Conducting a realistic and effective tabletop exercise (TTX) requires careful planning, a safe environment, and a focus on discussion rather than stress. Here is a step-by-step guide to running one smoothly:
Define the Objectives and Scope : Establish what you are testing (e.g., communication flow, evacuation protocols, or leadership decision-making during a specific crisis like a cyberattack or severe weather). Keep the scope manageable.
Design a Realistic Scenario : Build a timeline based on plausible local threats. Make sure the scenario has enough detail to force real choices, but avoid making it an unwinnable "doomsday" scenario that frustrates participants.
Select and Brief Participants : Bring together the right cross-functional team members (decision-makers, operators, and communicators). Give them a brief overview of the rules: it's a safe-to-fail learning environment, not an audit or a test of individual competence.
Appoint a Facilitator and Injectors : Use an experienced facilitator to keep the conversation moving and manage dominant personalities. Prepare "injects"—new pieces of information, curveballs, or media updates—to drop in at timed intervals to test adaptability.
Encourage Open Discussion : Pause the action to ask probing questions: , , or Focus on uncovering gaps in plans rather than rushing to a clean resolution.
Question: How do I conduct a realistic and effective tabletop exercise for our emergency response team?
Question: How do I conduct a realistic and effective tabletop exercise for our emergency response team?
Google AI Mode· Sep 9, 2026
Conducting a realistic and effective tabletop exercise (TTX) for your emergency response team comes down to balancing pressure with psychological safety. Here is a step-by-step framework to build, run, and debrief an exercise that actually moves the needle on your preparedness.
1. Define Objectives and Scope
Identify the goal: Pick 1 or 2 specific outcomes (e.g., testing our communication flow during the first 15 minutes, or evaluating decision-making under resource scarcity). Don't try to test everything at once.
Select the scenario: Choose a realistic threat based on your risk assessment (e.g., an active cyberattack, severe weather facility impact, or a critical supply chain failure).
Determine the audience: Decide who needs to be in the room—core responders, leadership, or external partners. Keep the group intimate enough that everyone speaks.
2. Design the Scenario and Injects
Establish a baseline: Start with a calm, normal operating picture so the disruption feels stark.
A useful scenario has complications, not just one dramatic event.
For example:
09:15 Monday: A severe storm damages part of the facility. Power is intermittent. Two employees are unaccounted for. The normal communications system is unavailable. Local authorities are issuing conflicting information about road closures.
Then introduce developments gradually:
+10 min: An employee reports a possible injury.
+20 min: Cellular service becomes unreliable.
+30 min: Someone posts an unverified claim about the incident on social media.
+40 min: A key manager cannot be reached.
+50 min: The team learns that a critical supplier will not be able to deliver.
+60 min: Leadership asks when normal operations can resume.
The important part is that participants don't know the injects in advance.
3. Build an exercise team separate from the players
Ideally, have:
Exercise director: owns the exercise.
Facilitator: drives discussion and keeps the group moving.
Controllers: introduce scenario developments.
Evaluators/observers: record what actually happens.
Players: the emergency-response personnel being tested.
CISA similarly recommends evaluators/data collectors who document how participants respond relative to plans, policies, and procedures.
Don't make the emergency manager both a player and the primary evaluator if you can avoid it.
4. Make participants use their real procedures
This is one of the biggest differences between a useful exercise and a discussion that merely sounds good.
If someone says:
“We'd notify the emergency operations center.”
Ask:
“Show us how you'd do that.”
Then determine:
Who makes the call?
What number/system do they use?
Who has authority?
What information goes into the notification?
What happens if that person doesn't answer?
Where is the action documented?
Don't rescue participants when they discover that a procedure doesn't work. The gap is one of the most valuable results of the exercise.
5. Use injects to create decisions, not chaos
Every inject should serve an objective.
A simple MSEL (Master Scenario Events List) might look like:
Time
Inject
Intended decision
Objective
09:00
Initial incident
Activate response structure?
Command
09:15
Missing employee
Search/evacuate?
Life safety
09:25
Communications failure
Switch communications method?
Communications
09:40
Media inquiry
Who responds and what do they say?
Public information
10:00
Critical supplier unavailable
Prioritize resources?
Continuity
10:20
Executive asks for status
What information is reliable?
Situational awareness
FEMA provides an MSEL template specifically for organizing exercise events and injects.
6. Let the participants drive
A facilitator should resist the temptation to turn the exercise into a lecture.
Instead of:
“You should activate your emergency operations plan now.”
Ask:
“What are you doing next?”
Then:
“Who has authority to make that decision?”
And:
“What information are you basing that decision on?”
Good follow-up questions expose assumptions without telling participants what the “right” answer is.
CISA's guidance likewise recommends tailoring discussion questions to the exercise objectives rather than treating a question list as definitive.
7. Deliberately introduce uncertainty
Real emergencies rarely provide perfect information.
Give participants things like:
conflicting reports;
incomplete information;
unavailable personnel;
failed communications;
changing conditions;
competing priorities;
requests from senior leadership;
information that hasn't yet been verified.
But avoid making the scenario artificially difficult just for entertainment. Every complication should test something meaningful.
8. Evaluate behaviors, not personalities
Observers should record things such as:
Good evidence
“At 09:18, the team identified an incident commander and established a communications channel.”
Useful gap
“Participants could not identify who had authority to approve external communications.”
Not useful
“The team seemed disorganized.”
Use objective evidence wherever possible. FEMA describes Exercise Evaluation Guides as a way to consistently collect observations against objectives, capabilities, targets, and critical tasks.
9. Conduct a hotwash immediately
At the end, ask each participant:
What worked?
What didn't work?
What surprised you?
What information did you wish you had?
What decision was hardest?
Which procedure needs to change?
What should we practice next?
Don't let senior leaders dominate this discussion. Front-line participants often identify the most consequential practical problems.
10. Turn findings into actual corrective actions
This is where many exercises fail.
Don't finish with:
“We need better communication.”
Turn it into:
Finding: Primary emergency notification system depends on a single administrator account.
Corrective action: Establish two backup administrators and document the credential-recovery process.
Owner: IT/Business Continuity
Due: 30 days
Validation: Conduct a communications test.
FEMA specifically treats improvement planning as a core part of the exercise cycle, with corrective actions tracked and implemented rather than simply documented.
A practical 2-hour format
For a first exercise, I'd use something like:
0:00–0:10 — Welcome, objectives, ground rules
0:10–0:20 — Initial scenario
0:20–0:40 — Response discussion
0:40–0:50 — Inject #1
0:50–1:10 — Response discussion
1:10–1:20 — Inject #2
1:20–1:40 — Complications/decision-making
1:40–1:50 — Final inject and transition toward recovery
1:50–2:00 — Hotwash
For the first exercise, two hours of focused discussion is generally more useful than a four-hour marathon.
The realism test
Before running the exercise, ask yourself:
“If this happened tomorrow morning, would our team actually have to make these decisions with this information and these constraints?”
If the answer is yes, you're probably testing something meaningful.
FEMA also provides downloadable HSEEP templates for exercise plans, facilitator guides, MSELs, evaluation, conduct, and AAR/improvement planning.
If you tell me what kind of organization you have (business, hospital, school, municipality, industrial facility, etc.), team size, and the emergency you want to test, I can build you a complete 2-hour tabletop package with the scenario, injects, facilitator questions, evaluator checklist, and hotwash/AAR template.
Validation: Conduct a communications test.
FEMA specifically treats improvement planning as a core part of the exercise cycle, with corrective actions tracked and implemented rather than simply documented.
A practical 2-hour format
CISA's guidance likewise recommends tailoring discussion questions to the exercise objectives rather than treating a question list as definitive.
7. Deliberately introduce uncertainty
Real emergencies rarely provide perfect information.
Give participants things like:
Ready.gov
Draft the Inject Schedule : Create a timed timeline of "injects"—incoming phone calls, news alerts, or escalating field reports—that force participants to react, adapt, and communicate dynamically during the exercise.
Assign Roles Clearly : Designate specific participants for the response team (Incident Commander, Operations, Communications, etc.), a neutral facilitator to keep pacing, and evaluators to observe decision-making without interfering.
Establish Ground Rules : Announce at the start that it is a "no-fault" learning environment. Emphasize that making mistakes and exposing friction points during the exercise is a success because it prevents those errors during a real crisis.
Execute the Exercise : Run the scenario while the facilitator introduces injects and presses participants for concrete actions, resource requests, and inter-agency or internal notifications.
Conduct the Hotwash Immediately After : Hold a debrief right when the exercise ends while details are fresh. Ask participants what went well, where communication broke down, and what tools or information they wished they had.
Write the After-Action Report (AAR) : Document the lessons learned, assign accountable owners for identified gaps, and set strict deadlines for updating your emergency response plans.
If you want to tailor this further, let me know:
What specific type of emergency or threat you are planning to test
How much time you have for the exercise
I can help you outline a customized scenario timeline and inject list.
Run the Simulation and Inject Pacing : Introduce the starting scenario and pace the injects based on how the team responds. If they get stuck, the facilitator can nudge them with clarifying questions rather than giving away solutions.
Conduct a Hot Wash (Immediate Debrief) : Hold a facilitated discussion right after the exercise while memories are fresh. Ask three simple questions: What went well? What challenges did we face? What are our top three action items to fix?
Document and Follow Up : Write an After-Action Report (AAR) summarizing the lessons learned. Assign owners and deadlines to the corrective actions identified so the exercise translates into real-world resilience.
Would you like help drafting a sample scenario or building a Master Scenario Events List (MSEL) template for a specific type of emergency (like a severe weather event or data breach)?
A realistic tabletop exercise (TTX) should test decisions, coordination, communications, and procedures—not reward people for knowing the “right” answer. FEMA’s HSEEP framework uses a cycle of design, conduct, evaluation, and improvement planning, which is a useful structure for almost any emergency-response team.
1. Start with 3–5 concrete objectives
Avoid a vague objective such as “test our emergency plan.” Instead, make objectives observable:
Determine whether the team can establish incident leadership within 15 minutes.
Test how quickly critical information reaches decision-makers.
Determine whether staff understand evacuation/shelter-in-place authorities and responsibilities.
Test coordination with external responders.
Identify gaps in communications, staffing, supplies, or continuity procedures.
Your objectives should drive the scenario and evaluation criteria. FEMA specifically recommends aligning exercise objectives with the capabilities and critical tasks being evaluated.
2. Pick a scenario that is plausible—but uncomfortable
Use a hazard your organization could realistically face, based on your risk assessment.
For example:
09:15 Monday: A major incident disrupts normal operations. Initial information is incomplete and conflicting. Several employees/customers are affected. Communications are degraded. The emergency response team must determine what happened, protect people, establish priorities, communicate internally, and coordinate with outside agencies.
Then introduce complications progressively:
Initial incident.
Conflicting information.
Loss of a key person or communication channel.
Increased number of affected people.
External agency involvement.
Media/social-media attention.
Resource shortage.
Transition from immediate response to recovery.
The important part is not making the disaster spectacular. It is creating situations where participants have to make realistic decisions.
3. Don't give participants the whole scenario
Have a facilitator reveal information in stages through injects.
Example:
Time
Inject
Question for participants
0:00
Initial incident report
Who takes command? What happens first?
0:10
Communications partially fail
How do you communicate now?
0:20
Employee/customer reported missing
Who verifies the information?
0:30
Outside responders arrive
A good facilitator should occasionally say “You don't know” when participants ask for information that their team would not realistically have.
That uncertainty is valuable—it tests how they operate with incomplete information.
4. Make participants use their actual procedures
This is where a tabletop becomes much more useful than a discussion about emergency preparedness.
Put the team's actual:
Emergency Operations Plan
contact lists
organizational chart
evacuation maps
notification procedures
communications procedures
vendor/contractor information
continuity procedures
mutual-aid agreements
on the table.
Then ask:
“Show me where that is addressed in your plan.”
If nobody can find it, that is an exercise finding, not a failure to be hidden.
FEMA describes exercises as a way to validate plans and capabilities and identify gaps and areas for improvement.
5. Assign a facilitator and separate evaluators
Ideally, don't have the person running the exercise simultaneously trying to evaluate everyone.
Facilitator
Introduces injects.
Keeps the discussion moving.
Challenges assumptions.
Prevents one person from dominating.
Does not solve problems for participants.
Evaluators/observers
Record what actually happened.
Note decisions and timing.
Compare performance against objectives.
Capture both strengths and deficiencies.
FEMA's Exercise Evaluation Guides are specifically designed to make observation and data collection consistent and to support the eventual After-Action Report.
6. Force decisions, rather than hypothetical discussion
Instead of:
“What would you do if communications failed?”
say:
“Your primary communications system has just failed. You have five minutes. What communication method are you using, who activates it, and who needs to be notified?”
Then follow up:
Who has authority?
What information do you need?
Where will you get it?
What is your deadline?
Who documents the decision?
What happens if your first option fails?
This exposes ambiguity in roles and procedures very quickly.
7. Include realistic friction
Real emergencies rarely provide perfect information.
Consider deliberately introducing:
conflicting reports
unavailable personnel
failed technology
competing priorities
incomplete information
delayed external assistance
language/accessibility needs
transportation problems
unexpected resource shortages
a decision-maker who cannot be reached
Don't make the exercise artificially difficult just for drama. Each complication should test one of your objectives.
8. Conduct a hot wash immediately afterward
Spend roughly 15–30 minutes asking:
What went well?
What surprised you?
Where did you get stuck?
Which procedures worked?
Which procedures were unclear or missing?
What information did you wish you had?
What should we change before the next incident?
Capture observations before people leave.
9. Turn findings into an improvement plan
This is arguably the most important step.
Don't finish with:
“We'll improve communications.”
Turn it into an actionable item:
Finding
Corrective action
Owner
Due date
Staff couldn't locate emergency contact list
Create centralized offline contact list
Emergency Manager
Oct. 15
Authority for evacuation was unclear
Clarify decision authority in EOP
Operations
Nov. 1
Backup communications weren't understood
Conduct communications drill
HSEEP explicitly treats improvement planning as part of the exercise cycle, with corrective actions tracked toward completion.
A practical 2-hour format
0:00–0:10 — Introduction
Purpose
Ground rules
Objectives
Roles
0:10–0:25 — Initial situation
Present scenario
Let team establish its initial response
0:25–1:15 — Interactive play
Introduce 4–6 injects
Force decisions
Introduce uncertainty
1:15–1:30 — Escalation/recovery
Introduce a major complication
Test transition toward recovery
1:30–1:50 — Hot wash
Strengths
Problems
Surprises
Immediate recommendations
1:50–2:00 — Close
Explain next steps
Assign responsibility for the AAR/improvement plan
The biggest mistakes to avoid
Making it a lecture. Participants should be doing most of the talking.
Trying to test everything. Pick a handful of objectives.
Making the scenario too dramatic. Realistic ambiguity is more valuable than cinematic disaster.
Rescuing participants when they get stuck. Their confusion may be the finding you need.
Treating the exercise as a pass/fail test. The purpose is learning and improvement.
Failing to follow up. An exercise without corrective-action tracking can become an expensive discussion rather than a preparedness improvement.
For a U.S. organization, FEMA's HSEEP templates are particularly useful: they include planning, facilitator, evaluation, Master Scenario Events List, and improvement-planning materials. Preparedness Toolkit CISA also provides tabletop exercise packages with planner, facilitator/evaluator, participant-feedback, and AAR templates.
If you tell me what kind of organization your emergency response team supports (e.g., hospital, school, corporate office, manufacturing site, campus, municipality) and the hazard you want to exercise, I can build you a complete 90–120 minute tabletop package with the scenario, injects, facilitator script, participant questions, evaluator checklist, and AAR template.
Run the Simulation : Walk through the timeline step-by-step. Force participants to talk through who does what, when they notify leadership, and what specific tools or templates they use.
Debrief and Capture Actions : Right after the exercise, run a "hot wash" debrief while thoughts are fresh. Ask what went well, what caused friction, and what gaps emerged. Assign specific owners and deadlines for fixing those gaps.
Would you like me to help you draft a specific scenario (such as a ransomware attack, severe weather evacuation, or active threat) and create a list of timed injects for your team?
A good tabletop exercise (TTX) should feel just realistic enough to force decisions, without becoming a scripted test that participants can simply “pass.” FEMA’s HSEEP framework is a useful model: establish objectives, design the scenario, conduct and facilitate the exercise, evaluate performance, and turn findings into corrective actions.
1. Start with 2–4 specific objectives
Don't start with “test our emergency plan.” Start with observable things you want the team to demonstrate.
For example:
Establish an incident-management structure within 15 minutes.
Demonstrate how the team obtains and shares situational information.
Make and document decisions when critical resources are unavailable.
Issue an initial internal/external communication using the organization's approved process.
Identify when and how the team escalates an incident to executives or outside agencies.
FEMA recommends aligning objectives with the capabilities you actually want to evaluate.
Rule of thumb: If you can't tell afterward whether an objective was achieved, rewrite it.
2. Pick a scenario that is plausible for your organization
Use your actual risk assessment, previous incidents, near misses, outages, or exercise findings.
A strong scenario has:
A credible initiating event.
Incomplete information.
Several simultaneous problems.
Decisions that genuinely have tradeoffs.
A plausible reason the situation could deteriorate.
No single obvious solution.
For example:
09:15 Monday: A severe storm causes a regional power outage. Your primary facility is operating on backup power. Several employees cannot reach the site, one critical vendor is unreachable, and social media reports are circulating that the facility has been evacuated.
Then progressively introduce complications.
The objective isn't to predict exactly what will happen in a disaster. It's to expose whether your plans, people, communications, authorities, and resources work under pressure.
3. Build the exercise around "injects"
An inject is new information introduced during the exercise.
A 90-minute exercise might look like:
Time
Inject
What it tests
0:00
Initial incident report
Activation/assessment
0:15
Critical system becomes unavailable
Prioritization
0:30
Key decision-maker cannot be reached
Delegation/authority
0:45
Conflicting information appears
Don't make every inject a catastrophe. Ambiguity and conflicting information are often more revealing than bigger disasters.
FEMA provides a Master Scenario Events List (MSEL) specifically for managing exercise injects.
4. Separate players, facilitators, controllers, and evaluators
This is particularly important for realism.
Players make decisions as they would during an actual incident.
Facilitators keep discussion moving and ask questions such as:
“What would you do next?”
“Who has authority to make that decision?”
“What information do you need?”
Controllers manage the exercise and release injects.
Evaluators observe and record what actually happens.
Don't let evaluators constantly correct participants. If the team makes a mistake, let the exercise expose it.
FEMA's HSEEP materials explicitly distinguish these exercise functions and provide separate conduct and evaluation resources.
5. Give participants only information they'd actually have
This is one of the biggest differences between a realistic TTX and a discussion about a disaster.
Don't tell participants:
"The backup generator will fail in 20 minutes."
Instead:
"Facilities reports that fuel consumption is higher than expected. Current estimates suggest approximately 45 minutes of remaining runtime."
Let them decide what to do.
Likewise, don't automatically answer questions they wouldn't be able to answer in reality. If they ask, “What's the status of the vendor?” the facilitator might respond:
“You have attempted to contact them twice. No response yet.”
That uncertainty is part of the exercise.
6. Force decisions, not just conversation
A common TTX failure mode is:
“We would call X.”
“We would notify Y.”
“We have a plan for that.”
Whenever someone says “we would…”, ask:
“Okay—who does it, when, using what authority or procedure, and what happens if it doesn't work?”
Have participants actually identify:
Who makes the decision.
What information they need.
Which plan/procedure applies.
Who needs to be notified.
What resource is required.
What the fallback is.
How the decision gets documented.
That turns a conversational exercise into a capability test.
7. Introduce friction deliberately
Real incidents rarely fail because the first plan is completely useless. They fail because several small assumptions stop being true simultaneously.
Useful friction includes:
A key person is unavailable.
A communication channel fails.
Information conflicts between two sources.
A vendor doesn't respond.
A resource is delayed.
Leadership asks for an answer before the facts are complete.
An employee reports something on social media.
A neighboring organization requests assistance.
The situation improves in one area while deteriorating in another.
Don't manufacture absurd complications just to make the exercise difficult. Each inject should connect to an objective.
8. Establish ground rules before starting
Tell participants:
This is an exercise, not an evaluation of individual employees.
Assume normal policies and authorities unless the scenario says otherwise.
Say what you would actually do, rather than what sounds ideal.
It's acceptable to say “I don't know.”
If you discover that a procedure doesn't exist, that's a useful finding.
Don't solve problems by inventing resources or authorities that don't exist.
Exercise information stays within the agreed exercise boundaries.
A psychologically safe environment is important because you want people to expose weaknesses rather than hide them.
9. Evaluate behaviors, not personalities
Instead of:
“The operations manager didn't communicate well.”
Record something observable:
“No common operating picture was established during the first 30 minutes, and participants used three different versions of the incident status.”
Then ask:
What was supposed to happen?
What actually happened?
What explains the difference?
What consequence could that have?
What corrective action would reduce the gap?
FEMA's Exercise Evaluation Guides are designed to make observation and data collection more consistent and to connect findings to objectives and corrective actions.
10. End with a structured hotwash
Immediately afterward, ask each participant:
What worked?
What didn't?
What surprised you?
What information did you wish you had?
Which decision was hardest?
Which procedure or plan needs clarification?
What is one thing we should change before the next incident?
Don't immediately argue about whether someone's observation is correct. Capture it first.
11. Turn findings into an improvement plan
This is arguably the most important step.
For every significant finding, assign:
Finding → Corrective action → Owner → Due date → Measure of completion
For example:
Finding
Corrective action
Owner
Due
Emergency contact list contained outdated numbers
Establish quarterly verification process
HR
30 days
Authority for emergency procurement was unclear
Document delegation thresholds
Finance/Legal
45 days
Situation reports lacked a common format
Create standard SITREP template
FEMA describes improvement planning as a continuous process rather than simply producing a report and putting it on a shelf.
A practical 2-hour TTX format
Before the exercise
Define objectives.
Choose scenario.
Identify players/facilitators/evaluators.
Prepare injects.
Establish evaluation criteria.
Brief facilitators separately.
Prepare participant materials.
0:00–0:10 — Briefing
Explain purpose, rules, scenario assumptions, and exercise boundaries.
0:10–0:30 — Initial incident
Give participants the opening situation and let them establish their response.
0:30–0:50 — Complication #1
Introduce a significant operational problem.
0:50–1:10 — Complication #2
Introduce uncertainty, resource constraints, or conflicting information.
1:10–1:30 — Escalation
Test leadership, communications, coordination, or external interfaces.
1:30–1:40 — Transition
Introduce stabilization/recovery decisions.
1:40–2:00 — Hotwash
Capture strengths, gaps, and immediate corrective actions.
The realism test
Before running the exercise, ask your planning team:
“Could this actually happen to us, and would the participants genuinely have to make difficult decisions?”
If the answer to either is no, redesign the scenario.
FEMA's HSEEP resources include templates for exercise plans, facilitator guides, MSELs, evaluation plans, participant materials, and after-action/improvement planning.
If you tell me what kind of emergency response team you have (corporate ERT, hospital, school, government, industrial facility, etc.) and the hazard you want to exercise, I can build you a complete tabletop package: scenario, objectives, inject timeline/MSEL, facilitator questions, evaluator sheet, and hotwash questions.
“We would call X.”
“We would notify Y.”
“We have a plan for that.”
Whenever someone says “we would…”, ask:
“Okay—who does it, when, using what authority or procedure, and what happens if it doesn't work?”
Have participants actually identify:
Who makes the decision.
What information they need.
Which plan/procedure applies.
Who needs to be notified.
What resource is required.
What the fallback is.
How the decision gets documented.
That turns a conversational exercise into a capability test.
7. Introduce friction deliberately
Real incidents rarely fail because the first plan is completely useless. They fail because several small assumptions stop being true simultaneously.
Useful friction includes:
A key person is unavailable.
A communication channel fails.
Information conflicts between two sources.
A vendor doesn't respond.
A resource is delayed.
Leadership asks for an answer before the facts are complete.
An employee reports something on social media.
A neighboring organization requests assistance.
The situation improves in one area while deteriorating in another.
Don't manufacture absurd complications just to make the exercise difficult. Each inject should connect to an objective.
8. Establish ground rules before starting
Tell participants:
This is an exercise, not an evaluation of individual employees.
Assume normal policies and authorities unless the scenario says otherwise.
Say what you would actually do, rather than what sounds ideal.
It's acceptable to say “I don't know.”
If you discover that a procedure doesn't exist, that's a useful finding.
Don't solve problems by inventing resources or authorities that don't exist.
Exercise information stays within the agreed exercise boundaries.
A psychologically safe environment is important because you want people to expose weaknesses rather than hide them.
9. Evaluate behaviors, not personalities
Instead of:
“The operations manager didn't communicate well.”
Record something observable:
“No common operating picture was established during the first 30 minutes, and participants used three different versions of the incident status.”
Then ask:
What was supposed to happen?
What actually happened?
What explains the difference?
What consequence could that have?
What corrective action would reduce the gap?
FEMA's Exercise Evaluation Guides are designed to make observation and data collection more consistent and to connect findings to objectives and corrective actions.
A strong tabletop exercise (TTX) should feel real enough to expose weaknesses, but controlled enough that people can learn without fear of failure. FEMA’s HSEEP framework is a good model: establish objectives, design a realistic scenario, conduct the exercise, evaluate performance, and turn findings into corrective actions.
1. Start with 3–5 specific objectives
Don't make the objective “practice emergency response.” Make it measurable.
For example:
Determine whether the team can activate the emergency response plan within 15 minutes.
Test how leadership makes decisions when information is incomplete.
Validate internal and external communication procedures.
Identify who has authority to shut down operations or evacuate.
Test coordination with fire/EMS, law enforcement, utilities, vendors, or local government.
FEMA recommends aligning objectives with the capabilities you actually want to evaluate.
2. Pick a scenario that is plausible for your organization
Choose a hazard based on your actual risk assessment—not the most dramatic disaster you can imagine.
Good TTX scenarios might include:
Severe weather followed by a prolonged power outage
Fire or hazardous-material release
Active threat requiring shelter/evacuation decisions
Cyberattack disrupting critical systems
Loss of a key facility or utility
Mass casualty incident
Pandemic/communicable-disease event
Supply-chain failure
Combined events, such as tornado → power outage → communications failure
The best scenarios contain ambiguity and competing priorities, rather than having an obvious correct answer.
3. Give participants only what they would actually know
This is one of the biggest differences between a useful exercise and a rehearsal where everyone already knows the answers.
At the beginning, give them something like:
08:15 — A severe storm has moved through the area. Several employees report structural damage at the facility. Power is intermittent. Cellular service is congested. The emergency operations center has not yet been activated.
Then ask:
“What do you do?”
Don't immediately provide the next step.
Let participants explain:
Who makes the decision?
Who gets called?
What information do you need?
Where do you get it?
What authority do you have?
What happens if that person isn't available?
How do you communicate with employees?
What happens to critical operations?
That exposes gaps in plans much more effectively than simply walking through the emergency plan page by page.
4. Use injects to progressively complicate the situation
Prepare a sequence of developments that force decisions.
For example:
Time
Inject
Question
08:15
Initial incident
What is your first action?
08:25
Power is lost
What critical functions must continue?
08:35
Two employees are unaccounted for
Who coordinates accountability/search?
08:45
Cell service becomes unreliable
FEMA's HSEEP materials specifically provide tools for developing scenarios and a Master Scenario Events List (MSEL) to manage injects.
5. Assign clear exercise roles
You generally want:
Players — the emergency response team making decisions.
Facilitator — keeps discussion moving and asks probing questions.
Controller — manages scenario information and injects.
Evaluators/observers — document what actually happens.
Exercise director — responsible for the overall exercise.
Don't let the facilitator become the person who solves every problem. Their job is to ask questions such as:
“Who has authority to make that decision?”
“What procedure are you following?”
“What information would you need before making that decision?”
“Your normal communication channel isn't available. What do you do?”
FEMA identifies facilitators/controllers and evaluators as distinct exercise roles.
6. Make the exercise psychologically safe
Tell participants explicitly:
This is not a test of individual performance. We're testing the system. Finding a problem is a successful outcome of the exercise.
Avoid turning the exercise into a “gotcha.”
If someone discovers that a phone number is wrong, a backup generator procedure is unclear, or nobody knows who has authority to make a particular decision, that's valuable information.
7. Evaluate decisions—not just whether people followed the plan
Create a simple evaluation sheet around your objectives.
For each objective, capture:
What was expected?
What actually happened?
What worked?
What didn't?
Why?
What consequence could the gap create?
What corrective action is needed?
FEMA describes Exercise Evaluation Guides as a way to systematically collect observations and connect results to objectives, capability targets, and corrective actions.
Transition from immediate response to sustained operations
1:35–1:50 — Hotwash
What worked?
What failed?
What surprised us?
1:50–2:00 — Priorities
Identify the top 3–5 corrective actions
For a more formal exercise, FEMA provides templates for the exercise plan, facilitator guide, MSEL, evaluation plan, situation manual, and other components.
The key test
A realistic TTX should repeatedly make participants say:
“We need to figure that out.”
That's exactly what you want. If everyone instantly knows the answer to every problem, you're probably conducting a briefing rather than exercising the response system.
If you tell me what type of organization you have (business, hospital, school, municipality, nonprofit, etc.), team size, and the top 1–2 hazards you're concerned about, I can build a complete 90-minute tabletop package with the scenario, injects, facilitator questions, evaluator checklist, and hotwash questions.
Debrief and Capture Lessons (Hotwash) : Immediately following the exercise, hold a "hotwash" session while impressions are fresh. Ask participants what worked, what felt ambiguous, and what tools or resources were lacking.
Document and Iterate : Compile the findings into an after-action report (AAR) with clear, assigned action items, deadlines, and owners to update your actual emergency response plans.
Would you like me to help you outline a specific scenario (like a ransomware attack or facility fire) or provide a template for the after-action report?
A good tabletop exercise (TTX) should feel real enough to expose weaknesses, but controlled enough that nobody is actually put at risk. FEMA’s HSEEP framework is a strong model: design around clear objectives, conduct the exercise, evaluate performance, and turn findings into corrective actions.
1. Start with what you want to learn
Don't begin with a dramatic scenario. Begin with 2–4 specific objectives.
For example:
Determine whether the emergency response team can establish incident command within 15 minutes.
Test how quickly critical information reaches senior leadership.
Determine whether evacuation/shelter decisions are made using the current plan.
Test coordination between security, facilities, IT, communications, HR, and external responders.
Identify gaps in emergency communications and business continuity.
Objectives should drive both the scenario and the evaluation—not simply be things you hope to observe afterward.
2. Choose a plausible scenario
Pick a hazard that is credible for your organization and difficult enough to test your objectives.
Examples:
Severe weather causes building damage and loss of power.
A fire requires evacuation while several employees are unaccounted for.
A hazardous-material release affects part of the facility.
A cyber incident disrupts communications during a physical emergency.
A suspicious package triggers a security response.
A regional disaster disrupts transportation, staffing, utilities, and suppliers.
The best scenario usually combines one primary incident with secondary complications.
For example:
10:05 a.m.: A severe storm damages the facility. Power is intermittent.
10:20: Two employees cannot be accounted for.
10:30: The primary communication system fails.
10:45: Local news reports conflicting information about the incident.
11:00: A critical supplier says it cannot deliver.
11:15: Senior leadership asks whether operations should be suspended.
Those developments force participants to make decisions rather than simply recite the emergency plan.
3. Get the right people in the room
Include the people who would actually have to make or execute decisions.
Depending on your organization, that might include:
Emergency response/team leadership
Security
Facilities
IT/cybersecurity
HR
Communications/public information
Business continuity
Operations
Senior management
Safety/health personnel
Key external partners or emergency-management representatives
Keep the exercise planning team separate from players where practical. CISA specifically recommends that planners develop the exercise rather than simultaneously participating as players.
4. Make it interactive
A weak tabletop is essentially a PowerPoint presentation.
A strong one continually asks:
"What do you do now?"
For every major inject, ask:
What information do you have?
What don't you know?
Who has authority to make the decision?
What is your immediate action?
Who needs to be notified?
What resources do you need?
What happens if that resource isn't available?
What policy, plan, or procedure are you relying on?
Don't rescue participants when they get stuck. Let the exercise expose the gap.
Tabletops are specifically intended for discussion, problem-solving, and identifying strengths and shortfalls rather than simulating every operational action.
5. Introduce realistic friction
Real emergencies rarely provide perfect information.
Add complications such as:
Conflicting reports
Missing personnel
Failed radios or phones
Delayed information from outside agencies
Key decision-makers unavailable
Conflicting priorities
Public/media inquiries
Transportation problems
Power or network outages
Resource shortages
Changing weather
A second incident occurring while the first is unresolved
The goal isn't to "trick" the team. It's to see whether the system remains functional when assumptions fail.
6. Use an exercise controller/facilitator
Have one person facilitate rather than allowing the discussion to become an uncontrolled meeting.
The facilitator should:
Introduce the scenario.
Deliver timed injects.
Keep discussion moving.
Ask probing questions.
Prevent one person from dominating.
Record unresolved issues.
Distinguish "we would do X" from "our plan actually says X."
Stop debates that aren't relevant to the objectives.
Have separate evaluators/data collectors record what actually happens. FEMA recommends planning evaluation from the beginning and collecting objective data during exercise play.
7. Evaluate decisions, not personalities
Create an evaluation sheet around your objectives.
For each objective, capture:
Observe
Example
Expected behavior
Incident command established
What actually happened
Leadership structure unclear for 12 minutes
Strength
Team quickly identified life-safety priorities
Gap
No agreed backup communications method
Impact
Delayed notification of leadership
FEMA's Exercise Evaluation Guides are designed specifically to organize observations against objectives, capabilities, and critical tasks and support the after-action report.
8. Finish with a structured hotwash
Immediately afterward, ask participants:
What worked?
What surprised you?
What was unclear?
Where did the plan fail?
What information did you wish you had?
Which decision was hardest?
What capability do we need that we don't currently have?
What should we change before the next exercise?
Avoid turning this into a blame session. The objective is organizational learning, not determining who made a mistake.
9. Produce an After-Action Report and Improvement Plan
This is arguably the most important part.
Within a reasonable period after the exercise, document:
Strengths
Areas for improvement
Significant capability gaps
Recommended corrective actions
Responsible owner
Priority
Target completion date
Method for verifying completion
Then actually track the corrective actions.
HSEEP treats improvement planning as part of the exercise cycle—not an optional report-writing exercise.
A practical 90-minute tabletop
A simple format that works well:
0–10 min — Introduction
Objectives
Ground rules
Roles
Scenario assumptions
10–25 min — Initial incident
Present initial conditions.
Ask participants what they do first.
25–45 min — Escalation
Introduce the first major complication.
Force decisions around communications, resources, leadership, and safety.
45–65 min — Cascading problems
Introduce 2–3 simultaneous issues.
Remove one assumed capability.
65–80 min — Executive decision point
Give leadership a consequential decision: evacuate, close operations, shelter, notify authorities, activate continuity plans, etc.
80–90 min — Hotwash
Capture strengths, gaps, and immediate actions.
Then conduct the formal evaluation and improvement planning afterward.
The key test
At the end, you should be able to answer:
"What did this exercise teach us that we didn't know before we started?"
If the answer is "nothing," the exercise was probably too easy—or designed to demonstrate that the plan works rather than genuinely test it.
For a ready-made structure, FEMA provides HSEEP templates for exercise plans, facilitator guides, master scenario event lists, evaluation plans, and after-action/improvement planning; FEMA also provides Exercise Starter Kits that can be customized for specific hazards.
If you tell me what kind of organization you have (corporate facility, hospital, school, municipality, etc.) and your biggest emergency risks, I can build a complete 90-minute tabletop package with the scenario, injects, facilitator script, participant questions, evaluator checklist, and AAR template.
Prepare "injects": These are timed or conditional pieces of information (emails, fake news alerts, phone calls, or sensor data) introduced by the facilitator to force adaptation.
Add realistic friction: Introduce constraints like missing personnel, ambiguous data, conflicting priorities between departments, or a temporary communications blackout.
3. Establish Rules of Engagement
Create a safe space: Explicitly state that the TTX is a test of the process and plan , not the individual participants. Blame-free environments yield honest vulnerabilities.
Use the "Timeout" rule: Allow participants to pause the exercise ("time out") if they are completely lost or need a 60-second huddle to figure out their next strategic move.
Assign a facilitator/controller: Someone needs to drive the timeline, drop injects, and keep the pace moving without feeding answers to the team.
Assign an evaluator/observer: A neutral third party who takes silent notes on communication bottlenecks, missed protocols, and implicit assumptions.
4. Execute the Exercise
Run the timeline: Walk through the phases (Initial notification → Assessment → Escalation → Mitigation).
Force verbalization: Insist that participants say things out loud ("I am now calling the vendor," "We are authorizing X budget"). Avoid people saying "I would do that" without tracing the actual steps.
Track the friction: Watch where momentum stalls. Is it an ego clash? A missing phone number? An unclear chain of command?
5. Conduct a Hot (and Cold) Debrief
The Hot Wash (Immediate): Right after the exercise, spend 15–20 minutes asking three simple questions:
What went well?
What surprised us?
What are 2 or 3 immediate fixes we can implement this week?
The After-Action Report (AAR): Within a week, document the observer's notes, map out the timeline gaps, and assign accountability for fixing broken processes.
If you'd like, tell me:
What specific type of emergency or scenario you are planning for
How large your emergency response team is
I can help you draft a customized timeline or a sample inject sequence for your exercise.
Who coordinates with them?
0:40
Rumor spreads online
Who issues an official message?
0:50
Key resource unavailable
What gets prioritized?
1:00
Situation stabilizes
How do you transition toward recovery?
IT/ERT
Nov. 15
Situational awareness
1:00
External stakeholder requests an update
Communications
1:15
Resource previously assumed available is unavailable
Contingency planning
1:25
Situation stabilizes but recovery decisions arise
Transition to recovery
Emergency Management
30 days
What's your backup communication method?
09:00
Local media reports the incident
Who communicates externally?
09:15
A senior executive cannot be reached
Who has decision authority?
09:30
Families begin calling
Who handles employee/family communications?
09:45
Facility may be unavailable for 48 hours
How do you transition to continuity/recovery?
45 days
Staff accountability inconsistent
Implement standardized accountability process
HR/Safety
Medium
60 days
Corrective action
Establish and train on alternate communications procedure