Making SET and Field Day count: what to test, how to script it, and what to put in the after-action report
- Replies 2
- Views 15
- Created
- Last Reply
A better way to browse. Learn more.
A full-screen app on your home screen with push notifications, badges and more.
Most clubs run Field Day and the Simulated Emergency Test (SET), and many walk away with a good time and a stack of logs but few changes to how they would actually respond. Here are some ideas for turning both events into practice that shows up in your next activation, and I'd like to hear what others have done differently.
Start with a scenario, not a band plan. Pick a plausible event for your area: a tornado outbreak that knocks out commercial power and cell service in two counties, a wildfire evacuation with the county EOC on generator, a river flood that isolates a shelter, or an earthquake that damages repeater sites. Then write down the questions the served agency would ask. Which shelters are open? Is the hospital reporting a bed count? Who needs a welfare check? Build the exercise traffic around those answers, not around whatever contacts are easy to make.
Treat Field Day as a drill in setup and endurance. It's a poor test of message handling because contest-style exchanges don't resemble real traffic. It is a good test of other things: how fast a team can deploy antennas and power, whether the go-kit has the adapters, fuses and logbooks it needs, how operators handle fatigue and shift changes, and whether you can run on generator or battery without noise problems. Consider adding a small 'served agency' station, such as a table where someone hands operators formal messages to send. That adds a real message-handling component to an otherwise unrelated event.
Net scripts should be short enough to use. A good script covers the preamble (purpose of the net, who is in control, how to check in), check-in categories (emergency or priority traffic first, then station types or locations), a way to call for traffic, and a close with the next net time. Write it so a backup net control operator can pick it up cold. Use tactical call signs tied to location or function (for example 'Shelter North' or 'EOC Liaison') so the operator can change while the function stays the same, and still give your FCC call sign at the intervals required. Leave out 10-codes and jargon. Plain language works better across agencies.
Message handling is where drills show weaknesses. Practice with both the ICS-213 general message form and the ARRL radiogram format, because served agencies and traffic nets may use either. Radiograms have a standard preamble: message number, precedence (Routine, Welfare, Priority, Emergency), station of origin, check (word count), place of origin, time and date filed, followed by the address, text, and signature. Common drill failures are miscounted checks, missing phone numbers in the address, messages that run too long, and operators who rewrite the sender's text. The rule is to send what is written, read back anything uncertain, and keep a log of when each message was received, sent and delivered.
Include the served agency, if they'll participate. Even a short conversation beforehand helps: what formats do they use, who is authorized to originate messages, where do operators check in on arrival, and what do they expect when something goes wrong? If they can't take part, ask whether they'd review your scenario for realism. Remember that your role is to supplement their communications, not to decide priorities, and that sensitive health or personal information has to be handled according to their direction.
Write an after-action report people will actually read. A hot wash right after the exercise, while memory is fresh, works well. Then write a short report with the exercise objectives, who participated, what worked, what didn't, and specific corrective actions with an owner and a deadline. 'Improve coordination' isn't an action item. 'Net control will keep a printed list of all tactical call signs and locations at the table; assigned to the net manager before the next meeting' is. Follow-up matters more than the document: check next quarter whether each fix was made and retest it.
What scenario has your group found most useful, and what's the one problem that keeps turning up exercise after exercise?
Link to comment
https://www.hamradiobase.com/forums/topic/11749-making-set-and-field-day-count-what-to-test-how-to-script-it-and-what-to-put-in-the-after-action-report/Share on other sites