Key takeaways
- Write the report as soon as the scene is safe; memory fades within hours.
- Cover who, what, where, when, actions taken and follow-up needed.
- Separate facts you observed from what others told you and from your opinion.
- Photos with a short caption are worth more than a paragraph of description.
- Post the report in the right group so it is searchable and reaches the people who act on it.
An incident report is only useful if someone can rely on it later: a supervisor deciding what to fix, an insurer assessing a claim, a client asking what happened on their site. Most weak reports fail for the same reasons: written too late, too vague, mixed with opinion and missing evidence. This guide gives you a structure that works for security, facilities, construction, cleaning, retail or any team in the field.
Why it matters
A good report protects people and the business. It shows that the incident was taken seriously, it helps prevent a repeat and it gives a clear timeline if the matter escalates. A poor report does the opposite: it raises questions you cannot answer months later.
If an incident is ongoing or someone is at risk, deal with that first and call your local emergency number when needed. The report comes after the situation is safe.
The facts every report needs
Answer these questions, in this order:
| Element | What to write | Example |
|---|---|---|
| When | Date and exact time, plus when you noticed | 14 March, 02:40, noticed during patrol |
| Where | Specific location | Loading dock B, east roller door |
| What | Factual description in sequence | Door found raised about 50 cm, lock bar bent |
| Who | People involved, witnesses, their roles | No one present; driver J. Ortiz arrived 02:55 |
| Impact | Injuries, damage, losses | No injuries; lock bar damaged |
| Actions | What you did immediately | Secured door with chain, checked dock area |
| Notified | Who you informed and when | Supervisor 02:45, client contact 07:00 |
| Follow-up | What still needs action, and by whom | Maintenance to replace lock bar |
Write in short sentences, past tense, and use exact times rather than “around midnight”.
Photos and evidence
Photos turn a description into evidence. Take them before you move or fix anything, if it is safe to do so.
- Wide shot first to show the location, then close-ups of the damage or detail.
- One subject per photo, with a short caption: East roller door, lock bar bent.
- A short video helps when motion or sound matters, such as a leak or an alarm.
- Location sharing confirms where you were when reporting, which is useful on large sites.
- Do not edit or filter evidence photos.
For a deeper guide, see photo evidence best practices for field staff. In C Chat you can attach photos and videos directly to the report message, along with files up to 25 MB.
Template you can copy
Pin this in your reporting group so anyone can copy it:
INCIDENT REPORT Date / time: [date], [time] (noticed at [time]) Location: [site, area, exact spot] What happened: [facts in order] People involved / witnesses: [names, roles, contact] Injuries / damage: [none, or details] Immediate actions: [what you did] Notified: [who, when] Follow-up needed: [action, owner] Evidence: [number] photos attached, video, location Reported by: [name, role]
Post the report in the group for that site or team, not in a direct message, so supervisors see it and it stays in the company record. Security teams can see how this fits with client updates in client reporting for security companies.
Common mistakes
- Writing hours later. Times and details become guesses.
- Opinion as fact. “The driver was careless” is a conclusion; “the truck reversed into the door” is a fact.
- No evidence. A report without photos invites disagreement.
- Burying it. An incident mixed into a routine handover gets missed; post it separately.
- No owner for follow-up. Every open action needs a name.
- Sharing it widely. Reports often contain personal data; keep them in the relevant group.
How C Chat helps
C Chat lets field staff file a report from where they stand: text, photos, videos, voice notes, files and location in one message, posted in the right group. Read receipts show whether the supervisor has seen it, and search finds old reports by site or keyword. Team owners and admins can audit and export group conversations for insurers or clients, while direct messages stay private. For ready-made workflows, see incident reporting by chat, with photos, security guard incident reports and construction daily logs with site photos.
Getting started
Create a reporting group for each site or team at getcchat.com/c, pin the template above and ask your staff to use it for the next incident, however small. After a month, review the reports together and adjust the template to your operation.
Frequently asked questions
What are the key elements of an incident report?
Date and time, exact location, a factual description of what happened, the people involved and any witnesses, injuries or damage, actions taken immediately, who was notified and what follow-up is needed. Attach photos or other evidence and sign with your name and role.
How soon should an incident report be written?
As soon as the situation is safe and any emergency is handled. Details such as times, positions and exact words fade quickly, so a short report within the hour is more reliable than a long one written the next day. You can add a follow-up later if new facts appear.
Should an incident report include opinions?
Keep opinions out of the main description. Write what you saw, heard and did, and label anything you were told by others as reported by that person. If your company wants your assessment of the cause, put it in a separate section clearly marked as your opinion.
Can I send an incident report through a chat app?
Yes, and for field teams it is often the fastest way to get a report and photos to supervisors. Use a company group rather than a personal chat so the report is part of the company's record. If your organization also requires a formal form, the chat report gives you the facts and photos to complete it.