What It Costs When a Mayor Fires a Police Chief
Tracks what municipalities actually pay when a mayor or council removes a police chief without the required process: reinstatement with back pay, jury verdicts, and five- to six-figure settlements across the Sturgeon, Colfax, Rochester, and Mount Vernon cases. Each record carries jurisdiction, court, ruling date, penalty or settlement amount, and case status so counsel can benchmark exposure before a removal is attempted.
- Jurisdiction
- Missouri, USA
- Court
- Missouri Court of Appeals, Western District
- AI tool named
- No AI tool named
- Ruling date
- Jan 1, 2023
- Source document
- View primary court order ↗
- Last verified
- Aug 3, 2026
Lex Machina Review is an independent risk-tracking and reference resource. Nothing on this site is legal advice, and using it does not create an attorney-client relationship. Every record is reviewed against primary sources but may not reflect the most current status of a matter — always verify directly against the cited court order, rule text, or a licensed attorney before relying on it.
Companion explanation — secondary to the source document above
The cost of a failed police-chief removal is not confined to a severance line or one angry council meeting. In the Sturgeon, Missouri record, the removal dispute produced reinstatement with roughly 20 months of back pay, a Boone County jury verdict of $300,000 in compensatory damages and $15,000 in punitive damages, and a later Missouri Court of Appeals decision treating the statutory removal hearing as a contested case under Missouri law. [1][2][3]
That is the practical legal implication when the required notice, hearing, or just-cause record is skipped: the municipality may be buying more than litigation defense. It may be buying back pay, reinstatement risk, jury damages, punitive exposure, settlement pressure, records-work burden, insurer scrutiny, and months of after-the-fact record reconstruction.

Benchmark records
Non-advice notice: this record is for legal-risk benchmarking and editorial analysis only. It is not legal advice and does not substitute for jurisdiction-specific counsel review. Legal-background reviewer: not supplied in the available source materials; record-level verification below is limited to the materials available for this article.
| Record | Jurisdiction / forum | Ruling or settlement date | Amount or remedy | Status | Process issue flagged in available materials | Last verified |
|---|---|---|---|---|---|---|
| Halderman v. City of Sturgeon | Sturgeon, Missouri; Boone County circuit proceedings and Missouri Court of Appeals, Western District | Reinstatement order in 2019; jury verdict in July 2021; appellate decision in 2023 | Reinstatement with roughly 20 months of back pay; $300,000 compensatory damages; $15,000 punitive damages | Court-tested record; appellate holding available | Removal without required process; statutory police-chief removal hearing treated as a contested case | 2026-08-03 UTC [1][2][3] |
| Colfax police-chief removal settlement | Colfax; forum not identified in available source materials | Settlement date not identified in available source materials | $435,000 settlement | Settlement benchmark; not a liability finding | Available brief identifies removal-process exposure; available source materials do not provide a primary link | 2026-08-03 UTC |
| Rochester police-chief removal settlement | Rochester; forum not identified in available source materials | Settlement date not identified in available source materials | $75,000 settlement | Settlement benchmark; not a liability finding | Available brief identifies removal-process exposure; available source materials do not provide a primary link | 2026-08-03 UTC |
| Mount Vernon police-chief removal settlement | Mount Vernon; forum not identified in available source materials | Settlement date not identified in available source materials | $65,000 settlement | Settlement benchmark; not a liability finding | Available brief identifies removal-process exposure; available source materials do not provide a primary link | 2026-08-03 UTC |
The distinction in the status column matters. A settlement amount is a useful exposure signal because it shows what a municipality paid to close the dispute. It is not, by itself, proof that the city violated the law. Sturgeon carries more weight because it supplies the mechanism: a process failure, judicial remedies, jury damages, and an appellate treatment of the removal hearing.
Sturgeon shows the failure chain, not just the bill
The Sturgeon record is the one municipal counsel should read before assuming a chief’s removal can be cleaned up later. The appellate opinion in Halderman v. City of Sturgeon addressed the character of the removal hearing required under Section 106.273, RSMo, and held that the hearing was a contested case. [1]
That holding is not a clerical footnote. If a hearing is a contested case, the city is not merely managing an employment conversation. It is creating — or failing to create — the administrative record that later courts, lawyers, insurers, and taxpayers will have to live with. The missing notice, the unheld hearing, and the absence of a defensible just-cause finding become evidence problems as much as governance problems.
The available Missouri materials describe a sequence that should be familiar to anyone who has watched a municipal dispute become a public-records file: the chief was removed, a court found a due-process violation, reinstatement with roughly 20 months of back pay followed, and a later Boone County jury awarded $300,000 in compensatory damages and $15,000 in punitive damages. [2][3]
The financial implications are layered. Reinstatement can reopen the employment relationship rather than simply price its end. Back pay ties the cost to time. Compensatory damages can move the matter beyond payroll arithmetic. Punitive damages, even at $15,000 in this record, change the conversation for elected officials, coverage reviewers, and defense counsel because they signal that the jury saw more than a harmless procedural miss. [2]
The important lesson is narrower than “never remove a chief.” Missouri law supplied a removal procedure, and the court record treated that procedure as legally meaningful. When officials proceed as though the process can be supplied after the termination letter, the later fight is no longer about management discretion alone. It is about whether the municipality had legal authority to act in the way it acted, at the time it acted.

What the settlement records add
Colfax, Rochester, and Mount Vernon do not carry the same court-tested detail in the available source materials. They still belong in the benchmark set because their dollar amounts show the settlement range municipal defendants have faced after police-chief removal disputes: $435,000 in Colfax, $75,000 in Rochester, and $65,000 in Mount Vernon.
Those figures should be read conservatively. A settlement can reflect litigation risk, defense cost, political fatigue, insurance dynamics, evidentiary uncertainty, or a practical desire to end the matter. It does not establish that every mayoral removal with a process dispute will produce liability, and it does not prove that every removed chief had a meritorious claim.
For benchmarking, though, the settlements still do useful work. They prevent counsel from treating Sturgeon as a one-off Missouri outlier with an unusually developed record. The numbers cluster where municipal risk managers do not like to see routine personnel matters cluster: five figures at the low end of the supplied set, six figures when the dispute becomes harder to close, and a court-tested record showing that reinstatement and jury damages are not theoretical remedies.
The recurring failure mode
The repeated risk signal is not that cities can never change police leadership. It is that a mayor or council cannot safely treat the removal process as a ceremonial stop on the way to a decision already made. Where a statute, ordinance, contract, civil-service rule, or recognized property interest requires process, the financial control is the process itself.

In practical terms, the pre-removal file should answer the questions a later reviewer will ask first, not the questions officials wish had mattered most at the time:
- What legal source gives the chief removal protection, hearing rights, or a just-cause standard?
- Who has authority to initiate removal, who has authority to decide it, and whether those roles are separated or combined under local law?
- What notice was delivered, when it was delivered, and whether it identified the charges or grounds with enough specificity to permit a response?
- Whether the chief had a meaningful opportunity to be heard before the removal became final?
- Whether the city made a just-cause finding where just cause was required, and who signed it?
- Whether any protected-speech, whistleblower, political-retaliation, or public-policy allegation is already visible in the record?
- Whether the minutes, notices, exhibits, personnel file, and closed-session record will make sense to someone who was not in the room?
The retaliation overlay is especially expensive because it changes the emotional and evidentiary shape of the case. A pure process defect can sometimes be explained as a hurried or mistaken reading of local authority. A process defect paired with alleged retaliation invites a different inference: that the skipped hearing was not an administrative lapse, but part of the removal strategy.
That is why the Sturgeon record should make city officials pause before relying on a later explanation. Once a court is reviewing whether the required hearing occurred, and a jury is hearing damages evidence, the city is no longer controlling the narrative from the dais. It is defending documents, dates, votes, notices, and omissions.
Counsel’s pre-removal benchmark
Before a removal vote, notice, suspension, or termination letter, counsel can benchmark the exposure against the records above without pretending the cases are identical. The point is not to predict the exact settlement value of the next dispute. It is to identify whether the city is about to reproduce the same risk pattern: protected position, incomplete notice, no meaningful hearing, weak or unsigned just-cause record, and facts that support a retaliation theory.
| If the file shows | Risk implication | Benchmark consequence |
|---|---|---|
| No clear statutory, ordinance, contract, or civil-service authority mapped before action | Officials may be acting faster than the legal record can support | Post-removal litigation begins with an authority problem |
| No notice identifying charges or grounds | The city may struggle to show the chief had a meaningful chance to respond | Due-process and reinstatement risk increase |
| No hearing opportunity where one is required | The defect is easy for a later reviewer to see | Back pay may accumulate while the dispute is pending |
| No just-cause finding where just cause is required | The city may have a management reason but not a legally usable record | Settlement pressure rises because the proof problem is documentary |
| Retaliation allegations already visible | The dispute may move beyond procedural correction | Compensatory and punitive exposure become harder to dismiss early |
The municipal cost is measurable enough to check before the decision is made. Sturgeon supplies the hard-edged version: reinstatement, back pay, compensatory damages, punitive damages, and appellate treatment of the removal hearing as a contested case. Colfax, Rochester, and Mount Vernon supply settlement benchmarks that show the exposure can still be material even when the available public record does not produce a full merits narrative.
For a city considering removal, the required process is not a courtesy to be documented later. It is a financial control to be tested before the vote, before the notice goes out, and before the termination letter becomes the first exhibit.
References
- Halderman v. City of Sturgeon, FindLaw
- Beware the Perils of Improperly Removing a Police Chief, municipalfirm.com
- What it takes to fire a police chief, KOMU
Related records
Tool profile
How Meta's AI Spending Reshapes Law Firm ProfitabilityGoverning regulation
Browse the obligations tracker →Preventive workflow
Browse verification workflows →
Report a correction or tip
Spotted an outdated figure, a misstated fact, or a ruling this case record should reflect? Public comments are disabled for this content given the professional cost of a misreported case outcome, penalty amount, or rule text — use the structured correction channel instead.
Report a correction or tip for this record →