Repeating Your Employer's False Reason to a Job Interviewer Can Be the "Publication" in a Minnesota Defamation Case — but Compulsion, Foreseeability, and Proof of the Interviews Are All Required

The rule Minnesota adopted, and the sentence it is contained in

Minnesota recognizes a defamation claim in which the only person who ever repeated the employer’s statement is the employee. The Minnesota Supreme Court created it on July 3, 1986, in Lewis v. Equitable Life Assurance Society of the United States, 389 N.W.2d 876 (Minn. 1986), where four dental claim approvers were fired for “gross insubordination” after refusing to revise expense reports they said were honest. The company itself said nothing to anyone outside: “[t]he company neither published nor stated to any prospective employer that plaintiffs had been terminated for gross insubordination.” Id. at 882. Each plaintiff, asked in job interviews why she had left, said “gross insubordination” and tried to explain.

The holding is one sentence, at 888:

Accordingly, we hold that in an action for defamation, the publication requirement may be satisfied where the plaintiff was compelled to publish a defamatory statement to a third person if it was foreseeable to the defendant that the plaintiff would be so compelled.

Read the sentence as a list of conditions rather than as a permission. It supplies one element of a defamation claim — publication — and leaves every other element where it was.

“Compelled” means no reasonable alternative, not “asked”

Lewis framed the doctrine in terms of the absence of alternatives, not the presence of a question. At 888:

The concept of compelled self-publication does no more than hold the originator of the defamatory statement liable for damages caused by the statement where the originator knows, or should know, of circumstances whereby the defamed person has no reasonable means of avoiding publication of the statement or avoiding the resulting damages; in other words, in cases where the defamed person was compelled to publish the statement.

On the facts, the compulsion came from the interview itself: the St. Paul office manager admitted it was foreseeable that prospective employers would ask why the plaintiffs were discharged, and, as the court put it at 888, “[t]heir only choice would be to tell them ‘gross insubordination’ or to lie. Fabrication, however, is an unacceptable alternative.”

The court attached a duty to that. At 888, mitigation “can be further protected by requiring plaintiffs when they encounter a situation in which they are compelled to repeat a defamatory statement to take all reasonable steps to attempt to explain the true nature of the situation and to contradict the defamatory statement.” An employee who repeats the reason and says nothing else is not doing what Lewis contemplated.

The Court of Appeals has read the compulsion requirement to reach a case where the prospective employer did not ask the reason for the termination. In Kuechle v. Life’s Companion P.C.A., Inc., 653 N.W.2d 214, 219–20 (Minn. Ct. App. 2002), a nurse was fired by a letter accusing her of disobeying a direct order and abandoning a vulnerable client; her employers separately told her they had no choice but to report the incident to the Minnesota Board of Nursing, though they never did. She volunteered the reason in a later interview. Id. at 218. The court affirmed, holding that she had no reasonable means to avoid self-publishing even though her potential employers “did not directly ask her the reason for her termination,” and that “she was compelled to self-publish so that she could defend her professional reputation.” Id. at 219–20. The compulsion in Kuechle came from what she had been told about the board, not from an interviewer’s question.

The element that ends most of these cases is proof of the interviews

Eight years after Lewis, the same court threw out a self-publication claim for want of evidence that the plaintiff had ever published anything.

Rouse v. Dunkley & Bennett, P.A., 520 N.W.2d 406 (Minn. 1994), reached the Supreme Court as a legal-malpractice case: a loan officer sued the lawyers who had let the two-year defamation limitations period run on a claim arising from his firing. Whether the malpractice claim survived depended on whether the underlying defamation claim would have survived summary judgment. It would not have. At 411:

The only evidence Rouse has provided is his own deposition testimony, during which he submitted a list of thirteen companies where he interviewed. Rouse remembered some details about the interviews, such as roughly where the companies’ offices were located and, in a few cases, whether he interviewed with a man or a woman. However, he could not provide names of interviewers nor provide any documentary evidence of having filled out applications, sent resumes or received rejections. We hold that Rouse has not met his burden on the element of publication ….

Rouse is the operative case for anyone measuring a real claim. Thirteen interviews, recalled in general terms, was not enough. The court did not reach the employer’s privilege defense at all, id. at 411 n.8 — the claim died on documentation.

Truth, and what the truth has to be about

The employer’s first defense is that the statement was true, and Lewis answered the version of that argument employers usually make. The company said the statement to test was the one the plaintiffs made — that they had been fired for gross insubordination — which was true. The court disagreed, holding at 889 that “[r]equiring that truth as a defense go to the underlying implication of the statement, at least where the statement involves more than a simple allegation, appears to be the better view.” The question is whether the employee actually did the thing, not whether the employer actually said it.

The court wrote that limit into the sentence itself — the rule is stated “at least where the statement involves more than a simple allegation” — and it distinguished an earlier case on that basis, because there “the underlying statements were presented merely as ‘allegations of misconduct,’” while in Lewis “the company’s charges against plaintiffs went beyond accusations and were conclusory statements that plaintiffs had engaged in gross insubordination.” Lewis, 389 N.W.2d at 889. How far below a conclusory charge the rule reaches is not answered by the opinion, and this page does not answer it.

The qualified privilege, and the two ways it ends the case

Lewis gave employers a privilege in the same opinion that gave employees the doctrine. At 890: “We conclude that an employer’s communication to an employee of the reason for discharge may present a proper occasion upon which to recognize a qualified privilege.” The court’s reason was practical — without a privilege, employers would stop giving reasons.

Three mechanics follow, all from Lewis at 890:

• Whether the occasion is privileged is a question of law for the court; whether the privilege was abused is a jury question.
• The privilege is qualified, meaning it “may be lost if it is abused.”
• The burden is on the plaintiff to show the privilege has been abused.

Abuse means malice, and in the employment setting Minnesota uses the common-law definition rather than the constitutional one: a statement made “from ill will and improper motives, or causelessly and wantonly for the purpose of injuring the plaintiff.” Lewis, 389 N.W.2d at 891 (quoting Stuempges v. Parke, Davis & Co., 297 N.W.2d 252, 257 (Minn. 1980)). The Lewis jury made that finding, which is why the plaintiffs won.

A privilege can also fail at the threshold, before malice is ever reached, if the employer’s investigation was too thin to supply “reasonable or probable cause.” That is what happened in Kuechle, 653 N.W.2d at 220: the employer “did not conduct a thorough investigation, failed to interview respondent, and ignored the supervisor’s statement that she made a request, rather than gave a direct order,” and “[b]ecause of the cursory nature of appellants’ actions, we conclude the district court properly found they are not entitled to a privilege.” The court added the consequence: “Where there is no privilege, there is no need for respondent to prove malice ….” Id.

Punitive damages are off the table, and that is a holding, not a tendency

Lewis affirmed the plaintiffs’ compensatory damages in full — including damages for future harm to earning capacity, on the reasoning at 891 that “[a] person who brings suit against a former employer is likely to be a less attractive employment candidate to prospective employers.” It reversed the punitive award, and stated the rule categorically at 892:

Accordingly, we hold that punitive damages are not available in defamation actions based upon compelled self-publication, and therefore the award of punitive damages to plaintiffs is reversed.

The stated concern was that the risk of punitive damages, even with a qualified privilege in place, would push employers to refuse to state any reason for a discharge.

The doctrine is confined to defamation

Phillips v. State, 725 N.W.2d 778 (Minn. Ct. App. 2007), settled that the doctrine does not travel to other causes of action that carry a publication or dissemination requirement. A community-college instructor whose fixed-term appointment was not renewed argued that his own explanations to colleagues supplied the dissemination element of a constitutional liberty-interest claim. The court held at 785:

But we hold that, in Minnesota, the doctrine of compelled self-publication as it relates to separation from employment is limited to defamation actions and does not support a claim alleging violation of a liberty interest.

Three statutes that take the statement out of reach before you get to any of this

The termination-reason letter you requested. If you used Minn. Stat. § 181.933, subd. 1, to demand the reason in writing, the answer is not available to you as a defamation claim. Subdivision 2:

No communication of the statement furnished by the employer to the employee under subdivision 1 may be made the subject of any action for libel, slander, or defamation by the employee against the employer.

The bar is drawn to the statement furnished under subdivision 1, to the three named torts, and to the employee suing the employer. It has a condition the employer sometimes forgets: in LeBaron v. Minnesota Board of Public Defense, 499 N.W.2d 39, 42 (Minn. Ct. App. 1993), the court held that “[b]ecause both parties admit they failed to follow the timing requirements of Minn. Stat. § 181.933, no absolute privilege can flow from that statute to protect the employer from liability for defamation.” The mechanics of the request and the deadlines are set out in the guide on the termination-reason letter.

What the employer tells a prospective employer. Minn. Stat. § 181.967, subd. 2, sets a proof standard most claims will not reach:

No action may be maintained against an employer by an employee or former employee for the disclosure of information listed in subdivisions 3 to 5 about the employee to a prospective employer or employment agency as provided under this section, unless the employee or former employee demonstrates by clear and convincing evidence that:

(1) the information was false and defamatory; and

(2) the employer knew or should have known the information was false and acted with malicious intent to injure the current or former employee.

Both elements, at the clear-and-convincing level. The protected disclosures are itemized in subdivisions 3 to 5, and for a private employer the free-standing list in subdivision 3(a) is short: dates of employment; compensation and wage history; job description and duties; training and education provided by the employer; and documented acts of violence, theft, harassment, or illegal conduct that resulted in discipline or resignation. Written evaluations, written disciplinary warnings and actions from the five years before the date of the authorization, and “written reasons for separation from employment” are in subdivision 3(b), which reaches those disclosures only where there is “written authorization of the current or former employee.” Subdivision 6(b) carves out one category: “This section does not apply to an action involving an alleged violation of chapter 363 or other statute.” The section is treated at length, subdivision by subdivision, in the guide on references and what a former employer may say.

What the employer told the unemployment agency. Minn. Stat. § 268.19, subd. 2(c):

Information obtained under the Minnesota Unemployment Insurance Law, in order to determine an applicant’s entitlement to unemployment benefits, are absolutely privileged and may not be made the subject matter or the basis for any civil proceeding, administrative, or judicial.

The Minnesota Supreme Court construed that sentence on October 29, 2025, in McBee v. Team Industries, Inc., No. A23-1879 (Minn. Oct. 29, 2025). Its syllabus:

As used in Minnesota Statutes section 268.19, subdivision 2(c), the phrase “absolutely privileged” provides immunity from liability in civil actions for which information submitted to the Department of Employment and Economic Development, in order to determine an applicant’s entitlement to unemployment benefits, forms the subject matter or basis of the claim.

Two halves of that matter, and they cut in opposite directions. The immunity is not limited to defamation — the court rejected reading subdivision 2(c) that narrowly because such a reading “would effectively ignore the second phrase, which broadly applies to ‘any civil proceeding,’ not only claims of defamation.” Slip op. at 15. But it is an immunity, not an evidentiary rule: “Section 268.19, subdivision 2(c), does not state an evidentiary rule of general inadmissibility.” Slip op. at 3. In McBee itself, the questionnaire the agency sent the employer, which the employer completed and returned, “is not the subject matter or basis of McBee’s employment discrimination claim,” so “the district court erred by excluding the document from evidence at trial” — an error the court then held was not prejudicial. Id.

A note on currency

Lewis has not been overruled by any decision retrieved for this page, and the Minnesota Supreme Court applied it as settled law in McBee on October 29, 2025, citing it at 889 for the ordinary rules of privilege. [UNVERIFIED — Lee: no citator was run. CourtListener's index was not queried for this guide, so the statement that no later decision has narrowed the holding at 888 is a report of the sources retrieved here, not a complete search. Two decisions flagged internally as possible later treatment were retrieved and neither concerns compelled self-publication: Glay v. R.C. of St. Cloud, Inc., No. A23-1464 (Minn. Jan. 28, 2026), is a wrongful-death case tried on an innkeeper-negligence theory that cites Lewis at 885 for the standard of prejudicial instructional error, and McBee construes § 268.19, subd. 2(c). Please run the citator pass.]

What this page does not do

This page describes a doctrine and the elements around it. It does not evaluate a separation, and the distance between the doctrine and a claim is where most of the work sits: whether the reason was false, whether the compulsion was real, whether the job search generated documents, and whether the employer’s investigation was thorough enough to earn the privilege. The two-year period in Minn. Stat. § 541.07(1) runs from the statement, not from the interview — that is what the lawyers in Rouse were sued over.

Related: was my firing illegal, the termination-reason letter, and your personnel file.