Getting Started with Leaderboard Award Tracking
In a traditional Leaderboard competition, the objective is to work a particular target callsign -- often a DXPedition -- in as many slots as possible, where a slot is a band-mode combination. Considering all of the bands between 160m and 2m except 60m, and considering the CW, Phone, and Digital modes, there are a total of 33 possible slots. Many DXPeditions host their leaderboard competitions on Club Log.
There are variations:
not all target callsigns are QRV on all 11 bands, or in all 3 modes
sometimes the objective is to work a target callsign on each of 11 bands
sometimes the objective is to work a target callsign in each of 3 modes
To pursue a callsign on multiple bands, in multiple mode, or multiple band-modes, add its callsign to the Special Callsign List with a Leaderboard tag, as described in the step-by-step instructions below. A callsign present on SpotCollector's Special Callsign List with a Leaderboard tag is referred to as a leaderboard callsign.
The determination of whether a leaderboard callsign is unworked is made by searching the current log in DXKeeper for QSOs with that callsign made after 1900-01-01. You can change this Leaderboard Start Date by typing a new date in YYYY-MM-HH format in the Start Date text box in the Leaderboard panel on the Configuration window's Special Callsigns tab. If the date you type is invalid, it will be displayed in red font.
Checkboxes in the Leaderboard panel on the Configuration window's Special Callsigns tab enable you to specify whether leaderboard callsigns should be pursued on all bands, and/or in all modes, and/or in all band-modes.
If the Unworked bands are needed box is checked, Spot Database Entries for leaderboard callsigns that are unworked on the Entry's band (160m, 80m, 40m, 30m, 20m, 17m, 15m, 12m, 10m, 6m, 2m) after the Leaderboard Start Date will be considered needed; the letter J will be inserted into the Entry's Need field.
If the Unworked modes are needed box is checked, Spot Database Entries for leaderboard callsigns that are unworked on the Entry's mode (SSB, CW, digital, user-specified digital mode family) after the Leaderboard Start Date will be considered needed; the letter K will be inserted into the Entry's Need field.
If the Unworked band-modes are needed box is checked, Spot Database Entries for leaderboard callsigns that are unworked on the Entry's band-mode combination (160m, 80m, 40m, 30m, 20m, 17m, 15m, 12m, 10m, 6m, 2m)- (SSB, CW, digital, user-specified digital mode family) after the Leaderboard Start Date will be considered needed; the letter L will be inserted into the Entry's Need field.
If you specify and enable a User-specified digital mode family in the DXCC Bands & Modes panel on DXKeeper's Configuration window's Awards tab, then the Unworked modes are needed and Unworked band-modes are needed objectives - if enabled - are extended to include working each leaderboard callsign in that user-specified digital mode family and on each band in that user-specified digital mode family, respectively.
If you'll be participating in Leaderboard competitions, then on the Audio tab of SpotCollector's Configuration window, check the Announce special callsigns box in the Audio Alarm panel .
To pursue a specific callsign in a Leaderboard competition, add that callsign to SpotCollector's Special Callsign List with the tag Leaderboard by following these steps:
select the Special Callsigns tab of SpotCollector's Configuration window
in the Special Callsign List panel,
if necessary, scroll the Special Callsign List so that its last row is visible; this row contains an asterisk in its left-most column
type the callsign into the Callsign column of the last row of the Special Callsign List; this will create a new row with a pencil icon in it's left-most column
type Leaderboard into the Tag List column of the newly-created row of the Special Callsign List
strike the Enter key
Post a question or suggestion on the DXLab Discussion Group
Getting Started with DX Information
Getting Started with Spot Collection, Active DX Identification, and Analytics