Industry Knowledge
Security guard report writing: how to write reports clients trust
Security guard report writing made simple: what every report needs, how to describe people and events, and the mistakes that weaken a report later.

Security guard report writing is the skill that turns a shift into proof. A good report says what happened, when, where and who was involved, in plain words, without guesses. This guide covers what every report needs, how to describe people and events, and the habits that make a report hold up when a client, an insurer or a court reads it weeks later.
Key points#
- A strong security report answers who, what, where, when and how, and says what the officer did about it.
- Officers should write what they saw and heard, not what they think happened, and mark anything they were told by someone else.
- Reports are written as soon as possible after the event, while times and details are still fresh.
- Short sentences, exact times and plain words make a report easier to read and harder to challenge.
- Supervisors should review reports and give feedback, because report writing improves with practice.
Why report writing matters for a guard company#
For a client, the report is often the only part of the job they see. They are not on site at 2 a.m. when the door alarm goes off. What they read the next morning is your company's work, and it shapes whether they renew the contract.
Reports also travel further than the client's inbox. An incident report may be read by the client's lawyer, an insurance adjuster or the police. A vague or careless report can hurt the client and your company, even when the officer did the right thing on the night.
The six questions every report answers#
Teach officers to check each report against six questions before they submit it:
- Who was involved: names when known, or a clear description when not.
- What happened, in the order it happened.
- Where it happened, as exactly as possible: building, floor, door, parking row.
- When it happened, with times for each step, not just the start.
- How it happened, if the officer saw it.
- What the officer did: who they called, what they said, what they recorded and how it ended.
If a question cannot be answered, the report says so. The officer did not see how the window was broken is better than leaving a gap the reader has to fill.
Write facts, not opinions#
The most common weakness in a report is opinion written as fact. The man was drunk is a conclusion. The man smelled of alcohol, slurred his words and held on to the wall to stand is what the officer observed, and the reader can draw the conclusion.
The same rule applies to intent. Officers should not write that someone tried to steal unless they saw it. They can write what the person did: He placed two bottles inside his jacket and walked past the registers toward the exit.
When information comes from someone else, say so: The store manager said the woman had been in the store twice that morning. That keeps first-hand observation separate from what the officer was told.
Describe people and vehicles the same way every time#
A fixed order helps officers remember details under stress and makes reports easier to compare. For people, a simple order is: sex, approximate age, height and build, hair, clothing from top to bottom, and anything distinctive, such as a bag, a limp or a tattoo.
For vehicles: color, make and body type if known, plate number and state, damage or stickers, and the direction it left in. Write partial plate when only part was seen, rather than guessing the rest.
Times, places and order#
Every report should run in time order. Officers should note the time of each step, not just the first one: when they noticed the problem, when they called a supervisor, when police arrived, when the area was clear.
Places should be specific enough for a stranger to find. North stairwell, level 3, by the fire door is useful. Upstairs is not. If the site has numbered doors, gates or patrol checkpoints, use those names, because the client knows them too.
Plain words and short sentences#
Reports are not the place for police jargon or long, formal sentences. Officers should write as they would explain the event to a calm colleague: one idea per sentence, active voice, no slang.
Some habits that help:
- Write I or the officer consistently, as your company's policy says.
- Spell out abbreviations the first time.
- Avoid words that suggest emotion or blame, such as hysterical or obviously.
- Read the report back once before submitting it, and fix anything a reader could misunderstand.
Photos and attachments#
A photo often says more than a paragraph: a forced lock, a blocked exit, a spill on the floor. Officers should take photos of the scene before anything is moved, when it is safe, and mention each photo in the text so the reader knows what it shows and why it was taken.
Your post orders should say what officers may and may not photograph at each site. Some clients restrict photos of people, screens or certain areas, so check the contract and the client's rules.
Write it soon, and do not change it later#
Memory fades fast, especially after a stressful event. The best time to write a report is right after the situation is under control. If an officer cannot write the full report at once, a few notes with times are better than nothing.
Once a report is submitted, it should not be quietly changed. If something was missing or wrong, the officer adds a correction or a follow-up note, and the original stays as it was. That keeps the record honest.
Daily activity reports versus incident reports#
A daily activity report is a log of the shift: patrols, checks, visitors, small issues and how they were handled. It should be steady and brief, so a client can scan it in a minute.
An incident report covers one event in detail. It is longer, more careful and more likely to be read by people outside the client's team. Officers should know which form to use for what, and supervisors should agree with each client on what counts as an incident at that site.
How supervisors can raise the standard#
Report writing improves with feedback. A short weekly review of a few reports, with one thing done well and one thing to fix, does more than a single training session. Use real, anonymized examples from your own sites in training, because officers learn faster from familiar situations.
Supervisors should also check that reports reach the right people on time. Software can help here. In Guardix, officers file incident reports from the mobile app, and managers can approve or reject them and send clients scheduled reports. The habits in this guide matter whatever tool you use.
Frequently asked questions#
What should a security guard report include?#
A security report should answer who was involved, what happened, where and when it happened, how it happened if the officer saw it, and what the officer did. It should be written in time order, with exact times and places, and should say clearly when information came from someone else.
How soon should a security officer write a report?#
As soon as the situation is under control and it is safe to do so. Details such as times, descriptions and the order of events fade quickly. If the full report must wait, the officer should write short notes with times right away.
Should security officers write opinions in a report?#
No. Officers should write what they saw, heard and did, and let the reader draw conclusions. Describing behavior, such as slurred speech or unsteady walking, is stronger than writing a conclusion like drunk, which the officer may not be able to prove.
Can a security report be changed after it is submitted?#
The original report should stay as it was written. If something is missing or wrong, the officer adds a correction or a follow-up note that explains what changed and why. That keeps the record honest and easier to defend.
- Reports
- Training
- Operations