Copy Pasta from a word document so there may be inconsistencies.
Chapter 2 – Communications
2-Z : Phone Tree Protocol
The Phone Tree is used to facilitate rapid communications between members of the group. The objective of the phone tree is to alert everyone to a disaster while reducing the amount of time the Area Commander has to spend on the phone. The list generally goes as follows but can be customized by the AC to suit their area’s needs.
AREA COMMANDER dials HEADS OF HOUSEHOLD who then dials each MEMBER of that household. Upon receiving confirmation that each MEMBER is aware and taking action, HEAD OF HOUSEHOLD notifies AREA COMMANDER.
No uuencoded commands should be issued via the phone tree, both to reduce the potential for miscommunication and because all telephones are unsecure lines of communication. Rather, codes will be issued to indicate the severity and nature of the alert. They will be issued as DEFCON with a numeric code for severity. Those codes are listed on the following table.
(Defcon codes redacted; these should be tailored to your specific group and AO.)
PHONE TREE SAMPLE SCRIPT
Examples: DEFCON SAMPLE SCRIPT
AC notices an unusual number of EMS vehicles in the neighborhood. TV news reports ethnic rioting is growing in the area with unconfirmed reports of “flash mob” activity. He immediately declares a DEFCON 2 and contacts each head of household.
AC: “This is your AC, we have a DEFCON 2, possible civil unrest.”
HoH: “This is XXXXX acknowledging DEFCON 2. Will report back with states of readiness.
HoH immediately turns on cable news while contacting each member of their household, getting an update on their location and status. All members are safe, one at home and the other two at or on the way to work. HoH reports back to AC.
HoH: “This is HoH reporting for household. Member A is at home, with me. Member B is at work at <location> and member C is en route to work at <location>.”
AC: “Good work. Center of mob activity appears to be 4th & Kirkwood according to the news chopper. I’ll update you as necessary. It appears everyone is off work at 1700; meet up at my place then.”
HoH relays meeting time and place to the rest of the group for a non critical meeting. Some time later, the rioting grows worse and the mob grows larger, with more reports of armed violence. Reviewing the situation as it worsens, AC upgrades the situation to a DEFCON 3. He places a call to each HoH.
AC: “Attention, the situation is worsening. I’m calling a DEFCON 3, repeat, DEFCON 3 for civil unrest.”
HoH: “Acknowledging DEFCON 3. Meeting place still the same?”
AC: “Same place, but critical now. Get your people out of there, that mob is on the move.”
HoH: “Acknowledged. I’ll get ahold of my people now.”
HoH contacts each member of their household and instructs them rendezvous with the group at the designated point. Member C gives a DEFCON 99.
HoH: “This is HoH informing you that the situation has been upgraded to DEFCON 3; meeting place is unchanged but get your ass over there now.”
MEMBER C: “Uh, actually I’ve got a DEFCON 99 over here.”
HoH: “I’m confirming, you have a DEFCON 99? What is your location and situation?”
MEMBER C: “I’m at work at <location> and I have hostile rioters between me and the parking garage. Doors are secure but they are beating on the windows and I’m unarmed.”
HoH immediately reports the situation to AC.
HoH: “AC, I have a confirmed DEFCON 99, Member C.”
AC: “Seriously? Confirming DEFCON 99? What’s going on out there?”
HoH: “Member C is trapped at work with hostiles between him and his car in the parking garage. He is requesting assistance immediately.”
AC: “Shit fuck dog rapist god damnit. All right. Inform member C. I’m going to dispatch a Fire Team to escort him to his vehicle. Tell him to stand by and keep us posted.”
2-Y : COMM & COMSEC Procedures
These are the methods for secure bugout communications via our current GMRS radios. Terminology is listed in the following table.
Table 2-B : Radio Comm Terminology
Radio Operator: The person in the unit who has the radio and is responsible for maintaining communication with Command and other units in the field.
Command: The person commanding the mission. Command assigns Handles, Authorization and Reply Codes for the mission.
Handle: A user's call sign.
Authorization Code: A numeric and digital code that prefixes any communication, used to verify the broadcaster's authenticity.
Reply Code: A numeric and digital code used to verify a receiver’s authenticity.
Before the mission begins, a handle is assigned to each radio operator and to command. These are designated by Command. Authorization and reply codes will also be issued. Each should be in an easy to remember format. Mission specific codes like objective designations or contingency designations will also be assigned at this time. Radio Operators should familiarize themselves with the appropriate codes at this time. Frequencies will be designated on at this time as well.
Once everyone has been briefed on the codes and the mission begins, radio silence is expected except for emergencies. Remember that these are not secure encrypted communications and so must be used with caution. Communication protocols should proceed as such.
PROTOCOL: Open signal
This is for a radio operator to reach anyone else in the field, and covers the basic comsec necessities. It is used to verify a signaler's identity and should be used after any long period of radio silence.
Radio operator 1: This is <Handle> requesting a signal from <Handle or All> <Authorization Code> Over
Radio Operator 2 : This is <Handle> acknowledging signal request. <Reply Code> Over
Radio Operator 1: <Proceed with message>
Only after this protocol has been followed should communication continue.
PROTOCOL: Frequency Change
A frequency change chart will be given to Radio Operators during mission briefing. They will be short numeric codes assigned to specific frequencies to designate a new radio frequency for the team to communicate on. Only Command can order a frequency change. This is done to avoid other radio traffic. Format should be as follows.
Command: This is <Handle> <Authorization Code> Please Signal <Frequency Chart Code> starting in 30 seconds, over
Radio Operator 1: This is <Handle> <Reply Code> Acknowledging Signal Change, over
Radio Operator 2: This is <Handle> <Reply Code> Requesting Repeat, over
Command: This is <Handle> repeating: Please signal <Frequency Chart Code> starting in 30 seconds, over.
All Radio Operators should consult their charts and change frequencies at this point. Once on the new frequency after the time limit is reached, command should call for a signals test on the new line.
PROTOCOL: SIGNALS TEST
A signals test is used whenever there is a possible change, failure or break in communications. It should follow the following format.
Command: This is <Handle> Requesting a Signals test, all operators check in, over.
Radio Operator 1: This is <Handle> checking in, over.
Radio Operator 2: This is <Handle> checking in, over.
Command: All signals confirmed, over.
PROTOCOL: BLACKOUT
A signal blackout is called whenever radio communications are believed to be compromised. Command calls a blackout, but any radio operator can do so if they have cause. Blackout is enforced until communication via another means is established between the calling unit and Command, or until Command repeals the blackout. A blackout should never include an authorization or reply code. Format is as follows.
Command: This is <Handle> calling for blackout. Do not reply, over.
All units should immediately turn off their radios and make contact by any other means (backup communications such as cell phones, or by physically being present with other members if nothing else)
(Signal Chart redacted)
thats a