An arrest that goes wrong in Minnesota gives you two cases out of one set of facts, and I plead them both. There’s the federal constitutional claim under 42 U.S.C. § 1983, and there’s the ordinary state tort claim — battery, false imprisonment, negligence — against the officer and, through Minn. Stat. § 466.02, against the officer’s employer.
They aren’t two labels for the same lawsuit. They have different defendants available, different immunity doctrines with different tests, different ceilings on recovery, and different deadlines. A claim that survives on one track can be dead on the other, in either direction. I’ve read too many complaints that pick one track without ever noticing there was a choice.
The federal side — qualified immunity, and Monell‘s bar on holding a city liable for its officers’ acts — I cover in what “clearly established” actually requires and municipal liability under Monell. This one’s about the state track. It runs on Minnesota common law and Minnesota statutes, and most talk about police liability skips it entirely.
The biggest difference: the city answers for the officer
Under § 1983 there’s no respondeat superior. A city answers only for its own policy or custom.
Minnesota’s Municipal Tort Liability Act starts from the other end. Minn. Stat. § 466.02:
Subject to the limitations of sections 466.01 to 466.15, every municipality is subject to liability for its torts and those of its officers, employees and agents acting within the scope of their employment or duties whether arising out of a governmental or proprietary function.
That’s vicarious liability, stated plainly. On the state track I don’t have to prove a policy, a custom, or a pattern of failure to train. Prove the officer committed a tort in the scope of employment and you reach the city directly.
Then the rest of chapter 466 takes a lot of that back. Section 466.03 removes twenty-nine categories of claim from § 466.02’s reach, and a claim that lands in one of them doesn’t get sent back to ordinary negligence — it gets sent to whatever other statute supplies liability, and to immunity if none does. I map that section in twenty-nine municipal immunities and won’t redo it here.
Official immunity isn’t qualified immunity with a Minnesota accent
Statutory immunity under § 466.03, subd. 6 protects the municipality’s policy choices. Official immunity protects the individual official’s judgment. People mix the two up constantly, and the Minnesota Supreme Court has warned against exactly that. In Elwood v. County of Rice, 423 N.W.2d 671, 678 (Minn. 1988), the court said it had “recently stressed the importance of distinguishing between the common law immunity of a government employee and the immunity of a governmental unit under the state and municipal tort claims statutes,” and explained why: “Both doctrines are phrased in terms of whether discretion was involved, but they are based on entirely different rationales.”
The official immunity rule itself is old and short. Quoting Elwood, the court restated it in Vassallo ex rel. Brown v. Majeski, 842 N.W.2d 456, 462 (Minn. 2014):
[A] public official charged by law with duties which call for the exercise of his [or her] judgment or discretion is not personally liable to an individual for damages unless he is guilty of a willful or malicious wrong.
The court applies a three-step inquiry, restated most recently in Kariniemi v. City of Rockford, 882 N.W.2d 593 (Minn. 2016), quoting Vassallo: official immunity “turns on: (1) the conduct at issue; (2) whether the conduct is discretionary or ministerial …; and (3) if discretionary, whether the conduct was willful or malicious.” Vassallo, 842 N.W.2d at 462.
In my experience two features of that test decide most cases.
For one, “discretionary” means something broader here than it does under § 466.03. For statutory immunity, discretion means policy-level judgment. For official immunity, it reaches any act involving a significant exercise of independent judgment, including at the operational level — the officer on the street.
And a “ministerial” duty is the plaintiff’s way in. A ministerial duty is “one that is ‘absolute, certain, and imperative, involving merely the execution of a specific duty arising from fixed and designated facts.’” Id. If the officer had a ministerial duty and breached it, official immunity doesn’t attach to that conduct at all. You never get to the malice question.
These cases are won in the department’s own manual
Nothing in federal law looks like this part of Minnesota law, and it’s why the state track earns its place in the complaint.
The Minnesota Supreme Court has “rejected the argument that ‘all police conduct in emergencies is discretionary,’” recognizing that “governmental entities have the authority to eliminate by policy the discretion of their employees.” Vassallo, 842 N.W.2d at 462 (quoting Mumm v. Mornson, 708 N.W.2d 475, 493 (Minn. 2006)). A government policy that “sets a sufficiently narrow standard of conduct will make a public employee’s conduct ministerial if he is bound to follow the policy.” Id. at 463 (quoting Mumm, 708 N.W.2d at 491).
Put two cases side by side — decided eight years apart on almost the same facts — and watch it work.
In Thompson v. City of Minneapolis, 707 N.W.2d 669 (Minn. 2006), the Minneapolis pursuit policy read: “Officers shall use red lights and siren in a continuous manner for any emergency driving or vehicular pursuit.” The court held: “the Pursuit Policy creates a ministerial duty to continuously operate emergency lights and siren during a ‘vehicular pursuit.’” Id. at 675. If the officers violated it, official immunity was gone as to claims arising from the non-use of lights and siren.
In Vassallo, the Hennepin County policy read: “The use of both red lights and siren is required when responding to an emergency.” The court held that wasn’t enough. The Hennepin policy “does not require that red lights and siren be used in a continuous fashion,” 842 N.W.2d at 464, and without words denoting constant or continuous use it “fails to create a duty that is ‘absolute, certain, and imperative,’” id. at 465. The deputy kept his immunity, and the county kept its.
Three words — “in a continuous manner” — are the whole difference between those two outcomes. No constitutional standard turns on the wording of a municipal manual. Minnesota official immunity does. That’s why the department’s written policies, general orders, and training bulletins sit at the top of my discovery list on the state claim, and why I chase the unwritten practices too: the court has held an unwritten protocol capable of creating a ministerial duty where it was consistently taught and enforced. One adverb in a general order can be the case.
Malice is a hard standard
If the conduct was discretionary, the only route left is willfulness or malice, and I tell clients up front how demanding that standard is.
Vassallo, at 465, doesn’t mince words: “Malice is not negligence.” It is “the intentional doing of a wrongful act without legal justification or excuse, or, otherwise stated, the willful violation of a known right.” Rico v. State, 472 N.W.2d 100, 107 (Minn. 1991). And the exception “anticipates liability only when an official intentionally commits an act that he or she then has reason to believe is prohibited.” Ibid.
That’s not a good-faith test and it’s not an objective-reasonableness test. It asks what the officer knew about the lawfulness of what the officer was doing.
It isn’t toothless either. Elwood said so while granting immunity on trespass and battery claims against sheriff’s deputies: “The doctrine protects honest law enforcement efforts, and is not intended to shield police brutality.” 423 N.W.2d at 679.
If the officer wins, the city wins
Minnesota extends the officer’s personal immunity to the employer. In Pletan v. Gaines, 494 N.W.2d 38, 43 (Minn. 1992), a high-speed pursuit case, the court held “that with respect to high-speed police pursuits, the police officer’s official immunity extends to the officer’s public employer.” The general rule, quoted in Vassallo at 465:
Where an employee or agent is protected by official immunity, the government entity will not be called on to indemnify that individual nor will the government entity be liable under the doctrine of respondeat superior.
So § 466.02’s vicarious liability is real, but it comes with a condition. It delivers the city only if the officer isn’t immune. That’s the federal problem in a mirror: on the federal track a plaintiff can beat the officer’s qualified immunity and still lose the city under Monell; on the state track a plaintiff who loses the officer to official immunity loses the city with him.
Pletan also left a door cracked, noting that an earlier decision “suggests this court might under some circumstances find an exception to vicarious official immunity.” 494 N.W.2d at 42. I wouldn’t build a case around that sentence. But it’s there.
Ceilings and deadlines split hard
The state claim is capped; the federal claim isn’t. Minn. Stat. § 466.04, subd. 1(a)(3) and (7) limit municipal liability to $500,000 per claimant and $1,500,000 per occurrence for claims arising on or after July 1, 2009. Subdivision 1(b) is one sentence: “No award for damages on any such claim shall include punitive damages.” Subdivision 1a extends the same limits to the officer individually, and subdivision 1b provides that naming the officer doesn’t add a layer. Look at the cap’s own scope language — it limits liability “on any claim within the scope of sections 466.01 to 466.15,” which is the Municipal Tort Liability Act, not federal law.
Punitive damages are available on the federal side, against the individual. Smith v. Wade, 461 U.S. 30, 56 (1983): “a jury may be permitted to assess punitive damages in an action under § 1983 when the defendant’s conduct is shown to be motivated by evil motive or intent, or when it involves reckless or callous indifference to the federally protected rights of others.”
The officer is defended and indemnified — with conditions. Minn. Stat. § 466.07, subd. 1 requires a municipality to “defend and indemnify any of its officers and employees … for damages, including punitive damages,” provided the officer “was acting in the performance of the duties of the position” and “was not guilty of malfeasance in office, willful neglect of duty, or bad faith.” Hold those conditions up against the malice standard above: the same finding that defeats official immunity is the kind of finding that can put the officer outside the indemnity.
And the clocks run at three different speeds. The § 1983 claim runs six years; the state battery, false imprisonment, and defamation claims run two under Minn. Stat. § 541.07(1); and against a municipality the 180-day notice under Minn. Stat. § 466.05 runs first and fastest. I work all three through in the § 1983 limitations period in Minnesota and the deadline that ends your case against a Minnesota city.
Why I plead both
The two tracks fail for unrelated reasons, and each one covers a gap in the other.
Qualified immunity turns on whether a prior case put the constitutional question beyond debate. Official immunity turns on whether the officer had a ministerial duty and, if not, whether the officer acted with malice. A case with no closely analogous federal precedent can still be a case where a department policy said “shall,” in continuous terms, and the officer didn’t. A case with a clear constitutional violation can still run into the fact that Minnesota law asks about the officer’s knowledge of prohibition rather than about objective reasonableness.
The money looks different too. The federal claim is uncapped and carries fee shifting under 42 U.S.C. § 1988(b), which I take up in why these cases get taken at all. The state claim is capped, can’t reach punitive damages against the municipality, and — where the officer isn’t immune — reaches the city without any Monell showing.
Neither one is the safe choice. Picking between them before discovery, because one theory sounds better in the abstract, is how a viable claim gets left out of a complaint that was filed on time. Plead both, and let discovery tell you which one carries the case.
Here’s the thing I keep coming back to. Minnesota’s official immunity doctrine can be beaten by the defendant’s own paperwork, and the federal doctrine can’t. Qualified immunity asks what the federal courts have already held. Official immunity asks, first, what the officer’s department told the officer to do, in words — and whether those words left room for judgment. Those words live in documents the plaintiff doesn’t have on the day the file opens. Go get them.
Madgett Law, LLC litigates civil rights and police misconduct claims in Minnesota state and federal court, including claims against municipalities under Minn. Stat. ch. 466 and the immunity and notice questions that come with them. Whether to take the state track, the federal track, or both is a call best made early. Send us a message or call 612-470-6529.
Sources: Minn. Stat. § 466.02 (2025) (municipal liability for the torts of its officers, employees, and agents acting within the scope of employment, quoted in full); § 466.03, subd. 6 (discretionary function or duty — referenced, not re-derived; the full enumeration is treated in our companion article); § 466.04, subd. 1(a)(3) and (a)(7) ($500,000 per claimant and $1,500,000 per occurrence for claims arising on or after July 1, 2009), subd. 1(b) (“No award for damages on any such claim shall include punitive damages.”), subd. 1a (officers and employees within the same limits, with the outside-professional-services carve-out), and subd. 1b (single-occurrence total), together with the scope language of subd. 1(a) (“any claim within the scope of sections 466.01 to 466.15”); § 466.05 (180-day notice — referenced only); § 466.07, subd. 1 (mandatory defense and indemnification “for damages, including punitive damages,” conditioned on performance of duties and the absence of “malfeasance in office, willful neglect of duty, or bad faith,” and applicable to all school districts); § 541.07(1) (two-year period for libel, slander, assault, battery, false imprisonment, or other tort resulting in personal injury) (Minnesota Office of the Revisor of Statutes, 2025 Minnesota Statutes, revisor.mn.gov). Elwood v. County of Rice, 423 N.W.2d 671, 677, 678, 679 (Minn. 1988) (official immunity formulation at 677; “based on entirely different rationales” and the statutory/official immunity contrast at 678; “The doctrine protects honest law enforcement efforts, and is not intended to shield police brutality,” and the grant of official immunity on trespass and battery claims against sheriff’s deputies, at 679). Vassallo ex rel. Brown v. Majeski, 842 N.W.2d 456, 462, 463, 464, 465 (Minn. 2014) (official immunity formulation, the three-step inquiry, the ministerial-duty definition, and the rejection of the proposition that all emergency police conduct is discretionary, quoting Mumm v. Mornson, 708 N.W.2d 475, 493 (Minn. 2006), all at 462; the “sufficiently narrow standard of conduct” rule, quoting Mumm at 491, at 463; “does not require that red lights and siren be used in a continuous fashion” at 464; “fails to create a duty that is ‘absolute, certain, and imperative’” at 465; “Malice is not negligence,” the Rico definition, and the Watson v. Metropolitan Transit Commission, 553 N.W.2d 406, 415 (Minn. 1996) vicarious rule, all at 465). Kariniemi v. City of Rockford, 882 N.W.2d 593 (Minn. 2016) (restating the official immunity purpose and three-step inquiry, quoting Vassallo). Thompson v. City of Minneapolis, 707 N.W.2d 669, 675 (Minn. 2006) (text of Minneapolis Pursuit Policy § 7-405 and the holding that it creates a ministerial duty of continuous lights and siren during a vehicular pursuit). Rico v. State, 472 N.W.2d 100, 107 (Minn. 1991) (malice definition; liability “only when an official intentionally commits an act that he or she then has reason to believe is prohibited”). Pletan v. Gaines, 494 N.W.2d 38, 42, 43 (Minn. 1992) (the suggestion that an exception to vicarious official immunity might exist, at 42; the holding extending official immunity to the public employer in high-speed pursuit cases, at 43). Smith v. Wade, 461 U.S. 30, 56 (1983) (punitive damages standard under § 1983). Case text: Caselaw Access Project, static.case.law. This article does not state whether any particular department policy creates a ministerial duty, does not address statutory immunity under § 466.03 beyond identifying it, and does not address whether or how Minn. Stat. § 609.066 or § 609.06 bears on a civil claim. This article is general legal information about Minnesota law, not legal advice, and reading it does not create an attorney–client relationship. Whether any immunity applies depends on the facts, the entity, the policy language, and the version of the statute in force when the claim arose. No outcome is promised or implied.