Who Actually Reads a Report
On an ordinary night, your supervisor reads it and nobody else ever does. Most reports are routine, and that's fine. The trouble is you can't tell in the moment which report is the ordinary one and which is the one that ends up mattering.
A single report can travel a long way. It can be read by your supervisor and the company's management, by the client and their property manager, by an insurance adjuster weighing a claim, by a police officer building a case, and by attorneys on either side of a lawsuit. If it goes that far, a judge or a jury may read it too, and they'll read it word for word.
Incident report
- What it is
- a written, factual record of what an Officer observed and did during a specific event on a shift.
- What it does
- it preserves the scene in real time, so people who weren't there can understand what happened and when.
- Why it matters
- it can become evidence, and once it does, it either holds up under questioning or falls apart.
You're writing for the routine reader and the rare one at the same time. The only way to do both is to write every report to the higher standard.
Write It Like a Stranger Will Read It
The person who ends up reading your report probably wasn't on site, doesn't know the property, and doesn't know you. They have your words and nothing else. So the test for a good report is simple: could someone who wasn't there see the scene from what you wrote?
That means the basics, every time. When it happened, with a real time. Where, specifically. Who was involved, described plainly. What you saw, in order. What you did about it. Who you told, and when. Leave out the shorthand and the assumptions the reader can't share. If they have to call you to understand it, the report didn't do its job.
Here's a line I hold with our Officers. We don't write "all clear, no issues" if that isn't true. If there was an overloaded outlet, a propped fire door, a light that's been out for a week, it goes in the report, even when it would be easier to leave it out and keep the shift looking clean. The report isn't there to make us look good. It's there to be true. Because the day someone pulls that report and reads it back to you, and people do, the thing that protects you is that you wrote down exactly what happened. Write it honest the first time and you never have to remember what you said.
Facts, Not Conclusions
The fastest way to weaken a report is to write your conclusions instead of your observations. "He was drunk" is a conclusion. "He was unsteady on his feet, his speech was slurred, and there was a strong smell of alcohol" is what you actually saw, and it's much harder to pick apart.
Write what you observed, not what you assumed, and don't write something you didn't personally see. If someone told you about it, say who told you and what they said. If you didn't witness it, don't write it as though you did. A report that claims more than the Officer could have known is the one that comes apart the moment anyone questions it.
Write It That Night
Memory is at its best right after the event and fades fast. A report written the same shift, while the details are fresh, is more accurate and more credible than one rebuilt from memory days later. The gap between the event and the writing is one of the first things a careful reader, or an attorney, will notice.
So build the report in real time. Note the time when it happens. Get it down before the end of the shift, not a week on. The habit feels like overkill on the quiet nights. It's the whole game on the one that isn't.
A Report That Holds Up Vs One That Doesn't
| The test | Falls apart | Holds up |
|---|---|---|
| The reader | Assumes you know the site and the people | Written so a stranger sees the scene |
| The content | Conclusions and labels | Observations, in order |
| Time | Vague, "later that evening" | Specific, with real clock times |
| What you didn't see | Written as fact anyway | Attributed to who reported it |
| When it was written | Rebuilt from memory days later | Written the same shift |
Check Your Own Reports
Before you close out a report, run through these:
- Could someone who wasn't there picture the scene from your words alone?
- Did you write what you observed, or what you concluded?
- Is every time in it specific, not "a little later"?
- For anything you didn't see yourself, did you say who told you?
- Are you writing this now, while it's fresh, or trusting your memory later?
- Would this report still make sense, and still hold, if you read it aloud in a year?
How We Handle It at ARDENT
We treat the report as a real deliverable, not an afterthought at the end of a shift. Our Officers report through the shift on a set cadence, including the quiet stretches, so there's a record built in the moment rather than reconstructed after something goes wrong.
We train the standard directly: facts over conclusions, specific times, only what you saw, and write it now. We'd rather a report read plain and accurate than polished and vague. When a client, an insurer, or an investigator asks what happened at a certain hour, the answer is already written down, in the Officer's own words, from that night.
None of this is about sounding official. It's about being able to stand behind every line, because the report that matters is the one nobody knew would matter when it was written.
Key Takeaways
- A security report can be read by clients, insurers, law enforcement, and attorneys, and can end up as evidence in court.
- You can't predict which report will matter, so write every one to the standard the important one needs.
- Write so a stranger can see the scene: specific times, plain descriptions, and the order things happened.
- Record observations, not conclusions, and don't write what you didn't personally witness.
- Write it the same shift. A report rebuilt from memory days later is weaker and easier to challenge.
Frequently Asked Questions
Do Security Reports Really Get Used in Court?
They can. A report can be requested in a lawsuit, reviewed by attorneys, and entered as evidence, and the Officer can be asked about it under oath. It doesn't happen with most reports, but you can't know in advance which one it will be, so the safe habit is to write every report as if it will be.
What's the Difference Between an Observation and a Conclusion?
An observation is what you saw or heard: "he was unsteady and slurring." A conclusion is your interpretation of it: "he was drunk." Reports should be built on observations, because they're specific and they hold up. Conclusions invite the question, "how did you know that?"
Is It Better to Write More or Less?
Write enough to make the scene clear, with no filler. A report should be complete and specific without padding. Leave out opinion and speculation, keep every fact that helps a reader understand what happened, and stop there.
Should I Write a Report Even When Nothing Happened?
Yes. A record of a quiet shift has real value: it shows the post was covered and attentive, and it establishes what normal looked like right before an incident. When in doubt, write the report.