Making SET and Field Day Count: Scenario Ideas, Net Scripts, Message Handling and Served-Agency Lessons
- Replies 2
- Views 34
- 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 a Simulated Emergency Test or Field Day every year, but it's easy to treat them as participation events: make contacts, log them, take photos, go home. They can also be rehearsals for the things that go wrong in real activations. This thread is for comparing ideas on how to build exercises that expose weak points while the stakes are low.
A useful way to start is to pick a hazard and ask what it breaks, rather than which radios to bring. Each hazard stresses a different part of the communications plan:
Hurricanes give warning, so the problems tend to be about sustained operations. Think shift schedules, fuel and battery logistics, operators who evacuate or can't reach the shelter, and long-haul traffic when the local area is damaged. A good exercise injects a mid-event change, such as a shelter closing and its occupants moving to another site, and checks whether net control and the served agency's liaison hear about it at the same time.
Wildfires change fast, and repeaters on mountaintops can be lost to fire or power failure. Exercise a simplex fallback plan, route changes when a road closes, and what happens when an evacuation zone sits on top of your planned operating location. Check whether operators know where the agreed fallback frequencies are without looking them up on a phone.
Floods make access the main issue. Bridges, low roads and flooded parking lots can cut off a site from its operators. Scenario injects can include a gauge-reading report, a request for a welfare check, or a shelter that needs supplies. They also test whether your messages say exactly where something is rather than "the usual spot."
Earthquakes come without warning and may take out infrastructure in patterns that are hard to predict. The first hour is usually about check-ins and damage assessment, so practice a structured net that collects short, standardized reports instead of letting everyone call in at once. Also test whether people can reach their assigned site if their usual route is blocked.
Tornadoes are localized and quick. Spotter-style communication, clear reporting of location and direction, and a clean handoff between a weather-focused net and a post-event damage net are good things to test. The after-event phase often gets less practice than the warning phase.
Grid failures are good for testing the unglamorous parts: how long do your batteries really last under a realistic duty cycle, can you recharge, does anyone know the generator's fuel plan, and what happens when cell service and internet degrade together? A long outage scenario also reveals operator fatigue and the need for relief schedules.
Field Day is not an emergency exercise by itself, but it is excellent practice for the underlying skills: setting up quickly away from home power, solving antenna and interference problems, managing a station log, and working as a team. To get more from it, add an emergency-style element: a traffic-handling station that originates and delivers formal messages, a short drill where one station must set up in a different band or mode on short notice, or a rotation that makes someone who normally runs a station take on net control or logging duties.
For net scripts, short is usually better than clever. A script should cover the net's purpose, the call for emergency or priority traffic first, then check-ins by category, then routine traffic, then closing and next net time. Consider keeping a printed copy with a separate quick-reference card for new net control operators, containing the frequency plan, the agency contact list, and the rules for who may speak. If a script only works for the person who wrote it, it isn't really a script.
Message handling deserves its own drill. In the ARRL radiogram format, the preamble carries a message number, precedence, any handling instructions, station of origin, check (the word count), place of origin, and time and date filed, followed by the address, text and signature. The check matters because it gives the receiving operator a way to notice that something was dropped. Common precedences include Routine, Welfare, Priority and Emergency, and it helps if operators agree beforehand on what qualifies. Also practice the discipline of reading back figures and unusual names, spelling them phonetically, and not paraphrasing the text. The sender's wording is what the served agency actually wrote.
On working with served agencies, the most useful exercises are the ones where a real agency contact takes part, even in a limited way. Ask what information they actually need, in what form, and who is authorized to hand it to you. Agencies often want concise, verified, actionable reports rather than everything an operator hears. It helps to settle questions like these in advance: who tasks the volunteers, how are operators identified at the site, what is the policy on releasing information, and how do you hand off when a shift ends?
Finally, an exercise isn't finished until it produces an after-action report. A simple structure works: objectives, what actually happened, what went well, what didn't, causes (not blame), and specific corrective actions with an owner and a due date. Corrective actions that nobody owns tend to reappear unchanged next year.
Questions to get things going: What inject has most reliably exposed a weakness in your group's plan? How do you keep a scenario realistic without making it so complicated that participants spend the time reading instructions? And how do you get served-agency staff to take part in an exercise they may see as the club's event rather than theirs?
Link to comment
https://www.hamradiobase.com/forums/topic/10903-making-set-and-field-day-count-scenario-ideas-net-scripts-message-handling-and-served-agency-lessons/Share on other sites