📻 Radio Communications & Protocols

In situations where phones fail, surveillance increases, or coordination must stay fast and local, radios become essential. This course covers how to use two-way radios (walkie-talkies), keep communication secure, and build pod-level protocols.

---

Why Use Radios?

• 📴 Phone service may be down or compromised
• 🔐 Radios reduce reliance on surveillance-prone platforms
• 🧭 Radios work peer-to-peer — no towers or accounts needed

---

Types of Radios

Type	Range	License Needed?	Best For
FRS	0.5–2 miles	No	Short-range pod comms
GMRS	1–5+ miles	Yes (FCC)	Neighborhood coordination
HAM	2–100+ miles	Yes + Exam	Long-distance or disaster ops
Mesh (LoRa)	0.5–3 miles/node	No	Text-only, encrypted mesh networks

---

Basic Radio Etiquette

• 🎯 Keep messages short and clear
• 🚫 No full names, addresses, or legal risk info over air
• 🎙 Always identify yourself (e.g., “Blue 3 to Red 1”)

---

Sample Call Protocol

[Red 1]: “Blue 3 to Red 1 — eyes on ICE near 5th and Mission.”
[Blue 3]: “Copy. Heading that way. ETA 3 minutes.”
[Red 1]: “Stay in view, no contact. Will update.”
[Blue 3]: “Understood. Blue 3 out.”

---

Channel Protocol

• Choose a primary channel before deployment
• Always agree on backup channels (e.g., “If jammed, switch to Ch. 6”)
• Keep chatter minimal on shared channels — move to secondary if needed

---

Callsigns, Codewords & Pre-Arranged Phrasing

Strong radio discipline relies on clarity, privacy, and consistency. Here’s how to set yours up.

---

📛 Choosing Callsigns

Use descriptive but anonymous identifiers. A good callsign is short, memorable, and doesn’t reveal legal identity or personal details.

Best practices:

• Use colors + numbers for roles (e.g., “Blue 3” = Legal Observer)
• Avoid initials, birth years, or anything personally identifying
• Assign backups in case of radio handoff or tech failure

Example Pod Map:

Role	Callsign	Backup Callsign
Field Lead	Red 1	Red 5
Legal Observer	Blue 2	Blue 4
Care Station	Green 3	Green 7
Rideshare Lead	Yellow 6	Yellow 9

---

🗣️ Using Codewords

Assume radios are being listened to. Use codewords to reduce risk and simplify decisions.

Replace sensitive terms with neutral or benign alternatives.

Sensitive Info	Suggested Codeword	Notes
ICE agent presence	“Visitors”	Avoid “ICE” or “police” over air
Immigration van	“Grey box”	Refers to surveillance transport
Arrest in progress	“Package moving”	Keep it calm and unclear
Location compromised	“Flooded”	Evacuate that area
Need for backup	“Send a jacket”	Use code instead of “help!”

---

🔑 Pre-Arranged Phrasing

Agree on specific questions, responses, and alert phrases before the action. This reduces confusion and stress.

Examples:

• “Check pulse on Blue 4” = “Is Blue 4 still active and safe?”
• “Grey box circling” = “Unmarked vehicle is doing surveillance”
• “Transfer complete” = “Person has safely exited the situation”
• “Switch water” = “Move to backup channel”

Practice these in your pod. Adjust based on comfort and clarity.

---

Drill It Before It’s Real

Set up practice scenarios using only radios and code. Then debrief:

• Did everyone understand the codes?
• Did it feel natural or confusing?
• What would improve clarity without compromising safety?

Drills make discipline second nature. Confidence in language = confidence in the field.

---

Example Channel Plan

Channel	Use
1	Field Ops (Main)
2	Care & Logistics
3	Emergency / Backup
4	Training & Drills

---

Encryption & Privacy Tips

• FRS/GMRS radios are not encrypted — assume anything you say is public
• Use codewords or pre-arranged phrasing for sensitive situations
• Avoid saying “ICE” or specific names — use phrases like “visitor” or “grey van”

---

Hardware Setup

🛠 Before using radios:

• Charge fully (bring spares/batteries)
• Test range in your area
• Label each radio with callsign
• Carry headphones for stealth

---

Radio Drills

Practice builds confidence. Run pod drills monthly:

• Silent check-in (“Tap twice on mic every 5 minutes”)
• Relay practice across terrain
• Emergency “panic” phrase test

---

Redundancy Plans

Always have backup methods:

• Text trees / Signal groups
• Flyers with QR codes for regrouping
• Location meet points (“If all fails, meet at Elm & 14th at 4pm”)

---

Final Tips

• Radios are tools, not magic — they work best with protocols and prep
• Teach others in your pod how to use and troubleshoot them
• Update channel/callsign plans every 1–2 months to stay adaptable

---

---