Making SET and Field Day count: scenario design, net scripts, message handling and honest after-action reports
- Replies 2
- Views 43
- Created
- Last Reply
Top Posters In This Topic
-
Admin_Terry 1 post
-
Mod_Chad 1 post
Most clubs run Field Day and the Simulated Emergency Test (SET) and walk away with a log, a few photos and a general feeling that it went fine. That feeling isn't much use when a real event hits. This thread is for swapping ideas on turning those events into practice that exposes weak spots while the stakes are still low.
Start with the scenario. "Hurricane" is too vague to drive anything. Pick the specific failures it causes: commercial power is out for days, cell sites are on battery and then go dark, the repeater site is on generator with limited fuel, and the EOC wants shelter status every few hours. Each hazard stresses different things. Floods cut roads, so you may need to relocate operators and pre-position them. Wildfires move fast, force evacuations of your own members, and fill the air with traffic from agencies that are not yours. Earthquakes mean damage assessment, welfare inquiries, and the question of which of your own antennas and repeaters are still standing. Tornadoes are short and sharp, so the practice is mostly spotter coordination and fast, clean reporting. A long grid failure is the slow one, and it tests shift schedules, fuel, batteries and operator fatigue more than any single radio skill.
Field Day is good practice for some things and poor for others. It teaches fast, portable setup, power management, antenna work in bad conditions, and working as a team under time pressure. It does not teach message handling, agency liaison or disciplined net operation unless you add those on purpose. Consider building a short side exercise into the weekend: a station that does nothing but originate, relay and deliver formal messages, or a mock served-agency request that arrives mid-event and has to be answered with a short report. Even something small, like losing the main generator or a key operator at a set time, shows how well your plan survives a surprise.
Net scripts deserve more attention than they usually get. A good script is short enough to read under stress and written so that a substitute net control can run it cold. Useful elements include a clear opening that states the purpose and whether the net is directed, a call for emergency or priority traffic before anything else, check-in categories (for example, stations with traffic, stations at served-agency locations, mobile or portable, general), a plan for how traffic gets passed, and a closing with the next scheduled net time. Practice the handoff to a relief net control, and practice a net where the primary repeater is declared unavailable and everyone moves to a simplex or backup plan. A script that has never been used with a backup frequency is a script with an untested assumption.
On message handling, there are two lanes worth drilling. Formal radiogram format (preamble with message number, precedence, station of origin, check, place of origin, time and date, then address, text and signature) is the NTS standard and works well for traffic that has to move through several hands without being altered. Agency forms like the ICS 213 General Message are what many served agencies actually hand you. Operators should know how to take an ICS 213 and, when needed, convert its content to radiogram form or pass it verbatim, and should know which one the agency expects. Practice precedence too: emergency, priority, welfare and routine are not interchangeable, and treating every message as urgent buries the ones that matter. Watch for the common failure points, which are word counts that do not match the check, abbreviations the receiver does not understand, and unclear signatures or addressees.
Served agencies are the part clubs most often leave to the last minute. Find out in advance what each agency wants from you and in what form: who is authorized to request support, where operators report, what identification they need, what the agency's own communications already cover, and who the point of contact is when you arrive. Invite the agency to take part in the exercise, even in a limited way, and ask them to write a realistic request instead of a polite hypothetical. Their feedback on what was useful and what was noise is worth more than your own log.
Finally, the after-action report. Keep it plain and specific. Record what the objectives were, what actually happened, what worked, what did not, and what will be changed, with a named owner and a date for each fix. Separate observations from opinions. "The net took twelve minutes to pass four messages" is more useful than "traffic handling was slow." Include equipment failures, gaps in the roster, and any confusion about who was in charge. Then, at the next exercise, check whether last time's items were actually fixed.
What have you built into your SET or Field Day plans that exposed something uncomfortable? And how do you handle the tension between formal message formats and the plain language that agencies often prefer?
Link to comment
https://www.hamradiobase.com/forums/topic/11042-making-set-and-field-day-count-scenario-design-net-scripts-message-handling-and-honest-after-action-reports/Share on other sites