SQLite database (.sqlite/.db/.hrd), HRD XML backup (.xml), or ADIF export (.adi) — format auto-detected. The report is computed entirely from this file's evidence.
The DXCC_QSLs_….adi download — every credit in your DXCC record, including card-era ones LoTW never verified. Collapsed to one QSO per entity per award, then applied on top of the log to show what your totals would become.
Your lotwreport.adi download. Applied on top of the loaded log without changing it, so the report shows what your totals would become after importing it — and which credits it would add.
The LoTW Account Credits pages printed to PDF, one per award. These name the callsign the ARRL credited for each entity, so the deduplicated file keeps the QSO the ARRL actually used rather than guessing. Drop as many as you have.
Paste the LoTW Account Status table (select the page, copy, paste). Adds LoTW's awarded counts and a Δ column so discrepancies are explicit per award.
Entity status comes from the built-in Countries001 table (402 entities, 340 current, 62 deleted, dated 16-Jan-2026). The DXCC QSL file and the log's own country names are used only as cross-checks — those names are a snapshot from logging time and miss entities deleted since. Manual codes are always honoured.
Columns mirror HRD's Award Tracking exactly: Confirmed splits into Granted, Submitted (applied for, not yet granted) and Not submitted. The last five columns come from the LoTW Account Status paste and show the derivation in full: Total less New LoTW QSLs (no application made) and LoTW QSLs in Process (applied for, not yet granted) gives LoTW Awarded — the credits the ARRL has actually granted. Δ is HRD Granted less that figure; zero means the log is in step with the ARRL. Click a non-zero Δ to list the entities behind it. Credits are granted only through a DXCC application — importing a file records credits the ARRL has already issued, it never confers them. Projected Granted and Projected Δ are a dry-run only — nothing is written to the log — showing what Granted becomes after importing lotwreport.adi followed by the missing-credits delta file below. Projected Granted is current Granted plus lotwreport credits a real HRD import will apply plus missing-credits-file credits that are importable today (a matching QSO exists in the log and HRD recognises the token). Where Projected Δ is nonzero, the note above decomposes the residual — vocabulary-blocked VHF+ credits awaiting an HRD update, credits whose QSO must be added to the log first, and records needing manual date reconciliation — so it is explicit why zero is not reachable today and what unblocks each piece. The optional Verified-only column counts entities whose credit came through LoTW verification — a diagnostic, not an HRD figure. Click an award name for the entity-level drill-down.
| Award | Worked | Confirmed | Need QSL | Entities Needed | Not submitted | Submitted | Granted | LoTW Total (Current) | New LoTW QSLs | LoTW QSLs in Process | LoTW Awarded (Current) | Δ | Projected Granted | Projected Δ |
|---|
Every case where the log grants a credit that the current DXCC QSL Download does not confirm for that callsign — checked directly against the QSL Download's own record for the same call, not inferred. Two patterns: remapped means the log has the QSO assigned to a different DXCC entity than ARRL's own record names for that call (a log-side correction — e.g. a rare-prefix callsign resolved to the wrong island group); unlisted means the callsign does not appear in the QSL Download under any entity at all, so there is nothing ARRL-side yet to reconcile against. These are exactly the entities behind a Δ or Projected Δ that importing a file can never close, since an import can't move a QSO to a different entity — only correcting the log's own DXCC field can. Read-only: nothing here is changed automatically. Requires the DXCC QSL file (step 2).
| Award | Callsign | Band | Log says | ARRL QSL Download says |
|---|
Every credit the ARRL lists in the award PDFs that your log does not currently hold, with the reason. These are precisely what the deduplicated DXCC QSL file below would supply. Requires a log (step 1) and the award PDFs (step 4); the DXCC QSL file (step 2) improves entity resolution.
| Award | Entity | Country | Credited call | Why it is missing | Import fixes it? |
|---|
A lotwreport credit only counts as delivered when the record carrying it will actually match on import — checked per record against HRD's matcher behaviour (±30-minute window, mode grouping, and tokens its importer recognises; validated against HRD's own import log) — with the DXCC QSL Download supplying the rest. This builds the second half only: credits that lotwreport does not deliver and — when a log is loaded — that the log does not already hold on some QSO. Each record is anchored to the matching QSO in your own log — its time, band, and mode — so HRD's LoTW import (call + band + mode group, ±30 minutes, update-only) will actually apply it; the ARRL-named callsign still decides which QSO holds the credit. Credits whose QSO is missing from the log or logged under a different date are listed instead of being emitted uselessly, and VHF+ credits HRD's vocabulary cannot store yet are counted separately — they ride along in the file so re-importing it after an HRD update applies them. Import lotwreport.adi first, then this file. Nothing is written twice, so no credit ends up flagged on two QSOs. Requires the DXCC QSL file (step 2) and lotwreport (step 3).
| Award | Entity | Country | Offered | Kept | Chosen because | Discarded |
|---|
Only one QSO can hold a given award slot, so where two or more carry the granted flag for the same entity and award, the extras are redundant. Report totals are unaffected — entities are counted distinctly — but the drill-down lists show more rows than credits, and surplus flags can carry into applications and exports. Keep the QSO that LoTW credits, clear the flag from the others, and where the extra row is a duplicate QSO consider deleting the QSO itself.
| Award | Entity | Country | Flags | QSOs carrying the flag | Pattern |
|---|
Every entity relevant to this award, with the evidence found. Diagnostic reading: CONF without a granted chip means confirmed-but-uncredited; V without TOKEN means Verified status with no credit token (or vice versa) — a signature of which import path wrote the data.
| Entity | Country | QSOs | Evidence | Best QSO |
|---|