<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Callsigns on AD8FD</title><link>https://ad8fd.com/tags/callsigns/</link><description>Recent content in Callsigns on AD8FD</description><generator>Hugo</generator><language>en-US</language><managingEditor>bbathe@willyboy.com (Brian Bathe)</managingEditor><webMaster>bbathe@willyboy.com (Brian Bathe)</webMaster><lastBuildDate>Fri, 13 Feb 2026 06:32:22 -0500</lastBuildDate><atom:link href="https://ad8fd.com/tags/callsigns/index.xml" rel="self" type="application/rss+xml"/><item><title>Additional Callsigns</title><link>https://ad8fd.com/posts/additional-callsigns/</link><pubDate>Fri, 13 Feb 2026 06:32:22 -0500</pubDate><author>bbathe@willyboy.com (Brian Bathe)</author><guid>https://ad8fd.com/posts/additional-callsigns/</guid><description>How to add your additional callsigns across all the various system we use in amateur radio.</description><content:encoded><![CDATA[<h2 id="adding-a-new-callsign-before-the-next-trip">Adding a New Callsign Before the Next Trip</h2>
<p>I recently added another callsign, and like most things in amateur radio, the updates across all the different systems take more time than you’d expect. Since this will follow me onto future trips, I wanted to get everything sorted now rather than discovering a missing certificate on some island with spotty Wi‑Fi.</p>
<p>Here’s the sequence that worked for me.</p>
<h3 id="lotw-comes-first">LoTW Comes First</h3>
<p>Being able to confirm QSOs in <a href="https://lotw.arrl.org/" target="_blank" rel="noopener noreferrer">LoTW</a> is critical, so that’s where I start. It can also take time for ARRL to review the request, approve it, and issue the certificate, so getting this done early avoids delays later.</p>
<p>I requested the new certificate in TQSL and waited for the automated email asking for proof. Once I replied and the certificate was issued, I imported it on the same computer I used for the request. After that, I exported the <code>.p12</code> file so I can bring it on whichever laptop comes with me on the trip.</p>
<p>It’s not exciting work, but fixing LoTW problems from the field is worse.</p>
<h3 id="add-the-callsign-to-pota">Add the Callsign to POTA</h3>
<p>Next stop was <a href="https://parksontheair.com/" target="_blank" rel="noopener noreferrer">POTA</a>. Under <em>My Account</em>, I added the new callsign. Quick and easy. No verification needed.</p>
<p>Some of my portable trips overlap with parks, so it’s better to have this sorted ahead of time.</p>
<h3 id="update-the-places-people-will-look-you-up">Update the Places People Will Look You Up</h3>
<p>Once you touch <a href="https://www.qrz.com/" target="_blank" rel="noopener noreferrer">QRZ</a>, the whole ecosystem starts noticing: <a href="https://www.dx-world.net/" target="_blank" rel="noopener noreferrer">DX‑World</a>, <a href="https://www.dailydx.com/" target="_blank" rel="noopener noreferrer">Daily DX</a>, <a href="https://dxnews.com/" target="_blank" rel="noopener noreferrer">DX News</a>, all of it. So timing matters.</p>
<ul>
<li>
<p><strong>Suffix/Prefix Callsigns</strong><br>
For operating variations like <code>/P</code>, <code>/4</code>, <code>/VE3</code>, or similar, these get added under:<br>
<strong>Account → Secondary Callsigns</strong></p>
<p>This keeps all your derivative calls linked properly to your main profile.</p>
</li>
<li>
<p><strong>Newly Issued Callsigns</strong><br>
If the callsign is actually <em>issued to you</em>, it goes under:<br>
<strong>Account → Managed Callsigns</strong></p>
<p>This ensures the new callsign has a proper identity on its own, while still being tied to your main account for logging and profile management.</p>
</li>
</ul>
<h3 id="club-log-for-the-log-uploads-that-matter">Club Log, for the Log Uploads That Matter</h3>
<p>Finally, I added the callsign under <em>Settings → Callsigns</em> in <a href="https://clublog.org/" target="_blank" rel="noopener noreferrer">Club Log</a>.</p>
<h3 id="wrapped-up">Wrapped Up</h3>
<p>It’s not glamorous, but getting a new callsign integrated everywhere is just part of the prep work: same category as booking houses, sorting flights, or confirming rental cars. Now that it’s done, the next time this callsign goes on the air, everything should just work.</p>
]]></content:encoded></item></channel></rss>