Neighborhood Net Control SOP
This Standard Operating Procedure (SOP) is built for families and small groups running a simple neighborhood net for emergencies. It reduces confusion by giving one person clear authority, a predictable flow, and short scripts anyone can follow.
What This SOP Covers
Neighborhood Net Control (NCS) is the person who runs the net. Their job is not to solve every problem—it’s to move information, track needs, and prevent chaos on the channel.
When to use it
- Storms, power outages, civil disruptions, missing persons, medical coordination.
- Any time multiple households need updates and you want one channel for shared awareness.
What “good net control” looks like
- Short transmissions, clear priority, one person talking at a time.
- Consistent check-in order and a simple message format.
- Logs that make sense hours later.
Roles and Responsibilities
Net Control (NCS)
- Opens/closes the net and sets rules.
- Calls stations in order; manages priorities.
- Tracks who is up, who is out, and what’s needed.
Logger
- Writes down check-ins, time, and key messages.
- Records actions assigned and follow-ups needed.
- Can be the NCS if you’re short-handed.
Stations (Households)
- Follow the check-in format.
- Keep transmissions short.
- Move detailed talk off-net when directed.
Rule of thumb: NCS runs the channel. Everyone else helps by being brief, patient, and predictable.
SOP: Step-by-Step Neighborhood Net Control
1) Pre-net setup (2–5 minutes)
- Confirm primary channel and backup channel.
- Confirm net name and the check-in window (example: every hour at :10 for 10 minutes).
- Get your log ready (paper is fine): time, station, status, needs, actions.
- Set a priority rule: Emergency ? Urgent ? Routine.
- If possible, assign a secondary (backup NCS) in case you lose power or must step away.
2) Open the net
Use the opening script below, then pause 3–5 seconds to listen for urgent traffic.
Opening Script: “This is Net Control for the Neighborhood Net. Stand by for priority traffic. Emergency or urgent stations, call now.”
3) Take priority traffic first
- If anyone calls with Emergency, stop everything and handle it.
- If it’s Urgent (time-sensitive but not life-threatening), handle it next.
- Anything else is Routine and waits for check-in order.
4) Run check-ins (structured, predictable)
Choose one order and stick to it: by street, by household number, or a simple list you keep in the log.
| Item | What to say |
|---|---|
| Who you are | Household name or call sign (pick one and be consistent) |
| Status | OK / Monitoring / Need assistance / Out of service |
| People | “All accounted for” or “Need wellness check at…” |
| Needs | Water, meds, transport, info request, etc. |
| Notes | Short: hazards, blocked roads, generator status, etc. |
Check-in Script for stations: “[House] checking in. Status OK. People all accounted. Needs none. Notes tree down at Oak & 3rd.”
5) Move details off-net
If two stations need to coordinate, keep the main channel clear. Give them a clear instruction and a time to come back with results.
NCS Script: “Stations A and B, move to backup channel for details. Return here in 5 minutes with a one-sentence update.”
6) Close or suspend the net
- Close when the check-in window ends, or when there is no traffic.
- Announce the next scheduled check-in time.
Closing Script: “No further traffic heard. Neighborhood Net is closed until the next check-in at [time]. Monitor this channel for emergency traffic. Net Control clear.”
Checklists
Net Control checklist
- Primary/backup channel confirmed.
- Log ready: time, station, status, needs, actions.
- Priority rule stated: Emergency ? Urgent ? Routine.
- Check-in order set (street/list) and used consistently.
- Off-net coordination directed when needed.
- Next check-in time announced.
Household checklist (before check-in)
- Radio on, volume set, battery check done.
- Know your status: OK / Monitoring / Need assistance.
- Know your key notes: hazards, blocked routes, medical issues.
- One person speaks; others stay quiet.
- Keep it short—save details for off-net.
Scripts and Templates
Priority traffic template
Use this exact order so NCS can log it fast.
- Type: Emergency or Urgent
- Location: address / cross street
- Situation: one sentence
- Need: what you want done
- Best contact: who to call back
Example: “Emergency. 214 Oak Street. Adult collapsed, not responsive. Need EMS. Call back Oak House.”
NCS log template (paper)
Draw columns like this. Keep it simple.
| Time | Station | Status | Needs | Action / Follow-up |
|---|---|---|---|---|
| 10:12 | Oak House | OK | None | Tree down noted |
| 10:14 | Pine House | Need assistance | Water | Route check off-net; report 10:25 |
“Hold the channel” script (when people talk over each other)
“All stations, stand by. One at a time. Emergency traffic only. Stations calling, wait for Net Control to recognize you.”
Common Mistakes to Avoid
Net Control mistakes
- Letting the channel turn into a chat. Redirect details off-net.
- No check-in order. People will jump in randomly under stress.
- Not stating priority rules. Say it out loud every net.
- Skipping the log. You will forget details within an hour.
Household mistakes
- Long stories. Give one sentence; offer details off-net.
- Multiple people talking. Pick one speaker per household.
- “Any updates?” every two minutes. Wait for the scheduled check-in.
- Using unclear location info. Give address/cross street first.
Quick Reference (Print This)
Priority order
- Emergency: life safety now.
- Urgent: time-sensitive, could become dangerous.
- Routine: updates, requests, general info.
Net flow
- Open net ? listen for priority traffic.
- Handle Emergency ? Urgent.
- Run check-ins in order.
- Move details off-net and set return time.
- Summarize actions ? announce next check-in ? close.
Shortest possible check-in
“[House] check-in. Status OK. Needs none. Notes none.”
Simple Glossary
Net Control (NCS)
The station running the net and managing who talks and when.
Off-net
Moving detailed coordination to another channel so the main channel stays clear.
Priority traffic
Emergency or urgent messages that must be handled before routine updates.
Log
A written record of check-ins, needs, and actions—your memory backup.
Training tip: Run a 10-minute practice net on a calm weekend. The first time you use this should not be during a real emergency.
