← All skills
Operating Skills · Beginner
Logging and What Happens After
Log it right at the park, get it uploaded, and understand what POTA does with it — including why your hunters are waiting on you.
~14 min · 0 of 8 checked
Run this checklist every activation. It is never marked finished — start fresh each time you head out.
Why this matters more than it looks
Logging feels like paperwork. It isn't — it's the part of POTA that other people depend on. Hunters never submit logs. Every contact they earn credit for comes from an activator's submission. When you don't upload, everyone who worked you loses that contact. Your log is the record for the entire QSO, both sides.
Remember
This is the strongest argument for logging carefully and uploading promptly. A sloppy or missing log doesn't just cost you an activation — it silently costs credit to every person who took the trouble to find you.1 · Logging at the park
Discipline
- Set your logger to UTC before you start, and leave it there permanently
- Log the contact as you make it, not from memory afterward
- Confirm the callsign back to the operator. It's the last chance to catch an error
- Keep a paper log running alongside. Phones die, overheat in the sun, and become unreadable in glare
- Pencil, not pen — pens fail in cold and rain
- If you're unsure of a call, log your best copy and note the uncertainty. A logged approximate beats a missing contact
On the air
The UTC day is the trap. It is not your local day. An evening activation in the US crosses midnight UTC partway through, splitting your session into two UTC days — and eight contacts plus four contacts is two failed attempts instead of one successful activation. Know when the rollover happens before you start.What POTA actually needs per contact
- Their callsign
- Date and time in UTC
- Band
- Mode
- Your own callsign (as station and/or operator)
- That's it — POTA requires no specific exchange. Signal reports are conventional courtesy, not a rule
2 · Choosing a logger
| Option | Strength | Consider |
|---|---|---|
| World Radio League (WRL) | Purpose-built for POTA, scales into contests. Leaderboards by mode, CAT control on common rigs, QRZ and LoTW upload on premium. | Works well on phone; laptop unlocks CAT and the dashboard |
| HAMRS | Simple, fast entry, popular starting point | Fewer features as you grow |
| Paper | Never fails | Manual transcription afterward |
| General logging software | If you already use one, ADIF export is what matters | Make sure it writes the required fields |
Practice goal
Two loggers, two jobs. The app you use at the park should optimize for speed of entry under pressure — you're logging with one hand during a pileup. The software you use at home optimizes for records and awards. They don't have to be the same tool, and ADIF is what moves between them.Before your first activation
- Practice entering a few contacts at home so the interface isn't new
- Find the ADIF export function and use it once. Discovering it at the picnic table wastes operating time
- Confirm your park reference is entered where the logger expects it
- Check that the app is writing UTC, not local
3 · Submitting to POTA
The flow
- Export your log as ADIF from whatever you used at the park
- Sign in to your POTA account
- Upload the ADIF, selecting the correct park and — if the park straddles a state line — the correct location
- Check the result. The upload tool reports accepted and rejected contacts
- Fix and re-upload anything rejected
Rules that govern submission
- Only activators submit. Hunters never do
- There's no deadline — but hunters are waiting, so don't sit on it
- One log covers one park in one location, even across multiple days
- Submit even if you got fewer than ten. It won't be an activation, but your hunters still get their credit
- Multi-park activation means a separate log for each park
- Club or group logs upload through the club's POTA account, not a personal one
Why contacts get rejected
| Reason | Fix |
|---|---|
| Duplicate | Same call, mode, date, band, park, location already logged. Note that a different band or mode is not a duplicate |
| Dated in the future | Almost always a local-vs-UTC error |
| You worked yourself | CALL can't match your own station or operator callsign |
| Missing required field | Check band, mode, date, time, and callsign are all present |
| Wrong park selected at upload | Re-upload against the correct reference |
4 · Beyond POTA
- Logbook of the World — upload the same ADIF if you're chasing ARRL awards. Separate system from POTA; both can have the same contacts
- QRZ logbook — popular for confirmations and a nice public record
- eQSL and paper QSL cards — optional, and a good use of the QSL card designer if you want physical cards
- None of these are required for POTA credit. POTA only cares about your POTA upload
Remember
Export once, upload several places. The same ADIF file feeds POTA, LoTW, and QRZ. Getting the log right at the park is what makes all of it painless afterward.5 · Awards and tracking
- Activator awards accrue from successful activations and unique parks; hunter awards from parks worked
- Park-to-park contacts count separately and are tracked on their own
- Your POTA profile shows activator and hunter statistics, awards, and endorsements
- Awards arrive on their own if you simply keep activating and uploading — chasing them is optional
- The most useful tracking early on isn't awards, it's noticing which bands, times, and parks actually work for you
Practice goal
After each activation, note three things: what band worked, what you forgot, and what you'd do differently. Three activations of that and you'll have learned more than any guide can teach you — including this one.Before you leave the park
When you get home
Official references
Built from the official POTA logging requirements and Submitting Logs documentation (docs.pota.app, Rules v1.2, 10 July 2026). Logger-specific steps change with app updates — verify against your logger's current documentation. Accurate as of July 2026.