FT8 looks intimidating the first time you open a piece of digital mode software and watch dozens of short text lines scroll past. But underneath the clutter, nearly every FT8 contact follows the same tight, four-step pattern. Once you can read that pattern, you can follow any exchange on the waterfall, and you can take over the keyboard and run a contact by hand instead of just clicking "Enable TX" and hoping the software does the right thing.
What FT8 Actually Is
FT8 is a weak-signal digital mode built around short, structured text messages rather than free-form conversation. Each transmission lasts about 15 seconds, and the mode is designed to pull a readable message out of a radio signal that's far too weak to hear as voice. That efficiency is why FT8 has become so popular on HF: two stations can complete a verified contact with very little power and a very ordinary antenna.
The tradeoff is that messages are short and formatted. You can't chat on FT8 the way you can on single sideband phone or even CW. Instead, the mode uses a small set of message types, and learning what each one means is really the whole skill.
The Anatomy of an FT8 Message
Almost every message you'll see has the same basic shape: who it's for, who it's from, and then one piece of data. That data might be a grid square, a signal report, or a simple acknowledgment. Software displays these as compact lines, something like a callsign, another callsign, and then a grid or a number. There's no punctuation to speak of and no extra words, because every character costs transmission time and decoding margin.
If you remember nothing else, remember this: the mode is built around answering three questions in sequence. Who's calling? Who's answering, and where are they? How well did we hear each other, and are we done?
Step One: The CQ Call
A general call starts with the word CQ, followed by the calling station's own call sign, followed by a four-character Maidenhead grid square. The grid square is a compact way of encoding approximate location, and it lets the receiving station estimate distance and direction without any extra conversation. This single line does the job that used to take a full sentence on phone.
Calling CQ on FT8 is still calling CQ, in the same spirit described in our guide to calling CQ properly: you're announcing you're listening and ready for a contact, just in a much more condensed form.
Step Two: The Reply
When another station answers that CQ, their message includes both call signs: the original caller's call sign first, then the replying station's own call sign, then that replying station's grid square. Including both calls matters because many stations are transmitting in the same narrow slice of the waterfall at once, and software needs to know exactly which reply belongs to which call before showing it to you.
This is the point where a human watching the waterfall has to pick, if there are several replies, which one to answer. The software can automate that choice, but understanding it is what lets you click deliberately instead of just taking whatever the program highlights first.
Step Three: The Signal Report
Once the original station answers back, the message changes shape slightly: it still has both call signs, but the grid square is replaced by a signal report expressed as a signed number, roughly from -24 to +50, representing decibels relative to the noise floor as measured by the decoder. A report of -10 means a weak but clearly decodable signal; a report near +10 or higher means a strong one. These numbers are not the same scale as the old 59 phone reports, and there's no "readability" component since the software either decodes the message or it doesn't.
The replying station then sends its own report back, using the same format. At this point both stations have exchanged call signs, grid squares, and signal reports, which is everything required for a valid, loggable contact.
Step Four: RRR, RR73, and the Final 73
To close things out, the station that received the signal report sends an acknowledgment. Depending on the software and the operator's choice, this appears as RR73, meaning "received, and 73," or sometimes just RRR to confirm receipt before a separate 73 message. The word 73 itself is a long-standing shorthand for "best regards," and it's the conventional way to end a contact on nearly every mode.
Many contacts these days are completed in exactly four transmissions: CQ, reply with report, report back, and RR73. That's a complete, both-ways-confirmed contact in about a minute.
Why Timing Matters So Much
FT8 divides time into fixed 15-second slots, and every station on a given frequency transmits during the same slots. If your computer's clock drifts even a couple of seconds, your transmissions land in the wrong slot and nothing decodes properly, even though your signal is perfectly readable on the air. This is one of the most common sources of frustration for new digital mode operators, and it has nothing to do with your radio or antenna.
If you haven't checked your system clock recently, it's worth doing before your next session; our guide to syncing your PC clock for FT8 walks through the free tools that keep you within the needed tolerance.
Taking Manual Control
Most FT8 software defaults to fully automatic sequencing: it picks a station to answer, sends the next logical message, and advances through the exchange without you touching anything beyond the first click. That's fine for quick contacts, but it can also mean you don't really understand what just happened.
Turning off auto-sequencing, even temporarily, lets you watch each decoded line, choose your own reply, and manually select which message to send next. Doing this a few times is the fastest way to genuinely learn the exchange instead of just trusting the software. It also helps when conditions get crowded and the automatic logic picks a reply you didn't intend.
Common Mistakes to Watch For
- Answering a CQ that wasn't meant for the band segment you're licensed on. Data sub-bands and privileges differ between the USA and Canada, so confirm your license class covers the frequency before transmitting.
- Letting clock drift go unchecked. A slow, drifting clock causes missed decodes that look like a radio problem but aren't.
- Overdriving the audio into the radio. Too much drive causes distortion that spreads your signal across the waterfall and makes you harder to decode, not easier.
- Logging before the exchange is actually complete. A contact isn't confirmed until both signal reports have been exchanged, not just after the first reply.
- Confusing RR73 with a guaranteed two-way confirmation. It confirms you received their message; it's still good practice to check your own log afterward.
Audio drive issues are common enough that they deserve their own attention; see our piece on setting digital mode audio levels correctly if your reports seem lower than expected.
Before You Transmit: A Short Checklist
- Confirm your license and local rules allow transmitting on that band and mode.
- Sync your computer clock to within a second or two of accurate time.
- Check that your grid square is entered correctly in the software.
- Set transmit audio so you're not overdriving the interface.
- Glance at the live HF propagation page to see whether the band is actually open before you call.
- Let the decoder run for a minute first so you understand what's already active on the frequency.
Logging the Result
Once RR73 and the final 73 have gone out, the contact is complete and ready to log. Most FT8 software can export directly in ADIF format, which drops straight into the free online logbook, so your grid squares, reports, and timestamps stay organized without retyping anything. If you want a quick reference for grid squares, Q-codes, and other shorthand you'll see in digital modes, the ham radio quick reference page is a handy page to keep open in another tab while you're learning.
Wrap-Up
FT8's text exchanges look cryptic at first, but they're really just a CQ, a reply, two signal reports, and a goodbye, repeated in the same order every time. Learn that four-step pattern, understand what the grid square and the dB numbers actually represent, and you'll be able to read any FT8 contact on the waterfall and run your own by hand whenever you choose to. The automation is convenient, but understanding what it's doing is what makes you an operator instead of just a button-pusher.
How HamRadioList can help
Once you start logging FT8 contacts, the free {{svc:logbook|online logbook}} keeps every grid square and report organized, and the {{svc:propagation|live HF propagation page}} helps you pick a band worth calling CQ on before you even open the software.
- Free online ham radio logbook - log every contact, import and export ADIF, sync with QRZ.com and keep your awards organised.
- Live HF propagation - see current band conditions before you call CQ.
- Ham radio quick reference - bands, modes, phonetics and Q-codes on one page.
- QSL and QSO cards - create shareable QSO and QSL cards from your logged contacts.
- License exam practice - practice questions for the US and Canadian amateur exams.
New here, or getting back on the air? Create your free HamRadioList account to log contacts, check band conditions and practise for your exam, or browse more guides from the blog. HamRadioList is built by amateur radio operators in Nova Scotia for operators everywhere.