Making SET and Field Day Count: Scenario Ideas, Net Scripts, and What After-Action Reports Should Capture
- Replies 2
- Views 33
- 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 of us agree that drills are supposed to prepare us for real events. In practice, a Simulated Emergency Test or a Field Day weekend can turn into a contact-count exercise where everyone has fun, the antennas go up, and nothing is learned about handling traffic for a served agency. I'd like to collect ideas on how to make these events better practice, and how to write up the results so the next drill is better than the last.
One way to start is to pick a scenario that stresses a different failure each time. A hurricane scenario stresses long-duration operations, fuel and battery logistics, shift rotation, and welfare traffic going out of the affected area. A wildfire scenario stresses evacuations that change quickly, repeater sites losing power or access, and the need to work with an incident command structure that is moving. Flooding tends to cut roads and strand people, so you can practice relaying between shelters and an EOC when your normal routes are blocked. An earthquake scenario means assuming that infrastructure is damaged without warning and that many of your usual contacts are unavailable. Tornado scenarios compress everything into a short window, which suits spotter nets and quick check-ins. A grid failure scenario tests what happens when the internet, cell service, and repeater backup power fail together.
Then there is the message side. Whatever the scenario, I think every exercise should push real formatted traffic, not just "test, test" exchanges. That means practicing both the ARRL radiogram format (number, precedence, station of origin, check, place of origin, filing time and date, addressee, text, signature) and the general message form your served agencies actually use, such as an ICS-213 if that's what they hand you. Writing a message clearly, counting words for the check, and reading it back accurately are skills that go stale quickly. The precedences (Routine, Welfare, Priority, Emergency) are also worth drilling, because operators often default to treating everything as urgent.
For net scripts, the best ones are short enough to read under stress. A useful script covers: who is net control and why the net is open, the type of net (directed, informal, resource, or tactical), a check-in method that keeps the frequency from being swamped (by region, by capability, or by priority traffic first), a clear place to call for emergency or priority traffic, and a clean close with a time for the next net. Tactical call signs or location names such as "Shelter North" or "County EOC" keep things straightforward when operators rotate. And remember to identify with your FCC call sign as required.
Finally, the after-action report. A report that says "it went well" is not much use. Better to record what was planned, what actually happened, what the gap was, and what the fix is, with an owner and a deadline for each fix. Useful questions include: how long did it take to get the first station on the air and the first message delivered, did the served agency know who to contact and what we could and couldn't do, where did the message handling break down, which equipment or power plan failed, and which operators were overloaded.
So, what scenarios have you found most useful for SET, what would you change about how Field Day is used as practice, and what do you include in your after-action reports?
Link to comment
https://www.hamradiobase.com/forums/topic/11121-making-set-and-field-day-count-scenario-ideas-net-scripts-and-what-after-action-reports-should-capture/Share on other sites