Incident reporting for security companies: what to record and why

What a security incident report should record, how to grade severity, run follow-ups, tell the client and keep records, with a sample incident report format.

  • StrataMax team
  • 10 min read
On this page

A good security incident report records what happened, where, when, who was involved, how serious it was, what the guard did, who was told, and what happened next, in plain facts, with photos and witness details attached. It is graded on a fixed severity scale (for example low, medium, high, critical), it stays open until every follow-up is done, and it is kept long enough to answer any later claim.

Below is how to set that up for a security guard company: the fields to record, how to grade severity, how to run follow-ups, how to tell the client, a sample report structure you can copy, and how long to keep the records.

Why does incident reporting matter for a security company?

When something goes wrong at a post, the client asks three questions: what happened, did your guard do the right thing, and what are you doing about it. A written incident record answers all three. Without it, the answer is whatever the guard and supervisor remember, told over the phone, slightly differently each time.

Good records also protect your company:

  • Client disputes. If a client blames the guard for a theft, the record shows when the guard noticed, who was called and at what time.
  • Insurance and police. An insurer or police officer will ask for the time, place, people involved and evidence. A record made on the day is far more credible than one written a week later.
  • Guard management. A guard who handled an incident well deserves credit. A guard who was absent when it happened needs a documented conversation.
  • Learning. Three trespass incidents at the same rear gate in two months is a pattern you only see if each one was recorded the same way.

What should a security incident report record?

Use the same fields for every incident, whatever the type. The table below is a sample incident report structure.

Field What to record Example
Incident type One category from a fixed list Trespassing
Client and post The client, the site and the specific post Tamarind Court Residency, Rear Gate
Date and time of incident When it happened, as precisely as known 9 Mangsir 2083, about 23:30
Date and time reported When the office was told 9 Mangsir 2083, 23:40
Reported by Name and role Suresh Tamang, guard on duty
Guard(s) on duty Who was rostered and present Suresh Tamang
Description Facts in order: what was seen and done, no opinions Two men climbed the rear wall near the parking area. Guard shouted, used whistle and torch. Men ran back over the wall. Nothing appeared to be taken.
People involved Names if known, otherwise descriptions Two unknown men, early twenties, dark jackets
Witnesses Name, contact, what they saw Resident of flat B-4, saw the men from the balcony
Severity Low, medium, high or critical High
Immediate action What the guard and supervisor did Guard raised alarm, called supervisor; supervisor arrived 23:55, checked the perimeter
Who was informed Client contact, police, management, with times Client site manager called 23:58; police not called (no entry to buildings)
Media Photos, CCTV clips, documents Photo of footprints on wall, CCTV clip requested from client
Status Open, investigating or closed Investigating
Follow-ups Dated entries with notes and media 10 Mangsir: CCTV footage attached, client informed. 12 Mangsir: extra night patrol visit added.
Closed by and date Who closed it and when Operations manager, 20 Mangsir 2083

Use a fixed list of incident types

Free-text types (“guy jumped wall”, “intrusion”, “trespass”) make it impossible to count anything. Pick a short list and stick to it. A list that fits most guard companies:

  • Theft
  • Trespassing
  • Fire
  • Vandalism
  • Accident
  • Injury
  • Harassment
  • Other

“Other” should be rare. If you see the same kind of event under “Other” every month, add it to the list.

Keep the description factual

The description is the part most likely to be read by a client, insurer or police officer. Teach supervisors to write it the same way every time:

  • Chronological. What happened first, then next.
  • Observed facts, not conclusions. “The man put a phone in his pocket and walked out without paying at the counter” rather than “the man stole a phone”.
  • Times wherever possible. Even approximate times (“about 23:30”) are better than none.
  • Who said what. If information came from a resident, say so.
  • No blame or speculation. Opinions about whether the guard was negligent go in the internal review, not the incident description.

Record witnesses properly

For each witness: full name, how to contact them, where they were, and a short summary of what they saw. Witnesses move away, change numbers and forget. A witness recorded on the night is worth much more than one tracked down a month later.

How do you grade the severity of an incident?

A severity scale tells everyone how fast to act and who must be told. Four levels are enough. Write your definitions down and give them to every supervisor.

Severity Typical definition Examples Expected response
Low No injury, no loss or negligible loss, no disruption to the client Minor vandalism (graffiti), visitor argument at the gate, a guard’s torch broken Record the same day; include in monthly report
Medium Minor injury needing first aid, small loss or damage, short disruption Small item stolen from reception, minor vehicle scrape in the parking, attempted entry stopped Supervisor informed during the shift; client told the same day
High Injury needing medical treatment, significant loss or damage, intruders on site, threat to people Break-in attempt at night, theft of equipment from a warehouse, harassment of a resident Supervisor and operations manager informed immediately; client called immediately; police where appropriate
Critical Serious injury or death, fire, armed threat, major loss, or anything that stops the client’s operations Fire in a building, armed robbery, serious assault, guard seriously injured Emergency services first; management and client called immediately; senior manager takes charge

Two rules keep severity honest:

  1. Grade on what happened, not on how it looks for the company. A theft during a guard’s absence is not “low” because it is embarrassing.
  2. Raise the severity when new facts appear. An “accident” that turns out to involve a hospital stay moves from medium to high. Record the change and the reason as a follow-up.

How should incident follow-ups work?

Most incidents are not finished on the night. The CCTV has to be pulled, the client has to respond, the guard has to give a statement, the lock has to be replaced. Follow-ups are how you track that.

Use three statuses:

Status Meaning
Open Recorded, not yet being worked on
Investigating Someone is collecting facts, waiting on the client or police, or fixing the cause
Closed All actions done, outcome recorded, nothing pending

Each follow-up is a dated entry with a note, the person who made it, and any media (a CCTV clip, a photo of the repaired lock, a scanned police report). Do not overwrite the original description. If the facts change, add a follow-up that says what changed.

Before closing, check:

  • Was the client informed of the outcome?
  • Were all actions assigned at the start actually done?
  • Is the guard’s role documented, including any warning or commendation?
  • Are the causes fixed (light repaired, wall raised, register procedure changed)?
  • Is the outcome written in one or two sentences a stranger could understand?

An incident that stays “investigating” for months is usually waiting on someone who has forgotten. Review open and investigating incidents weekly.

How should you communicate an incident to the client?

Clients do not like surprises. Agree the reporting rule in the contract, then follow it every time.

A simple rule many companies use:

Severity First contact Written report
Low Not needed at the time Listed in the monthly summary
Medium Phone or message to the site contact during the day Short written summary the same day
High Immediate phone call to the site contact Written report the same day; update when the incident is closed
Critical Immediate phone call to the site contact and a senior client contact Written report as soon as facts are clear; daily updates until closed

A written report to the client should include the date, time and post, what happened, what your guard did, who else was informed, the current status, and the next steps with dates. Leave out internal matters such as disciplinary decisions or the guard’s personal details beyond name and role.

Be prompt even when the news is bad. A client who hears about a theft from your supervisor at midnight will usually be calmer than one who hears about it from a tenant the next morning.

A worked example

At 23:30 on 9 Mangsir 2083, two men climb the rear wall at a residential complex. The guard on duty sees them, uses his whistle and torch, and they run off. He calls his supervisor at 23:40.

  • The supervisor records the incident as Trespassing, severity High (intruders on site at night), status Open.
  • At 23:55 the supervisor reaches the post, checks the perimeter and photographs footprints on the wall. He adds the photos.
  • At 23:58 he calls the client’s site manager. He records the call time in “Who was informed”.
  • He takes the name and number of a resident who saw the men from her balcony.
  • Next morning, the operations manager moves the status to Investigating and asks the client for the CCTV clip.
  • On 10 Mangsir, the clip is attached as a follow-up and the client is sent a written summary.
  • The patrol schedule for that post is changed to add a night visit. That change is recorded as a follow-up.
  • On 20 Mangsir, after ten nights with no repeat and the client’s agreement to add a light at the wall, the incident is Closed with the outcome recorded.

Every step is on the record, with times. If the client asks at renewal “what happened with that break-in”, the answer takes a minute to find.

How do incident records connect to patrols and guard records?

Incidents should not live in a separate notebook. They belong on the same record as the post, the client and the guard.

  • Patrol visits find problems before they become incidents (a broken floodlight, a gap in the wall). When a patrol finding turns out to be a security event, open an incident and link the two. See our guide on patrol visits and supervising guards across many posts.
  • Guard records should show the incidents a guard handled. Over a year, that history matters for promotions, warnings and training.
  • Client reporting gets easier when incidents and patrols for a client can be listed together for a month.

How long should you keep incident records?

There is no single retention period that suits every case, so set one in writing and apply it consistently. Points to consider with your legal adviser and insurer:

  • Contract life. Keep incident records at least for the life of the client contract, plus a period after it ends in case of a later dispute.
  • Claims and cases. Keep anything linked to an insurance claim, police case or court matter until that matter is fully settled, and then for the period your adviser recommends.
  • Injuries to staff. Incidents involving injury to your own guards may later matter for compensation or insurance, so keep them with the employee’s records.
  • Media. Photos and CCTV clips attached to incidents should be kept for the same period as the incident itself. Clients often overwrite their own CCTV after a short time, so attach the clip you need to the incident record instead of relying on the client’s system.

Whatever period you choose, the rule is: delete according to the policy, not because a folder got full, and never delete a record that is part of an open dispute.

Who should be able to see incident records?

Incident records can contain personal details of witnesses, injured people and suspects. Limit who can view and edit them: supervisors and operations managers typically need full access, while most office staff do not. Keep a record of who changed what, so an edited description can always be traced.

Checklist: incident reporting for a security company

  • A fixed list of incident types is used for every report.
  • Every report records client, post, incident time and reported time.
  • Descriptions are factual, chronological and free of blame.
  • Witnesses are recorded with name, contact and what they saw.
  • Severity uses a written four-level scale that supervisors have been trained on.
  • Severity is raised, with a reason, when new facts appear.
  • Immediate actions and everyone informed are recorded with times.
  • Photos and CCTV clips are attached to the incident, not kept on personal phones.
  • Follow-ups are dated entries; the original description is never overwritten.
  • Open and investigating incidents are reviewed weekly.
  • The client reporting rule by severity is written into the contract and followed.
  • Incidents are linked to the post, the client and the guards involved.
  • Access to incident records is limited by role, and changes are traceable.
  • A written retention period exists, and records linked to claims or disputes are never deleted early.

How StrataMax records incidents

In StrataMax, incidents are recorded in the web app against the client and post, with a type (theft, trespassing, fire, vandalism, accident, injury, harassment or other), severity from low to critical, witnesses, and photos or other media. Follow-ups with notes and media are added until the incident moves from open through investigating to closed, on the same record as your guards, posts and patrol visits. See how it works on the field operations page, or book a demo to walk through it with your own posts.

Frequently asked questions

What should a security incident report include?

At minimum: the incident type, the post and client, the date and time it happened and when it was reported, who reported it, a factual description, people involved and witnesses, the severity, immediate action taken, who was informed, photos or other media, and the current status. Follow-ups are added as dated entries until the incident is closed.

How do you decide the severity of a security incident?

Use a fixed scale such as low, medium, high and critical, defined by harm to people, loss or damage to property, and impact on the client's operations. Write the definitions down so two supervisors grade the same event the same way, and raise the severity if new facts appear.

When should the client be told about an incident?

Agree the rule in the contract. A common approach is to call the client's site contact immediately for high and critical incidents and to send a written summary within the same day, while low incidents go in the regular monthly report.

How long should incident records be kept?

Keep them at least as long as any claim, insurance case, police case or client dispute about the incident could still be raised, and at least for the life of the client contract. Set a written retention period with your legal adviser and insurer rather than deleting records ad hoc.

Next step

Let StrataMax do this every month

Payroll with SSF and TDS, IRD-approved billing and every guard and post on one record. Book a 30-minute walkthrough.