Making SET and Field Day count: what do your exercises actually test, and what do the after-action reports say?
- Replies 2
- Views 23
- Created
- Last Reply
Top Posters In This Topic
-
Mod_Chad 1 post
-
Mod_Chrissy 1 post
Most of us agree that exercises matter, but a lot of them end up as "everyone checked in, everyone had fun, see you next year." I'd like to compare notes on how to make the Simulated Emergency Test and Field Day more useful as disaster-communication practice. The question is what a given exercise tests, and whether the lessons make it into the next one.
Start with scenario design. A hurricane scenario stresses different things than a wildfire or an earthquake. Hurricane response is mostly about lead time: pre-staging, rotating operators, fuel, and what happens when the storm has passed but power and cell service are still out for days. A wildfire is fast-moving and boundary-driven. Evacuation zones change, repeater sites may be threatened, and the served agency's needs change by the hour. Earthquakes and tornadoes give little or no warning, so the test is how quickly you can go from a normal day to a functioning net with whoever is available. Floods tend to isolate people by geography, which raises questions about which bridges, roads and relay sites you can reach. A grid failure tests everything on battery and generator, including whether your repeaters and linking systems stay up. A good exercise picks one or two of these stresses and builds around them, rather than trying to simulate everything.
Field Day is not an emergency exercise by design, but it's valuable practice for a few specific things. It lets you set up antennas and power away from home, run on generators and batteries, work as a team under time pressure, and find out which cables, adapters and logging tools are missing. It does not automatically practice message handling or serving an agency. If you want it to, add a deliberate element, such as a formal message-handling station that passes a few messages in a standard format, or a short drill where one station acts as a served-agency liaison. The ARRL Field Day rules have traditionally awarded bonus points for things like handling formal messages, so there's a built-in reason to try it.
On net scripts, the most useful ones are short enough to use under stress. A decent script covers who is in control, the purpose of the net, how to check in, how to signal priority or emergency traffic, and how to close or hand off. Check-in categories help the net control station sort people quickly, for example stations with traffic, stations available for assignment, and stations that are just monitoring. Plain language works better than codes, especially when agency personnel are listening. A script should help a new net control operator get through the first ten minutes, and it should leave them room to adapt.
Message handling is where drills often reveal the most. A standard ARRL radiogram has a number, a precedence, a station of origin, a check (the word count), a place of origin, a time and date, then the address, text and signature. Many served agencies use ICS-213 or a similar general message form instead. Both are fine, but operators need to know which one applies and how to convert between them without changing the meaning. Typical failure points are unclear handwriting, unspoken numbers, dropped words, and long messages that should have been split or summarized. Phonetics for ambiguous words and a readback for critical numbers, such as addresses, quantities and names, make a big difference.
Working with served agencies deserves its own debrief. Useful questions: Did we know who our point of contact was, and did they know what we can and can't do? Did requests arrive as clear, actionable messages, or as vague wishes? Did we understand the agency's priorities, or did we send everything we heard? Did we respect their chain of command? Agencies like emergency management offices, the Red Cross, hospitals and the National Weather Service each have their own routines. Learning them before the event matters more than any piece of equipment.
Finally, the after-action report. A simple structure works: what we planned to do, what actually happened, what worked, what didn't, and what we will change, with an owner and a date for each change. Many emergency-management programs use a format with strengths, areas for improvement and corrective actions, and that style is easy to borrow. The point is that action items get assigned and revisited at the next meeting. A report that nobody reads again is just a diary.
So for discussion: what do you try to test in your section's SET? How do you structure the AAR so that fixes actually get done? And if you've found a way to add real message handling or agency interaction to Field Day without wrecking the fun, what does that look like?
Link to comment
https://www.hamradiobase.com/forums/topic/11647-making-set-and-field-day-count-what-do-your-exercises-actually-test-and-what-do-the-after-action-reports-say/Share on other sites