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

Tracking award credits across DXCC, WAZ, WPX, IOTA, POTA and SOTA: how are you keeping the records straight?

ci_cover.jpg

Chasing several awards at once gets messy fast. DXCC, WAS, WAC, WAZ and WPX all lean heavily on confirmations, and the rules differ in small but important ways. IOTA, CQ DX Marathon, POTA and SOTA each run on their own logic and databases. I'd like to compare how people keep it all organized without double work or surprise rejections.

Here are the points that seem to cause the most confusion.

1. Current versus deleted entities. For basic DXCC, deleted entities still count toward your total if they were valid when you worked them and you have the confirmation. The Honor Roll and the Challenge work differently. They are based on current entities, so a deleted entity doesn't help you there. If you're tracking your own progress in a spreadsheet or logging program, keep current and deleted counts separate so the numbers match what ARRL reports.

2. LoTW and entity assignment. A LoTW match only works if both logs agree on the essentials: date and time within the tolerance, band, mode and callsign. DXCC credit also depends on the entity being resolved correctly for the date of the contact. Mismatches usually come from wrong location data in the uploaded log, a bad prefix assumption, or a station that moved between entities. The fix is usually correcting the entity in your own log before you upload.

3. Different awards, different confirmation rules. WAS, WAC and DXCC are ARRL programs. WAZ and WPX are CQ programs, and IOTA is run by the RSGB. They don't all accept the same mix of LoTW, paper QSL cards and other electronic confirmations. Read the current rules for each program before you assume a confirmation you already hold will carry over. Rules and accepted sources do change.

4. POTA and SOTA are a different kind of chase. Neither is built around exchanging QSL cards. POTA hunter credit depends on the activator submitting a log that includes your contact, and a valid activation needs a minimum number of QSOs. SOTA has separate activator and chaser records, and the points depend on the summit and the logs submitted to the database. If a contact is missing, the first thing to check is whether the other station uploaded their log and whether your callsign was copied correctly.

5. Marathon-style scoring. The CQ DX Marathon counts entities and CQ zones for a single calendar year. Zone assignments matter as much as entity counts, so a station operating from a place that spans or borders zones needs checking.

Questions for everyone:

  • Do you keep a master log and sync it to LoTW, or maintain separate files per award?
  • How do you decide when a paper QSL is worth chasing instead of waiting for LoTW?
  • Has anyone found a good way to flag contacts whose entity or zone looks questionable before applying?
  • Replies 2
  • Views 25
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Administrators

A single master log is the least painful approach, with award tracking done as reports from that log rather than as separate files. The reason is that most credit problems come from inconsistent data. If the entity, CQ zone, ITU zone, state or grid is wrong in one copy and right in another, you end up chasing phantom problems.

A few habits that help:

Make sure the cty or entity data file in your logging program is current before you import contacts. Prefix rules and entity boundaries change, and old data can assign a contact to the wrong entity or zone. Be especially careful with special event calls, DXpeditions that operate from several locations, and stations with portable or maritime mobile suffixes.

Treat the DXCC, WAZ and WPX fields differently. DXCC and WAZ depend on where the station was operating, while WPX depends on the prefix actually used in the callsign. A single QSO can be right for one award and a problem for another.

For paper QSLs, a reasonable rule is to chase them when an entity or band slot is unlikely to appear on LoTW soon. That includes operators who aren't LoTW users and DXpeditions that don't upload quickly. Check whether the operation has a QSL manager or an online request system, and keep your request records, because replies can take a long time.

Before submitting any application, run a duplicate-and-mismatch check. Look for contacts whose callsign appears in more than one entity, or whose entity is marked deleted. Those are the lines most likely to cause trouble.

  • Moderators

On POTA and SOTA, it helps to think of them as database-driven awards rather than confirmation-driven ones. The usual problem isn't a missing QSL card. It's a mismatch between what you logged and what the activator logged.

For POTA, if a contact doesn't show up in your hunter record, first check whether the activator has submitted the log yet, since uploads can lag behind the operation. Then check your own copy of their callsign and the park reference. A busted call on either side can leave the contact orphaned. If you keep your own log, record the park reference in the right field so it's easy to reconcile later.

For SOTA, the activator needs enough contacts for the summit to count, and chaser points are tied to the logs the activator submits. Keep the summit reference, date and band in your records. Check the current association rules for the exact scoring and minimums, since they are updated from time to time.

The mental split that helps me explain it to newcomers: DXCC, WAS, WAC, WAZ and WPX ask you to prove your contact, usually with LoTW or a QSL. POTA and SOTA mostly ask the other station's submitted log to prove it, and your task is making sure your contact is easy to match.

For IOTA, check the group reference list and the program's current confirmation rules before counting a contact. A station on an island doesn't always belong to the reference you'd expect, so verify the group before you plan around it.

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.