Informal Duty to Intervene Policy - Protocol For Law Enforcement and Security Professionals
- William DeMuth
- 11 hours ago
- 3 min read
Everyone gets caught at the wrong moment. Stress, fatigue, and difficult people can push any officer past their best self. This protocol gives teammates a quiet, face-saving way to step in before a situation escalates using everyday-sounding language that only officers recognize. No formal write-up. No embarrassment. Just a teammate watching your back.
Core principles
Rank neutrality. Any officer regardless of rank may use a code phrase to signal concern. A junior officer may step in for a supervisor. Seniority does not override the protocol.
No-fault assumption. The signal is never a judgment of character. It means "I've got you" not "you're wrong." The receiving officer should stand down without shame.
Seamless handoff. The intervening officer takes over naturally so citizens perceive nothing unusual. The original officer steps back, takes a breath, and re-engages if and when appropriate.
No retaliation, ever. Using or receiving a code phrase carries zero professional consequence. Retaliating against a teammate who intervened is the only offense under this protocol.
Confidential within the team. Code phrases are internal only. They are never disclosed to the public, media, or in written reports unless required by law.
Code phrases — by escalation level
Three levels reflect how urgently a situation needs a handoff. Each sounds like routine radio or conversation to any bystander.
Level 1 — soft check "Did you catch that call from Sgt. Peters?" Tone is drifting. Pause and recalibrate. Intervener moves nearby. | Level 2 — step in "Hey, I've got this one -go ahead and clear." Handoff requested. Original officer disengages now. | Level 3 — immediate "Radio's been going - let me jump in here." Situation is escalating. Full, immediate handoff required. |
Phrase "Did you get that call from Sgt. Peters?" → Step back, I'll move in alongside you. | Level 2 Phrase "Hey, I've got this - go ahead and clear." → You're done here. I'm taking over fully. | Phrase "Radio's been going - let me jump in here." → Full handoff, right now. No hesitation. |
Phrase "Dispatch has something for you when you're done here." → Wrap this up calmly and exit. | Phrase "I know this address, let me take the lead." → Plausible reason given. Step aside naturally. | Phrase "I need you on the other side of the lot." → Physical removal with purpose. Follow immediately. |
Phrase "I can take notes on this one if you want." → I'm moving in. You lead less, I'll cover. | Phrase "Sarge wanted me to run point on this call." → Authority frame used. Disengage without question. |
How receiving officers respond
When you hear a code phrase accept it. Do not argue, question, or delay. A simple "copy" or a nod is all that is needed. Your teammate is doing their job and protecting you.
Step away with purpose move to a vehicle, attend to equipment, or address another task. Never walk away blank; give yourself and bystanders a reason.
After the scene is clear, a quick private debrief between the two officers is encouraged not required, but healthy. "You good?" is enough.
Rank neutrality in practice
Rank tells you who leads operations. This protocol exists outside that chain for one narrow purpose: preventing unprofessional conduct. A patrol officer may use a Level 2 phrase with a lieutenant. A sergeant may use one with a chief. The receiving officer regardless of rank is expected to honor the signal.
The intervening officer assumes full responsibility for the interaction from the moment of handoff. The original officer's prior conduct is not documented under this protocol only future behavior from that point forward matters.
Remember
This protocol is not a disciplinary tool. It does not replace formal use-of-force policies, misconduct reporting, or supervisor oversight. It is a human layer built on trust for the moments before things go wrong. Use it. Accept it. It means your team sees you as worth protecting.
