Thursday, August 27, 2026
24 check-insThis Week's Question
“You’re deployed at a hospital. Net Control announces ‘Emergency traffic only.’ A hospital official hands you an important logistical message about incoming supplies that are needed. How should you classify and handle this traffic?”
“And because every good net needs a little levity between the serious stuff - what is your favorite donut?”
Classifying Traffic Under NTS: Precedence, Pressure, and (Yes) Donuts
Why Precedence Still Matters
Anyone can pass a message. What separates a trained traffic handler from someone just keying a mic is the ability to correctly classify what they're carrying - and to move it with speed and accuracy that matches its true urgency.
The National Traffic System (NTS) has been training operators in exactly this skill for decades, and the underlying discipline is just as relevant today - whether you're passing a formal radiogram or relaying a quick message at a served-agency deployment.
When precedence is assigned correctly, nets flow smoothly: genuine emergencies get instant attention, important-but-not-critical traffic still moves promptly, and routine chatter doesn't clog the channel. When precedence is assigned incorrectly - in either direction - things go wrong fast.
Inflating Traffic
Calling everything "Emergency" trains net control and other stations to stop trusting your precedence calls - and it can bury an actual life-safety message under a pile of false urgency.
Downgrading Traffic
Marking something "Routine" because it feels awkward to interrupt the net can delay a message that a served agency is actively waiting on.
Formal traffic handling - real radiograms, real precedence, real procedure - is what lets served agencies (hospitals, EOCs, shelters) trust that when we say something is Priority, it actually is.
Tonight's Scenario: The Hospital Hand-Off
You're deployed as communications support at a hospital during a regional disaster response. Net Control keys up: "Emergency traffic only, all other stations please stand by."
A few minutes later, a hospital logistics official walks up to your table and hands you a note: incoming medical supplies are needed, and someone needs to relay that information back through the net - soon.
It's not a shouting-match emergency. Nobody's life is hanging in the balance in the next sixty seconds. But it's clearly not "just chatting" traffic either. Net Control just told you the channel is closed except for the highest precedence. What do you do with this message?
Traffic Precedence at a Glance
NTS defines four precedence levels. Higher precedence traffic is always handled before lower precedence traffic when a net or circuit is busy.
| Precedence | Abbreviation / Form Usage | What It Means | Typical Examples | Relative Urgency |
|---|---|---|---|---|
| EMERGENCY | Always spelled out in full on the form - never abbreviated | Life-or-death urgency; immediate threat to human life or property | Medical emergencies, severe/imminent disaster threats to life | Highest - absolute priority |
| PRIORITY | P | Important, time-limited messages tied to official disaster relief - not life-or-death in the moment | Official relief traffic, notices of injury/death in a disaster zone, urgent logistics | High |
| WELFARE | W | Inquiries about, or advisories on, the health and welfare of people inside a disaster area | "Is my family OK?" inquiries; "I'm safe" advisories | Moderate |
| ROUTINE | R | Normal, everyday traffic with no urgent time element | Greetings, check-ins, general inquiries | Lowest - handled last when busy |
How Should This Hospital Traffic Be Classified?
In most cases like this, the supply message is best classified as PRIORITY. It's official, disaster-relief-related, and time-sensitive - but at the moment you receive it, it isn't a life-or-death emergency. That combination is the textbook definition of Priority traffic.
A few habits keep this kind of call clean and defensible in the moment:
- Clarify the message with the hospital official if anything is unclear
- Get it into proper radiogram form before passing it
- Preserve accuracy - don't paraphrase details that matter
- Mark the precedence correctly - Priority, not Emergency
- Move it promptly once net control opens the floor for it
- Don't inflate routine traffic into Emergency - and don't downgrade something truly urgent, either
The "Ask Yourself" Table: Categorizing Any Message
Precedence isn't guesswork - it's a short chain of questions. Work down the table below in order and stop at the first question you answer "yes". That row is your precedence.
| Ask Yourself | If Yes... | Why |
|---|---|---|
| Does someone's life, safety, or health change if this message doesn't move in the next few minutes? | EMERGENCY | Immediate threat to life takes absolute priority over everything else on the net. |
| Is it official, disaster-relief-related, and time-sensitive - but not an immediate life-or-death situation right now? | PRIORITY | Important and urgent, but there's no immediate danger if it takes a few more minutes to move. |
| Is it asking about - or reporting on - the health and welfare of a specific person in a disaster area? | WELFARE | Personal, but not tied to an active operational deadline - families waiting on word, not supplies waiting on a truck. |
| Is this just a greeting, check-in, or general inquiry with no urgency at all? | ROUTINE | Everyday traffic - move it when the circuit is free, never ahead of higher precedence traffic. |
This Week's Question
The Traffic Question
You're at a hospital deployment. Net Control says "Emergency traffic only." A hospital official hands you an important logistical message about needed incoming supplies. How do you classify and handle it?
The Donut Question
What is your favorite donut - and why does it earn that spot?
Donuts, Morale, and Field Fuel
Formal message handling is serious business - but morale matters too, and it doesn't take much to keep a deployed team in good spirits. A box of donuts at 6 AM has ended more grumbling than most pep talks.
Best "Energy" Donut
A classic glazed - quick sugar, quick carbs, gets you through the next hour on the radio.
Best Morale Donut
Whatever the box has the fewest of left - claiming the last chocolate frosted feels like a small victory.
"Healthiest" Donut
Debatable - but a plain cake donut with coffee is about as close as this category gets.
Small comfort items - donuts, coffee, a decent chair - don't replace good procedure, but they do help a team stay sharp through a long operational period. Take care of your people, and they'll take care of the traffic.
A Few Things to Think About
- Have you ever had to decide how to classify a message under pressure?
- What clues tell you something is Priority rather than Emergency?
- Do you feel comfortable turning an informal message into a formal radiogram?
- What part of traffic handling do you want to practice more?
- Would you have handled the hospital scenario differently?
- What is your favorite donut, and why?
The Real Goal
Traffic handling is a core communications skill, and NTS standards exist so that every operator on the net - regardless of experience level - is speaking the same language of precedence. Formal radiogram practice is a skill worth sharpening, even if most nights it stays quiet. And a little humor and morale-building along the way just makes the training stick better.
Resources & Further Reading
NTS - National Traffic System
- NTS for the 21st Century The main hub for modern NTS information and resources.
- Send a Radiogram by Amateur Radio The core message format used throughout NTS.
- Radiogram Call Script Guide Good on-air procedure for passing traffic correctly.
- Standards & Procedures Precedence definitions and formal handling standards.
- Bulk Traffic Best Practices Handling traffic accurately and in a timely fashion at volume.
- ARRL Radiogram Form (Fillable PDF) Print or fill out digitally - keep a few blank copies in your go-kit.
Check-In List
| # | Call Sign | Unit # | Name | City | Member |
|---|---|---|---|---|---|
| 1 | N8VDZ | 2 | Mike | Warren | Member |
| 2 | KE8WUO | 20 | John | Warren | Member |
| 3 | W8VOX | 30 | Jon | Macomb | Member |
| 4 | KC8KJO | 14 | Tom | Memphis | Member |
| 5 | N8CAF | 26 | Cliff | Clinton Township | — |
| 6 | N8HAP | 15 | Joe | New Baltimore | — |
| 7 | AD8OD | 21 | John | Troy | — |
| 8 | KE8YNU | 1 | Dave | New Haven | — |
| 9 | WA4MLD | 18 | Ray | Warren | Member |
| 10 | W8BPD | 24 | Brian | Warren | Member |
| 11 | N8KJV | 38 | Jason | Warren | — |
| 12 | K8WA | 19 | Bill | Warren | Member |
| 13 | KF8FQZ | 41 | Lisa | Warren | — |
| 14 | KF8ETQ | 23 | Darren | Fraser | Member |
| 15 | WC8E | 8 | Jeff | Sterling Heights | Member |
| 16 | KE8LAX | 22 | Dean | New Haven | Member |
| 17 | N8HLY | 12 | Tom | Sterling Heights | Member |
| 18 | N8WCB | 6 | Dave | Sterling Heights | Member |
| 19 | KF8FGS | 32 | David | Utica | — |
| 20 | N8WRO | 10 | Tim | Richmond | — |
| 21 | N8BZR | 27 | Brian | Harrison Township | Member |
| 22 | W8VD | 9 | Wally | New Baltimore | Member |
| 23 | KA8UHG | 28 | Steven | Saint Clair Shores | Member |
| 24 | KF8FRA | 44 | Peter | Warren | — |