Start here: Formal message handling uses a defined format and repeatable procedure so a written message can move through one or more stations without changing its content, routing, precedence, or accountability.
Picture the operating situation
A formal message is successful when the addressee receives the same information the originator approved and the system can show how it moved. It is not made formal merely by reading it slowly.
Use this sequence
- Use the format required by the net or served agency.
- Preserve names, numbers, punctuation instructions, and group order exactly.
- Request fills instead of guessing.
- Record relay, receipt, delivery, and service information.
- Practice across voice, digital, and CW workflows used by the local system.
Common ways the plan fails
- Correcting the originator’s wording during relay.
- Leaving the addressee or contact path incomplete.
- Combining separate messages to save airtime.
- Treating an informal status update as a formal record.
Operating boundary:
Follow current license conditions, land or facility rules, the active communication plan, and the responsible organization’s directions. Keep antennas and supports away from power lines and uncontrolled public access. Do not self-deploy to an incident.
Primary source
Rules and response doctrine change. Confirm the current requirement at ARRL National Traffic System methods before relying on this guide.
