Tracking award credits across DXCC, WAS, WAZ, WPX, IOTA, POTA and SOTA: how do you keep it all straight?
- Replies 2
- Views 23
- Created
- Last Reply
Top Posters In This Topic
-
Admin_Terry 1 post
-
Mod_Chrissy 1 post
Chasing several awards at once gets messy fast, because the programs define a "credit" differently. A single QSO can count toward a DXCC entity, a CQ zone, a WPX prefix, an IOTA group and a POTA park, and each sponsor wants its own kind of proof. I'd like to compare notes on how people organize this. Please check current rules with each sponsor, since details and fees change.
Here are the distinctions that trip people up most often:
DXCC (ARRL). Credit is by entity, not by country in the everyday sense. The basic award starts at 100 entities, with mode and band endorsements on top, and 5BDXCC is its own track. Deleted entities count toward standard DXCC totals if the QSO was made while the entity was valid, but they do not count toward the Honor Roll or the Challenge. The Honor Roll is based on current entities only. The Challenge is a band-entity point total across the HF bands plus 6 m. That makes a confirmed deleted-entity contact valuable for your base total and worthless for the higher-tier goals.
WAS and WAC. These are simpler in concept, but the details still matter. For WAS, the station you worked has to actually be operating from the state you are claiming, so check the location in the QSO record. For WAC, you need all six continents, and the confirmation just has to match on the basics.
WAZ and WPX (CQ). WAZ counts the 40 CQ zones, which do not map neatly to DXCC entities. Several large entities span more than one zone, so your DXCC log can mislead you about zones. WPX counts callsign prefixes, so a special-event or unusual prefix can add a credit that no entity list would suggest.
IOTA, CQ DX Marathon, POTA and SOTA. IOTA depends on the island group reference, such as EU-005, and the program has its own checking and credit process, so confirm which confirmation types it accepts. The CQ DX Marathon scores entities and zones worked within the calendar year, so only contacts made in that year count. POTA and SOTA are largely database-driven. Activators upload logs and hunters or chasers get credit from matched records, so a paper QSL is generally not the point. Activation thresholds differ, and SOTA's points are tied to the summit.
On LoTW, two things catch people out. First, a confirmation only appears when both stations have uploaded matching QSOs and the band, mode and time agree within the tolerance. Second, the other station's certificate location decides which entity and zone the QSO is tied to. If a DXpedition or portable operator uses the wrong location, or a QSO falls outside the entity's valid dates, the credit may not appear or may not be what you expected.
Questions for the group:
1. What do you use as your master log: LoTW, Club Log, a desktop logger, or a spreadsheet? How do you reconcile them?
2. How do you handle deleted entities and entities whose validity depends on the QSO date?
3. When a contact is unconfirmed, what is your routine for chasing it: a direct card, the bureau, or just waiting for an upload?
4. Do you pursue the Honor Roll and Challenge separately from the lower DXCC endorsements, or do you treat them all as one list?
Link to comment
https://www.hamradiobase.com/forums/topic/11583-tracking-award-credits-across-dxcc-was-waz-wpx-iota-pota-and-sota-how-do-you-keep-it-all-straight/Share on other sites