Emergency Protocols (In Progress)
Uhuru – Emergency Communications (EmComms) Protocol (Draft) - 2026-05-04
Overview
This is a template for local groups to use when developing their emergency communications (EmComms) protocols.
Emergency Communications refers to any network that ensures communications can be maintained in an emergency situation using unconventional technologies such as amateur radio, CB radio, LoRa/Meshtastic, POC, satellite phones, etc. (most often the Baofeng Option).
A Communications Emergency exists whenever the situation could impact your ability to communicate with each other in the conventional way (Internet, cell, landline, etc). This could include situations where there is concern that the conventional channels are being closely monitored and used against you (lockdowns, arrests, etc.). There are any number of scenarios that could prompt a Communications Emergency. (see Emergency Scenarios).
Of course emergency communications is just one aspect of your response to an emergency situation – albeit a crucial one. By maintaining contact with other members of your group you are in a better position to address the specific demands of the emergency situation (see Responses).
There are two scenarios for triggering a Communications Emergency.
If conventional comms are still in effect, they can be used by the LNC to get the message out to the Group
This is a template for local groups to use when developing their emergency communications (EmComms) protocols.
Emergency Communications refers to any network that ensures communications can be maintained in an emergency situation using unconventional technologies such as amateur radio, CB radio, LoRa/Meshtastic, POC, satellite phones, etc. (most often the Baofeng Option).
A Communications Emergency exists whenever the situation could impact your ability to communicate with each other in the conventional way (Internet, cell, landline, etc). This could include situations where there is concern that the conventional channels are being closely monitored and used against you (lockdowns, arrests, etc.). There are any number of scenarios that could prompt a Communications Emergency. (see Emergency Scenarios).
Of course emergency communications is just one aspect of your response to an emergency situation – albeit a crucial one. By maintaining contact with other members of your group you are in a better position to address the specific demands of the emergency situation (see Responses).
There are two scenarios for triggering a Communications Emergency.
If conventional comms are still in effect, they can be used by the LNC to get the message out to the Group
Getting Ready
Each group should have a designated Local Net Controller (LNC) – the person responsible for everything to do with comms, in particular establishing Protocols (see Roles). In many cases it will be the Group Organizer, particularly at the outset, but it is best if it is someone else.
If you plan to be part of the Main Network and receive updates from across the region, the country and the world, you will want to have an SDR Operator.
Once these people are in place you should start developing your Protocols.
One of the first things you want to do is to identify when an emergency is in effect, known as the Trigger. This is the signal that lets people know they must implement their Protocols.
It is the role of the LNC to declare that there is an emergency to the Group. This means getting the message out that everybody should start their protocols. It is intended that if the emergency is more than just local (eg severe weather).
It may very well be the case that the LNC can not get the message out due to the nature and timing of the emergency, in which case individuals should determine for themselves that an emcomms emergency exists and that they should initiate their part of the protocol.
This means connecting with your Main Point(s) of Contact (MPCs) on the prescribed frequency at the appropriate time.
You then follow a script of what needs to be said, including an acknowledgement (see Script).
Each group should have a designated Local Net Controller (LNC) – the person responsible for everything to do with comms, in particular establishing Protocols (see Roles). In many cases it will be the Group Organizer, particularly at the outset, but it is best if it is someone else.
If you plan to be part of the Main Network and receive updates from across the region, the country and the world, you will want to have an SDR Operator.
Once these people are in place you should start developing your Protocols.
One of the first things you want to do is to identify when an emergency is in effect, known as the Trigger. This is the signal that lets people know they must implement their Protocols.
It is the role of the LNC to declare that there is an emergency to the Group. This means getting the message out that everybody should start their protocols. It is intended that if the emergency is more than just local (eg severe weather).
It may very well be the case that the LNC can not get the message out due to the nature and timing of the emergency, in which case individuals should determine for themselves that an emcomms emergency exists and that they should initiate their part of the protocol.
This means connecting with your Main Point(s) of Contact (MPCs) on the prescribed frequency at the appropriate time.
You then follow a script of what needs to be said, including an acknowledgement (see Script).
Trigger
A Trigger is the thing that will initiate the Protocols. It can be something done by the LNC or it can be self-inititated based on circumstance.
If conventional comms are still in effect but likely to go dark, the LNC would sound the alarm to let everyone in the group to immediately put the Protocols into effect. This can be an alarm email or text, coded or not.
If conventional comms are down and it is not possible for the Trigger Alarm to be sent or received members of the groups should assume the Protocols are in effect
A Trigger is the thing that will initiate the Protocols. It can be something done by the LNC or it can be self-inititated based on circumstance.
If conventional comms are still in effect but likely to go dark, the LNC would sound the alarm to let everyone in the group to immediately put the Protocols into effect. This can be an alarm email or text, coded or not.
If conventional comms are down and it is not possible for the Trigger Alarm to be sent or received members of the groups should assume the Protocols are in effect
First Action
When an Emergency Situation is in effect, everyone in the group should reach out to their Main Contacts according to the schedule outlined in the Protocols.
The Protocol will make it
When an Emergency Situation is in effect, everyone in the group should reach out to their Main Contacts according to the schedule outlined in the Protocols.
The Protocol will make it
Details / Glossary
Conventional Communication Channels
• Internet
• cellphones
• landlines
Emergency Communication Channels
• amateur radio
• CB radio
• LoRa/Meshtastic
• POC
• satellite phones
• etc.
Roles
• Main Net Controller (MNC)
• Group Leader
• Local Net Controller (LNC)
• Main Point of Contact (MPC)
• Group Members
• SDR Operator
Main Net Controller (MNC)
Local Net Controller (LNC)
responsible for all things EmComms related for the Group
Main Point of Contact (MPC)
Group Members
SDR Operator
Role of Local Net Controller (LNC)
• determine network foundation
• procure comms devices
• setup SDR Operator
• establish local emcomms protocol
• train group in use of comms devices and protocols
Script
• ID (Call/Response)
• Intro (Codename)
• Message (See Codes)
• Acknowledgement
There are two roles in EmComms
• status reports
• request/response to Help message
Code Messages (remove Real during EmDrils)
• Real Windy: EmComms Emergency is in effective
• Real Cold: EmComms Protocols partially activated
• Real Hot: EmComms Protocols are fully activated
• Real Code Blue: We have a health emergency at our location
• Real Code Red: We have a security issue at our location
• Real Code Green: We are coming to provide assistance
• Real Code Black: We are unable to provide assistance
• Real Code White: Meet at Rally Point
Comms Emergency response
• Follow the Protocol
• follow the connection schedule
• Maintain your Comms Device is good order (batteries charged, faraday cages)
Government Emergency Services
• Ontario Corp
• RAC ACS
• RAC ARES
•
The next thing to do is to intitiate your emcomms protocol. This means getting on your device and connecting at the prescribed time.
Emergency Scenarios
• electrical power is out
• Internet is down
• cell service is down
• landlines are down
• satellites are down
• all usual comms are down
• lock down underway (people have been ordered to shelter in place)
• evacuation order has been issued
• weather emergency has been declared
• space weather emergency has been announced
• mass arrests underway
• financial crisis is underway
Conventional Communication Channels
• Internet
• cellphones
• landlines
Emergency Communication Channels
• amateur radio
• CB radio
• LoRa/Meshtastic
• POC
• satellite phones
• etc.
Roles
• Main Net Controller (MNC)
• Group Leader
• Local Net Controller (LNC)
• Main Point of Contact (MPC)
• Group Members
• SDR Operator
Main Net Controller (MNC)
Local Net Controller (LNC)
responsible for all things EmComms related for the Group
Main Point of Contact (MPC)
Group Members
SDR Operator
Role of Local Net Controller (LNC)
• determine network foundation
• procure comms devices
• setup SDR Operator
• establish local emcomms protocol
• train group in use of comms devices and protocols
Script
• ID (Call/Response)
• Intro (Codename)
• Message (See Codes)
• Acknowledgement
There are two roles in EmComms
• status reports
• request/response to Help message
Code Messages (remove Real during EmDrils)
• Real Windy: EmComms Emergency is in effective
• Real Cold: EmComms Protocols partially activated
• Real Hot: EmComms Protocols are fully activated
• Real Code Blue: We have a health emergency at our location
• Real Code Red: We have a security issue at our location
• Real Code Green: We are coming to provide assistance
• Real Code Black: We are unable to provide assistance
• Real Code White: Meet at Rally Point
Comms Emergency response
• Follow the Protocol
• follow the connection schedule
• Maintain your Comms Device is good order (batteries charged, faraday cages)
Government Emergency Services
• Ontario Corp
• RAC ACS
• RAC ARES
•
The next thing to do is to intitiate your emcomms protocol. This means getting on your device and connecting at the prescribed time.
Emergency Scenarios
• electrical power is out
• Internet is down
• cell service is down
• landlines are down
• satellites are down
• all usual comms are down
• lock down underway (people have been ordered to shelter in place)
• evacuation order has been issued
• weather emergency has been declared
• space weather emergency has been announced
• mass arrests underway
• financial crisis is underway
Readiness Checklist
• [ ] LNC in place
• [ ] SDR Operator in place
• [ ] Protocols established (Times, Frequencies, Codes, Actions, etc.)
• [ ] Devices acquired
• [ ] Training completed
• [ ] Contacts/relays established
• [ ] Regular testing/drills in place
• [ ] LNC in place
• [ ] SDR Operator in place
• [ ] Protocols established (Times, Frequencies, Codes, Actions, etc.)
• [ ] Devices acquired
• [ ] Training completed
• [ ] Contacts/relays established
• [ ] Regular testing/drills in place
Em Comms Protocols Template
Group Leader _______________________________________________________________
Local Network Controller (LNC) _______________________________________________
SDR Operator (if different from LNC) ___________________________________________
Network Device (eg Baofeng UV-5R) ____________________________________________
Rally Point: _________________________________________________________________
Trigger Alarm: _______________________________________________________________
First Action:
Connect with your Main Contacts
Time: ______________________________________________________________________
Frequency: __________________________________________________________________
Subsequent Actions:
Meet at Rally Point:
Time: ______________________________________________________________________
Conduct Welfare Checks; _______________________________________________________
Respond to Help Requests: _____________________________________________________
Other Actions:
Group Leader _______________________________________________________________
Local Network Controller (LNC) _______________________________________________
SDR Operator (if different from LNC) ___________________________________________
Network Device (eg Baofeng UV-5R) ____________________________________________
Rally Point: _________________________________________________________________
Trigger Alarm: _______________________________________________________________
First Action:
Connect with your Main Contacts
Time: ______________________________________________________________________
Frequency: __________________________________________________________________
Subsequent Actions:
Meet at Rally Point:
Time: ______________________________________________________________________
Conduct Welfare Checks; _______________________________________________________
Respond to Help Requests: _____________________________________________________
Other Actions: