1. Observe
Send initial details quickly and discreetly.
Build fast awareness without creating loud, unfocused chatter.
Use this security BOLO template for church safety teams: specific details, discreet routing, and a clear observe - route - resolve sequence that keeps worship as steady as possible.
Copy these fields into a printable card, team binder, or structured SMS workflow. Specificity beats dramatic language.
Send initial details quickly and discreetly.
Supervisor targets alerts to relevant on-duty roles.
Review timeline and follow-up actions after service.
A BOLO is only as good as the specificity and restraint of the first message. Clothing, direction of travel, and behavior beat adjectives that sound alarming but do not help responders converge. Supervisors should have a practiced habit: confirm who is moving, who is watching exits, and who stays with the congregation so worship stays steady when possible.
After resolution, capture what changed: Was law enforcement involved? Did children's ministry need a quiet heads-up? Was parking rerouted? Those answers belong in structured follow-up, not in a long debrief thread. Compare watchlist governance and parking escalation when your BOLO overlaps perimeter or sensitive populations.
Include time observed, last known location, clothing and distinguishing features, direction of travel, behavior of concern, who is responding, and what help is needed.
Use a discreet channel with supervisor routing. Specific details and restraint matter more than volume. Confirm who is moving, who is watching exits, and who stays with the congregation.
Yes. Use the fields above as a printable checklist or copy them into your structured SMS workflow so volunteers send consistent reports.
SMS thread demo: BOLO workflow on operational templates (Casey, Sam, Lee phones
with WATCHLIST and @LEO).
Watchlist add-on (optional): Screenshots, Ask Supervisor flow, and supervisor alert copy live on watchlist access control. Module definition: premium add-ons.