Key takeaways
- Agree a check-in interval per post and pin it in the site group.
- Each check-in is short: 'OK', a location pin, and anything unusual.
- The office owns the missed check-in procedure: call, escalate, send someone.
- The 🚨 alert notifies the whole group at once; the guard still calls the local emergency number.
- C Chat does not track location continuously; location is shared only when the guard sends it.
Night shifts at warehouses, construction sites, car parks and remote facilities often have one guard and nobody else for hours. If that guard falls on a patrol, is confronted by an intruder or has a medical problem, the only way anyone finds out is when the next shift arrives, unless there is a routine that makes silence noticeable. A check-in routine turns “no news” into a signal.
Why lone guard check-ins break down without a system
- Calls get skipped. Hourly phone calls to the office are tedious, so they stop happening after a few weeks.
- Nobody is watching the clock. A missed check-in only matters if someone is responsible for noticing it.
- No location. “I’m on patrol” doesn’t tell the office which part of a large site the guard is in.
- No escalation plan. When a check-in is missed, the office improvises.
The general approach for any lone worker is in lone worker check-ins by chat; this page adapts it to guard posts.
The workflow in C Chat
- At shift start the guard posts the first check-in in the site group with a location pin, using location sharing.
- At each interval the guard posts a short check-in: “OK – patrol north fence” plus a location pin.
- Anything unusual goes in the same message or a reply, with a photo if helpful. Real incidents get a full report as in guard incident reports.
- The office reacts to each check-in so the guard knows it was seen.
- If a check-in is missed, the office follows the pinned procedure.
- In an emergency the guard taps the one-tap emergency alert, which notifies the whole group, and calls the local emergency number.
Group setup and message template
Check-ins go in the site group, where the office is already a member. With the CGuard Pro integration, that group contains the guards on duty, the office and the client, and guards off duty can’t read it. Clients often find check-ins reassuring; if they prefer less detail, the office can summarize as described in security client updates.
Pin this in the site group:
LONE GUARD ROUTINE – [site] Interval: every [60] min between [22:00] and [06:00] Check-in: “OK” + location pin + anything unusual Missed check-in (office): +5 min message · +10 min call · +15 min call supervisor · +20 min dispatch / call emergency number Emergency: 🚨 alert + call the local emergency number
Large events with roaming guards use a similar rhythm at a bigger scale; see event security coordination.
Roles, oversight and records
The office or dispatcher owns the check-in monitoring for each shift; write their name in the shift change report. Supervisors are team admins.
Messages, including location pins and photos, are encrypted in transit with TLS and at rest with AES-256 using per-organization keys. Security companies using CGuard Pro can audit groups and security-related chats with guards and office, so the check-in history is available if an incident is reviewed. Direct messages between people stay private.
When a guard leaves the company, their access ends instantly with CGuard Pro and their check-in schedule must be handed over; see removing former guards.
Common mistakes to avoid
- No one assigned to watch. A check-in routine without an office owner is decoration.
- Intervals nobody can keep. Too frequent and guards stop; too rare and help comes late.
- Relying on the chat as an alarm system. It is a messaging tool; follow your company’s safety procedures and local regulations for lone workers.
- Using check-ins to track people off shift. Location is shared only during work, and only when the guard sends it.
Other sectors with lone workers apply the same pattern: private investigators, energy and utilities field crews and night staff at condos and HOAs.
Getting started
Choose the interval for each post, pin the routine in the site group, assign an office owner per shift and run a test night. With CGuard Pro, site groups are already set up with on-duty guards and the office. Start at getcchat.com/c.
Frequently asked questions
How often should a lone guard check in?
It depends on the site's risk and your company policy. Many companies use hourly check-ins at night and shorter intervals for higher-risk posts. Whatever you choose, write it down, pin it in the site group and make sure the office can actually monitor it.
Does C Chat track the guard's location automatically?
No. C Chat does not do continuous GPS tracking. The guard shares a location pin in a message when checking in. That gives the office a point at each check-in time without tracking the guard all shift.
What happens if a guard misses a check-in?
C Chat does not raise automatic missed check-in alarms, so the office needs a procedure: for example, message the guard after five minutes, call after ten, then call the supervisor and dispatch someone. Pin that procedure so everyone knows it.
What does the 🚨 alert do?
It sends a one-tap emergency alert to the group, so the office and anyone else in the site group are notified at once. It does not contact emergency services; the guard or office must call the local emergency number.