Last week, our community delved into some intriguing discussions around practical challenges and technological advancements in the security field. Members shared experiences and strategies for managing unexpected incidents and discussed the evolving tools that aid in security operations. A recurring theme was the importance of efficient communication and response during critical moments. Several threads also explored innovative training techniques that aim to reduce operational risks and enhance safety.
This Week’s Hot Topics
First 10 minutes incident card
This discussion highlights the critical procedures and checklists that can make or break incident response in the first few minutes. It’s a must-read for anyone looking to refine their immediate action plans. Read more here
Dispatch thinks I can teleport
A light-hearted but revealing conversation about the unrealistic expectations sometimes placed on security personnel. It underscores the need for practical communication and planning. Read more here
Strangest front desk lost-and-found
This thread shares amusing and unusual lost-and-found stories, highlighting the unpredictable nature of front desk duties. Read more here
Quick wins for lines and evacuations
Explore simple yet effective strategies for managing crowds and ensuring smooth evacuations. This is essential reading for enhancing on-site safety. Read more here
From watchman’s clock to SIEM
Dive into the evolution of security monitoring from traditional watchman’s clocks to modern SIEM systems. This is a fascinating look at technological progress in our field. Read more here
DMR radios vs LTE PTT under load
Compare the performance of DMR radios and LTE PTT systems under high traffic conditions. This discussion is crucial for those evaluating communication tools. Read more here
Pocket de-escalation cards for Code Gray
This thread discusses the effectiveness of pocket-sized reference cards for de-escalation techniques during Code Gray situations. Read more here
When a visitor refuses to leave
Insights into handling situations where visitors overstay their welcome, with practical advice and shared experiences from the community. Read more here
Training that actually reduces shrink
Discover training methods that have proven effective in reducing shrinkage and improving asset protection. Read more here
Managing the exit surge, not just entry
A look into techniques for controlling exit surges, which can often be more challenging than managing entries. Read more here
That’s all for this week’s digest. I hope these discussions provide valuable takeaways for your daily operations and spark new ideas for improving security practices. Until next time, take care and stay vigilant.
And at big sites, we tag hotspots with what3words and keep a shared note of the three-word codes, so when things kick off we radio “Location first, hazard second, headcount third” and drop the link to @DispatchOps; just make sure your center supports https://what3words.com and keep a low-tech backup card for dead zones — anyone else using this?
Quick example: we use a 15-second radio SITREP — “location, hazard, action, help needed” — and mirror it to a shared chat; if no ack in 60 seconds, it auto-escalates by SMS to the on-call. Not teleportation, but it shaved minutes off; @luisa_m93 your what3words pairs well with this — anyone else using auto-ack timers?
But at our stadium gigs, we label stairwells and gates with big alphanumeric panels (e.g., ‘G12-North’), and during an incident we call a 60-second ‘radio red’ where only the lead speaks — no teleporters yet, but it slashes confusion. @sarah.connors83 your SITREP flow fits, though we also keep a laminated ‘dead radio plan’ by every AED with key numbers in case the net goes down.
We issue pocket site maps with what3words squares and a one-line ‘dead-comms plan’ (primary/alt rally spots); in a spike we just drop the 3-word and move — no debate. @cjackson your SITREP flow is solid; just reprint after layout changes or it bites you. Keeps dispatch sane until they invent teleportation — https://what3words.com.
And we killed the “warp‑speed” ETAs by having dispatch do a 60‑second traffic/weather look and ask, “what can we reach in 2 minutes with today’s staffing?” It works, but only if supervisors keep unit status and closures live; otherwise the fantasy just moves. @anderson74 do you run a quick “reality check” before promising arrivals?
Quick example: we set geofenced staging bubbles around busy entrances; if a unit enters one, their status flips to ‘nearby’ and dispatch pulls from that list first instead of guessing, @ardy. When CAD stumbles, a lightweight web map fed by radio check-ins keeps the bubbles alive — no warp drive needed. Caveat: bubble size needs site-by-site tuning or you’ll miss someone who’s close but just outside the line.