How to Run a Tabletop Exercise That Finds Real Gaps (HSEEP)

A tabletop exercise is the cheapest way to find out that your plan does not work. It requires no field units, no overtime, and no equipment. Three hours in a conference room with the right people will surface problems that would otherwise wait for a real event to reveal themselves.

It is also the easiest exercise to do badly. A tabletop where everyone agrees the plan is fine, nobody is uncomfortable, and the after-action report says "the exercise was a success" has cost you a morning and taught you nothing.

This guide follows the Homeland Security Exercise and Evaluation Program (HSEEP), which is the common standard for how exercises get designed, conducted, and learned from. You do not need to run a full HSEEP program to benefit from its discipline.

What a tabletop is, and what it is not

HSEEP separates discussion-based exercises from operations-based ones. A tabletop sits in the first group, alongside seminars, workshops, and games. Nobody deploys. People sit at a table, receive a scenario, and talk through what they would do.

Do not ask a tabletop to do a functional exercise's job. A tabletop tells you whether people know their roles and whether the plan supports the decisions they would have to make. It does not tell you whether your radios reach the county line.

Start with objectives, not a scenario

The most common design error is picking a dramatic scenario first and working out what it might test afterward. Do it the other way. Decide what you need to learn about your program, then construct a scenario that forces those questions.

Good objectives are specific, observable, and tied to a capability. Compare:

Three to five objectives is the right number for a three-hour tabletop. More than that and the discussion never gets past the surface of any of them. Each objective should map to a core capability so findings connect to your broader preparedness reporting.

Build the scenario backwards

Once objectives are set, design the scenario to make them unavoidable. If the objective is about emergency procurement authority, the scenario must include a moment where something has to be bought immediately and the normal purchasing process cannot run.

A workable tabletop scenario has three or four modules, each ending with discussion questions:

• Module 1: Warning and initial notification. What triggers activation, who calls whom, and what the first thirty minutes look like.
• Module 2: Response and coordination. The incident is underway. Resources are competing. Decisions have to be made with incomplete information.
• Module 3: Escalation or complication. Something fails: a facility is unusable, a key person is unreachable, a second incident begins, or the media reports something inaccurate.
• Module 4: Transition to recovery. Demobilization, documentation, cost capture, and the handoff to long-term recovery. This module is routinely skipped, and it is where counties lose reimbursement money.

Keep the hazard plausible for your jurisdiction and ground it in your risk assessment. A county that has never had a hurricane learns less from a hurricane scenario than from the ice storm or the industrial release that is actually in its hazard profile.

The documents you actually need

A full HSEEP package is extensive. A county tabletop needs a practical subset:

• Situation Manual (SitMan). The participant handout: purpose, objectives, scenario modules, discussion questions, ground rules, and participant list. This is the one document you cannot skip.
• Facilitator guide. The same material plus timing, probing questions, and notes on where discussion is likely to stall.
• Exercise Evaluation Guides (EEGs). One per objective, giving evaluators something concrete to observe against rather than general impressions.
• Participant feedback form. Collected before people leave the room, while opinions are fresh.
• After-Action Report and Improvement Plan (AAR/IP). Produced afterward, covered in detail in our AAR guide.

Send the SitMan in advance to those who need to prepare, but keep the complications in Module 3 out of the pre-read. Surprise is part of the instrument.

Who should be in the room

The single biggest determinant of a tabletop's value is who attends. Three rules:

1. Send the person who would actually be there. If a deputy runs the desk at 2 a.m., the deputy attends, not the director who would be asleep.
2. Include the functions that create friction. Finance, procurement, legal, human resources, and public information are where real activations bog down, and they are the functions most often left off the invitation.
3. Invite the partners you would have to call. A tabletop that includes the hospital, the school district, the utility, and the neighboring county surfaces coordination assumptions that an internal exercise cannot.

Keep the working group to a size where everyone can speak. Beyond about twenty-five participants, break into functional tables and reconvene for report-outs.

Facilitating the discussion

Facilitation is the skill that separates a useful tabletop from a polite one. A few things that consistently work:

• Set ground rules out loud. No-fault environment, rank is left at the door, and the goal is to find problems now rather than later. Say it, and then protect it when someone gets defensive.
• Ask "show me where." When a participant says the plan covers something, ask them to find it. The gap between what people believe the plan says and what it says is one of the most valuable findings a tabletop produces.
• Follow the decision, not the answer. "Who has authority to make that call, and what happens if they are unreachable?" is more productive than confirming that a good answer exists.
• Let silence work. When you ask a hard question, wait. The first answer after an uncomfortable pause is usually the honest one.
• Redirect war stories. Experience is valuable, but a facilitator who lets the room relive the 2019 flood for twenty minutes has lost an objective.
• Watch the clock per module. Running out of time before recovery means the recovery objective is untested, and that is where the money is.

Capturing findings while they are still true

Assign a dedicated note-taker. The facilitator cannot do both well. Capture findings in the moment, in the participants' own words, tied to the objective and the module where they arose.

Hold a hot wash immediately after the last module, while people are still in the room. Ask three questions: what worked, what did not, and what one change would help most. Then collect the feedback forms before anyone leaves.

Findings should be written as problems with owners, not as observations. "Communications could be improved" is not a finding. "No single position is responsible for compiling the situation report, and three departments each produced their own version" is a finding, and it has an obvious fix.

Six ways tabletops go wrong

1. Scenario first. The exercise becomes entertainment rather than assessment.
2. Too many objectives. Nothing gets tested to depth.
3. The wrong people. Department heads attend, deputies respond.
4. A facilitator with a stake. The person who wrote the plan will unconsciously defend it. Use an independent facilitator where you can.
5. No documentation discipline. Findings live in someone's notebook and never become an improvement plan.
6. An improvement plan with no due dates. The same findings reappear in the next exercise, and the next.

If your last three exercises produced findings that are still open, another exercise will not help. Closing the loop will.

Common questions

How long should a tabletop exercise be?

Three to four hours is the usual sweet spot for a county or organizational tabletop, including a briefing, three or four modules, and a hot wash. Shorter than two hours and you cannot get past module one. Longer than a half day and attention fades, particularly among the partners who drove in for it.

How much does a tabletop exercise cost?

An internally run tabletop costs staff time and a room. A professionally designed and facilitated exercise varies with scope: the number of objectives, the number of participating organizations, whether evaluators are provided, and whether a formal HSEEP documentation package and AAR/IP are included. The honest driver of cost is documentation, not the day in the room.

Do we have to use HSEEP?

Not always, but it is usually in your interest. Several federal preparedness grant programs expect HSEEP-consistent exercises and documentation, accreditation standards reference it, and it gives your findings a structure that your state and your partners already recognize.

Who should facilitate?

Someone who did not write the plan being tested. An author facilitating their own plan will instinctively explain rather than probe. If you have no one internal who is independent enough, trading facilitators with a neighboring jurisdiction works and costs nothing.

How often should we exercise?

Build a multi-year training and exercise plan that escalates: seminars and workshops, then tabletops, then drills and functional exercises, then full-scale. Annually is a reasonable floor for a tabletop. Some sectors have specific requirements, such as the CMS Emergency Preparedness Rule for healthcare providers, which we cover on our healthcare page.