give me an example? A qso has been confirmed , submitted and verified, and now doesnt show, or the opposite, LOTW thinks and entity has been verified, but hasnt? last I looked ( a few weeks ago) my LOTW records, dxcc records, and my dxkeeper records all matched, I can look again, if I know what I am looking for.
toggle quoted message
Show quoted text
------ Original Message ------
From "Dave AA6YQ" <aa6yq@...>
To
[email protected]Date 3/30/2025 11:19:09 AM
Subject Re: [DXLab] Verified vs Confirmed on LoTW
The problem reported in this thread is not "user confusion over terminology", as implied by the post below. The problem is that LoTW has begun misreporting "DXCC Credit" status for some QSOs confirmed via LoTW and submitted for DXCC credit.
73,
Dave, AA6YQ
Not so complicated:
Confirmed QSOs
* A confirmed QSO means that both parties (you and the other operator) have uploaded matching logs to LoTW.
* The system checks the date, time, frequency, and mode, and if they match within certain tolerances, it confirms the QSO.
* This is what counts toward award credit (e.g., DXCC, WAS, VUCC).
So:
Confirmed = Matched and valid in LoTW = Counts for awards.
________________________________
? Verified QSOs
* A verified QSO is typically one that has already been used for award credit, such as a confirmed QSO you've applied toward your DXCC or WAS certificate.
* It’s like a step beyond "confirmed" — it's confirmed and officially credited in your award application.
So:
Verified = Confirmed + Used for award credit (and accepted).
