A security incident report is a written record of a security event in an estate, such as an intrusion, theft, fire, fight or suspicious activity, stating what happened, where and when, who was involved, and what action was taken.
How it works in a Nigerian estate
Guards raise a report as soon as possible after the event, while details are fresh. The chief security officer or facility manager reviews it, adds follow-up actions, and escalates serious incidents to the exco and, where appropriate, the police. A useful report includes the date, time and exact location; the type of incident; people involved and witnesses; a factual description; actions taken; and any evidence such as photos or CCTV references.
Illustrative example: at 2:40am a guard on night patrol in a Gwarinpa estate sees a man climbing the back fence near house 31. He raises an intruder alarm, two guards respond, the man flees, and the report records the time, location, description and the damaged fence section for repair.
Why it matters
Incident reports turn one-off events into patterns: the same weak fence section, the same hour, the same gate. They support police investigations and insurance claims, and help the exco decide where to spend security money. See the security guard SOP and the emergency response plan.
In Zenus360
Guards raise alarms and incident reports (alarm, SOS, fire, intruder) from the security app with GPS location, broadcast in real time to the estate's management, who review incidents in the manager app and dashboard. Resident emergencies raised with the panic button are recorded too. See the estate security app.
Frequently asked questions
Who should write a security incident report?
The guard or officer who witnessed or responded to the incident, as soon as is safe, with review by the chief security officer.
How long should incident reports be kept?
The estate should set a retention period in its security policy, keeping reports at least long enough to support investigations, insurance claims and trend reviews.