Legal Observer and Medic Check-in Protocols at Protests
Role-specific protocols for support teams: different schedules, one shared coordinator. Set them up so a missing person is noticed within minutes.
On this page
TL;DR
Legal observers and street medics at protests operate under different risk profiles but need to report to the same coordination contact. Each observer and medic runs their own heartbeat with the same coordinator as contact, so each role keeps its own cadence (observers every 45 minutes, medics every 60) and every missed check-in alerts that coordinator, who opens the message with their PIN and can act immediately with the role, assigned zone, buddy, and legal-support contacts written in it.
Who is this for?
Legal observers, street medics, and coordination leads supporting lawful demonstrations. Also useful for any team deploying multiple people in different roles at large public events where communication may be unreliable.
Why Do Support Teams Need Dedicated Check-in Protocols?
Support teams at public demonstrations face a coordination problem that scales with group size. Legal observers document at arrest lines. Street medics move between treatment zones. Both roles require freedom of movement, and both become invisible to their team the moment cell networks degrade or crowds surge.
The National Lawyers Guild trains observers to work in pairs, but pairs get separated. A medic who follows a patient to a hospital may drop off comms for hours. A structured check-in protocol transforms a missing person from an hours-long mystery into a minutes-long response.
What Are the Key Risks for Support Teams at Protests?
Overlapping but distinct hazards. A good protocol accounts for each.
What Protocols Should Support Teams Follow at Events?
Four protocols, from first deployment to final all-clear.
01
Role-based check-in cadence
Observers and medics need different intervals. Observers check in on a fixed schedule, while medics check in after each treatment or relocation.
Setup · Heartbeat: 45 minutes for observers, 60 minutes for medics. Both report to the same coordination contact.
02
Positional status update
The check-in itself is one tap. What carries the detail is the emergency message you write before deploying: role, assigned zone, buddy.
Setup · Alert message: "[Role] [Name], zone [Location]. Buddy: [Name]. Legal hotline: [number]". One tap confirms. A miss alerts the coordinator, who opens that message with their PIN.
03
Detention / separation alert
A missed check-in automatically alerts the coordinator, and your message tells them the role, zone, and buddy.
Setup · Include the NLG number or legal-support hotline in the emergency message so the coordinator can act immediately.
04
End-of-event all-clear
A final check-in confirms every team member is accounted for. The coordinator doesn't stand down until all roles confirm.
Setup · Schedule one final check-in 30 minutes after the planned end time.
Multi-Person Protocol Coordination
Separate protocols on different cadences, and one coordination contact who receives all alerts.
| Role | Cadence | Zone | Buddy | Status |
|---|---|---|---|---|
| Legal Observer A | Every 45 min | Intersection 1 | Observer B | On schedule |
| Legal Observer B | Every 45 min | Intersection 2 | Observer A | Overdue, 12 min |
| Medic C | Every 60 min | Mobile, rear | Medic D | On schedule |
How to Set Up a Team Check-in Protocol
Four steps to configure before deployment.
Assign roles and pair buddies
Designate each person as legal observer or medic. Pair everyone with a buddy from the same role. Record pairs in a shared document.
Set role-specific check-in intervals
Observers: a heartbeat with a 45-minute interval. Medics: 60 minutes. Each tap resets the timer, and the alert fires once an interval passes without one, after a grace of at most 30 minutes, so the interval has to absorb temporary cell congestion. Delayed Delivery is not available on a heartbeat, and the optional grace after each due time defaults to none, so put the margin in the interval.
Write your emergency message
Include your name, role, assigned zone, buddy's name, and the legal-support hotline number. Example: "Observer [Name] missed check-in. Assigned zone: [intersection]. Buddy: [Name]. NLG hotline: [number]."
Run a pre-event dry run
Have every team member activate their protocol and confirm once. The coordinator verifies that every confirmation email arrives. On the Survival plan ($9.99/mo), SMS alerts reach the coordinator even if cell data is throttled.