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 412.9 km/s
Aurora 1
Updated 14:00 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

Organizing award chasing: DXCC, WAS, WAZ, WPX, IOTA, Marathon, POTA and SOTA, and how to keep the credits straight

ci_cover.jpg

I'd like to start a thread on how people organize award chasing when several programs overlap. The same QSO can count toward DXCC, WAZ, WPX, a Marathon score and possibly a POTA or SOTA log, but each program has its own confirmation rules, and it's easy to lose track of what counts where.

Here is a quick map of the main programs, so we start from the same page. Please correct me where I'm off.

DXCC (ARRL) is based on the DXCC entity list, which is not the same as countries or prefixes. Entities that have been removed from the list are deleted entities. Their QSOs can still count toward the standard DXCC totals, but not toward the Honor Roll. The Honor Roll is based on current entities, and the Challenge uses entity-band points across the bands the rules list. Check the ARRL rules for the exact band list and the current thresholds.

WAS (ARRL) needs the 50 states. WAC needs all six continents, which is usually the easy one. WAZ (CQ) is built on the 40 CQ zones, not DXCC entities, so a rare entity may be no use to you if you already have the zone. WPX (CQ) counts prefixes, which is why contest activity feeds it so well. IOTA (RSGB) counts island groups and references such as EU-005, and its confirmation rules are not the same as the ARRL's. CQ DX Marathon is a calendar-year competition scoring entities and zones, so it resets every January 1.

POTA and SOTA work differently. They aren't built on paper QSLs or LoTW. Activator logs go to the program's own database, and hunter or chaser credit comes from matching your contacts against those logs. That means the main thing you control as a hunter is that your callsign and the contact details in your own log are accurate.

These are the questions I'd like to hear your approach on:

  • Do you keep one master log and export from it for each program, or keep separate logs?
  • How do you handle contacts that are valid for DXCC but need a different confirmation for another program? An example is a station that isn't on LoTW but sends a paper card.
  • How do you track entities that were valid on the date of the QSO but have since been deleted, or entities whose boundaries or dates of validity changed?
  • When you apply for an endorsement, do you do it in small batches or wait until you have a large set of credits?
  • Replies 2
  • Views 30
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

For me the key idea is keeping a single log as the source of truth and treating every award program as a report generated from it. The details that cause trouble are the ones in the QSO record itself: the exact UTC date and time, the band and mode, the callsign as the other station actually used it, and the DXCC entity assigned. If the entity is wrong in your log, every downstream count is wrong too.

On deleted entities, date matters. DXCC rules look at when the QSO happened relative to the entity's valid period, so a deleted entity that was valid on the QSO date can still count toward the main DXCC listing, but it will not help the Honor Roll. Keep a separate view of current-only entities so you can see what you actually need. Logging software with a regularly updated country file helps, but check any odd result against the official ARRL entity list instead of trusting the software blindly.

For WAZ, don't assume zones follow entities. A few entities span more than one zone, and for those the station's actual location decides the zone, not the entity default. For big countries like the US, Canada, Russia, and a few others, a log that stores the zone per QSO saves a lot of confusion.

  • Administrators

One practical point on confirmations: LoTW is convenient because the matches arrive without waiting for a card, but a match only happens when both stations upload and the QSO details line up closely enough, including date, time, band and mode. So when a QSO you expected to match doesn't, the usual cause is a mistake on one side: a wrong band, a wrong callsign, or a certificate that doesn't cover the QSO date for that station. It's usually worth checking your own log before blaming the other station.

Also look at how each program treats confirmations. ARRL awards and CQ awards don't necessarily accept exactly the same things, and IOTA has its own checkpoint-based process, so read each program's current rules before you assume a credit transfers. POTA and SOTA are a different case again. As a hunter or chaser, you mostly need your log to match the activator's, so if a credit seems to be missing, compare callsign, date, band and mode with what the activator uploaded.

For applications, a sensible approach is to submit once you have a meaningful batch, not one contact at a time, because it's easier to review what you're claiming. Keep your own record of what's been submitted and credited, so you don't count the same contact twice when you plan the next step. And for Marathon, remember that the score starts from zero each year, so a different plan is needed, for example concentrating on new entities and zones early in the year when everything is new.

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.