Making SET and Field Day count: what are you actually practicing, and how do you write it up?
- Replies 2
- Views 21
- Created
- Last Reply
Top Posters In This Topic
-
Admin_Terry 1 post
-
Mod_Tom 1 post
A better way to browse. Learn more.
A full-screen app on your home screen with push notifications, badges and more.
Most clubs treat the Simulated Emergency Test and Field Day as annual events. Both can be better practice for disaster communication if you decide beforehand which skills you want to test. Contacts logged and band points earned are not the same as served-agency readiness.
Field Day is good for power, antennas, setup speed, logging, operating in poor conditions and working as a team. It says little about message handling unless you add that on purpose. A simple way is to have the station captain or a "served agency" volunteer hand out a few written messages in ICS-213 or radiogram format and require that they be sent, received, copied, and delivered. Check them for accuracy at the end. Common errors include a wrong check count, a missing addressee phone number, and text that was paraphrased instead of sent as written.
SET is the better place to test the net structure. A solid net script covers the following:
A script is only useful if the people running it have read it before the exercise starts.
Different scenarios stress different things. A hurricane is a long-duration event with fuel, rest rotation, shelter communications and welfare traffic. A wildfire changes quickly, can take out repeaters and power, and creates evacuation and shelter traffic. A flood tests access, gauge or road-closure reports and moving between sites. An earthquake can take down telephone, cell and repeater infrastructure at the same time, which tests simplex and initial damage reporting. A tornado is short-fuse, so activation speed and spotter reporting matter, with damage assessment afterward. A prolonged grid failure tests batteries, generator logistics and how long repeaters and cell sites can stay up.
When you write the after-action report, keep it plain. State the objectives, what was planned, what happened, what worked, what didn't, and corrective actions with a named owner and a due date. A hot wash right after the exercise, while memories are fresh, helps. An after-action report that lists problems but assigns no owners tends to repeat the same problems next year.
Working with served agencies is the other half. Learn what they need: for example, an emergency management office may want situational reports in a certain format, while a shelter may need supply requests and welfare lists. Use plain language with them instead of Q-signals or club slang, and follow their chain of command. Do not self-deploy unless your agreement says you can.
So what do you build into your exercises beyond making contacts? What has been hardest to test realistically?
Link to comment
https://www.hamradiobase.com/forums/topic/11289-making-set-and-field-day-count-what-are-you-actually-practicing-and-how-do-you-write-it-up/Share on other sites