Incident Reports: What Property Managers Should Expect From Their Guards

Expect one the same day, before the details fade

An incident report should reach you the same day as the event, usually before the officer’s shift ends, while what was seen and heard is still fresh. A report written a day or two later, from memory, loses the details that make it useful later on: the exact words a witness used, the order things happened in, the description of a vehicle that has since blurred into a general impression. If your current arrangement has incident reports arriving days after the event, or arriving only when you ask, that gap is the first thing to raise with the security company, because it will only get wider with time.

Expect a low threshold for what gets one

A good post writes an incident report for more than crimes: injuries, vehicle damage, disturbances, trespass warnings issued, fire alarms and the fire watch’s own findings, medical calls, water leaks found on a round, any contact with police, fire or EMS, and any use of force however slight. The cost of an unnecessary report is a few minutes of an officer’s time; the cost of a missing one is an argument months later with no record to settle it. A manager who only ever receives incident reports for serious crimes should ask whether smaller events are being logged only in the daily activity report, which is not built to carry the same level of detail.

Expect time order, first person, no conclusions

The narrative section is where most incident reports succeed or fail, and there are three rules a good one follows without exception. It is written in time order, so the sequence of what happened is clear. It is written in the first person, describing what the officer personally saw, heard and did. And it draws no conclusions about fault, intent or cause, which belong to the police, the adjuster or you, not the officer. “The suspect broke the window” is a conclusion dressed as a fact; “I heard glass break, walked to the north side, and saw a man in a grey hoodie running toward Lot B; the window of unit 312 was broken” is a record. If a report you receive reads with confidence about what someone intended or who was at fault, that confidence does not belong there.

Expect names, times and a structure that holds up later

Beyond the narrative, expect the report to carry a consistent structure: who was involved, by name where known and by a specific description where not; witnesses with contact information; the actions the officer took, each with a time, from calling 911 to notifying you to securing an area; and a list of evidence, photographs, video, physical items, with enough detail that someone could locate them months later. A police case number, when officers responded, belongs in this section because you and your insurer will both ask for it eventually.

A manager should expect	Because
Same-day delivery	Details fade fast, and a delayed report is a weaker one
Time-ordered, first-person narrative	Readable and defensible months later, by anyone who was not there
No stated conclusions about fault	Conclusions belong to police, adjusters or you, not the officer
Named people and specific descriptions	The difference between a usable record and a vague impression
Photographs and evidence listed with detail	Evidence found later is only as good as the record pointing to it
A police case number, if applicable	You and your insurer will ask for it

Expect it to connect to the daily report, not replace it

An incident report is a stand-alone document, but it should also appear as a single line in that shift’s daily activity report, with a time and a pointer to the fuller account. This is what lets you scan a week of daily reports and know an incident happened on a given night without reading the full report every time, and it is also what lets you find the full report quickly when a resident or an adjuster asks about a specific date weeks later.

What to do when a report falls short

Send it back the same week, and be specific about what is missing: a time that was not recorded, a notification that should have happened but is not listed, a sentence that states an opinion rather than a fact. A supervisor who hears this promptly can correct the specific gap with the officer directly, which is a very different conversation than a general complaint raised at a monthly meeting after several reports have already fallen short the same way.

Keep a short list of what was wrong and when, even after the individual report is fixed. One thin report is a training moment; three thin reports across two months from the same post is a pattern worth raising with the supervisor directly, since it usually means the officer has settled into a habit rather than had one off night. Bringing dates and specifics to that conversation gets it addressed faster than a general impression that reports have gotten weaker.

The document itself

The incident report template lays out every section described here, from classification through notifications and signatures, and is useful both for checking reports you receive now and for understanding what a complete one looks like before the first one ever arrives. For the routine record an incident report sits alongside, see how to read a daily activity report.