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: how do you keep DXCC, WAS, WAZ, WPX, IOTA and the rest straight without losing track?

ci_cover.jpg

Once you work toward more than one award at a time, the rules start to overlap in confusing ways. This thread is for comparing how people keep it all organized. Rules and fees change, so check each sponsor's current rules before you rely on anything below.

Here is how I understand the main programs. DXCC (ARRL) counts entities on the current list, and the basic award starts at 100 confirmed. Deleted entities still count toward your total for the award, but they don't help you reach the Honor Roll, which is measured against the current list. The Challenge counts band-entity combinations rather than entities alone, so it rewards working the same place on many bands. WAS is the 50 states, and WAC is the six continents. WAZ (CQ) uses the 40 CQ zones, which are not the same as ITU zones. Zone boundaries trip people up, especially in places like Russia, Canada and South America. CQ WPX counts prefixes, so it works better than DXCC for contest-heavy operators. IOTA counts island groups under its own reference list. The CQ DX Marathon is a calendar-year program, so it resets each January.

POTA and SOTA are a different kind of chase. Their awards are mostly about activating and hunting references, and the credit comes through each program's own logging and database system, not through paper QSLs or LoTW. Many hunters and activators also use those contacts toward WAS, WAC or even DXCC, as long as the QSOs get confirmed through an accepted channel.

Some questions I'd like opinions on:

1. Do you rely on LoTW alone, or do you also chase paper QSLs, eQSL or direct cards for the entities that rarely upload? If you mix confirmation types, how do you track which award accepts which?

2. How do you handle entity-list changes in your logging software? Updating country files is easy, but I'd like to hear how people sanity-check older QSOs against the entity that existed on the contact date, especially around deleted entities and split or merged ones.

3. What is your workflow before you submit an application? Do you check callsign, band, mode and date mismatches first, or do you just let LoTW matching do the work?

4. For WAZ and IOTA especially, do you trust the log's automatic zone or reference assignment, or verify it by hand?

I'm not looking for the one right answer. I'd like to see how people set up their spreadsheets, logger filters and reminder habits so award credits don't turn into a mess.

  • Replies 2
  • Views 23
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Administrators

My suggestion is to keep a separate "needs confirmation" view in your logger, not just a worked/confirmed split. Entries fall into different categories: waiting on LoTW, waiting on a paper card, mismatched data, and not eligible for a particular award. A QSO that's perfectly good for WPX may be useless for DXCC if it's a mode or entity issue, so one yes/no flag isn't enough.

On LoTW, the common problem is a mismatch between the station's certificate and the QSO details, such as callsign, location, or the date range the certificate covers. When an expected match doesn't show up, check the other station's callsign and the QSO time first, before assuming they never uploaded. For DXCC, also make sure the entity LoTW assigns agrees with what you think you worked. That sometimes surprises people on islands and border-area operations.

For deleted entities, I'd keep them in your logs and just filter them out of the Honor Roll count. You don't want to throw away real contacts because the list changed.

  • Moderators

I'd separate the programs by how credit is verified, because that decides your workflow. DXCC, WAS and the Challenge go through ARRL and LoTW or accepted QSL evidence. WAZ, WPX and the Marathon go through CQ's own rules and submission processes. IOTA has its own references and checking, and POTA and SOTA have their own databases. If you mix them up, you can spend effort confirming a contact in a system that doesn't help the award you actually want.

One thing that helps with WAZ is to confirm the zone from the other station's actual location, not just from the prefix. A prefix can suggest the wrong zone. For IOTA, check the reference number against the current list and the operator's stated location, because a lookalike group can lead you astray.

For POTA and SOTA, I'd keep hunting and activating records separate from your DX award logs. They answer different questions: "did this contact count for the park or summit program" versus "did it count for entity, zone or state credit." Exporting from one system and importing into another without checking the fields can introduce duplicates or odd mode and band entries.

Finally, before applying, do a dry run on a small subset. Pull a handful of contacts per band and read them against the rules. Catching a systematic error early beats finding it after you've built a full application.

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.