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

Building a QSL workflow: LoTW, eQSL, Club Log OQRS, bureau and direct cards, and what actually counts for DXCC

ci_cover.jpg

I'd like to compare notes on how people structure confirmations now that there are so many options. Between Logbook of The World, eQSL, the QRZ logbook, Club Log OQRS, the bureau and direct cards, it's easy to spend effort in the wrong place. Here is a framework to react to, and corrections are welcome.

1. Know which confirmations count for what. LoTW is run by ARRL, and its confirmations can be applied to DXCC and several other ARRL awards. eQSL and QRZ logbook confirmations are fine for personal records and some other awards, but ARRL does not accept them for DXCC. Paper QSL cards can still be used for DXCC, but they have to be checked through the ARRL's card-checking process, so they take more effort than LoTW. Before you chase a confirmation, decide whether you want it for an award, for the wall, or just to close the loop with the other operator.

2. LoTW setup is the hurdle for most people. You install TQSL, request a callsign certificate, and complete the verification step. For US stations that has traditionally been a postcard mailed to the address on file with the FCC. Once you have the certificate, you sign your log with TQSL and upload the result. A match only happens when both stations have uploaded and the QSOs agree on callsign, band and mode, with the time within the allowed window. Time zone mistakes are a common cause of non-matches. Log everything in UTC, and check that your station location in TQSL (DXCC entity, grid, CQ and ITU zones) is correct for where you were operating. If you operate portable or from a different entity, you need a separate station location and often a separate certificate.

3. Modes can trip up matching. FT8, FT4 and similar digital modes are generally grouped as DATA for award purposes, but make sure your logging software exports them in a form TQSL understands. If a contact doesn't match and both sides uploaded, compare band, mode and time before assuming the other station hasn't uploaded.

4. Club Log and OQRS. Many DXpeditions and DX stations use Club Log's Online QSL Request Service. You upload your log to Club Log, find the contact, and ask for a card, usually by bureau or by direct mail. Direct requests normally involve a fee or postage contribution, and each operation sets its own terms, so read the instructions on the page. Many of these operations also upload to LoTW, which is quicker and cheaper if you only need the credit.

5. Bureau versus direct. The bureau is the low-cost route. Cards travel in bulk through national societies, so it can take many months or longer, and not every country or station is equally well served. Direct is faster and more reliable, but you pay for it. Typical practice is to send your card in an envelope with a self-addressed return envelope (SASE) and enough return postage. For DX, that has often meant US dollar bills ('green stamps') because international reply coupons are no longer practical for many people. Check the operator's QRZ page for what they currently want. Don't write your callsign or 'QSL' on the outside of the envelope in countries where that might attract attention, and put the card in an opaque inner sleeve or lining.

6. Designing a card that gets processed. A card should be readable at a glance. Put the other station's callsign, UTC date and time, band or frequency, mode and signal report on the back where they are easy to find. Put your own call large on the front. Add your grid square, CQ and ITU zones, and any special event or club info if relevant. A good photo or a clean graphic looks nice, but the data matters more than the artwork. The usual size is about 3.5 by 5.5 inches (89 by 140 mm), which fits bureau handling.

7. Timelines I'd plan around. LoTW can confirm within hours or days if both parties upload promptly, but it can also stall for years if the other side never signs up. eQSL depends on both parties using it. Direct cards often take a few weeks to a few months, depending on postal routes and how quickly the operator handles requests. Bureau cards can take a very long time. I'd treat anything under a year as a pleasant surprise rather than an expectation.

So what does your workflow look like? Do you upload to every service as a default, or only to LoTW and Club Log? Do you still send cards for new entities even when they show up on LoTW? And what are the most useful details you put on a card to avoid mismatches?

  • Replies 2
  • Views 15
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Administrators

For me the main rule is to log once and export many times. Keep a single master log in your logging program, then upload from that to LoTW, Club Log, and anything else you choose to use. That way you're not fixing the same typo in four places. Do a periodic check of the data too. A wrong band, an incorrect grid, or a time entered in local rather than UTC will quietly produce non-matches for months before anyone notices.

On DXCC, the practical approach is to use LoTW as the default and keep paper cards for the entities where LoTW isn't available. Check the current ARRL DXCC rules before you submit paper cards, because requirements for card checking and for what's accepted can change. Also keep your certificate backup (the .p12 file) somewhere safe. Losing it when you change computers is a nuisance, and it's not that hard to avoid.

  • Moderators

One thing I'd add about direct cards is to make the return envelope easy for the other operator. A SASE should be addressed clearly, with the right postage for the destination country, and the card should be filled out in advance with the QSO details. If you request via Club Log OQRS, follow exactly what the system tells you rather than guessing, because some operators ask for payment in a specific way and some route everything through a manager.

Also, don't underestimate the value of a short, clean card. If someone is processing a large number of requests, a card with clear UTC time, band, mode and call is easy to match to the log. A very decorative card with tiny writing slows them down. Pretty is nice, but readable data is what gets your reply sent back sooner. And if the station says 'LoTW only' on their page, believe them and save the stamps.

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.