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 across DXCC, WAZ, WPX, IOTA, POTA and SOTA: how are you tracking confirmations and avoiding wasted effort?

ci_cover.jpg

Once you work toward more than one award, the confirmations get messy. DXCC, WAS, WAC, CQ WAZ, WPX, IOTA, the CQ DX Marathon, POTA and SOTA all run on different rules, different confirmation methods and different definitions of a contact. A QSO that counts toward one award may not count toward another.

Here are the points that cause the most confusion. Please correct me if I've got any of this wrong.

Entity lists are not interchangeable. DXCC uses the ARRL entity list. CQ WAZ is based on the 40 CQ zones, and WPX is based on prefixes. IOTA counts island groups, and POTA and SOTA count references (parks and summits). A single contact might add an entity, a zone, a prefix and an IOTA group. It might not add any of them, depending on how each program defines the location. Check the current rules for each award before assuming a contact will count.

Deleted entities. Deleted DXCC entities generally still count toward the basic DXCC awards if you worked them while they were valid, but they do not count toward the Honor Roll, which is based on current entities. This matters when you plan Honor Roll pushes, because a deleted entity does not help you there.

LoTW is not a simple upload-and-done system. A QSO only becomes a confirmation when the other station uploads a matching record. The call, band, mode and time must match within the system's tolerance. The station location in TQSL also has to be set correctly, with the right DXCC entity, zones and grid. A wrong entity or zone in your TQSL station location can make a QSO look confirmed while it credits the wrong thing, or not credit at all. Operators who move between portable locations or use special event calls need to be careful here.

Paper QSLs and other routes. DXCC still accepts cards checked by approved field checkers. Other awards accept different evidence, and some do not accept LoTW at all. Always read the current confirmation rules for the specific award rather than assuming LoTW is universal.

POTA and SOTA are different animals. POTA and SOTA credit comes from logs submitted to their own databases, not from ARRL-style confirmation. Hunters and chasers need the activator's log to include them. Activator thresholds are also set by each program, so check them on the official sites.

I'd like to hear what you use. Do you keep a master log (Log4OM, N1MM, a spreadsheet, a database) and generate each award's reports from it, or do you keep separate trackers? How do you handle band-mode slots for DXCC Challenge without losing track of which ones are only worked and which ones are confirmed? And has anyone built a good routine for catching bad TQSL station location settings before they cause problems?

  • Replies 2
  • Views 22
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

My advice is to keep one master log with fields for everything you might need later, and treat each award as a report, not a separate record. Store the DXCC entity, CQ zone, ITU zone, state or province, IOTA reference and POTA/SOTA reference on every QSO that has them. Then you can run the same data through the ADIF export for LoTW, the Marathon, WPX and so on without retyping anything.

The big trap is that country and zone fields are often filled in automatically by a lookup against a prefix list. That works until you hit an exception, such as a station operating from a different entity than its callsign suggests, a special event call, or a DXpedition. Anything unusual deserves a manual check. Compare the entity in your log with what the operator actually signed or what the DXpedition's own page says.

For Challenge, I'd separate 'worked' from 'confirmed' clearly. Keep a status field per QSO (not confirmed, LoTW, card, or other) so you can filter easily. Otherwise you end up guessing what's missing when you want to push for the next 100 points.

  • Moderators

One thing I'd add is to read the actual award rules again before applying, even if you did it the last time. Programs update their rules, entity lists change, and application procedures move online. What counted two years ago may not match what the administrator wants now. I wouldn't trust anything on a forum, mine included, over the current official rules page.

For the TQSL problem, my approach would be to set up a separate station location for every distinct operating situation (home, each portable site, each different callsign) and give each a clear name. Never reuse one location and edit it afterwards. Before you sign and upload a batch, check that the location shown matches where the QSOs were made. If something is off, fix it before uploading, because trying to undo a bad upload is much harder.

Also keep in mind that not every award recognises every mode or band. WAS and DXCC have mode categories, and some programs treat digital modes differently from phone or CW. If you're chasing a specific endorsement, check that the mode in your log maps to the category you want. A QSO logged as one digital mode might not match a counterpart logged as another in LoTW, and that can look like a missing confirmation when the real issue is mode matching.

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.