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 384.8 km/s
Aurora 1
Updated 13:30 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

Chasing award credits without losing track: how do you organize DXCC, WAS, WAZ, WPX, IOTA and the rest?

ci_cover.jpg

I'd like to compare approaches to managing award chasing across several programs, because the rules differ more than the on-air part does. A single QSO can count toward DXCC, WAS, WAC, WAZ, WPX and an IOTA group, but each program has its own definition of a valid confirmation, and a few don't use LoTW at all.

Here is how I understand the landscape. Please correct anything that's out of date, since rules and fees change.

ARRL programs (DXCC, WAS, WAC): these accept LoTW confirmations as well as paper QSL cards checked by an authorized field checker. DXCC has the Mixed, CW, Phone and Digital categories and band endorsements. Honor Roll is based on current entities only, so deleted entities count toward your total but not toward Honor Roll standing. The Challenge counts band-entity combinations rather than entities, which makes it a very different long-term project. WAS and WAC are much easier to finish, but they still need the right mode and band endorsements if you want them.

CQ programs (WAZ, WPX, Marathon): WAZ is zone-based, so zone boundaries matter more than entity names. WPX is prefix-based, which means a special-event prefix can be a real multiplier. The CQ DX Marathon works on a calendar-year scoring basis rather than a lifetime total. Check the current CQ rules on which confirmations are accepted for each award.

IOTA, POTA and SOTA: these are their own ecosystems. IOTA depends on valid island group references and on its own documentation and confirmation process. POTA and SOTA depend on activators submitting logs and on the program databases processing them, not on LoTW credit. For POTA especially, hunter credit depends on the activator uploading a log that includes your callsign, so a LoTW match won't help if the log never reaches the program.

Questions for the group:

1. Do you keep one master log and generate separate ADIF exports for each program, or maintain separate tracking sheets?

2. How do you handle deleted entities and old contacts when the current list changes? Do you check the QSO date against the period the entity was valid before you count it?

3. When LoTW doesn't match, what do you check first: callsign busts, time or band mismatches, mode grouping, or the other station's location settings?

4. Is it worth paying for paper QSLs from the rarest entities, or do you wait for LoTW to catch up?

  • Replies 2
  • Views 33
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

I'd keep one master log and treat every award as a report generated from it. Most of the pain comes from having several partial copies that disagree. Store the full ADIF fields: band, mode, date and time in UTC, DXCC entity, CQ zone, state or grid where relevant, and any IOTA, POTA or SOTA reference. Then each award's tracker is just a filter.

On LoTW mismatches, the usual causes are fairly mechanical. First, a small time difference or a wrong band. Second, a different mode that falls in another category; FT8 and similar modes are grouped as digital, but a mislabeled mode can still stop a match. Third, a callsign typo in one of the logs. Fourth, the other operator's LoTW location being set to the wrong entity, zone or state. That last one is outside your control, but it explains why a QSO can look perfect in your log and still not confirm for the award you need.

One caution: LoTW is a confirmation source, not the award itself. You still need to apply, so check the program's current requirements before you assume a credit is already counted. For IOTA, POTA and SOTA, don't rely on LoTW at all. Check what each program wants for logs and references, because the confirmation path is different.

  • Moderators

On deleted entities, the main thing is to separate three questions: what counts toward your total, what counts toward Honor Roll, and whether the QSO date falls in the valid period for that entity. A contact with an entity that was valid at the time is a different case from a contact claimed after the entity was removed from the list. That's why a date-aware entity lookup matters more than a name lookup. Callsign prefix alone is not enough, especially for DXpeditions and for operations that straddle boundary changes.

I'd also keep a separate note field for anything with a doubtful status, such as a new operation that might need approval for DXCC credit. Don't count those toward your total until the program has accepted them. It's easy to feel like you're 'one away' when the credit is still pending review.

For paper QSLs, think about how much each card improves your odds. If the station uses LoTW and has a good upload record, waiting is usually cheaper. If the operation is rare, short-lived, and unlikely to upload to LoTW, a direct or bureau card may be the only realistic route. In that case, make sure the card includes the data the award checker will look for: callsign, date, time in UTC, band and mode.

For WAZ and WPX, the quirks are different. Zones can be missed when you assume 'near enough', and WPX can reward prefixes you wouldn't normally chase. Keep those in separate views so you don't confuse entity progress with zone or prefix progress.

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.