In security, the incident report you write today becomes the document that decides a court case two years from now. Or determines whether insurance pays out on a theft claim. Or defines whether your contract survives a client review.
Yet most Indian security agencies treat incident reports as an annoying formality. A supervisor scribbles half a page of generic prose. Nobody reviews it. It goes into a drawer. When it matters, it is either missing or useless.
Here is what a properly constructed incident report looks like, why each element matters, and where most agencies fall short.
The Anatomy of a Useful Incident Report
1. Precise timestamp
Not "around 2 AM." The exact minute — 02:17 hours. Preferably captured automatically by a digital system rather than written by a human. Courts scrutinize timestamps heavily, and human-estimated times get dismissed.
2. Exact location
GPS coordinates when possible. If not, the specific block, floor, wing, and landmark. "Near the back gate" is useless. "Back gate, north-east corner, adjacent to waste disposal area" is defensible.
3. Personnel involved
Full names and employee codes of all security personnel on duty during the incident. Names of any non-security persons (residents, visitors, vendors, police). What each person saw, did, and said — attributed individually.
4. Factual sequence
What happened, in order, in neutral language. No speculation, no opinion, no characterization. "The man raised his voice" — not "the man became aggressive."
5. Physical evidence
Photos (timestamped), CCTV references with timestamps, items collected, damages documented. Digital incident reports with embedded photo uploads are vastly more defensible than paper reports.
6. Actions taken
Every action by security personnel, in order. Response times matter. "Guard on duty called supervisor at 02:19, supervisor arrived at 02:26" beats "supervisor was called."
7. External involvement
Police called? When, which station, FIR number. Ambulance called? Response time. Client informed? When, which representative.
8. Witness statements
Brief, factual, attributed. Each witness signs their statement. For digital systems, a digital signature with timestamp suffices in most legal contexts.
What Never to Write
Opinions disguised as facts. "The man looked suspicious." Suspicious to whom, based on what? This sentence has destroyed cases.
Speculation. "Probably an inside job." You have no idea. Write what you observed, not what you inferred.
Characterizations. "The resident was rude." Describe behaviour objectively instead — "The resident raised their voice and used the phrase..."
Admissions of fault. "Our guard should have been patrolling that area." Never. If a review later concludes that, fine. The report should not prejudge it.
Emotional language. "Shocking incident." "Disturbing sight." The report is evidence, not narrative.
What Insurance Reviewers Look For
Insurance investigators evaluating a theft or damage claim look for three things:
- Was the incident reported promptly? (Within 24 hours is the standard.)
- Were security protocols followed? (Patrol logs, attendance records.)
- Is the incident report detailed enough to establish the facts?
Fail on any of these and claims get denied or reduced. Agencies with weak incident reporting lose 30-40% of legitimate insurance claims they file on clients behalf.
What Clients Scrutinize
During contract renewals, sophisticated clients ask for incident report samples. They want to see the quality of your documentation. A clean, structured, objective report signals a professional agency. A scribbled half-page signals exactly the opposite.
Our Recommendation
Digitize incident reporting. Use a system that enforces the required fields, auto-timestamps, captures photos, records GPS, and stores everything tamper-evidently. The cost of the software is a tiny fraction of the cost of one lost insurance claim or one lost client contract.
ZephyGuard incident module does this out of the box. But even if you use a competitor or build your own process, the structure matters more than the tool. Get the fundamentals right.
Questions about incident reporting best practices specific to your operation? Get in touch. Happy to share templates we use with customers.