Skip to content
View in the app

A better way to browse. Learn more.

Ham Radio Base

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.
Ham Radio Base — Education, Resources, Projects and Community
☀ Solar
SFI 99
SN 26
A 6
K 0 Quiet
X-Ray B2.3
Wind 384.8 km/s
Aurora 1
Updated 13:30 UTC HamQSL · N0NBH
Day 80/40m Good 30/20m Good 17/15m Fair 12/10m Poor
Night 80/40m Good 30/20m Good 17/15m Fair 12/10m Poor

Callsign Lookup
_
Vanity Call Signs Available
Enter filters above and click Search.
ⓘ Callsign lookups are in real time via the FCC database. Vanity callsign availability is refreshed daily at 6:00 AM CST. The vanity search may be unavailable for a few minutes during this update.
Live DX spots
Live DX Spots — 70cm via PSKReporter · scroll or pinch to zoom
Band
Mode
Time
Loading map data…
MHz DX Spotter Info
Recent spots —
Select a band above to load spots
Ready — select a band to fetch live spots

Making SET and Field Day count: designing exercises that expose real communication gaps

ci_cover.jpg

Most of us agree that exercises matter. The harder question is whether the ones we run test anything difficult. A Simulated Emergency Test where everyone checks in on the primary repeater, passes two tidy messages, and logs off after ninety minutes proves the repeater works on a good day. It tells us little about what happens when the repeater site loses power, the served agency's liaison is pulled away, or half the volunteers can't reach the staging location.

Here is a framework for building more useful exercises, and I'd like to see where people disagree with it.

1. Pick one failure per scenario and make it the point. Different disasters stress different parts of the system. A hurricane is mostly about duration: shift rotation, fuel and battery logistics, and traffic that changes from pre-landfall coordination to welfare inquiries and resource requests. A wildfire is about moving targets, with evacuation zones shifting, repeater coverage changing, and agencies needing situational information. An earthquake is about the sudden loss of infrastructure and the flood of unscheduled check-ins. A tornado or severe-weather event is short-fuse, so activation speed and clear reporting matter more than endurance. Flooding often brings road closures that decide who can physically get to a shelter or EOC. A grid failure is a good scenario for testing your own preparedness, because every station and every repeater is on battery or generator from the first minute. Choosing a single dominant problem makes the after-action review much clearer than throwing everything in at once.

2. Treat Field Day as practice, but add the missing pieces. Field Day is excellent for setting up antennas quickly, running on alternative power, operating in poor conditions, and working with people you don't operate with every week. It does not, by default, practice message handling, net control discipline, or interaction with an agency. If your group is already on site, consider a side activity: a small group formally originating and relaying a few messages while the contest-style operating continues. Even a short exercise shows who knows the format and who is guessing.

3. Use realistic, boring messages. The messages that matter in real events are rarely dramatic. They look like: request for 200 cots at a shelter, a road closure report, a generator fuel status, a change in shelter occupancy, a request for a medical resupply. Write exercise messages like that, with names, numbers, and locations that are easy to garble. Include at least one message that is long enough to tempt someone to paraphrase it, and one where the addressee can't be found.

4. Test the handoff between the agency form and the radio form. Served agencies often use their own forms, such as the ICS-213 General Message. Amateur traffic systems use the radiogram format, which has a message number, precedence, handling instructions, station of origin, check (word count), place of origin, time and date, addressee, text, and signature. Decide beforehand which format you'll use at the point of origin and which at the point of delivery, and who is responsible for the conversion. Practice sending the text exactly as written. A volunteer who "cleans up" the wording can accidentally change the meaning.

5. Write a net script, then see where it breaks. A good script is short enough to read under stress and covers: net identification and purpose, who is net control, how to check in (priority or emergency traffic first), what is being asked of stations, and how to ask for a repeat. Leave out unnecessary detail. The exercise should show whether net control can keep the channel moving when five stations call at once, and whether stations know to stand by instead of keying up with a long explanation.

6. Write the after-action report while it's fresh, and keep it structured. A simple format works: what we intended to test, what happened, what worked, what didn't, why, and what we'll change, with a named owner and a time frame for each change. The most useful reports separate observation from opinion. "Net control took eleven minutes to find a station able to relay to the shelter" is better than "coordination was weak."

Questions for the group: What failure do you think local exercises most often leave out? And has anyone found a good way to bring a served-agency counterpart into the exercise without turning it into a scripted show?

  • Replies 2
  • Views 30
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

On the served-agency question, the biggest improvement is usually getting the agency to give you the messages, or at least to approve what you send. If the exercise messages are all written by the radio group, you're testing the radio group's own assumptions. A message written by someone who doesn't think in radio terms will include abbreviations, internal jargon, and unclear locations, which is exactly what you'll receive in a real event.

Also decide in advance what you will and won't do. Does the agency want messages signed by a specific person? Who is authorized to send traffic on their behalf, and who confirms receipt? Amateur operators generally shouldn't be deciding the content or priority of an agency's message. They should be moving it accurately. If an operator thinks a message needs clarification, the right move is to ask the originator, not to rewrite it.

One easy drill: have the agency originate a message that needs a reply, and see how long the round trip takes. Not just delivery, but the full cycle of send, deliver, answer, send back. That number is often a surprise, and it's more convincing to an agency than a list of capabilities.

  • Administrators

I'd add one thing to the after-action section: separate people problems from equipment problems, because they get fixed differently. A dead battery is a checklist item. An operator who didn't know when to stand down is a training and scheduling item. Mixing them in one list makes it hard to assign owners.

For a grid-failure scenario, a useful constraint is to run part of the exercise as if there's no internet. That means no looking up frequencies, no emailing forms, no checking a shared document for the roster. Print the net script, the contact list, the frequency plan, and blank message forms, and keep them in a go-kit. You'll quickly find which things only exist on someone's phone.

Fatigue is also worth simulating even in a short exercise. You can't really recreate a multi-day hurricane response in an afternoon, but you can make people practice a clean shift change: what the incoming operator needs to know, which messages are still open, and what's pending a reply. A written handoff log is a small habit that makes long events much more manageable.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

Affiliate Disclosure: As an Amazon Associate, Ham Radio Base earns from qualifying purchases. Some links throughout this website may be affiliate links. If you purchase a product through one of these links, we may earn a commission at no additional cost to you. Your support helps us continue creating free articles, tutorials, reviews, and resources for the amateur radio community. N0TLB © Ham Radio Base - Powered by the Ham CQ DX Community. All rights reserved.

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.