Army Radio Etiquette Cheat Sheet

Why Nobody Reads the Field Manual Anymore

The FM 6-02.10 has 147 pages on radio procedures. I've read it. Nobody has. What actually works in the field is a condensed reference you can fold into your vest pocket and squint at when your hands are full and the squad leader is shouting over you. I built my first cheat sheet back in 2018 during a night operations exercise where the platoon sergeant made us copy three pages of procedure onto cardstock so we could survive comms checks without sounding like a rookie net. That's essentially what an Army Radio Etiquette Cheat Sheet is for, and it's what most units end up making themselves because the official stuff is designed for classroom study, not for 0300 hours in the rain. The core structure is straightforward. You need call signs, the NATO phonetic alphabet, brevity codes, procedure words, and the standard message format. What most people leave out are the edge cases that actually matter when things go wrong. I'll cover both. Here's the thing about radio etiquette that doesn't get enough emphasis: the format matters less than the discipline of keeping your transmissions short and predictable. A properly structured 45-second monologue will get you corrected faster than a sloppy 8-second one. I learned this the hard way during a live-fire exercise where our FIST liaison spent so long explaining his fire mission parameters that the target had already relocated twice. He knew the procedure. He just didn't understand that radio discipline is about information density per second of transmission, not about being thorough.

The standard call sign format is whatever your unit commander assigns. It's usually two to three syllables maximum. If you're operating with multiple platforms—ground net, air net, link net—you'll have different call signs for each. Write them down. Don't memorize them and hope. I've seen operators blank on their secondary net call sign during an actual comms handoff because they were relying on recall instead of a reference card. When you key the mic, wait a half-second after pressing the push-to-talk before you speak. That click you hear when the squelch opens? That's everyone on the net hearing the channel come alive. If you speak too early, the first word gets clipped. If you speak too late, you've created an awkward pause and someone else has already started talking. It's a timing thing that takes about two weeks of practice to internalize. During that learning period, keep it simple: key, pause, speak, release. Don't rush it.

The Message Format Nobody Remembers

A standard radio message follows the SALUTE format for reports and the 9-line medevac format for medical requests, but the everyday traffic you'll generate is usually shorter. Here's the default structure for a routine situation report: To: call sign of the station you're contacting From: your call sign

Message: the actual content, kept to one or two sentences End: phrase to close the transmission I once spent twenty minutes trying to complete a radio check because the guy on the other end kept asking me to repeat and I kept interpreting "say again" as a request for me to restate only the part I thought he missed rather than the entire transmission. He wanted the whole thing back. Every time. That's the default assumption. "Say again" means repeat everything unless you specify which portion you want repeated. I learned that after a particularly frustrating night patrol where we were trying to coordinate movement and I kept giving him fragments while he kept demanding the full message back, burning time we didn't have.

Numbers are pronounced digit by digit. Two zero four is "two zero four," not "two hundred four." Dates follow the YYYYMMDD format in written messages but on radio you'll hear things like "today is 1400 hours" or "the order was issued on the fifth." Time is always 24-hour format. There's no "oh hundred hours" in proper procedure, just "zero hundred hours." People who've been on the net a while will let it slide in casual conversation, but if you're writing a reference sheet for your squad, put it in correctly and don't make exceptions.

Phonetics and What Actually Matters

The NATO phonetic alphabet is Alpha, Bravo, Charlie, Delta, Echo, Foxtrot, Golf, Hotel, India, Juliett, Kilo, Lima, Mike, November, Oscar, Papa, Quebec, Romeo, Sierra, Tango, Uniform, Victor, Whiskey, X-ray, Yankee, Zulu. You should already know this. The part people forget is that you only use phonetics for individual letters that are critical to understanding. You don't phoneticize your entire name every time you introduce yourself on net. You use phonetics for call signs, grid coordinates, and any letter that could be confused in poor propagation conditions. I ran into a situation last year where a grid reference got botched because the operator spelled out "K" as "Kilo" when the receiving station was reading it as "Kay" from some old unit tradition. The difference was two hundred meters off target. We resolved it by agreeing on a standard before the operation, but the lesson was that phonetic consistency across a unit matters as much as knowing the alphabet. If your unit has its own shortcuts, document them. Don't assume everyone is reading from the same playbook.

When Everything Goes Wrong

Radio etiquette breaks down fast when you're dealing with interference, terrain masking, or equipment failure. The cheat sheet should address these scenarios because that's when you need procedure the most, not when the net is running clean. Here are the practical workarounds I've found: If you're being jammed or experiencing heavy static, slow down. Every word takes twice as long to get through clearly. Shorten your messages further. Drop filler words. Instead of "I am moving to the rally point now" just say "Moving to rally point." The receiver fills in the grammar. This is one of those counter-intuitive things: formal procedure sounds more natural in degraded conditions because it strips away everything non-essential. I found that our unit's comms clarity improved noticeably after we started drilling abbreviated transmissions during our weekly comms checks, even when conditions were perfect. It made the transition to degraded operations feel less like panic and more like routine. When you can't hear anyone and you need to get the net's attention, use "Break Break" before your transmission. This isn't standard traffic. It signals that you're interrupting and there's something important. I've seen operators misuse this during normal traffic flow and then wonder why everyone on net looked at them like they'd lost their mind. "Break Break" is for breaking into an active net, not for getting someone's attention when they're ignoring you. Those are different problems with different solutions.

Equipment failure is the silent killer of radio operations. I once had an AN/PRC-152 die mid-mission because the battery was old and the temperature had dropped below zero. We switched to the backup PLR-149 and spent ten minutes establishing a new net frequency because we hadn't pre-coordinated the backup plan. That's a gap in the cheat sheet that most people don't think about until it's too late. Include your backup frequencies, backup call signs, and a simple contingency procedure right on the reference card. Three lines at the bottom of the sheet that save ten minutes of confusion in the field.

Building Your Own Reference Sheet

Keep it to one side of a single 4x6 card. Front side gets call signs, phonetic alphabet, number pronunciation rules, and the standard message format. Back side gets the common procedure words (Wilco, Copy, Standing by, Out, Over), the 9-line medevac format, SALUTE report structure, and your backup contingency info. Waterproof it. Lamination works but it reflects light and becomes unreadable at night. I use a dry-erase marker on a matte laminate surface, which lets me wipe it clean and update it when call signs change, which is more often than you'd expect. If you want a starting point before you customize it for your unit, search for an Army Radio Etiquette Cheat Sheet template from MILPEP or the Combat Capabilities Development Command. The Army Publishing Directorate also has field-ready versions you can print. But here's the reality: the generic templates are fine for learning the structure, and they'll get you through basic training. For actual unit operations, you'll need to swap in your real call signs, your actual net frequencies, and the specific abbreviation your commander has approved. A template with placeholder text won't save you anything when you're on the radio and someone asks for your call sign.

The Unspoken Rules

There are things about radio discipline that never make it onto any official cheat sheet but determine whether your net runs smoothly or devolves into chaos. The first is listening. You cannot effectively operate a radio if you're only thinking about when it's your turn to talk. Listen to the net for at least thirty seconds before you key the mic. Figure out who's talking, what the current traffic is, and whether there's an established rhythm you should plug into or disrupt. The second is knowing when to hold your fire on the net. If two people are trying to talk at once, one of them needs to shut up immediately. There's no polite way to handle this. The person who realizes they've stepped on another transmission should key off, wait a beat, and try again. I've seen entire operations delayed because two operators kept talking over each other, each convinced the other would yield. They didn't. The net supervisor had to intervene and assign turns. Prevent that by developing the habit of yielding the first time you detect overlap. The third is that brevity is not the same as vagueness. "Moving to rally point" is brief and clear. "Moving" is brief and insufficient. You're not being penalized for providing necessary context. You're being penalized for providing context that the receiver already has or doesn't need. Read the room on the net. If the platoon sergeant already knows where the rally point is because he just gave the order, you don't need to restate it. Say "Moving." He'll know which rally point you mean because he just told the whole squad to move to it.