Key takeaways
- Use a pinned incident template so every guard reports the same fields.
- Attach photos, short videos, a location pin or a voice note as evidence (files up to 25 MB).
- Post incidents in the site group so the office and client see them at once.
- Supervisors reply in the same thread with instructions and follow-up.
- The security company can audit and export group conversations for client reports.
An incident report is only as useful as the moment it reaches the people who need it. A detailed report written at the end of the shift, on paper, can’t help the supervisor decide whether to send backup. A rushed text with no details can’t be used in the client’s monthly review. The goal is a fast first report with enough structure to be useful later.
Why guard incident reports break down without a system
- Reports arrive late. Paper forms are filled in at the end of the shift, hours after the event.
- Every guard writes differently. Key fields like the exact location or who was notified are often missing.
- Evidence lives on personal phones. Photos taken by a guard leave with the guard.
- No single history. The client asks for last month’s incidents and the office has to reconstruct them from texts and calls.
For the broader context, see secure messaging for security companies.
The workflow in C Chat
- Make it safe first. If there is danger, the guard calls the local emergency number and, if needed, sends the one-tap 🚨 alert to the site group.
- Capture evidence. Photos or a short video of the scene, damage or vehicle, taken directly in the chat so they land in the company’s group.
- Post the report using the pinned template. A location pin helps on large sites or patrol routes.
- Supervisor responds in the same thread with instructions: stay on post, wait for police, call the client contact.
- Close the thread with a follow-up reply once the situation is resolved: police report number, repairs requested, client informed.
If typing is hard in the moment, a voice note with the key facts is better than waiting; the guard can add the written fields once things are calm.
Group setup and message template
Incidents go in the site group where the guards on duty, the office and the client already are. With the CGuard Pro integration that group is created and maintained from the schedule. Pin this template:
INCIDENT – [type: intrusion / theft / damage / medical / fire / disturbance / other] When: [date, time] Where: [site, exact spot] + location pin What happened: [facts only] People involved: [descriptions] Action taken: … Notified: police (report #) / client / supervisor Evidence: photos / video / voice note Follow-up needed: …
The difference with a shift change report matters: the handover describes the state of the post, the incident report describes one event. See guard shift handover for the handover format.
Roles, oversight and records
Supervisors and operations managers are admins; the company owns the team. Guards post; the office replies; the client reads, and can ask questions in the same thread.
C Chat protects messages with TLS in transit and AES-256 at rest under per-organization keys. Security companies using CGuard Pro can audit groups and security-related chats with guards and office, and owners and admins can export group conversations. That export is the raw material for monthly client reports; the process is described in client reporting for security companies. Direct messages between people remain private.
When a guard who filed reports leaves the company, the reports stay in the group history while the guard’s access ends; see removing former guards.
Common mistakes to avoid
- Opinions instead of facts. “Suspicious guy” is less useful than “man, about 30, grey hoodie, tried the side door twice”.
- Photos sent by direct message to the supervisor. They never reach the site group or the client record.
- Editing the original report. Add corrections as replies to keep the history clear.
- Forgetting to close. An incident without a follow-up reply looks unresolved in every later review.
If you are comparing approaches, see how chat compares with two-way radio, Zello push-to-talk and other guard communication apps. Keeping the client informed is covered in security client updates.
Getting started
Enable the CGuard Pro integration or create a team with one group per site, pin the incident template and run a short drill so every guard posts a test report with a photo. Start at getcchat.com/c.
Frequently asked questions
What should a security guard incident report include?
Date and time, exact location, what happened in factual terms, people involved (described, not judged), actions taken, who was notified (police, client, supervisor), evidence attached and any follow-up needed. Stick to facts the guard saw or heard.
Is a chat message valid as an incident report?
It depends on your contract and local requirements. Many companies use the chat report as the first notice and then copy it into a formal report. Because group history can be exported, the original message and photos remain available as a record.
Can a guard edit an incident report after posting it?
Messages can be edited or deleted in C Chat. For incident reports, a safer practice is to add corrections as a reply ('Correction: time was 02:15') so the original and the change are both visible in the thread.
Should guards call the police or post in the chat first?
When there is danger to people or a crime in progress, the guard calls the local emergency number first, following company procedure. The 🚨 alert and the incident report in the group come after or in parallel, never instead.