What the Cabrillo checker validates
The checker requires START-OF-LOG first and END-OF-LOG last; inventories common V3 header tags; checks singleton fields, supported category values, callsign and contest shapes, claimed score, QSO frequency or band, mode, UTC date and minute, callsigns, chronological order, transmitter IDs, and the selected exchange template. Cabrillo V2 remains readable but is marked deprecated.
Contest templates and duplicate review
Automatic selection recognizes CQ WW/WPX-style RST exchanges, ARRL Field Day class/section, ARRL Sweepstakes serial/precedence/check/section, and common VHF grid exchanges; a generic RST-plus-exchange template is the fallback. Probable duplicates match worked call, derived band, and mode. They remain in output because actual duplicate and multiplier rules belong to the specific contest.
ADIF conversion without silent guesses
The converter reuses ToolQuill’s bounded ADI/ADX parser, maps supported modes and bands, and requires evidence for UTC date/time, station and worked callsigns, plus exactly the exchange fields selected by the template. Records without enough evidence are listed as omitted. A provided sent exchange is explicit user input—not inferred contest truth. Converted output contains only a minimal V3 header and QSO rows; add and verify all sponsor-required categories and entrant details before submission.
Validation boundary
A clean report is not proof of a valid contest entry or contact. This tool does not score QSOs, verify callsigns, check operating periods or band plans, resolve multipliers, query other logs, determine duplicates under organizer rules, validate every contest-specific exchange, sign or submit a log, or guarantee acceptance. Whitespace-normalized output preserves parsed values but should be tested as a copy.
Frequently asked questions
Why does the same station appear as a probable duplicate?
The review key uses worked call, band, and mode. Some contests allow repeat contacts by period, location, or another rule, so the checker never deletes them.
What does X-QSO mean?
Cabrillo marks X-QSO contacts to be ignored in the entrant’s log. They are inventoried separately and excluded from chronology and duplicate counts.
Why was an ADIF record omitted?
Its omission row lists the missing evidence. The converter refuses to invent a frequency, callsign, time, or template-specific exchange.
Authoritative references
The WWROF Cabrillo specification states that V2 is deprecated and V3 is current. Its V3 header reference defines required and common tags, while the QSO data reference defines frequency/band, modes, UTC fields, callsigns, and contest-defined exchanges. ADIF input follows the released ADIF 3.1.7 specification while ToolQuill’s converter discloses its bounded parser support.