Padilla Mills
•
5 min read

There is a troubling question regarding police encounters that needs to be addressed: When does a mistake become neglect of duty? If they aren't the same, where's the line between them?

When management doesn't like an officer's decision, when a supervisor believes something could have been handled differently, or when an incident produces an undesirable outcome, "neglect of duty" can become the convenient catchphrase that supposedly covers everything. It shouldn't. Words matter. Allegations matter.

And neglect of duty should actually require neglect.

As a union, we don't argue that officers should be immune from accountability. If an officer maliciously refuses to perform a legitimate duty, deliberately ignores a responsibility, or repeatedly fails to do something after clear instruction and training, there may be a legitimate disciplinary issue at hand. But that is very different from making a mistake.

You, as police and correction officers, make decisions in the real world, not in an administrative conference room six weeks later. An officer may have seconds to evaluate a situation involving incomplete information, radio traffic, conflicting statements, multiple calls, safety concerns, and competing responsibilities. All without the luxury of 20/20 hindsight.

Then comes the investigation, where everyone has time. Investigators can watch body-camera footage 10 times. They can freeze the video at the exact second something happened. They can compare timestamps, read every report, listen to radio traffic, review policy, interview witnesses, and discuss what the officer "should have done." That's useful for determining what happened, as we would do in a squad debrief. But it can also create a dangerous illusion that the officer making the original decision possessed all of the information investigators later accumulated. That is not a fair standard.

The disciplinary question at hand isn't, "What could the officer have done differently?" You can ask that question after almost any police call and find something.

The question should be: "Given what the officer reasonably knew at the time, did the officer make a good-faith effort to perform their job at that exact moment, with the facts they had in their specific situation?" You can't encourage discretion and punish it at the same time. Management frequently tells officers to use judgment, exercise discretion, take initiative, and solve problems. Then an officer exercises that judgment, the decision doesn't work out perfectly, and suddenly everyone discovers a policy provision that supposedly made the answer obvious. That's not accountability. That's Monday-morning quarterbacking.

If an officer maliciously violates a clear, established requirement, investigate it. But if policy permits discretion, management must accept an uncomfortable reality: discretion sometimes produces decisions that supervisors would have made differently. AND THAT'S OK! Otherwise, we're not actually giving officers discretion. We're asking them to unfairly predict what a supervisor will think several weeks later, using facts and perception the officer doesn't have at the time.

Ask the Most Important Question: Why?

Before sustaining an allegation of neglect of duty, an investigator should have to answer one basic question: Why didn't the officer do what management now says should have been done?

Did the officer intentionally avoid responsibility?

Or did the officer misunderstand information? Miss a radio transmission? Face competing priorities? Receive unclear instructions? Interpret an ambiguous policy differently? Make a judgment call that turned out to be wrong?

Those circumstances matter.

If we stop asking why and simply discipline based on the outcome, then neglect of duty becomes little more than a label applied to human error. If an agency expects officers to perform a task in a particular manner, those expectations should be clearly communicated, officers properly trained, and the standards consistently enforced. An unwritten expectation should not magically become a "clearly established responsibility" after something goes wrong. Neither should management be permitted to take a vague policy, interpret it in the most restrictive possible manner after an incident, and then discipline an officer for failing to anticipate that interpretation.

Fairness requires notice.

Good officers make mistakes. Every officer reading this has made a mistake. So has every sergeant. Every lieutenant. Every captain. Every chief and sheriff. The difference is that most mistakes don't mean someone neglected their responsibilities. There is an enormous difference between an officer with a demonstrated pattern of ignoring duties despite training and counseling and a hardworking officer who commits an error.

Sometimes an officer needs additional training. And sometimes a supervisor needs to say, "You made a mistake. Here's what I want you to do differently next time."

Not every problem requires a formal "Statement of Complaint" to be opened.

There is also a consequence management should consider. If every mistake can become neglect of duty, officers learn quickly. They stop taking initiative. They stop making discretionary decisions. They become more concerned about protecting themselves administratively than solving the problem in front of them. That is dangerous when faced with split-second decisions. That isn't the workforce any police organization should want.

We should encourage officers to think, make decisions, learn from mistakes, and improve. That requires an environment where legitimate misconduct is addressed but honest mistakes are recognized for what they are. Our position in the LVPPA is simple. We support accountability. We do not support manufacturing misconduct out of ordinary human error. When the facts establish genuine neglect, call it neglect. When they establish intentional misconduct, call it misconduct. But when an officer made a reasonable, good-faith effort and simply got something wrong, have the integrity to call it what it is: a mistake.

And when "neglect of duty" is used as a convenient catch-all because management can't identify what an officer actually neglected, we will challenge it. Because accountability and fairness aren't opposing ideas. Real accountability requires both.