KE5ZQV field note · 7 min read

Station documentation checklist

A practical checklist for documenting radios, power, antennas, grounding/bonding, feed lines, software accounts, and backup/export routines.

Why document the station?

Station documentation sounds boring until something breaks. Then a simple note about which cable goes where, which fuse protects what, or which account is used for uploads can save a lot of time.

The goal is not a fancy binder. The goal is a practical record that helps you troubleshoot, rebuild, explain, or improve the station.

Radio and accessory notes

For each radio, write down the model, serial number if you are comfortable storing it, power requirements, fuse size, microphone/accessory pinouts, data interface settings, and common menu settings. If the radio connects to a computer, document the USB port, driver, serial speed, and software profile.

Power documentation

Power is safety-relevant. Document the power supply, battery, fuse sizes, wire gauge, connector type, and which devices are on each circuit. Label polarity clearly. If you change a cable or connector, update the note the same day.

Stop condition: if you find an unfused lead, unknown polarity, overheated connector, or damaged insulation, stop using that part of the station until it is corrected.

Antenna and feed line notes

Record each antenna, feed line type, approximate length, connectors, lightning protection path, and known SWR behavior by band. Add analyzer screenshots or VNA sweeps if you have them. A baseline measurement is valuable later when something changes.

Software and account notes

Keep a list of logging software, radio-control software, digital-mode software, and online services such as LoTW, QRZ.com, and eQSL.cc. Do not store plain-text passwords in a public note. Do record which email/account owns each service and where backups/exports live.

Minimum station checklist

• Radio model and power requirements.
• Power supply/battery and fuse sizes.
• Antenna/feed line layout.
• Grounding/bonding notes.
• Computer/software settings.
• Logging/export backup routine.
• Known-good SWR or analyzer readings.
• Emergency shutoff or disconnect procedure.

Bottom line

Good documentation is part of good station building. It makes troubleshooting faster, upgrades safer, and recovery easier when a cable, radio, computer, or account changes.

This article is general ham-radio operating and station-building information, not legal, safety, or manufacturer-specific advice. Verify regulations, manuals, ratings, and measurements before acting.