Key takeaways
- Post the shift change report in the site group, not in a direct message to the next guard.
- Cover post status, keys and equipment, alarms, open issues and client instructions.
- The relieving guard replies to accept the post; the office sees the exchange.
- With CGuard Pro, off-duty guards can't read site groups and fired guards are removed instantly.
- The security company can audit groups and security-related chats with guards and office.
Guard posts run around the clock, and every relief is a point where something can slip: a key that wasn’t counted, a contractor still on site, a client instruction from the afternoon that the night guard never heard. Most security companies already ask for a shift change report. The problem is where it ends up — a paper log at the post, a text to the next guard, or nowhere.
Why guard shift handover breaks down without a system
- Reports go guard-to-guard. A text from one guard to the next is invisible to the office and the client.
- Paper logs stay at the post. Supervisors read them on their next visit, days later.
- Personal groups include the wrong people. Guards who moved to another site, or left the company, still read the post’s details.
- No proof of the relief. If the incoming guard arrived late, nobody can say when the post was actually handed over.
The general version of this problem is in shift handover communication; security posts add keys, alarms and client orders. See also secure messaging for security companies.
The workflow in C Chat
- The site group is ready before the shift. With the CGuard Pro integration, it contains the guards on duty, the office and the client.
- The outgoing guard posts the report ten minutes before relief, using the template below. Photos of the key cabinet or a damaged gate go with it.
- The relieving guard checks and replies: “Post accepted, keys 12/12, alarm armed.” That reply is the time-stamped handover.
- Exceptions go up immediately. If something doesn’t match, the guard replies in the same thread and the office sees it.
- Off duty, the guard loses access. With on-duty access, the outgoing guard can no longer read the site group after the shift.
Incidents that happened during the shift get their own report rather than a line in the handover; see guard incident reports.
Group setup and message template
One group per site or post. For large sites with several posts (gate, lobby, patrol), you can create a group per post and keep a site-wide group for the supervisor. Pin the post orders, emergency contacts and the template.
SHIFT CHANGE – [site / post] – [date, time] Post status: normal / issues Keys & equipment: [count], radio, flashlight, vehicle Alarms & access: armed/disarmed zones, faults On site now: visitors, contractors, cleaning crew Open issues: … (who follows up) Client instructions: new / unchanged Photos: attached
Night posts where a guard works alone benefit from a check-in routine on top of the handover; see lone guard check-ins.
Roles, oversight and records
The security company owns the team. Operations managers and supervisors are admins. With CGuard Pro, membership of site groups is driven by the schedule, so the admin doesn’t need to add and remove guards for every shift.
C Chat uses TLS in transit and AES-256 at rest with per-organization keys. Under its auditable model, the security company can audit groups and security-related chats with guards and the office, which matters when a client asks who was on post at 2 a.m. or what was reported at relief. Direct messages between people stay private. When a guard leaves the company, they are removed instantly; the details are in removing former guards from site chats.
Clients can follow the post in the site group or through the Mi Seguridad app. Keeping them informed without overloading them is covered in security client updates.
Common mistakes to avoid
- Handover by direct message. The office and the client never see it. Use the site group.
- “All normal” with no detail. Keys and alarms should always be counted and stated.
- Mixing incidents into the handover. Post incidents separately so they can be found and reviewed.
- One group for all sites. Guards end up reading other clients’ information.
Residential sites, garages and care facilities have their own twists; see condos and HOAs, parking operators and senior care facilities.
Getting started
If your company uses CGuard Pro, enable the integration and site groups are created with on-duty guards, office and client. Otherwise, create a team, add one group per site and invite guards by QR code. Pin the template and post orders, then start at getcchat.com/c.
Frequently asked questions
What goes in a security guard shift change report?
The post's status (normal or not), keys, radios and equipment handed over, alarm and access-control state, open issues or suspicious activity, visitors or contractors still on site, and any new instructions from the client or supervisor. Photos help for anything physical.
What happens if the relieving guard doesn't show up?
The outgoing guard posts that in the site group and stays on post according to your company procedure. Because the office is in the group, the dispatcher or supervisor sees the gap immediately and can arrange cover.
Can a guard read the site group on their day off?
Not when the company uses CGuard Pro. Site groups follow the schedule, so guards can read a site group only while on duty. Without CGuard Pro, the admin manages group membership manually.
Does the client see the shift change report?
If the client is a member of the site group, yes. Many companies prefer this because it shows the post is covered. If you want the client to see only summaries, keep the client in a separate group and post updates there.