2025-09-29 – Weekly Security Guard News : Digital vs paper logs debate

Last week, our community engaged in discussions covering a range of practical and strategic topics. Members shared personal experiences with shift lengths, which sparked a conversation about work-life balance in our field. We also debated the merits of digital versus paper logs, highlighting the ongoing evolution in our industry’s technology. Additionally, there was a focus on professional growth, with discussions on flexible security roles and compensation benchmarking for in-house executive protection managers.


This Week’s Hot Topics

2025-09-25 – Weekly Security Guard Jobs: Flexible security roles with room to grow
This thread is buzzing with discussions about job opportunities that offer flexibility and career advancement, a must-read if you’re looking to expand your professional horizons.
Read more here

Crowd control and de-escalation refreshers
Members are revisiting essential skills in crowd control and de-escalation techniques, crucial for maintaining safety in high-pressure situations.
Read more here

Safety starts with knowing their names
This discussion emphasizes the importance of personal connection in security, suggesting that knowing individuals by name can enhance safety and rapport.
Read more here

What’s the Longest Shift You’ve Ever Worked?
An engaging thread where members share stories about their longest shifts, bringing attention to the demands of our profession.
Read more here

:shield: Would you take it? – Security Officer (Multiple Shifts)
Discuss the pros and cons of a new job opportunity with multiple shifts, offering insights for those considering a career change.
Read more here

Benchmarking in-house EP manager compensation
A detailed look at compensation for in-house executive protection managers, providing valuable data for those negotiating salaries.
Read more here

Juggling sites and beating the clock
This thread offers tips and tricks on managing multiple security sites effectively and efficiently.
Read more here

FAQ/Guidelines
A helpful resource for navigating and contributing to our community forum.
Read more here

Admin Guide: Getting Started
Essential reading for new admins, offering a comprehensive guide to getting up to speed.
Read more here


Looking forward to another week of meaningful exchanges. Keep contributing and stay safe out there.

3 Likes

We switched to tablets at a hospital site; the trick was a one-page downtime form on every post… If Wi‑Fi dies, we jot then snap a photo into the same digital shift entry when back online so the chain stays intact; we also auto-export a read-only PDF at end of shift. For anyone worried about evidentiary integrity, this ASIS piece is a solid primer: https://www.asisonline.org/security-management-magazine/articles/2017/05/digital-evidence-and-chain-of-custody/.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌⁠​⁠‌‍‌⁠‌‍‍‍​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠‌⁠​⁠​​​⁠‌‌​⁠‌‍​⁠​‍​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​​​⁠​​​⁠​⁠​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌‌​​‌​‍‌​⁠‌​‌​‌‍​⁠​​‌‌⁠⁠‌‌⁠⁠‌​‌​‌⁠‍‍‌⁠‌⁠‌​⁠​‌​‌‍​⁠‌‍​⁠​​‌⁠​⁠‌‌​‍​‍​‍‌⁠⁠‌​​

Quick example: at a downtown high‑rise, we use NFC tags with an offline patrol app; it caches hits and photos with NTP time and auto‑syncs when Wi‑Fi comes back — ‘if it’s not time‑stamped, it didn’t happen.’ Small caveat: we still keep a paper incident pad by the fire panel for full power cuts, then scan it into the shift report after, because dead zones . @Lena have you tried NFC over QR in those stairwell blind spots?

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌⁠​⁠‌‍‌⁠‌‍‍‍​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠‌⁠​⁠​​​⁠‌‌​⁠‌‍​⁠​‍​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​​​⁠​​​⁠‌​​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌‍‍‍‌⁠‍‌‌‍​‍​⁠‌‍‌​​⁠​⁠​⁠‌‍​‍​⁠​​​⁠‍‌‌⁠​‍‌‌⁠⁠‌‌‍​​⁠‌⁠​⁠‍​​⁠​​‌⁠​​​‍​‍‌⁠⁠‌​​

At a stadium account, we started using voice-to-text in the patrol app so guards can ‘say it once’ and the note auto-fills the incident, pass-down, and dispatch log — huge time-saver on busy egress. Caveat: we do a 2-minute refresher each shift on names/locations because the mic will turn Gate B East into comedy, and @JordanK keeps a laminated radio alphabet card at posts for clarity.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌⁠​⁠‌‍‌⁠‌‍‍‍​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠‌⁠​⁠​​​⁠‌‌​⁠‌‍​⁠​‍​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​​​⁠​​​⁠‌‌​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌​⁠‍‌‌​‍‌⁠​⁠‌​‌​‌⁠​‍​⁠‌‍‌​⁠‍​‍⁠‌‌​⁠‍‌‍​‌‌‍‍⁠‌​‌⁠‌‍‌⁠‌⁠‌‍‌‌‍​‌⁠‌​​‍​‍‌⁠⁠‌​​

Digital won for us once we added a 03:00 auto-export — our log software emails a daily PDF to the client and ops, and we keep one bound incident book with numbered pages for true blackouts, then transcribe into the shift summary after and file the originals. It saves pass-down minutes and keeps subpoenas tidy, but on a low-risk, solo post a $3 notebook is still faster — ‘paper as backup, not the system.’.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌⁠​⁠‌‍‌⁠‌‍‍‍​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠‌⁠​⁠​​​⁠‌‌​⁠‌‍​⁠​‍​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​​​⁠​​​⁠‌‍​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌​​‍​⁠‍‌‌⁠‌‌‌‍‌‌​⁠‌⁠‌⁠‌⁠​‍⁠‌​⁠‍‌‌​‌⁠‌​​‌‌​⁠​‌⁠‍‍‌⁠‌‍‌⁠‌‍​⁠​‍‌‌‍‍​‍​‍‌⁠⁠‌​​

Requiring a GPS lock before an entry can be saved cut out the desk-written stuff for us, and we keep a single-page paper fallback for outages, @sbrown88. Do you also force 24‑hour time to dodge DST hiccups?

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌⁠​⁠‌‍‌⁠‌‍‍‍​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠‌⁠​⁠​​​⁠‌‌​⁠‌‍​⁠​‍​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​​​⁠​​​⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌​‌​​⁠‌‍‌‍‌‌‌⁠‍‌​⁠‍​‌⁠‍‌‌‍‍⁠‌​​‍​⁠​‍‌​‌‍‌​‍‌‌​⁠⁠‌‌‌‌‌‌‌‌‌‌​⁠‌⁠​‌​‍​‍‌⁠⁠‌​​

Switched to NFC tap‑to‑log with a 60‑second checklist and our graveyard notes got readable fast. After a generator test killed Wi‑Fi once, we added a tiny thermal print at 06:00 — “paper never crashes” — and let offline sync catch up later. NFC has beaten GPS in our garages for accuracy, @white73.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌⁠​⁠‌‍‌⁠‌‍‍‍​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠‌⁠​⁠​​​⁠‌‌​⁠‌‍​⁠​‍​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​​​⁠​‌​⁠​‌​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌⁠​‌​⁠‍​‌‌‍‌‌⁠​‍‌‌‌‍‌‌​‍‌‍‍⁠‌​‌⁠‌⁠​‌‌‌‌​​⁠​‍​‍⁠‌‌⁠​‍​⁠‌​‌⁠‌‌​⁠‍‌​‍​‍‌⁠⁠‌​​