Municipal liability cases often look straightforward from the outside. A person is harmed by a police department, jail, sheriff’s office, city agency, or county program, and the public reaction is immediate: if the officer or employee worked for the government, why not sue the city too?
That is where things get complicated.
Under 42 U.S.C. § 1983, a city or county is not automatically liable just because one of its employees allegedly violated someone’s constitutional rights. In Monell v. Department of Social Services, the Supreme Court explained that municipal liability turns on a government policy or custom that caused the injury, not simple employer responsibility. Later decisions like City of Canton v. Harris, Board of County Commissioners of Bryan County v. Brown, and Connick v. Thompson made clear that courts apply demanding standards for fault and causation in these cases.
That demanding standard is one reason systemic civil rights cases can become harder to prove than cases against a single officer. If you want a fuller foundation on how department policy, custom, supervision, and training failures fit into these claims, it may help to start with this overview of how city and department liability works.
In this post, you’ll learn seven common mistakes that can weaken a municipal liability case and why experienced case development often matters so much when the target is not just an individual employee, but an entire government system.
<aside> 💡 Scroll to the bottom for every post in this series.
</aside>
One of the biggest mistakes is assuming a city is liable the same way a private employer might be liable for an employee’s conduct.
That is not how federal municipal liability usually works. In Monell, the Supreme Court held that municipalities are “persons” that can be sued under § 1983, but not on a simple respondeat superior theory. Instead, liability attaches when the execution of a government’s policy or custom inflicts the injury. In practical terms, that often means the case rises or falls on whether the evidence connects the harm to an official rule, a tolerated practice, a failure in training or supervision, or a decision by an authorized policymaker.
This distinction is not just technical. It changes the whole structure of the case:
The Department of Justice’s law-enforcement misconduct materials reflect the same systemic focus. Federal pattern-or-practice investigations often examine policies, training, supervision, data collection, accountability systems, and recurring conduct, not only isolated incidents (DOJ overview; Special Litigation Section cases and matters).
Here’s what this often means: a person may have compelling evidence that an officer acted unlawfully, while still facing a separate and much harder task in proving the city or county itself is legally responsible.
A single incident can matter a lot, but many municipal liability claims become harder when the case is framed as one shocking event without the surrounding system.
Courts have repeatedly emphasized that municipal liability requires rigorous proof of culpability and causation. In Bryan County v. Brown, the Supreme Court said those standards help ensure a municipality is not held liable solely for an employee’s actions. In Connick v. Thompson, the Court also treated “failure to train” claims with caution, particularly where the plaintiff tries to infer a broader policy failure from limited proof.