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

Confirming contacts in 2024-style workflow: LoTW first, then bureau, direct, and Club Log OQRS for the rest?

ci_cover.jpg

I'd like to compare notes on a sensible order of operations for confirming contacts. The tools overlap a lot (LoTW, eQSL, QRZ logbook, Club Log OQRS, bureau, direct cards), and it's easy to spend effort on the wrong one for your goal.

Here's a rough framework to argue with.

1. Decide what the confirmation is for. If you're chasing DXCC, LoTW is the main digital route because ARRL accepts it for DXCC credit. eQSL and QRZ logbook confirmations are fine for personal tracking and for some other awards, but they don't count toward DXCC. If you only want a wall of cards or a nice record of contacts, paper and eQSL make more sense.

2. Get LoTW working properly. You install TQSL, request a callsign certificate, and wait for the verification step, which can take a while depending on how your identity and license are checked. Once the certificate is installed, back it up as a .p12 file somewhere other than the shack PC. Then sign and upload your ADIF or log through TQSL. A match only happens when both stations upload, and the QSO details have to line up on band, mode and time (the time window is about 30 minutes). A common cause of missing matches is a wrong mode or a logging program sending the wrong station location or DXCC entity.

3. Use the other online logs as extras. eQSL and QRZ logbook confirmations need the other station to also use that service. Club Log is useful in two ways: it tracks your DXCC status from uploads and LoTW matches, and its OQRS lets you request a card from DX stations that have enabled it. The operator or QSL manager sets the terms, so read what they ask for before you submit.

4. Bureau versus direct. The bureau is cheap but slow, and it can take months or longer for cards to arrive, so it suits non-urgent cards. Direct is faster but costs more: usually your card, a self-addressed envelope, and postage. For many DX stations that means a SASE plus return postage, often in the form of US dollars ("green stamps") when the station asks for them. Check the station's QRZ page or QSL info, because requirements differ and some operators prefer not to receive cash. Don't put a callsign on the outside of the envelope if the operator asks you not to.

5. If you design cards, make them easy to process. Put the other station's callsign and your contact details where they're easy to find. A standard card is about 9 x 14 cm (roughly 3.5 x 5.5 in). Include UTC date and time, band or frequency, mode, RST, and a clear "2-way" or "PSE/TNX QSL" box. Leave room for a QSL manager note and grid square if you want them. Keep your own callsign large and avoid dark backgrounds that make the QSO table hard to read.

What order do you use for confirmations, and what has worked for tracking which QSOs are still outstanding?

  • Replies 2
  • Views 23
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

One thing I'd add to the LoTW point: make the log clean before you upload, not after. If the time, band or mode are slightly off, the other station's upload won't match and it looks like they never uploaded. Check that your TQSL station location has the right DXCC entity, grid, and CQ/ITU zones too, especially if you operate portable or from more than one location. Each station location needs its own setup and should be signed with the right certificate.

For DXCC, remember that LoTW is only part of the picture. Some people still keep paper cards for older contacts, and those have to go through the ARRL's card-checking process. For anything you plan to submit, make sure the card actually shows what's needed: callsign, date, band or mode, and a legible entity. A very decorative card that hides these details is a poor confirmation.

  • Moderators

I'd treat bureau and direct as two separate queues. If a station is only a casual contact, let it ride via the bureau and don't pay for postage. If it's a rare entity or a short operation you may not get another chance at, a direct request via OQRS or a mailed card with SASE makes sense. Always check the QSL route before you send anything. Many DXpeditions publish a manager, an OQRS link, and sometimes a LoTW upload promise, and the fastest path may be just to wait for the LoTW upload rather than mail a card.

For direct requests, keep the envelope plain and the instructions short. Include a properly filled card, return envelope, and the postage the station asked for, with no extra notes. If the station says it uses OQRS only, follow that. Mailing a card to a manager who only accepts online requests usually just slows things down. And log the date you sent each request so you know when to follow up instead of guessing.

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.