An incident report is not paperwork. It's a legal record, and it's frequently the single most important document in the room when something goes wrong. A clear, factual report can end a dispute before it starts. A sloppy one can turn a defensible situation into a six-figure liability. The difference is technique, and technique can be taught.
The cardinal rule: report facts, not conclusions. "The male subject appeared intoxicated" is an opinion a defense attorney will shred. "The subject's speech was slurred, he was unsteady on his feet, and there was a strong odor of alcohol" is an observation a jury will believe. You are a camera and a notepad, not a judge. Describe what you saw, heard, and did — and let the facts speak.
Get the structure right every time. Who was involved (full names, descriptions, contact info). What happened, in plain chronological order. When, with specific times, not "around 9-ish." Where, with enough detail to put a reader at the scene. How you responded, step by step. And critically — what you did not do and why, if it's relevant.
The report is written immediately, while memory is fresh, not at the end of the shift from recollection. Times are exact. Quotes are in quotation marks. Photographs are attached and referenced. The officer's actions are documented as clearly as the subject's. The narrative reads the same to the officer, the manager, the insurer, and the attorney.
"Handled a disturbance, all good now." Vague timing. Editorializing about the subject's character. Gaps in the timeline. Conclusions with no supporting observations. Worst of all — a report written three days later because nobody made time for it, now riddled with the inaccuracies that memory invents to fill its own holes.
Train your team that the report isn't done when the incident is over. The report is part of the incident. The officer who can write a clean, factual, timely report is worth more than the one who's simply big — because when it matters, the report is what survives.