Exercises exist for one reason: to find the gaps in your plans, people, and equipment while the price of failure is still a red face in a conference room instead of a bad day in the field. After 25 years in this business, I have watched exercises change agencies and I have watched exercises waste everyone’s Saturday. The difference is almost never budget. It is design discipline, honest evaluation, and the willingness to actually fix what you find.

Why exercises exist at all

Disasters are the most expensive audit you will ever undergo. Every plan on your shelf contains assumptions that have never been tested: that the phone tree works, that the backup generator starts, that the person listed as logistics chief still works for the county, that two agencies who have never spoken can share a radio channel. A real incident will test every one of those assumptions at once, in public, with lives and property on the line. An exercise tests them one layer at a time, in private, for the cost of some staff hours and coffee.

That framing matters because it defines success correctly. An exercise that runs smoothly and finds nothing did not succeed. It either tested nothing hard, or it hid the findings. The purpose is discovery. If your after-action report reads like a press release, you paid for an exercise and got a pep rally.

Exercises also do quieter work. They build relationships across agencies before the incident, so the first time your public works director meets the hospital emergency manager is not at 2 a.m. in a parking lot. They train new staff on plans they have only read. They give elected officials a low-stakes look at what response actually requires, which pays off later at budget time. But the primary product is always the same: a validated list of what works and what does not, produced before the disaster produces it for you.

The exercise spectrum, from seminar to full-scale

Exercise types fall into two broad families, and a healthy program uses both. Discussion-based exercises happen around a table and test understanding, coordination, and decision-making. Operations-based exercises happen in the field or at operational posts and test whether people and systems can actually perform.

On the discussion-based side:

• Seminars orient people to a plan, a policy, or a new capability. Low stress, mostly one-way. Right when a plan is new or the audience is new.
• Workshops are working sessions that produce something: a draft annex, an agreed procedure, a shared contact roster. Use them when the plan itself needs building before it can be tested.
• Tabletop exercises walk a group through a scenario and ask, at each stage, what would you do, with what authority, using what resources. This is where assumptions start dying, cheaply.

On the operations-based side:

• Drills test a single function or capability: a notification callout, a decontamination line, an evacuation of one building. Narrow, repeatable, great for building muscle memory.
• Functional exercises test coordination and command in real time, usually from an emergency operations center or command posts, without moving field resources. They stress information flow, decision cycles, and resource tracking.
• Full-scale exercises put real people and real equipment in motion across multiple agencies. They are the most realistic, the most expensive, and the most dangerous to run badly, which is why they come last in a mature program, not first.

The right type is the cheapest one that can test your current objective. If you have never talked through your shelter plan, a full-scale shelter exercise is a waste; a two-hour tabletop will surface the same first-order gaps for a fraction of the cost.

HSEEP: the common playbook

You do not have to invent an exercise methodology, because the national one already exists. The Homeland Security Exercise and Evaluation Program, HSEEP, is the standard approach used across the United States for designing, conducting, and evaluating exercises. If you accept certain federal preparedness funding, following it is generally expected; even if you do not, it is simply good practice that someone else already wrote down.

In general terms, HSEEP pushes a handful of ideas that every good exercise program shares:

• Objectives drive everything. You decide what capabilities you need to evaluate first, then build the exercise around them, not the other way around.
• Scenarios are realistic and plausible for your jurisdiction, sized to stress the objectives and nothing more.
• Evaluation is planned in advance, with people assigned to watch specific objectives and record what actually happened.
• After-action reporting captures strengths and areas for improvement honestly.
• Improvement planning converts findings into assigned, tracked corrective actions, which is the step that separates programs from theater.

I am deliberately not quoting document titles, templates, or version details here, because doctrine gets updated. Verify the current HSEEP materials, templates, and any grant-related requirements with FEMA and with your state emergency management agency before you build your program around them. Your state exercise officer is also your best free consultant; use them.

Writing objectives that can actually fail

Objectives are where most exercises are quietly ruined, months before anyone shows up. The classic mistake is writing ten vague objectives so that everything counts and nothing can be measured. The fix is discipline: few, measurable, and tied to your actual plans.

• Few. Three to five objectives is plenty for most exercises. Every objective needs an evaluator watching it and data collected against it. Ten objectives means ten things evaluated badly.
• Measurable. “Improve communications” is a wish. “Establish a common operating picture between the EOC and both fire districts within 60 minutes of activation, using the procedures in the communications annex” is an objective. You can watch it succeed or fail, and you can time it.
• Tied to plans. Every objective should point at a specific plan, annex, procedure, or agreement. If an objective does not trace to a document or a defined capability, you are testing improvisation, and improvisation always passes because there is no standard to fail against.

A useful test: for each draft objective, ask “what would failure look like, and would we be able to see it?” If the honest answer is that failure is undetectable or unthinkable, rewrite it. An objective that cannot fail cannot teach.

Scenarios that stress the plan, not the imagination

The scenario is a delivery vehicle for the objectives, nothing more. New exercise designers fall in love with the story: the exotic hazard, the dramatic twist, the surprise second event. Experienced designers pick the most plausible hazard that forces play against every objective, and then get out of the way.

Good scenario discipline looks like this:

• Start from your hazard analysis. If your realistic top hazards are flooding, a chemical release on the highway, and a long power outage, exercise those. A scenario your players find implausible gives them permission to disengage.
• Size the stress deliberately. The scenario should exceed routine capacity in the specific ways your objectives require: more patients than one ambulance can move, more calls than one dispatcher can handle, a decision that requires an authority nobody in the room holds. Stress is a tool, applied where you want to look.
• Script injects to force decisions, not reactions. Each inject should push players toward a choice covered by a plan. If an inject exists only because it is exciting, cut it.
• Resist the urge to pile on. A second tornado, a cyber attack on top of the flood, the surprise loss of the EOC: cascading complications feel rigorous but usually just collapse play into chaos that teaches nothing attributable. One well-built problem, examined thoroughly, beats five problems examined not at all.

Theatrics have a cost beyond wasted effort. When players sense the scenario is a game designed to trick them, they play the game instead of their plan, and your data becomes worthless.

The safety imperative

Nobody gets hurt practicing. That rule is absolute, and it has to be engineered, not hoped for. Operations-based exercises put real vehicles, real tools, sometimes real patients-for-a-day into motion, often at speed, often with adrenaline involved. People have been injured in exercises across this profession’s history, and every one of those injuries was preventable with design discipline.

The core safeguards are simple and non-negotiable:

• A designated safety officer (or several, for larger events) with explicit authority to pause or stop the exercise, no questions asked and no permission required.
• Clear start and stop words that everyone is briefed on. Every participant must know the phrase that means the exercise is beginning, the phrase that pauses it, and, critically, the phrase that means a real-world emergency is now occurring and all play stops immediately.
• A real-world emergency procedure. If a participant has a genuine medical event mid-exercise, everyone must instantly distinguish it from simulated play. Decide in advance how real injuries are announced, who responds, and how play is suspended.
• No degradation of actual coverage. The community still needs protecting during your exercise. Backfill, mutual aid, or scope the exercise so that real response capability is never below acceptable levels.
• Site safety review beforehand. Walk the venue. Traffic, weather, trip hazards, tools, role players in moulage who could be mistaken for real casualties by a passerby: identify and control it all, and brief it.

The honest after-action and the discipline of closure

The exercise is not the product. The improvement is the product. Everything before the after-action review is data collection; everything after it is the actual return on investment.

Run the hot wash immediately, while memory is fresh, and run it honestly. Ground rules matter: no rank in the room for the purpose of the discussion, criticize plans and systems rather than people, and every observation gets written down even if it stings. Evaluators then combine their notes with player input into an after-action report that names strengths and, more importantly, names areas for improvement in specific, plain language. “Communications were challenging” is not a finding. “The EOC and the shelter used different radio channels for the first 90 minutes because the communications annex lists an outdated frequency” is a finding, because it points at a fix.

Then comes the part most programs skip: the improvement plan. Every corrective action needs an owner by name, a due date, and a tracking mechanism that someone actually reviews. My own habit for years has been to put corrective action review on a recurring calendar, and to open the next exercise’s planning cycle by pulling out the last improvement plan and asking what closed and what did not. Findings that appear in two consecutive after-action reports are no longer findings. They are decisions the organization has made, and they should be presented to leadership exactly that way.

One more piece of honesty: some corrective actions cost money you do not have. That is fine. Document them anyway. An unfunded, documented gap is a budget justification and a known risk. An undocumented gap is a surprise waiting for the worst possible moment.

Building a progressive program, and how small agencies start

One exercise is an event. A program is a multi-year climb. The progressive approach builds complexity deliberately: talk through the plan before you drill pieces of it, drill the pieces before you exercise coordination, and exercise coordination before you put the whole machine in the field. A reasonable multi-year cycle for a capability might run seminar, then tabletop, then drill, then functional exercise, then full-scale, with each event’s improvement plan feeding the design of the next. The full-scale exercise at the end is not the beginning of testing; it is the graduation exam for gaps you have already found and fixed at cheaper levels.

Along the way, avoid the failure patterns I have seen sink otherwise well-resourced programs:

• Exercises designed to succeed. Softball scenarios, pre-briefed answers, objectives that cannot fail. These produce great photos and zero learning.
• Star players carrying the room. If the same experienced hand answers every tabletop question, you have tested one person, not the organization. Rotate roles, exercise the backups, and occasionally declare the star unavailable in the scenario.
• Findings never fixed. The same corrective actions rolling forward year after year, until players stop reporting problems because reporting them changes nothing.
• The same scenario every year. Comfortable, predictable, and eventually memorized. Vary the hazard, the season, the time of day, and which plans take the stress.

And if you are a small agency with no exercise budget and no dedicated planner, do not wait for perfect. You can run a legitimate, valuable tabletop this quarter with what you already have.

Takeaways

• Exercises exist to find gaps cheaply before a disaster finds them expensively; a smooth exercise that finds nothing failed at its one job.
• Use the whole spectrum: seminars, workshops, and tabletops to test understanding; drills, functional exercises, and full-scale exercises to test performance. Pick the cheapest type that can test your objective.
• Follow the HSEEP approach of objectives-driven design, realistic scenarios, planned evaluation, after-action reporting, and improvement planning, and verify current doctrine with FEMA and your state emergency management agency.
• Write few, measurable objectives tied to specific plans, and get leadership agreement in advance that failing an objective is an acceptable outcome.
• Let the scenario serve the objectives: plausible hazards, deliberate stress, no theatrics, no pile-on complications.
• Safety is absolute: safety officers with stop authority, briefed start and stop words, a real-world emergency procedure, and no degradation of actual community coverage.
• The improvement plan is the product. Every finding gets an owner and a date, and repeat findings should be presented to leadership as organizational decisions, not surprises.