The Good, Bad, and Ugly of Security Incident Reports
Trackforce
June 17, 2015 · 10 min read

In this episode of our podcast, we discussed what separates a good security incident report from ones that are bad or just truly ugly. These reports are the most direct representation of your work to the customer, so it’s important to make sure they are thorough, detailed, and professional.
“A good report is accurate, specific, factual, objective, clear, complete, and concise,” says Chris.
Below is a recap of that conversation, plus one incident written three ways, a checklist to run before you submit, and how TrackTik helps officers get it right every time.
Key takeaways
- A good report is accurate, specific, factual, objective, clear, complete and concise.
Those seven qualities are the standard every report should meet. - Write for the reader who wasn’t there.
The client should understand exactly what happened without calling you for details. - Answer the five W’s and an H, then stop.
Who, what, when, where, why and how. A longer report is not a better report. - Professionalism shapes credibility.
Spelling, grammar and presentation affect how much a client trusts the facts inside the report. - The right system makes good reports the default.
TrackTik incident reporting uses required fields, photos and time stamps, and ReportPro AI turns rough field notes into clear, professional language.
Helping the Customer
These are our basic criteria, but how do we determine if a report meets those standards? To get a sense of how useful a report is, imagine reading it from the perspective of the customer.
The primary purpose of an incident report is to help someone who wasn’t there get a sense of precisely what happened.
Too often, however, we see reports that are almost incomprehensible to customers that didn’t witness the incident. Maybe there’s too much lingo, key details left out, inaccurate or biased statements, or the chronology of events is off. Whatever the case, a confusing report doesn’t help anyone.
Make sure to include all the necessary information, and nothing more. A longer report is not necessarily a better report. Too much information can confuse customers just as much as not enough information, so it’s important to keep the report as short as possible while still answering the five W’s and an H: Who, What, When, Where, Why, and How.
Good, Bad and Ugly: One Incident, Three Reports
Here is the same incident, a trespasser in a residential parking garage, written three different ways. The examples are illustrative, but every security company has seen versions of all three.
The ugly report
Guy in garage again. Told him to leave. He left.
What’s wrong: No time, no location, no description, no actions beyond “told him to leave,” and “again” hints at a pattern that is never explained. The client learns almost nothing.
The bad report
Late at night a suspicious man was in the parking garage. I approached him and asked him to leave the property, which he did after some arguing. No further issues.
What’s wrong: It reads better, but it is still vague. “Late at night” and “the parking garage” are not specific, there is no description of the person, and “suspicious” is an opinion with no facts to support it.
The good report
At 23:42 on March 14, during my scheduled patrol of Parking Level P2, I observed an adult male, approximately 30 to 40 years old, wearing a gray hooded sweatshirt and dark jeans, pulling on the driver’s door handle of a blue sedan parked in space 214. I identified myself as security and asked his reason for being on the property. He said he was looking for a friend’s car but could not name a resident. I asked him to leave, and he exited through the P2 pedestrian door at 23:46. I followed at a distance and confirmed he left the property at 23:49. No damage to the vehicle was observed. I photographed the vehicle and the exit, emailed the property manager at 23:55 and added the description to the shift pass-down log.
Why it works: It answers who, what, when, where, why and how, separates facts from opinion, records every action and notification, and points to supporting evidence. With ReportPro AI, officers can turn quick field notes into this kind of clear, professional report, then review it before submitting.
Professionalism
The way we present reports to customers heavily impacts the way they read them. A thorough, concise, and accurate report will still give customers a bad impression if it’s written in crayon. That’s not a joke either, Chris has actually encountered guards writing incident reports in crayon before.
Fortunately, there’s no reason to have to worry about the correct writing utensil anymore, as guards can just type in the information to incident reporting software on mobile devices. This can also help with grammar and spelling, another issue that makes reports appear unprofessional.
“As an officer, there’s not something that hurts your credibility more than improper punctuation, grammar, and spelling,” I tell Chris. “We don’t need to write a high-quality essay here, but we do need to make sure we’re spelling the basic words correctly.”
Accuracy and Specificity
An accurate report doesn’t just improve your relationship with the customer, it can help protect you and your guards against complaints. Too often in the security industry people are ready to assume we’ve messed up at our jobs, so keeping an accurate record of events is key to demonstrating what you’ve done correctly.
“Think about an average apartment community with 500 people, and one guard,” says Chris. “500 people with the ability to… complain about your guard. You’ve got to have detail, you really do.”
A bad report, one that contains inaccurate or incomplete information, can cause numerous problems. Imagine a property manager trying to follow up on an incident you reported, only she can’t because the report contains the wrong unit number, or it doesn’t record the full name of the parties involved, or doesn’t fully explain what happened.
Now, the property manager has to call you to fill in the details, which means you have to turn around and call the officer. Everyone’s unhappy, everyone’s having to do more work, and all because a couple key details were missing or wrong in the original report.
Using an incident reporting system, you can register residents’ names ahead of time to avoid miscommunication there, use audio files and pictures to supplement the text, and establish clear fields for the officer to fill out so that nothing is missing. This makes incident reporting quicker, more accurate, and more professional.
Incident Report Checklist: Before You Hit Submit
Reporting mistakes cost time, credibility and sometimes liability, as we explain in the true cost of security reporting mistakes. Run every report through this quick check before it goes to a supervisor or client:
- Does it answer who, what, when, where, why and how?
- Are times exact and written in one consistent format?
- Are names, unit numbers and locations spelled correctly and verified?
- Are facts kept separate from opinions and assumptions?
- Are events listed in the order they happened?
- Are photos, audio or other evidence attached?
- Does it record every action taken and every person notified?
- Has spelling and grammar been checked?
- Would a client who wasn’t there understand it without calling you?
For a deeper look at structure and defensibility, read What’s In a Report? Physical Security Incident Reporting the Right Way.
How TrackTik Makes Good Reports the Standard
A checklist helps, but the right system means officers rarely need one. Here is how TrackTik addresses the most common reporting problems:
| Common report problem | How TrackTik prevents it |
|---|---|
| Missing details | Required fields and configurable templates for each incident type |
| Wrong names or unit numbers | Site information, such as residents and units, is registered ahead of time |
| Poor grammar and unclear wording | ReportPro AI turns rough notes into clear, professional language for the officer to review |
| No proof | Photos, audio and GPS time stamps attached to the report automatically |
| Slow delivery to the client | Reports shared in real time, including through client portal access |
| No view of patterns | Incident trends by site and client in TrackTik business intelligence dashboards |
Want to see how your officers’ reports could look? Book a TrackTik demo.
Frequently Asked Questions
Latest Articles
Featured Resources
See Trackforce in action
Book a walkthrough with our team and see how it fits your operation.












