Guard.Academy
RegisterGet started
Site Operations

How to Write a Security Incident Report That Holds Up in Court

11 min read· Updated 2026-07-07· Free · No signup

Incident reports are legal documents. Six months from now, in a courtroom, a barrister will read yours word for word. Write it like they will and you'll never have a problem.

Key takeaways

  • Facts only, in chronological order.
  • Third person, past tense, active voice.
  • Timestamps to the minute.
  • Direct quotes in inverted commas.

The structure that never fails

Header (date, time, location, reporter). Chronology (what happened, in order, with times). Actions (what you did, in order). Outcome (final status, any handover). Attachments (CCTV timestamps, witness list, evidence log).

Language rules

'The customer entered the premises at 22:14', not 'the customer entered the premises about 10pm'. 'The customer said "I'll be back with my mates"', not 'the customer threatened to come back'. Specificity everywhere.

What to leave out

Opinion. Speculation. Assumption. Anything you didn't personally see, hear, or do. If a colleague told you something, attribute it: 'Colleague X reported that…'.

Quick checklist

  • Third person, past tense
  • Every time is precise
  • Every quote is in inverted commas
  • Opinion and speculation removed

Common mistakes

  • 'I think', 'I feel', 'seemed to' — remove them all.
  • Writing the report hours later from memory.

Frequently asked questions

How soon must a report be written?+

Within the shift; the same hour if the incident was significant.

Can I amend a report later?+

Only with a dated addendum. Never edit the original after submission.

Related guides

Site Operations

Patrol Techniques: Mobile and Static Best Practice

Read guide

Site Operations

Access Control for Security Guards: Getting the Basics Right

Read guide

Site Operations

Lone Working Security: How to Stay Safe on a Solo Site

Read guide