No Minnesota statute creates negligent retention or negligent supervision claims in general. One statute reaches an employer of a psychotherapist. Under Minn. Stat. § 604.202, that employer “may be liable under section 604.201” if it “fails or refuses to take reasonable action when the employer knows or has reason to know that the psychotherapist engaged in sexual contact with the plaintiff or any other patient or former patient of the psychotherapist” or “fails or refuses to make inquiries” of a disclosed employer that “employed the psychotherapist as a psychotherapist within the last five years” about sexual contact with patients or former patients. The general claims are common-law negligence claims that Minnesota courts built, together with negligent hiring, to hold an employer responsible when it should have stopped an employee from hurting someone. Suppose your company has just been served with one of these claims. The plaintiff must show what the company knew, what it failed to do, and that the failure led to a physical injury or a threat of one. A negligent supervision claim also requires proof that the employee’s actions occurred within the scope of employment.

The statutes that matter sit at the edges of the claim. They decide whether an employee plaintiff is limited to workers’ compensation, whether an employee’s criminal history comes into evidence, and when punitive damages can be added. More on employer-side disputes is on my Minnesota employment law page.

What Are Negligent Hiring, Retention, and Supervision Claims in Minnesota?

They are three separate court-made negligence claims against an employer for injuries its employee causes. The Minnesota Court of Appeals has said that “Minnesota recognizes three causes of action where a claimant sues an employer in negligence for injuries caused by one of its employees: negligent hiring, negligent retention, and negligent supervision.” M.L. v. Magnuson, 531 N.W.2d 849 (Minn. App. 1995).

The Minnesota Supreme Court recognized negligent hiring in 1983 and noted that it had already allowed recovery against an employer for a negligently retained employee. Ponticas v. K.M.S. Investments, 331 N.W.2d 907 (Minn. 1983). The three theories differ by timing and by legal basis:

  • Negligent hiring asks what the company knew, or should have learned, before the employee started.
  • Negligent retention asks what the company learned during the employment and whether it acted on it.
  • Negligent supervision asks whether the company used ordinary care in supervising the employee while the employee was doing the job.

A complaint can name all three theories together, and a plaintiff can add other claims on the same facts, such as a harassment claim under the Minnesota Human Rights Act. Each negligence theory has its own elements, so a defense that defeats one may leave another standing.

What Must a Plaintiff Prove in a Negligent Retention Case?

The plaintiff must show that, during the employment, the company knew or should have known of problems showing the employee was unfit, and that it did not act on them. In Yunker v. Honeywell, Inc., 496 N.W.2d 419 (Minn. App. 1993), the Court of Appeals quoted what it called a “useful definition” from a Florida decision: negligent retention arises “when, during the course of employment, the employer becomes aware or should have become aware of problems with an employee that indicated his unfitness, and the employer fails to take further action such as investigating, discharge, or reassignment.”

The base standard comes from Ponticas: “Liability is predicated on the negligence of an employer in placing a person with known propensities, or propensities which should have been discovered by reasonable investigation, in an employment position in which, because of the circumstances of the employment, it should have been foreseeable that the hired individual posed a threat of injury to others.” The proof for those elements comes from the company’s own records:

  1. Notice. Prior complaints, write-ups, threats, or incidents involving the employee, and who in management heard about them.
  2. Response. What the company did after each warning sign: an investigation, discipline, a transfer, or nothing.
  3. Foreseeability. Whether the earlier conduct made the later harm foreseeable to the person who was hurt.
  4. Causation and injury. Whether the company’s failure to act led to a physical injury or a threat of one.

The earlier conduct need not be the same type as the later harm. Ponticas explained that “negligence is not to be determined by whether the particular injury was foreseeable,” and that the jury could find “that it was reasonably foreseeable that a person with a history of offenses of violence could commit another violent crime, notwithstanding the history would not have shown him to ever have committed the particular type of offense.”

In Yunker, the employee had harassed coworkers, challenged a coworker to fight, threatened to kill another, and focused on the victim in the days before a death threat appeared on her locker. That history made violence foreseeable, so the court let the retention claim go forward. The court left breach and causation to the jury: “These are issues generally decided by a jury after a full presentation of facts.” If an employee has already made a threat, the steps on how to respond to workplace threats apply alongside the defense.

Courts guard against hindsight. In M.L., the court ordered a new trial on the negligence claims. Those claims had gone to the jury “on a single instruction of failure to use reasonable care.” In its retention analysis, the court wrote: “Perhaps in hindsight, given what has been learned about Magnuson’s severe pattern of abuse, his behavior seems suspicious.” The question is what the company knew or should have known at the time, not what the lawsuit later revealed.

Why Does the Physical Injury Requirement Matter for Your Defense?

Physical injury, or a threat of physical injury, is an element the plaintiff must plead and prove, and a complaint without it can be dismissed early. In Johnson v. Peterson, 734 N.W.2d 275 (Minn. App. 2007), the court held: “To set forth a legally sufficient claim for negligent hiring or negligent supervision, the complaint must allege actual physical injury or that the employee posed a threat of physical injury.”

Johnson involved an insurance agent accused of taking money from a vulnerable adult. The plaintiff alleged stress and resulting heart and anxiety problems. The court affirmed dismissal on the pleadings, explaining that “emotional distress is not a physical injury” and that “Economic harm alone is not enough to support negligent-supervision actions.”

The same element applies to retention. In Bruchas v. Preventive Care, Inc., 553 N.W.2d 440 (Minn. App. 1996), a former employee who alleged harassment won a jury verdict for negligent retention and negligent supervision. The trial court set the verdict aside, and the Court of Appeals affirmed, holding that a retention claim based on harassment still requires “some evidence of a threat of physical injury or actual physical injury resulting from the harassment.”

For a company that has been sued, this element shapes the first decision. The defense of “failure to state a claim upon which relief can be granted” may be raised by motion under Minn. R. Civ. P. 12.02, which is how the employer in Johnson won. A complaint that pleads a physical injury or threat meets this element at the pleading stage, and the element is then tested on the evidence. The element governs the negligence counts; sexual harassment claims under the Minnesota Human Rights Act are separate claims with their own elements.

How Is Negligent Supervision Different From Negligent Retention?

Negligent supervision depends on the employee acting within the scope of employment, while negligent retention does not. M.L., quoting a federal decision, defines negligent supervision as the employer’s failure “to exercise ordinary care in supervising the employment relationship, so as to prevent the foreseeable misconduct of an employee from causing harm to other employees or third persons.” Because the theory derives from respondeat superior (an employer’s responsibility for acts done in the course of the job), “the claimant must prove that the employee’s actions occurred within the scope of employment in order to succeed on this claim.”

Yunker shows the difference on one set of facts. The employee, who had just resigned, killed a coworker in her driveway hours after her shift ended. The supervision claim failed because he was not on the employer’s premises or using its equipment. The retention claim survived because his escalating threats made the harm foreseeable. The court held that this foreseeability created a duty of care “that is not outweighed by policy considerations of employment opportunity.” Being off the premises did not defeat that claim, because retention and hiring “are based on direct, not vicarious, liability” and address the risk of exposing others to a dangerous person.

A plaintiff may also plead respondeat superior itself, which makes the company liable without proof of its own fault. The Minnesota Supreme Court, quoting an earlier decision, has said an employer may be held liable for an employee’s intentional misconduct when “(1) “the source of the attack is related to the duties of the employee,” and (2) “the assault occurs within work-related limits of time and place.”” Fahrendorff ex rel. Fahrendorff v. North Homes, Inc., 597 N.W.2d 905 (Minn. 1999). In that case, the court reversed summary judgment for the employer on two grounds. First, a reasonable jury could find that the source of the counselor’s assault “was related to the duties of his employment.” Second, an expert affidavit described sexual abuse as a “well known hazard” in the group home industry. That evidence raised a question of fact as to whether the counselor’s acts “were foreseeable, related to and connected with acts otherwise within the scope of employment.”

When Does Workers’ Compensation Bar an Employee’s Negligence Claim?

When the plaintiff is the company’s own employee, the Workers’ Compensation Act can make workers’ compensation the only remedy, but not for every injury. Minn. Stat. § 176.031 states that an employer’s liability under the Act “is exclusive and in the place of any other liability to such employee, personal representative, surviving spouse, parent, any child, dependent, next of kin, or other person entitled to recover damages on account of such injury or death.” An employee hurt by a coworker on the job may therefore be limited to a compensation claim rather than a negligence suit.

The bar has two limits that matter in these cases. First, the Act’s definition of personal injury requires an injury “arising out of and in the course of employment,” and it excludes an assault for personal reasons. Minn. Stat. § 176.011, subd. 16 says: “Personal injury does not include an injury caused by the act of a third person or fellow employee intended to injure the employee because of personal reasons, and not directed against the employee as an employee, or because of the employment.” Second, when an employer fails to insure or self-insure its compensation liability, the injured employee may elect to sue for damages instead of claiming compensation.

Yunker, applying the Minnesota Supreme Court’s test, required three things for the bar to apply: the injury “(1) must arise out of the employment; (2) must be in the course of employment; and (3) must not come within the assault exception.” The court concluded that the killing, at the victim’s home hours after her shift, failed the “in the course of” requirement, and it said the killing was “almost certainly” within the assault exception. Of the negligence theories, only retention went forward; the court affirmed summary judgment for the employer on hiring and supervision. For an employee plaintiff, the defense should compare the facts against each requirement before answering. The Minnesota Workers’ Compensation Act also creates claims of its own that an employee may add.

How Does a Court Judge What the Company Knew When It Hired?

A court measures the hiring decision by what the company did before and at the time of hiring, with the depth of investigation scaled to the risk the job creates for others. Ponticas held that a breach “must be determined by their actions or omissions prior to and at the time of the hiring,” and that “The scope of the investigation is directly related to the severity of risk third parties are subjected to by an incompetent employee.”

The Ponticas employer hired an apartment manager, gave him a passkey to 198 units, and did not contact the two references on his application, neither of which had a telephone number. The references turned out to be his mother and sister. The jury could find that reasonable care required more. In Yunker, the employee was a custodian whose “job responsibilities entailed no exposure to the general public and required only limited contact with coemployees,” and the hiring claim failed. Under that rule, a job with keys to homes or time alone with customers calls for a deeper check than a production-line job, which Ponticas said might need “only slight care.”

Reference checks are part of that check, and a Minnesota statute limits the suits a former employee can bring over some reference disclosures. Under Minn. Stat. § 181.967, subd. 3, the limit covers a private employer that, in response to a request, discloses “acts of violence, theft, harassment, or illegal conduct documented in the personnel record that resulted in disciplinary action or resignation and the employee’s written response, if any, contained in the employee’s personnel record.” “A disclosure under clause (5) must be in writing with a copy sent contemporaneously by regular mail to the employee’s last known address.” Subdivision 2 bars a suit by the employee or former employee over a covered disclosure unless the employee proves two things by clear and convincing evidence. The employee must show that the information was false and defamatory, and that the employer knew or should have known it was false and acted with malicious intent. Subdivision 6 adds that the section “does not apply to an action involving an alleged violation of chapter 363 or other statute.” More on what a former employer may say in a reference is on a separate page.

What Limits Apply to Evidence of an Employee’s Criminal History?

A Minnesota statute keeps criminal-history evidence out of a suit against a private employer in four situations. The Minnesota Supreme Court has also rejected a rule that, as a matter of law, an employer must inquire into a prospective employee’s criminal record. Minn. Stat. § 181.981, subd. 1 provides that criminal-history information “may not be introduced as evidence in a civil action against a private employer or its employees or agents that is based on the conduct of the employee or former employee, if”:

  1. the job’s duties did not expose others to a greater degree of risk than the employee’s ordinary contact with the public outside the job, or than being employed in general;
  2. before the act behind the lawsuit, a court order sealed a record of the case, a record was sealed by automatic expungement, or the employee received a pardon;
  3. the record is of an arrest or charge that did not result in a conviction; or
  4. the action is based solely on the employer’s compliance with Minn. Stat. § 364.021.

Section 364.021 limits when a private employer may ask about criminal history. An employer generally may not inquire into or consider it until the applicant has been selected for an interview, or, without an interview, before a conditional offer. Subdivision 2 of § 181.981 adds that the section “does not supersede a statutory requirement to conduct a criminal history background investigation or consider criminal history records in hiring for particular types of employment,” so employers in regulated fields remain subject to their own background-check laws.

Ponticas rejected “the contention that, as a matter of law, there exists a duty upon an employer to make an inquiry as to a prospective employee’s criminal record even where it is known that the employee is to regularly deal with members of the public.” The court explained: “Liability of an employer is not to be predicated solely on failure to investigate criminal history of an applicant, but rather, in the totality of the circumstances surrounding the hiring, whether the employer exercised reasonable care. This is generally a jury question.”

A residential building owner hiring a manager has a statutory duty to check. Minn. Stat. § 299C.68, subd. 1 provides: “Before hiring a manager, an owner shall request the superintendent to conduct a background check under this section.” A manager is an individual “who has or would have the means, within the scope of the individual’s duties, to enter tenants’ dwelling units,” under Minn. Stat. § 299C.67, subd. 4. Minn. Stat. § 299C.69 sets what happens when the manager has a conviction for a background check crime listed in § 299C.67, subd. 2. For a crime in paragraph (a), the owner “may not hire the manager” and, if the manager was hired pending the check or the owner otherwise knows of the conviction, “shall terminate the manager’s employment,” except for some managers hired before July 1, 1995. For a crime in paragraph (b), the same rules apply “unless more than ten years have elapsed since the date of discharge of the sentence.”

How Do Punitive Damages Reach an Employer?

Minnesota’s punitive damages statute bars a complaint from seeking punitive damages, and punitive damages based on an employee’s act reach the employer only through one of four statutory routes. Minn. Stat. § 549.191 provides: “Upon commencement of a civil action, the complaint must not seek punitive damages. After filing the suit a party may make a motion to amend the pleadings to claim punitive damages.” The motion needs one or more affidavits showing the factual basis. The statute then provides: “At the hearing on the motion, if the court finds prima facie evidence in support of the motion, the court shall grant the moving party permission to amend the pleadings to claim punitive damages.”

A case in federal court follows different procedure rules. The Federal Rules of Civil Procedure “govern the procedure in all civil actions and proceedings in the United States district courts, except as stated in Rule 81,” and Rule 15(a)(2) sets its own test for amending a pleading: “The court should freely give leave when justice so requires.” A company sued in, or removed to, federal court should check which standard that court applies to a motion adding punitive damages.

The standard at trial is higher. Minn. Stat. § 549.20, subd. 1 allows punitive damages “only upon clear and convincing evidence that the acts of the defendant show deliberate disregard for the rights or safety of others.” Subdivision 2 then limits punitive damages against an employer for an employee’s act to four situations:

  1. the employer “authorized the doing and the manner of the act”;
  2. “the agent was unfit and the principal deliberately disregarded a high probability that the agent was unfit”;
  3. the employee held a managerial role “with authority to establish policy and make planning level decisions” and was acting in the scope of that employment; or
  4. “the principal or a managerial agent of the principal, described in clause (3), ratified or approved the act while knowing of its character and probable consequences” (clause (3) is the third route above).

The second route rests on the same idea as a retention claim, an unfit employee, with a higher bar: deliberate disregard of a high probability of unfitness. A file showing warnings were investigated and acted on is evidence against both the negligence count and a later punitive damages motion.

What Should a Company Do After Being Served With a Negligent Retention Lawsuit?

I suggest calendaring the answer deadline first and taking the steps listed below before choosing a strategy, because each one keeps a defense available. Minnesota’s civil rules provide: “Defendant shall serve an answer within 21 days after service of the summons upon that defendant unless the court directs otherwise pursuant to Rule 4.043.” Minn. R. Civ. P. 12.01. Check the current text of the rule before relying on that period, because court rules are amended. The rule also provides that “The service of a motion permitted under this rule alters these periods of time as follows unless a different time is fixed by order of the court: (1) If the court denies the motion or postpones its disposition until the trial on the merits, the responsive pleading shall be served within 14 days after service of notice of the court’s action; (2) if the court grants a motion for a more definite statement, the responsive pleading shall be served within 14 days after the service of the more definite statement.” The steps for what to do after your business is served cover the answer itself.

The first weeks should include these steps, because each one protects a defense that is hard to rebuild later:

  1. Notify your insurers. I suggest sending the complaint to the carrier under any employment practices liability insurance policy and any general liability policy, because each policy states its own notice requirements. Insurance is also part of the case: “Except as exempted by Rule 26.01(a)(2) or as otherwise stipulated or ordered by the court,” Minn. R. Civ. P. 26.01 requires a party, “without awaiting a discovery request,” to provide the other parties, “for inspection and copying as under Rule 34, any insurance agreement under which an insurance business may be liable to satisfy all or part of a possible judgment in the action.” In one employment discrimination lawsuit I defended, the company’s initial disclosures went to the plaintiff’s attorney with its employment practices liability policy attached.
  2. Preserve the records. A litigation hold should cover the employee’s personnel file, every complaint about the employee, the reference and hiring file, schedules, video, badge data, and messages. In 2026, I answered a trade publication’s posted request about what a medical practice should do after a physician was accused of attacking a colleague. I said the practice should preserve the security video, badge records, and messages from that day, because those records can be overwritten while everyone is still deciding what to do.
  3. Map the notice file. In that same answer, I said the practice’s real exposure was negligent retention and negligent supervision, and that prior complaints, prior outbursts, and prior quiet settlements are what build that claim. Before the answer goes out, a list of every prior warning sign, the date management learned of it, and the company’s response shows where the defense is strong and where it is exposed.
  4. Separate the people involved. If the employee still works for you and the plaintiff is a coworker or customer, changing that employee’s schedule or location protects people now and shows the company acted. For a coworker plaintiff who has “opposed a practice forbidden under this chapter or has filed a charge, testified, assisted, or participated in any manner in an investigation, proceeding, or hearing under this chapter” (the Minnesota Human Rights Act), Minn. Stat. § 363A.15 makes it a reprisal to “depart from any customary employment practice” or “transfer or assign the individual to a lesser position in terms of wages, hours, job classification, job security, or other employment status” because of that activity. The statute adds that “A reprisal includes, but is not limited to, any form of intimidation, retaliation, or harassment.” A neutral workplace investigation of the current facts should come before any decision about discipline.
  5. Test the complaint. Each count should be checked against its elements: physical injury or threat, scope of employment for supervision, the workers’ compensation bar for an employee plaintiff, and whether any criminal-history allegation runs into § 181.981. For an employer of a psychotherapist, the list should add the statutory claim under § 604.202. Each count should also be checked for timeliness. In M.L., the court applied the limitation period for the employee’s underlying battery to the respondeat superior claim, and “that period had expired by the time M.L. commenced his suit” against the employer. For a vicarious liability or respondeat superior claim based on sexual abuse, the current Minn. Stat. § 541.073, subd. 4 provides: “A claim for vicarious liability or liability under the doctrine of respondeat superior must be commenced within six years of the alleged sexual abuse, provided that if the plaintiff was under the age of 18 at the time of the alleged abuse, the claim must be commenced before the plaintiff is 24 years of age.” The subdivision adds: “This subdivision does not limit the availability of these claims under other law.” A negligence count based on sexual abuse falls under subdivisions 2 and 3 instead, because subdivision 3 applies the section to an action against a person “who was a cause of the plaintiff’s damages” by “negligence.” Such an action “must be commenced within six years of the alleged sexual abuse in the case of alleged sexual abuse of an individual 18 years or older” and “may be commenced at any time in the case of alleged sexual abuse of an individual under the age of 18, except as provided for in subdivision 4.” The 2013 law that added that rule “applies to actions that were not time-barred before the effective date,” and an otherwise barred action for abuse of a minor, including a negligence claim, “may be commenced no later than three years following the effective date of this section.” That law took effect May 25, 2013, so the any-time rule does not by itself reach a negligence count already time-barred then and not brought within that window. Check the current text of the statute before relying on those periods, because statutes are amended. Minn. R. Civ. P. 8.03 requires a party, in its answer, to “set forth affirmatively” defenses that include “statute of limitations.” Under Minn. R. Civ. P. 12.08(a), “A defense of lack of jurisdiction over the person, insufficiency of process, or insufficiency of service of process is waived” if it is left out of a Rule 12 motion the company makes, or “if it is neither made by motion pursuant to this rule nor included in a responsive pleading or an amendment thereof permitted by Rule 15.01 to be made as a matter of course.”

The legal options are not the only ones. Where the plaintiff is a current employee, the facts are clear, and the harm was limited, an early conversation between the attorneys about resolution can cost less than a motion and keep the workplace working. Where the complaint has no physical injury or threat, a Rule 12 motion can end the negligence counts early. Where an insurer accepts the defense, the policy’s terms on choosing the defense attorney and on settlement consent should be read before any strategy is set. The right choice depends on the company’s goals: closing the matter quickly, protecting a working relationship, or establishing that the company acted reasonably.

Can a company be liable for an employee's attack that happened away from work?

It can, on a negligent retention theory, if the company knew or should have known the employee was dangerous. In Yunker v. Honeywell, Inc., 496 N.W.2d 419 (Minn. App. 1993), an employee who had just resigned killed a coworker in her driveway. The Minnesota Court of Appeals let the retention claim go forward, because his escalating workplace threats made violence foreseeable. The negligent supervision claim failed in the same case, because the killing happened off the employer’s premises and without its equipment.

Does a lawsuit survive if the plaintiff alleges only emotional distress?

Not as a negligent hiring, retention, or supervision claim. The Minnesota Court of Appeals addressed the question in Johnson v. Peterson, 734 N.W.2d 275 (Minn. App. 2007). It held that a hiring or supervision complaint must allege actual physical injury or that the employee posed a threat of physical injury. Emotional distress is not a physical injury, economic harm alone is not enough, and dismissal on the pleadings was affirmed. In Bruchas v. Preventive Care, Inc., 553 N.W.2d 440 (Minn. App. 1996), retention and supervision claims failed as a matter of law without proof of personal injury or a threat of physical injury.

Is hiring someone with a criminal record negligent by itself?

No. In Ponticas v. K.M.S. Investments, 331 N.W.2d 907 (Minn. 1983), the Minnesota Supreme Court rejected a rule that, as a matter of law, an employer must inquire into a prospective employee’s criminal record. The test is reasonable care in the totality of the circumstances, generally a jury question. Minn. Stat. § 181.981 bars criminal-history evidence against a private employer in four situations. It does not supersede a statutory requirement to conduct a criminal history background investigation or consider criminal history records in hiring for particular types of employment. One example is Minn. Stat. § 299C.68 for residential building managers.

Can the plaintiff add punitive damages later in the case?

Yes, but only by motion. Minn. Stat. § 549.191 bars a complaint from seeking punitive damages, and the plaintiff must later move to amend with one or more affidavits showing the factual basis. If the court finds prima facie evidence in support of the motion, it shall grant permission to amend. In federal court, the standard in Federal Rule of Civil Procedure 15 may apply instead. Against an employer for an employee’s act, Minn. Stat. § 549.20, subd. 2 allows punitive damages only through four routes, including deliberately disregarding a high probability that the employee was unfit.

Can we be sued for negligent training in Minnesota?

Not as a separate claim. In Johnson v. Peterson, 734 N.W.2d 275 (Minn. App. 2007), the Minnesota Court of Appeals said current Minnesota law does not recognize a cause of action for negligent training. It affirmed dismissal of that count. The court then tested the supervision count against its own elements and affirmed its dismissal too, because the complaint alleged no physical injury or threat of one.

Should we fire the employee now that we have been sued?

No rule requires a termination because a suit was filed. A residential building owner that knows its manager was convicted of certain background check crimes must, with narrow exceptions, terminate the manager under Minn. Stat. § 299C.69. Retention liability rests on what the company knew and whether it took action such as investigating, discharge, or reassignment, as Yunker v. Honeywell, Inc., 496 N.W.2d 419 (Minn. App. 1993) describes. I suggest deciding after investigating the current facts, because a decision supported by documented facts is easier to explain to a jury than one made in reaction to the complaint.

What if the employee who caused the harm is a manager?

A manager’s act can open a route to punitive damages against the employer. Under Minn. Stat. § 549.20, subd. 2, one route covers an act of an agent employed in a managerial capacity with authority to establish policy and make planning level decisions. The agent must have been acting in the scope of that employment. A separate route turns on who approved the act: the employer, or a managerial agent with that authority, ratified or approved it while knowing its character and probable consequences. A negligent supervision claim still requires proof that the act fell within the scope of employment.

Defending the Claim on Its Elements

A Minnesota negligent retention or supervision claim is a common-law negligence claim with specific elements, and each element is a place to defend. The plaintiff must show the company knew or should have known the employee was unfit and failed to act, and that this caused a physical injury or a threat of one. Supervision claims also need conduct within the scope of employment. Workers’ compensation may bar an employee plaintiff’s suit, and § 181.981 keeps some criminal-history evidence out. Section 549.191 requires a later motion to add punitive damages, and § 549.20 limits punitive damages for an employee’s act to four statutory routes. The company’s own records of what it knew and what it did bear on each of these questions.

If your company has been served with a negligent retention or supervision claim and you want to know which defenses fit your facts, email [email protected] with a brief description. I can start an intake and conflict check before you send any confidential documents. More on these issues is on my Minnesota employment law page.