How correctional officers can improve use of force reports
There are several steps correctional officers can follow to write a use of force report that is both a thorough and accurate account of events
The CorrectionsOne Academy features several hours of coursework on correctional officer report writing including narrative skills, report writing checklists and how to write effective use of force reports. Complete the courses to improve and retain critical skills to help improve your written documentation of events in the field. Visit CorrectionsOne Academy to learn more and for an online demo.
Today’s correctional officers must possess a variety of skills. Physical and verbal communication skills must be complemented with the ability to clearly articulate enforcement actions in the form of written reports. In this article, I will discuss a specific type of report – use of force or subject control – and outlines how officers can improve their reports.
Set the foundation
When it comes to inmate control, what matters is exactly what the officer knew at the time their force was used. For this reason, a good subject control report includes everything the officer knew up to the point of the incident. Information obtained after the fact, while important to the overall criminal investigation, is not relevant in terms of the officer’s decision to use force.
Paint the picture
One of the most common mistakes I see when reviewing use of force reports is overgeneralized descriptions that fail to adequately paint the picture of what took place. For example, lines such as “the inmate started to become aggressive” or “the subject began to cause a disturbance” must be accompanied by specific descriptions of the subject’s actions. Failure to do this allows too much room for interpretation and argument when it comes time to explain the reasonableness of the actions taken.
Describe others' actions, not intentions
A common question, and often point of confusion, is how and when to report other officers’ actions. Some officers mistakenly think they only need to report what they did and that it is up to the other officers involved to report what actions they took. Officers think by doing this, there will be less chance of confusion. The problem is, many times one officer’s actions dictate how and why another officer acted in a certain way. So as a general rule, officers should describe what actions they observed from other officers, but never attempt to articulate why those officers took those actions. By following that guideline, the officer can properly describe what happened, without the added confusion of having to explain why another officer acted in a certain way.
Articulate the event without sugar coating
Incidents involving force are most definitely fluid and rapidly evolving. What they rarely are is picture-perfect. Too many officers try to “sugar coat” subject control incidents to make them appear less violent or heated. I have seen lines such as “I gently assisted the inmate to the ground” when in fact the inmate (justifiably) was rapidly tackled to the ground. There is nothing wrong describing forcibly taking someone to the ground by tackling them. Officers are expected to use a reasonable amount of force to control or maintain order in a given situation. When officers attempt to downplay their actions by describing them in more gentle terms, it often has the reverse effect and makes the reader question whether or not the officer is attempting to hide something. Clearly and decisively describing the actions taken is the most appropriate way to describe use of force incidents in corrections.
Proofread, get a second opinion and read other officer’s reports
The following tip applies not just to subject control reports, but for all reports an officer will ever write. After writing the report, an officer should take a few minutes to accomplish other tasks, then come back to it and proofread it thoroughly. This sounds simple, but in the rush of modern law enforcement, it is far too easy to type it, click send and let the sergeant deal with it. This can result in sloppy reports that increase the workload for both the sergeant and the officer when it comes to making corrections. Furthermore, asking other officers, preferably ones who were not on scene, to read reports and check for clarity is an excellent idea. This easy tactic will be beneficial for both the report writer and reviewer. Finally, it is beneficial to review other officer’s reports frequently. It is amazing how much reviewing other reports improves report-writing abilities.
Document after-action procedures
A well-written subject control report is not complete without documentation of the measures taken once the force was stopped and compliance was gained. Noting when and if medical staff responded to the scene, what injuries were observed or described, and what measures or security watches were put in place after the subject was placed into custody are excellent conclusions to a thorough report.
Even a reasonable, properly performed force incident can raise questions and come under scrutiny if the report describing the situation is not effectively written. If an officer keeps these concepts in mind, I have no doubt the clarity, accuracy and overall quality of their subject control reports will improve.