LoTW New User Guide

Get going with Logbook of The World

Version 1.01

You may be wondering “Why does Logbook of The World exist?

What is it for?” and “Should I bother with it?”
The answer is simple.
LoTW makes confirming contacts easier,
quicker and cheaper than traditional QSL methods.
Follow this step-by-step guide to get started on LoTW.

Quick-start
If you simply can’t wait to get going, and provided
these two bullet points makes sense to you:
1. Download and install TQSL.
2. In TQSL, request a Callsign Certificate.
Then read on. This guide has step-by-step
instructions and tips on how to get going with LoTW.

Note: this guide is occasionally updated.

The definitive current English version is available at
www.G4iFB.com/LoTW_New_User_Guide.pdf
Please use and share that URL.
 LoTW New User Guide

Logbook of The World

New User Guide

Contents
1 Introduction .............................................................................................................................. 2
2 Generating an electronic log ...................................................................................................... 7
3 Applying for your first Callsign Certificate .................................................................................. 8
4 Using LoTW ............................................................................................................................. 14
5 Applying for awards through LoTW .......................................................................................... 21
6 Troubleshooting ...................................................................................................................... 22
7 Further reading ........................................................................................................................ 27
Appendix: TQSL updates ................................................................................................................. 28
Appendix: Renewing a Callsign Certificate ....................................................................................... 29
Appendix: Backups ......................................................................................................................... 32

Document history
Version 2020 Changes made
1.01 17th Sept Yet more minor corrections (thanks Jim W2JC).
1 12th Sept Final corrections, plus notes about automating LoTW uploads. Ready to publish!
Added warning about not installing TQSL with privileges. Numerous corrections
0.8 11th Sept
(thanks Bob AK5U). Flow chart boxes linked to steps (thanks Jim W2JC).
Added links to help on logging software LoTW functions; “Quick Start Guide”
0.7 8th Sept
retitled “New User Guide” … but file name and URL not yet updated
0.6 7th Sept Added info about non-US hams’ license validation step
0.5 4th Sept Expanded chapter 4 on downloading LoTW confirmations
0.4 1st Sept Added info about postcard/FCC address validation code for US hams
0.3 30th Aug Transferred into MS Word to work on the formatting, diagrams, details and tips
Various additions & changes discussed & made by a team of collaborators and
0.2 July-Aug
commentators from the ARRL LoTW Forum
0.1 19th July First skeleton draft roughed out in Google Docs by ZL2iFB to launch the project

I’m grateful to members of the ARRL LoTW reflector for their inspiration and assistance in preparing
this guide, including: Antony K8ZT, Bart W9JJ, Bob AK5U, Chuck NC8Q, Dave AA6YQ, Ed KG4W,
Geoffrey KA1IOR, George K1IG, Gordon N0AB, Greg K0GW, Jerry K7UPJ, Jerry KB2GCG, Jim N6VH, Jim
W2JC, Joe W4TV, Jordi EA3JCV, Julio W4HY, Mike K1MK, Rick EA4M, Rick K1MU, Steve NS4P, Tim
N3QE, Wes N5WA, William KN4UNG … and others. Thanks friends! 73, Gary ZL2iFB

Copyright © 2020 ZL2iFB Page |1

 LoTW New User Guide

1 Introduction
Logbook of The World provides a reliable
means of validating and confirming QSOs.
The system is trusted by over 100,000 radio
amateurs from all parts of the globe ►. Part
of the reason that awards such as DXCC
remain popular is that they are widely
acknowledged as genuine, meaningful
achievements. Things are deliberately made
tough for cheaters and fraudsters so that
honest DXers can continue to trust the
awards.
After following a link, use Alt-left arrow to go back.
1.1 LoTW glossary On a Mac, try Command-left arrow. Good luck.
Term Meaning
A digital (electronic) file, issued by ARRL after they have checked that you are, in
Callsign Certificate
fact, the licensee for a properly-issued amateur callsign.
Both parties agree that they made a QSO at a given date and time, on a particular
Confirmed
band and mode.
Computer data gets sent ‘down’ from a server, such as the LoTW computer at
Download
ARRL, through the Internet to our computer.
ARRL’s prestigious DX Century Club award for confirmed QSOs with at least 100
DXCC
of the 340 recognised ‘entities’ (mostly countries).
Icon A distinctive little cartoon-like image, such as for a usable Callsign Certificate.
Log A set of QSO records, often in date and time order.
Logbook of The World – an ARRL computer system running a database
LoTW
application, plus the associated data and procedures.
Two QSO records ‘match’ if the pertinent details are identical or close enough to
Matching
indicate that both parties to the QSO consider it to have taken place.
A confirmation of a specified QSO in the form of a postcard or electronic record
QSL
stating the QSO record.
QSO A contact between two radio amateurs using the amateur bands.
Computer data about a contact with pertinent details (callsigns, date, time, band,
QSO record
mode etc.), similar to the information on a line of a traditional paper logbook.
As with a contract, when we “sign” a log of one or more QSO records before
uploading them, we are formally confirming that these QSOs took place according
Signing
to the QSO records. The electronic signature is a modern digital equivalent to a
wax seal on an important Mediaeval letter.

Copyright © 2020 ZL2iFB Page |2

 LoTW New User Guide

Term Meaning
Details about where the station is located such as the DXCC entity, state, province
Station Location
or oblast, county, Maidenhead grid square, CQ and ITU zones and IOTA reference.
An electronic log containing details of all the QSOs we have made, often under
Station log
several personal callsigns (e.g. novice/restricted and full licenses, contest calls).
The Trusted QSL program, used to manage Callsign Certificates and Station
TQSL
Locations, and sign and upload QSO records to LoTW.
Send computer data from our computer ‘up’ to a server, such as the LoTW
Upload
system, via the Internet.
An 8-character sequence mailed on a printed postcard to the registered FCC
Validation Code
addresses of US hams in order to confirm their license addresses.

NOTE: this simplified glossary complements the official LoTW glossary.

1.2 History
Logbook of The World (LoTW) was released by the American Radio Relay League (ARRL) on September
15th 2003. Writing for the ARRL’s QST journal in October 2003, Wayne Mills N7NG conjured up a vision:
“Imagine being able to submit evidence of a contact electronically, and have it count towards
awards. No muss, no fuss - just a simple procedure under a system that ensures the validity of
the QSO.” Right there at the outset, the fundamental objectives of LoTW were clear: it would provide a
simple way to ensure the validity of amateur radio contacts (QSOs) submitted for awards.

Figure from N7NG’s 2003 QST article

Copyright © 2020 ZL2iFB Page |3

 LoTW New User Guide

1.3 LoTW overview

Despite the name, Logbook of The World barely
qualifies as a logbook. It is a way to record only the
most basic information about the QSOs we make -
for example ►. The top section, Station, shows
information that LoTW has about me - my callsign,
DXCC entity, CQ and ITU zones, IOTA island reference
and my 6-character Maidenhead grid square. The
lower section, Worked Station, shows information
about a QSO I claim to have made with another ham.
I have told LoTW both our callsigns, the date and
time, the band and the frequencies on which I claim
to have made the QSO.
All of the information in that QSO record was
supplied by me. I generated and uploaded it … and I
may have made mistakes. I could even have made it
up. That’s why confirmations are so important.
Unless and until R2AL also uploads details of the same QSO, it is merely ‘Essentially the same’ does
a claim. If R2AL uploads something fundamentally different about the not mean ‘identical’. LoTW
QSO (e.g. if he claims that it was actually on 40m rather than 20m) then allows leeway on some of
LoTW would not accept the details, such as the time
that the QSO took place. and frequencies.
Only if our claims are
essentially the same does LoTW agree that we made the
QSO - in other words the QSO is confirmed.
◄ Here is the LoTW QSO record for a previous QSO with
R2AL. Vladimir has already uploaded his QSO record for
that QSO and the details match, so that QSO is confirmed
for both of us on LoTW. His DXCC entity, zones, grid
square and oblast are all shown - information that
Vladimir supplied in the QSO record he uploaded. He has
my QTH information as well – once a QSO is matched,
both parties have it.
A bit like those impressive awards and plaques on a DXer
or contester’s shack wall, digital certificates are
electronic proof of something. For LoTW, a Callsign
Certificate issued by ARRL proves that the person
claiming to be, say, “W1AW” really is the properly
licensed amateur holding that callsign. That’s important
because anyone could claim to be W1AW and claim to have W1AW’s definitive log. More likely, a pirate
or cheat might falsely claim to have the log for, say, “P5DX” hoping to confirm fake contacts with that
extremely rare DXCC entity.
Checking and verifying QSOs is the main purpose of LoTW. As with QSL cards, the aim is to provide
trustworthy evidence confirming or proving that logged QSOs really did take place as claimed between
duly licensed amateurs. The difference is that LoTW is all electronic, using digital data.

Copyright © 2020 ZL2iFB Page |4

 LoTW New User Guide

There’s more to this than piracy and fraud. Have you ever noticed someone getting your callsign wrong
during a QSO? With QRM and QSB, mistakes are common. That’s why we spell out callsigns phonetically
on voice modes, and repeat callsigns so often in QSOs on all modes. We also need to be careful to spot
and correct typing mistakes if we are logging electronically.
LoTW is designed to check the details from each party to a contact before confirming it. LoTW offers a
higher level of proof and security than other electronic QSL systems, sufficient to be used for awards such
as DXCC. Anyone could claim to have contacted more than a hundred countries: proving it takes more
effort!
These are the main controls associated with LoTW:
1. We must register with ARRL in order to submit our logs. The The way we demonstrate that
registration step involves proving that we are the properly we are properly licensed varies
licensed holders of our callsigns. between countries: US hams’
details are verified against the
2. Having registered, we are issued a Callsign Certificate that we
FCC’s records; non-US hams
will use to sign our log. Signing combines digital information
submit their license plus
from the Callsign Certificate with the logged QSOs in such a way
address information (such as a
that LoTW can confirm that:
utility bill) to ARRL HQ by post
(a) the log came from the holder of the callsign; and or send/take it to a local ARRL-
(b) the log was not altered after it was signed (e.g. by changing authorized DXCC card checker
or inserting false QSO details). to get it checked.

Under the covers, LoTW uses a Public Key Infrastructure based on a clever application of cryptography.
Applying certificates would be quite confusing for new users but most of the details are taken care of by
the software that we use - in particular, a program called TQSL (Trusted QSL). TQSL manages our Callsign
Certificates, signing and uploading logs, and requests for new or replacement Callsign Certificates. It
simplifies the process and hides the technical complexity for us.

1.4 Why should we use LoTW?

Prior to LoTW, confirmations were made using Other forms of QSLing are complementary, not
QSL cards - paper cards with written or printed alternatives, to LoTW. Some of us enjoy collecting
details of on-the-air radio contacts - that were exotic postcards from far-off lands as well as
sent by post, either directly from ham-to-ham or receiving electronic confirmations on LoTW. QSL
via QSL bureaus run by the radio societies. cards are worth showing to shack visitors or friends
Although QSL cards are still used by some, this is at the club, or pinning to maps on display boards
a slow, labor-intensive and relatively costly at special event and demonstration stations.
process. It generally takes months or years to
exchange QSL cards.
LoTW eliminates the need to exchange paper QSLs to confirm contacts. LoTW dramatically reduces the
effort, cost and time to receive confirmations. Many contacts made today will be confirmed in minutes
through LoTW. Cumbersome mailing and sorting systems are no longer required, and LoTW is free for all
licensed amateurs.

“When I returned to ham radio after >60 years of QRT, LoTW was one of the pleasant
surprises. For old folks like me, the chance to get confirmations very quickly is a real
blessing. Were it not for LoTW, I would never have made DXCC or WAS.” [W3UEC]

Copyright © 2020 ZL2iFB Page |5

 LoTW New User Guide

If you are a serious DXer, you know how frustrating it can be waiting for QSL cards to arrive to confirm
each new country. Whether you post your QSLs and cash direct, or just hope for cards to arrive via the
worldwide QSL bureau, collecting confirmations on paper can be tedious, not to mention expensive. Then
once you’ve got your tidy little stack of QSL cards and you wish to apply for awards such as DXCC or WAS,
you still need to get them checked and verified by the relevant organization.
Quite simply, LoTW makes the whole process quicker, easier, cheaper and more reliable.
It is worth using LoTW because:
• It is widely trusted by amateurs around the world
• It is free to upload your QSOs and download confirmations
• Confirmations from LoTW generally arrive within hours, days or weeks of the QSOs, rather than years
later for QSL cards sent via the bureau, and without the printing and postage costs
• Most of the process is automated: with the right software, your QSOs can be signed and uploaded in
the background as soon as they are logged
• Confirmed QSOs can be submitted by either LoTW simply checks and confirms that claimed
party for DXCC and other awards: even if you QSOs were genuine – no big deal, right? So why
are not chasing awards, the people you can’t LoTW use more basic security? The reason is
contact may be very grateful to have your that authentication is important. Would you be
QSOs confirmed so they can claim awards - happy if the LoTW confirmation of a QSO with, say,
especially if you are in a rare location or Heard Island was retracted because it was
making remarkable DX QSOs discovered the log had been faked or hacked?
• It’s quite a buzz to see ‘new ones’ appear in
the list of recently-confirmed QSOs, like this ▼ Those ticks against ‘TRISTAN DA CUNHA & GOUGH IS’
indicate that both I and
Nigel ZD9XF had uploaded
our QSO records to LoTW.
The LoTW system had
found two matches, and
noted that these now
confirmed QSOs counted
as a new country for me for the mixed, CW, Challenge, 30m and 17m DXCC awards. The confirmations
came through just a few days after the QSOs at essentially zero cost to both of us.
With LoTW, we upload our logs periodically to the ARRL’s LoTW website where they are entered into a
database system that cross-matches our QSO records against other uploaded logs generating electronic
confirmations for all QSOs that match. LoTW confirmations normally come through within days or weeks
as soon as both parties to a QSO upload their logs to LoTW, provided the QSO records match.
The LoTW system tracks our progress towards DXCC, VUCC, WAS and WPX awards and, when we are ready
to claim them, it handles the award applications electronically for us. For QSOs that have been verified in
LoTW, there is no need to hunt through our shoeboxes for the relevant QSL cards, fill out the application
form and submit the cards for verification. However, we may still choose to submit QSL cards for specific
DXCC countries or US states for those bands and modes which are not yet confirmed on LoTW ... or we
can wait patiently in the hope that eventually they will all be confirmed on LoTW. QSOs with all current
DXCC entities have been confirmed using LoTW.

Copyright © 2020 ZL2iFB Page |6

 LoTW New User Guide

2 Generating an electronic log

In order to use LoTW, you need an electronic record of your QSOs, specifically a log in ADIF or Cabrillo
format:
• Amateur Data Interchange Format (ADIF) lets us
send data about logged QSOs between
programs (e.g. between your logging software
and the LoTW system). It has records
comprising named fields for the pertinent
information about each QSO (e.g. dates, times,
bands, modes and callsigns)
• Cabrillo is a simpler columnar format, originally
designed for contest entrants to submit their
logs for adjudication. When viewed or printed,
a Cabrillo file resembles a physical logbook.
Some digital mode software such as WSJT-X
and JTDX, contest loggers such as N1MM+ and
WinTest, and portable loggers for SOTA etc.,
only provide basic QSO logging features … but
even these can usually generate and export
ADIF files. You can sign and upload those ADIF
files to LoTW using TQSL, or you can import the
ADIF into a full-function station logger first,
with the advantage of maintaining a complete
log of all your activities and the ability to
manage your QSL records, awards etc.

QSO details typed

into the log

◄ Most of us use logging programs to

generate and maintain electronic station logs.
QSOs logged in Logging programs can generate the ADIF or
another
program
Station Cabrillo files needed to upload our logs to
e.g. digimode
or contest
log LoTW.
Details about confirmed

software
You can probably type historical QSO
QSOs, awards etc.

details from old logbooks into your log.

ADIF or
Cabrillo files TQSL ◄ Full-featured logging programs can also
use confirmations downloaded from LoTW to
update our station logs, indicating which
logged QSOs have been confirmed, and
maintaining the statistics as we prepare to
LoTW apply for awards such as DXCC.

If you want to upload just a few QSOs from a paper log to

LoTW, you can type the QSO details into TQSL using the
Create an ADIF file for signing and uploading button ►.
Another option is the ARRL Basic Log 500 spreadsheet.

Fast Log Entry by DF3CB is a popular program for

typing-up old hand-written logs quickly and
efficiently, provided you can still read the scrawl …
and type!

Copyright © 2020 ZL2iFB Page |7

 LoTW New User Guide

3 Applying for your first Callsign Certificate

To join LoTW and obtain your first Callsign Certificate from ARRL, work your way systematically through

1
Download &
install TQSL

2
Run TQSL

TQSL
4a 4b
3
US hams Request a Non-US hams
Wait for Callsign
postcard to Certificate Submit license
arrive & ID for
validation
Enter
validation code Wait for Callsign
from postcard Certificate to
arrive by email

5
Load Callsign
Certificate

6
Define
Station
Location/s

7
Make a backup

the process using the step-by-step instructions that follow this clickable diagram:

Copyright © 2020 ZL2iFB Page |8

 LoTW New User Guide

1. Download the TrustedQSL program (TQSL). Pick the correct TQSL will even run on some
download for the operating system you are using i.e. Windows, ancient operating systems
MacOS/OS X, or Linux. Click or double-click the downloaded TQSL that are no longer supported
installer to install TQSL. by the original suppliers.

In Windows, do not use “Run as administrator” to run the installer. Administrative privileges are
unnecessary for the installation or use of TQSL.

2. Run TQSL e.g. by double-clicking the TQSL icon on your desktop.

3. Generate a Callsign Certificate

request:
• Click to open the Callsign
Certificate tab ►
• Click Request New Callsign
Certificate ►

Complete the information requested:

• Click to select the appropriate option –
most likely My current personal
callsign ►
• Click the Next > button ►

“I have dithered for years on installing LoTW. After having some initial
issues with the installation, I made two calls to ARRL. Now all is well;
the support I received from Newington was excellent!” [WU7X]

Copyright © 2020 ZL2iFB Page |9

 LoTW New User Guide

Complete the next form:

• Type in your callsign ►
• Click in the DXCC entity box to see the list of
countries: scroll down to find yours and click it
to select it ►
• In the same way, click, scroll down and click to
select the year, month and day for the Date of
the first QSO you made or will make using this
callsign. That is generally the ‘issued’ or ‘valid
from’ date stated on your license. ►
• Your license may also have an end date
(e.g. callsigns issued for special events, or novice
licenses that have been upgraded) but for
callsigns that remain current, leave the last QSO
date fields blank.
• Click Next > when you are ready to move on …
▲ You will not be able to sign and upload QSOs made before the first date or
after the second date (if any) with the Callsign Certificate you are now requesting.

Next form:
• Type your name and address ►
• Normally, this will be the address on
your license.
• For US hams, it must be the address
FCC holds for you.
• Click Next > when you are ready …

Click the Help button for

more information ►

US hams: does the FCC have your current station address, in fact?
Now is a good opportunity to check and update it if necessary, avoiding delays around step 4(a).

Copyright © 2020 ZL2iFB P a g e | 10

 LoTW New User Guide

Nearly done! Complete the final form:

• Type in Your e-mail address ►

• Click Finish to end the Callsign Certificate
request process:
• TQSL generates a digital message
and sends it via the Internet to ARRL
• Staff at ARRL check your license: if it
is all OK, they generate your Callsign
Certificate and email it to you

4. (a) US hams: wait for a postcard

sent to your station address
registered with the FCC. The
postcard has a Validation Code
printed just above your address ►
Follow the instructions printed on
the reverse of the postcard to enter
your Validation Code into the LoTW
postcard validation page (the
Validation Code shown here is just
an example and won’t work!).

4. (b) Non-US hams: get your license validated by:

• Scanning or photographing your license and identification information, then emailing it to ARRL
HQ; or
• Taking your license and ID in person to an ARRL-authorised DXCC card checker if there is one for
your country; or
• Airmailing a copy of your license and ID to ARRL HQ, preferably using registered post. The
information is sensitive and valuable, hence this is a last resort.

Copyright © 2020 ZL2iFB P a g e | 11

 LoTW New User Guide

5. Wait for your Callsign Certificate to arrive by email, then load the Callsign Certificate onto the same
computer you used to create the certificate request using TQSL.
• This may be as simple as double-
clicking the email attachment.
• If that doesn’t work, you may
need to save the attachment
first as a file on your computer
(the one on which you created
the certificate request), then
find that file and double-click it.
• If that still doesn’t work, you can
run TQSL, click to open the
Callsign Certificate tab ► then
select Load Callsign Certificate
from File and navigate to the file
you saved.
• TQSL electronically checks the Callsign Certificate, marries-up
the Callsign Certificate with the corresponding Callsign The email also provides your
Certificate request and, if it is all OK, enables the Callsign username and password to
Certificate for use. You are all set to use the Callsign Certificate login to LoTW. Go on, try it!
to sign your logs and upload them to LoTW (see next section).
6. Define one or more Station Locations. Station In this context, ‘station’ refers to the transmitter
Locations are needed because callsigns alone used to make contacts. If you use a remotely-
are seldom sufficient to know whereabouts a operated station, the Station Location is where
station is, especially within a large DXCC the transmitter is physically installed.
country.

• In TQSL, click Station Location on the top

menu, then click Add Station Location ►

You may not need the security of a password

to prevent someone else using your Callsign
Certificate to sign QSO records fraudulently. If
the risk is low, feel free to remove the
passwords from your Callsign Certificates in
TQSL using these instructions, making it a bit
easier and quicker to sign and upload your log.

Copyright © 2020 ZL2iFB P a g e | 12

 LoTW New User Guide

• Complete the form by selecting

from the drop-down lists and
entering the other details
requested ►

TQSL may suggest some values

but check them. Your Grid
square, ITU Zone, CQ Zone and (if
applicable) IOTA ID will be sent
with your QSOs to LoTW,
confirming them for the people
you contacted. If you are not
sure of the details, please look
them up or ask a friend.

• Allow ‘None’ for Call Sign lets you

define a Station Location from
which multiple callsigns may be used.
When you are signing QSOs made from that location, TQSL will ask which callsign you used in order
to select the correct Callsign Certificate (if indeed there is more than one).
7. Make a backup of your With a backup, simply by restoring the backup through TQSL you
Callsign Certificate and can recover lost information easily if, say, you get a new computer
Station Location/s using TQSL or the old one breaks down or picks up a virus. Without a backup,
– see the appendix. This step you’ll have to start the entire process again, from the top. …
is optional but highly
recommended.

“In short, consider TQSL to be putting your QSL card into the mail. You're
sending the QSO information out into the world to match a QSO by another
operator. That's the basic purpose of LoTW, which is to create QSLs which
can be applied to awards. TQSL gives you the way to put that card into ‘the
mail’ so LoTW can store it for QSL matches.” [K1MU]

Well done!
Having completed the most difficult part,
you are now all set to start using LoTW.
Trust me, the rest is easier and more fun.

Copyright © 2020 ZL2iFB P a g e | 13

 LoTW New User Guide

4 Using LoTW

4.1 Logging-in to LoTW

The email that delivered your first Callsign Certificate has the username and initial password you’ll need
to log-in to LoTW. Change the password to something memorable yet hard for anyone else to guess.

4.2 Signing and uploading your log to LoTW

Once you have obtained your Callsign Certificate, you are ready to start signing and uploading QSO records
from your log to LoTW. Here’s how …
2

TQSL LoTW
1 3

Log Sign Signed log

Callsign
Certificate

1. Export QSO records from your electronic log as Little and often works well. In future, export,
an ADIF or Cabrillo file. sign and upload only new QSOs, logged since the
2. Start TQSL. previous LoTW upload.
3. In TQSL, sign the log:
• Click the Sign log button If you have multiple callsigns, be
• Select the appropriate Callsign Certificate careful to export just the QSOs
made using a call for which you
• Select the correct Station Location have a Callsign Certificate, and be
• Click Next sure to select the correct Callsign
Certificate for the callsign and the
• TQSL uses your Callsign Certificate to generate a
Station Location from which QSOs
digital signature for the log, appends the signature to
were actually made.
the log, and then uploads it to LoTW via the Internet.
• Upon receiving the file, LoTW checks the Only new or changed QSO records are
digital signature to confirm that this is a imported into LoTW. Any exact duplicates of
legitimate upload, then imports the QSO QSO records previously imported are ignored.
records into the database.

Copyright © 2020 ZL2iFB P a g e | 14

 LoTW New User Guide

Upload new QSOs to LoTW as often as you can, ideally at
least once a month. If you are very active, upload new
QSOs more often and check your LoTW confirmations at
the same time. Uploading QSOs to LoTW is, in effect, an
off-site log backup but it only stores the essential QSO
details (date, time, call, mode, frequency/band). Other
QSO information (such as name, QTH, reports, notes etc.)
is callously discarded by the TQSL export and LoTW
import routines. See appendix.
When you upload a very large log file, you
may see a “Not Responding” alert at the top
of the window. If you click it, the window
will probably go gray and hazy. This is
normal! Your computer is busy processing
the upload, sending the file through the
Internet to LoTW. Just wait, patiently.
Don't go clicking around trying to ‘fix’ the
situation: you could cause problems.

If you have a huge log containing hundreds
of thousands of QSOs to upload (e.g. from a
major DXpedition or a lifetime’s log from an
active DXer or contester), you can simply
sign and upload it as usual. After uploading,
LoTW will process the log taking roughly an
hour to process each 100,000 QSOs.
However, if there are issues with the log
(e.g. QSOs with the wrong dates/times,
modes or bands), you would need to correct
then sign and upload the QSOs again, a
tedious process.
Tim N3QE suggests that, before you go ahead with a
huge log, it is better to upload a smaller batch first
(e.g. a thousand QSOs, preferably recent ones), then
check in LoTW how many of them have been confirmed
(you should expect something like five hundred
matches, roughly 50%). If you upload a thousand recent
QSOs and get zero matches, something is not right! If
the first batch goes to plan, continue uploading further
batches until you’re all done. The sequence doesn’t
matter but be sure to upload all the batches to avoid
leaving gaps in your log in LoTW.

4.3 Automatic signing-and-uploading

Some logging programs make updating LoTW seamless: as soon Disable the automatic LoTW
as a QSO is logged, the QSO details may be automatically updater during contests if the rules
exported, signed and uploaded to LoTW for you, in the prohibit the use of non-amateur
background. To find and configure such a function, browse the means to confirm contest QSOs
logging program’s menus, search the built-in help or ask for while the contest is still in progress.
assistance on the
See the further reading section.
program’s support forum.
Whether automated or not, the process may fail at several points in several ways, for example if the
appropriate Callsign Certificate or Station Location is not available, or if your Internet connection or the
LoTW system itself goes down at a critical point. How well the software deals with all possible failures
depends on its quality. Some logging programs identify and resolve such problems, recovering
automatically and notifying you only if there is something needing your attention. Others may simply fail,
perhaps silently … so, take care over the configuration and check that
your QSOs are, in fact, being received consistently by LoTW. Keep an
eye on the QSO record count in the top right corner of the LoTW screen
► and the date and time of the “Most recent QSO record” shown above
the form under the Your QSOs tab. For more detail, click the Your
Account tab then Your Activity on the left menu to check that recent
uploads have been received and processed correctly.

Copyright © 2020 ZL2iFB P a g e | 15

 LoTW New User Guide

4.4 QSO matching

The process of matching and confirming signed and uploaded QSO records is fully automated within the
LoTW system. Whenever an uploaded log is imported into the LoTW database, the system automatically
checks every QSO record for corresponding QSO records uploaded by the stations we have worked.

Logbook of
The World

▲ In this example, LoTW has Be patient, especially following major contests or when LoTW
imported a log uploaded by K8ZT. maintenance/upgrades occur. At busy times, you may need to
One of the K8ZT QSOs was with wait a few minutes, possibly as much as an hour or more, to see
N1UR, who has previously the first confirmations coming through. LoTW is not quite
uploaded his log to LoTW. LoTW instantaneous but it is much quicker than the weeks, months,
compares the QSO records. years or decades it can take to exchange QSL cards! If your
Provided there are no significant uploaded log isn’t processed as expected and no new
discrepancies, the QSO is now confirmations appear for some while (hours or days), check the
noted as confirmed for both K8ZT processing backlog on the Current LoTW status page.
and N1UR.
Now K8ZT and N1UR can use the confirmed QSO to apply for DXCC or other awards, just as if they had
exchanged QSL cards for the QSO … except the whole signing, uploading and matching process may have
taken place just minutes after the QSO, whereas QSL cards generally take weeks, months or years to
arrive, longer still for an authorized card-checker to determine by eye whether the cards and QSOs are
legitimate.

Copyright © 2020 ZL2iFB P a g e | 16

 LoTW New User Guide

4.5 Update your station log with confirmations received

Note: this is optional. You may not even have a station log to update! If you do, it is worth updating it
from time to time to record confirmations received through LoTW. Here’s how ▼

LoTW Station log

Confirmed 4
1 2 QSO details 3 Update QSL
Export downloaded Import
Login records and
confirmations confirmations
statistics

1. Login to LoTW if you are not logged in already. While you are there, by all means browse your recent
confirmations received:
• Click to open the yellow Recent QSOs tab.
• Click the Most recent QSLs button on the form (on the right side, under Common Queries) ▼

Copyright © 2020 ZL2iFB P a g e | 17

 LoTW New User Guide

• A Contacting logbook server message appears in pink at the bottom of the form for just a moment,
then you’ll see a batch of up to 25 confirmations similar to this ▼

• Click Next to see the next batch of 25, and so on.

• Click the underlined text to see further details about any QSO record.
• By selecting the relevant Award Account on the form before clicking the Recent QSLs button, you
will also see whether any of the confirmations are valid and can be claimed for awards such as
DXCC. Look for rows with a tick and details of the award for which the confirmed QSO may be
claimed, like this one with 9Y4DG ▼

Copyright © 2020 ZL2iFB P a g e | 18

 LoTW New User Guide

2. Export your recent confirmations from LoTW:

• Click the Download Report button on the QSOs Menu on the left
of the screen ►

• Specify which confirmations you want to download by

completing the self-explanatory form ▼

• Click the Download report button to generate an ADIF file called lotwreport.adi containing the
QSO records for your confirmed QSOs, then send it to your computer.
3. Import the confirmations into your station The name of the function varies between programs.
log using the program’s “import from See the further reading section for links to more info.
LoTW” function.
4. Your station log should now show which QSOs have been confirmed on LoTW, and are therefore
eligible to be claimed for supported awards (more below).

Copyright © 2020 ZL2iFB P a g e | 19

 LoTW New User Guide

4.6 Other things to do in LoTW

After you login to LoTW, there are several things you can do. We’re not going to spoil the surprise by
revealing all here: it is better to explore them on your own, at your own pace.

Those yellow boxes at the lower edge of the top black section are tabs - buttons taking you to the main
parts of LoTW. Just after you login, you will be at your “Home” page, similar to this one. As a reminder,
the word “Home” is in bold in its yellow box. If you get lost while wandering around LoTW, simply click
that “Home” button to return back to this page - ‘go home’, as it were.

Copyright © 2020 ZL2iFB P a g e | 20

 LoTW New User Guide

5 Applying for awards through LoTW

Provided you have accumulated sufficient confirmations, you can apply for some awards directly through
LoTW. The following awards are currently supported in LoTW: ARRL DXCC (DX Century Club); ARRL VUCC
(VHF/UHF Century Club); ARRL WAS (Worked All States); CQ WPX (World Prefix); CQ WAZ (Worked All
Zones).
The first step is to tell LoTW that you are interested in chasing DXCC by requesting a DXCC award account.
The same thing applies to the other awards. Your confirmed QSOs will not be credited to the awards
unless you have an award account.
Once you have the
award account/s, the
process continues:
1. Login to LoTW
2. Click the Awards
yellow tab to open
the Logbook
Awards screen ►
3. Click to select the
relevant award
and callsign from
the buttons on the
left
4. Follow the
on-screen
instructions!
The details vary
between awards.

Uploading old and especially rare logs to LoTW provides confirmations for those in the log, and can
make you very popular! Valid QSOs with DXCC entities that have since been deleted, for instance,
qualify for DXCC at the time the QSOs were made, adding to our ‘all time’ DXCC counts.

Copyright © 2020 ZL2iFB P a g e | 21

 LoTW New User Guide

6 Troubleshooting

6.1 What to do about missing confirmations

It can be frustrating when a QSO is not confirmed, particularly the rare or special QSOs you would like to
claim for an award. Maybe the QSO was incomplete or incorrectly logged by either party? Did you work
a pirate? Does the other person actually use LoTW, and if so when will they get around to uploading their
log?
What to do about that:
• Wait patiently! Although the LoTW process is generally faster than direct or bureau QSLs, it is
unreasonable to expect instant gratification. DXpeditions may wish to consolidate logs from different
computers, check and correct known issues (such as obvious typos, QSOs logged in local time instead
of UTC, or QSOs logged on the wrong band or mode) before signing and uploading the complete,
definitive log to LoTW.
• Check when the other person last uploaded to LoTW. Some amateurs don’t upload very often,
particularly those living in exotic DX locations without Internet access. Some aren’t particularly
interested in LoTW or DXCC, and can’t be bothered uploading. Some may have forgotten how to do
it. A polite email may be enough to persuade them, especially if you state the QSO details and explain
why you need their confirmation, preferably on LoTW.
• Carefully double-check the QSO record in your log. Did you log the No matter what anyone
date and time in UTC? Is the band and mode correctly logged? believes or claims, laws,
What about the callsign: if someone appended their callsign on air compliance and conventions
with, say, “portable 3”, it is uncertain whether they used just their vary in practice around the
base callsign or added /P or /3 when they signed and uploaded the world. Sorry, that’s just how
QSO record to LoTW. Some location modifiers are prepended it goes.
while others are appended.
• If you alter QSOs in your log (for example correcting busted
Annual re-uploads are a
callsigns when QSL cards arrive), you should re-upload the
reasonable compromise, for
changed QSO records to LoTW. While you might be able to
example on your birthday, extract,
extract the changed QSOs and just upload them, an easier
sign and re-upload every QSO
way is periodically to re-upload your entire log. LoTW
made since your last birthday.
automatically ignores exact duplicate QSOs. It is not
TQSL will warn you about
unreasonable to re-upload your entire log occasionally.
duplicate uploads, but it’s OK to do
Please don’t re-upload the same QSOs repeatedly, though, as
it anyway. Call it a birthday treat.
the processing wastes energy, slows down LoTW and can
cause delays for other users.
• If you are desperate to get a confirmation, you might like to generate, sign and upload duplicate QSO
entries with likely callsign variations … but it may be better to email the person concerned to ask for
advice.
• Search for and double-check the QSO information stored in LoTW: has the QSO in question in fact
correctly completed the entire process of being exported from your log, signed and uploaded using
TQSL, then imported successfully into the LoTW database system? Errors are possible along the way.

Copyright © 2020 ZL2iFB P a g e | 22

 LoTW New User Guide

● Contact the counterparty to check
their log. Make it easy for them by
clearly stating your callsign, the
UTC date and time of the QSO, plus
the band and mode.
● If necessary, correct the QSO
details in your log, export it as an
ADIF file, then sign and upload it to
LoTW using TQSL.
Rare DX operators and QSL managers are well aware of
chancers ‘fishing’ for confirmations using common
excuses such as “I forgot to log the QSO” or “My hard drive
crashed”, even though they know or suspect their QSOs
were incomplete. Don’t waste your effort making vague
claims such as “I think it must have been the morning of
the 21st” or “It could have been 12 or 15m - my computer
disconnected from the radio due to RF interference”. This
is unethical and inappropriate.

How to increase your LoTW confirmation rate:

• Take care to log QSOs accurately: typos or other logging mistakes cause a lot of grief.
• If possible, connect your computer to your radio to log frequencies and modes.
• Make more digimode QSOs. Almost all digmoders today are using computers to send and receive
the digital modes, as well as for logging. Many of us use LoTW too.
• Participate in contests. Competitive contesters log on computers, and most of us upload our logs
to LoTW at the same time we submit our logs for adjudication – not least because it substantially
reduces the burden and costs of traditional QSL cards.
• Preferentially contact other LoTW users. The LoTW user list identifies us, and you may be able to
integrate the LoTW user data with your DXcluster monitoring or logging software.

6.2 Bad Callsign Certificates

If TQSL shows a Callsign Certificate icon without its gold ribbon, it is not usable. This can happen if you
reload an out-of-date .tq6 file, because whenever you request a new Callsign Certificate from LoTW, any
older Callsign Certificates for the same callsign are automatically marked “replaced”.
You can tell the state of a Callsign Certificate by its icon in TQSL, under the Callsign Certificates tab ▼

Copyright © 2020 ZL2iFB P a g e | 23

 LoTW New User Guide

Beside every callsign for which you have requested a Callsign Certificate on your computer, you will see
an icon indicating its status:

Valid. This Callsign Certificate is current, functional and ready to use.

Pending*. This Callsign Certificate has been requested but not yet supplied and loaded.

Replaced*. A more recent Callsign Certificate is available for this callsign.

Expired*. This Callsign

Certificate reached the end of its
validity period. It is no more. You
can delete it by right-clicking it
then selecting Delete Callsign
Certificate ►

Broken. This Callsign Certificate

is missing a vital component or has
become corrupted and is useless.
You might as well delete it too.

* Pending, Replaced or Expired can occur

because you previously requested a
Callsign Certificate but for some reason
failed to complete the process. You may
be able to repair it like this:

1. Click here to download your current Callsign Certificates ◄ The repair process can only
(LoTW will likely ask you to log in with your LoTW username complete a corresponding
(callsign) and password). A file called certs.tq6 will be saved certificate request, changing a
in your Downloads folder. Pending, Replaced or Expired
2. Run TQSL. Callsign Certificate into a Valid one.
3. Click to open the Callsign Certificates tab ▼

Copyright © 2020 ZL2iFB P a g e | 24

 LoTW New User Guide

4. Click the Load a Callsign Certificate button, then navigate to Any messages about duplicate
your Downloads folder and click to select the certs.tq6 file Callsign Certificates can be safely
downloaded in step 1. When the load is complete, your ignored at this point.
computer has the most recent Callsign Certificates for any
callsigns related to your LoTW account. In TQSL you should see at least one icon indicating a
current, working, Callsign Certificate. If not, start over by making a fresh Callsign Certificate request:
5. Delete the Callsign Certificate for
the callsign which you want to
use:
a. In TQSL, click to open the
Callsign Certificates tab ►
b. Right-click the Callsign
Certificate you want to
delete ►
c. Click Delete Callsign
Certificate ►
d. Read the warning message,
double-check that you have
selected the correct Callsign
Certificate, then click Yes to
delete it ►
6. Request a new Callsign Certificate for
that callsign.
7. Wait patiently! Do not do anything
with the pending certificate in TQSL.
You must wait for the ARRL staff to
approve and issue you a replacement
Callsign Certificate, manually. Don't
be tempted to ignore the warnings
that there is a certificate pending and
delete it. Be patient … or you will have
to go back around this circuit again!
8. As soon as it is ready, ARRL will sent you a new callsign.tq6 file as an email attachment, where callsign
is the callsign for this Callsign Certificate. Save the callsign.tq6 file from your email client to your
Downloads folder (how to do that depends on what email software you are using: try clicking, double-
clicking or right-clicking the attachment).
9. Open TQSL, if it isn’t already running.
10. Select the Callsign Certificates tab as shown in the image above.
11. Click Load Callsign Certificate from File.
12. Navigate to your Downloads folder, and double-click to open the callsign.tq6 file which you
downloaded and saved in step 4.
13. Your Callsign Certificate should now show the valid icon meaning that it is ready to use. Success!

Copyright © 2020 ZL2iFB P a g e | 25

 LoTW New User Guide

14. When you're all done, delete the callsign.tq6 file. It is a single-use file. You won't need it again. Should
you need to do so, you can always request a replacement Callsign Certificate through TQSL, starting
from step 1 of this procedure.

6.3 TQSL shows a “Database Error” when signing a log

In order to reduce the number of duplicate QSOs submitted to LoTW, TQSL maintains an internal list on
your computer with information about the QSOs that you have uploaded already.
“Database Error" means that, somehow, TQSL’s internal QSO list has Don’t fret! Although TQSL may
become corrupted. This has nothing to do with the log being have lost its list of previously-
processed, or LoTW: it is a fault within TQSL itself. processed QSOs, LoTW still has
If a “Database Error” happens when TQSL is initially setting up to sign all your signed, uploaded and
a log, TQSL will recover automatically by deleting its list of uploaded processed QSO records stored
QSOs and starting afresh, but if you're in the middle of signing a log safely on the server. LoTW
when the error happens, the automated fix doesn't work so you efficiently skips past exact
must step in. duplicate QSOs if they are ever
uploaded again.
To correct “Database Error” manually (on a Windows system):
1. Open Windows Explorer by holding down the Windows-logo key and pressing "E".
2. In the address bar (labeled "Quick access" in windows 10), click and then enter the following:
%AppData%\TrustedQSL
Then press Enter to open the directory where TQSL stores its QSO list.
3. Right-click any of the following files and choose Delete to remove them:
• duplicates.db
• __db.* meaning files such as __db.001, __db.002, __db.register etc.
• log.* meaning files like log.00000010 etc.
4. TQSL will re-create its internal QSO list automatically the next time you sign and upload a log.

Feedback comments, corrections, additional tips

and other suggestions to improve on this guide
are very welcome: please email Gary@isect.com.

Copyright © 2020 ZL2iFB P a g e | 26

 LoTW New User Guide

7 Further reading
Here are some useful reference sources with additional information:
• ARRL’s online help for LoTW is extensive, well written, definitive and worth browsing.
• ARRL LoTW reflector is an email group for LoTW users, a source of hints and tips, and a great place to
go for help if you get stuck or have queries and concerns. Members of the reflector initiated and
provided numerous inputs to this very guide.
• ARRL LoTW Getting Started Guide plus brief quick-start guides (available soon!).
• Current LoTW status shows recent uploads queued up, waiting to be processed into the database.
• Last upload dates shows when stations last uploaded their logs to LoTW.
• List of LoTW users maintained by ARRL and HB9BZA.
• Websites for LoTW, ARRL, DXCC, ADIF, TQSL etc.
• LoTW help desk has FAQs and troubleshooting tips, and you can ‘submit a ticket’ to ask for human
assistance with specific LoTW problems.
• DXCC help desk lists the email addresses for human assistance with specific DXCC problems.
• Guidance on connecting logging programs to LoTW:
• Amateur Contact Log: LoTW help
• Club Log: how to use LoTW
• DX4win: look for LoTW in the help
• DXLab: step-by-step instructions for QSLing with LoTW and reference documentation
• HRD Logbook: setup instructions (may change as the documentation gets updated)
• Log4OM: full instructions (from page 100)
• Logger32: uses the L32logSynch add-on by N2AMG
• LOGic: LoTW uploads and downloads are automated (browse built-in help for more)
• MacLoggerDX: instructions
• QRZ Logbook: LoTW Certificate Import and LoTW Download quick start guides
• Swisslog: LoTW support information
• Wayne Mills, N7NG (2003). "Introducing Logbook of The World". QST 87 (October), pages 46-47.
• Wikipedia page: https://en.wikipedia.org/wiki/Logbook_of_The_World

Copyright © 2020 ZL2iFB P a g e | 27

 LoTW New User Guide

Appendix: TQSL updates

The Trusted QSL application (TQSL) is updated by its author from time to time. Sometimes the program
itself is changed, sometimes the ‘configuration file’ with details about countries and zones, occasionally
both.

If you see messages like this after you start TQSL …

… then it’s time to update:

1. Click OK. If there are two messages each with OK buttons, do the “new TQSL release” (program
update) first.
2. Gaze on in bewilderment as the software downloads the new release and updates itself,
automatically. This can take a moment. You may notice TQSL closing and reopening.
3. If there is a further update still waiting, click the OK
button and wait for the configuration file to download
and update itself, automatically. This is usually
quicker, almost instantaneous, and ends by displaying
a success message ►
4. Start using the updated TQSL the same as the original
version – only with different (hopefully fewer!) bugs
and the proper configuration.

If something goes wrong with an update, programs usually revert to the previous un-updated version and
warn you that the update failed ... but then you’re on your own. Sorry, the automation has let you down.
You may be lucky if you run the update again, perhaps after rebooting your computer first. If the update
still fails, you can try emailing the author of the software, asking a passing computer whizz-kid for
assistance, calling the help desk or emailing the LoTW reflector.

Please don’t just ignore update messages and warnings though. If it is not a convenient time to update,
it is OK to click the cancel button/s on the update messages and continue using the current un-updated
application for a while, but probably not forever.

Copyright © 2020 ZL2iFB P a g e | 28

 LoTW New User Guide

Appendix: Renewing a Callsign Certificate

When TQSL starts up, it automatically checks

for program updates and Callsign Certificates
nearing the end of their 3-year validity, soon to
expire. You’ll see pop-up messages telling you
what’s going on.
It’s easy to renew a Callsign Certificate through
TQSL: simply follow the prompts.

You will be asked to confirm the callsign,

DXCC entity and license validity period. ►

The Callsign Certificate generation process

is largely automated and normally takes
minutes. However, it may be delayed if the
LoTW systems are busy, down for
maintenance etc. Unusual Callsign
Certificate requests need to be checked
manually by ARRL staff before being
processed, which takes time. If the emails
don’t arrive, wait patiently. Check your
spam box. If you still haven’t received the
emails a few days later, contact the ARRL
LoTW help desk for assistance.

It’s best to apply for a

replacement Callsign
Certificate before your old
one expires … but even if
you are a bit late, the old
one can still be used to
sign a request for a
replacement.

Copyright © 2020 ZL2iFB P a g e | 29

 LoTW New User Guide

You should receive a pair of emails from ARRL, first one confirming that the Callsign Certificate request
has been received and checked, and your certificate is being generated:

Shortly after you should receive a further email with your new Callsign Certificate attached.

Copyright © 2020 ZL2iFB P a g e | 30

 LoTW New User Guide

Don’t forget to make a

fresh backup at the end
of the process - see the
next appendix.

Copyright © 2020 ZL2iFB P a g e | 31

 LoTW New User Guide

Appendix: Backups
Backups protect us against incidents and accidents that
would damage or destroy valuable information. Trust me,
it is much easier and quicker to restore a backup than
attempt to recreate your log from scratch following a
computer crash, theft, virus infection or mistake when
“tidying up the directories”. The trick is to make backups
and store them safely.
Radio clubs might usefully offer a backup
service, helping members generate
backups of their logs and TQSL information,
storing them safely, and helping members
restore backups if needed. How about
suggesting this to your club’s committee?

Backing up your Callsign Certificates and other information from TQSL

Backup your TQSL data whenever significant changes occur, such as adding new Callsign Certificates or
station locations.
It’s easy to do. In TQSL, you will find the
option under the File menu ► Simply click
Backup Station Locations, Certificates, and
Preferences … and follow the prompts to
specify where on disk to store the backup. It
creates a backup file called tqslconfig.tbk by
default, storing it in the directory you
selected.
Copy the backup file to removable media such
as a USB memory stick, CD-ROM/DVD etc.,
then store it safely away from the computer.

Cloud storage may be more convenient but what happens if the cloud service fails, or someone
accidentally deletes the stored data, or it gets corrupted by ransomware? Do not rely entirely on cloud
backups for any really important or valuable data. Remember, clouds may bring rain!

Restoring TQSL data (Callsign Certificates,

Station Locations etc.)
If for some reason you need to do this, you can
restore a .tbk backup to a fresh installation of
TQSL:
1. Download and install TQSL.
2. Run TQSL
3. Click the File menu option.
4. Click Restore Station Locations,
Certificates, and Preferences
5. Follow the prompts to locate and load the
.tbk file.
6. Check that your Callsign Certificates and Station Locations are present and correct.
You can restore a .tbk backup to a recent
installation of TQSL on any computer - for instance
if a broken shack computer has been replaced, or
perhaps you have a laptop for traveling or a
friend’s computer (e.g. a club computer).
However, if you elected not to use a password to
protect a Callsign Certificate, anyone with access to
that system could potentially sign and upload QSOs
under your callsign. So either add a password, or
only give the .tbk file to people you trust.

Copyright © 2020 ZL2iFB P a g e | 32

 LoTW New User Guide

Backing up your electronic log

If you thought TQSL backups were easy, log backups are even Any backup drives or media that remain
easier: simply sign and upload your QSOs to LoTW. LoTW physically connected to or accessible
keeps the essential QSO details in its database, and we can from your computer (including cloud-
download them later if for some reason we need to recover based backups) are vulnerable to being
the information. corrupted/damaged, deleted or stolen.
Explain how to download the basic log from LoTW Ransomware typically locks up all
accessible data before demanding a
However, LoTW only stores essential QSO information
ransom payment. A shack fire may well
i.e. callsigns, dates, times, modes and bands or frequencies.
destroy everything. Connect backup
Other details such as operator names, QTHs, QSL
devices only while you are making or
information and notes are not stored by LoTW - in fact they
restoring backups. At other times,
are not even uploaded since TQSL strips them out before
store them safely in a different place,
signing our logs.
ideally a fire safe or safety deposit box.
If you aren’t willing to risk losing all that additional If you are as cautious/paranoid as me,
information needed to recreate your complete log following make multiple backups and store them
an incident, you must make backups of your log by some separately.
means e.g.:
• Your logging program probably has a backup function that lets you save your complete log to disk. It
may even do this automatically for you. Check the File menu, read the help or ask for support from
the software supplier.
• Your logging program probably lets you export your log as an ADIF file. This has the advantage that
you can import the ADIF log into other logging programs if the original one turns out to be unusable
for some reason (e.g. no longer supported and unable to run on current systems).
• Copy the saved log file to removable storage such as a USB memory stick, external hard drive or CD-
RW disk, then remove or disconnect it.

Restoring your electronic log Tidy up old files from time to time. Once you
1. Install and configure a modern logging program to have sent a .tq5 certificate request to LoTW,
your liking. received back the .tq6 certificate file and
loaded it into TQSL, you can safely delete
2. Find and run the option to import an ADIF log file.
both files. Likewise with the .tq8 signed logs
3. Find your most recent ADIF backup and import it. that you have uploaded to LoTW: there is no
4. Deal with any import errors (e.g. correct any invalid need to hold on to the .tq8 files after they
QSO details). have been uploaded. Be careful not to
delete your ADIF logs, of course (.adi files),
5. Check that you now have a reasonably complete log and keep those TQSL backups (.tbk files).
e.g. does it contain the correct number of QSOs?
Are there any unexpected gaps? Are the awards reports showing the correct info? If not, you may
need to import other backups as well, hoping that the logging software automatically detects and
skips duplicates (otherwise you may have some tedious work ahead to find and delete the dupes - or
this may be your cue to install better logging software that handles dupes more intelligently!).
6. Make a fresh ADIF backup of your newly-restored log, and store the backup safely. Trust me, you
don’t want to go through all that hassle again!

Copyright © 2020 ZL2iFB P a g e | 33