When an employee raises a legal concern, what an owner does next is heavily regulated in Minnesota. The state’s primary anti-retaliation statute, Minn. Stat. § 181.932, is short, but it is broader than most owners assume, and the case law has moved meaningfully in favor of reporting employees over the past decade. A 2017 Minnesota Supreme Court decision eliminated a defense employers had used for years, and the burden-shifting framework Minnesota courts use at summary judgment makes documentation and timing more important than the statute’s plain text alone suggests. This article walks through what § 181.932 actually prohibits, what counts as a protected report, the post-Friedlander good-faith standard, and how the remedies and defenses work in practice. For the broader picture of Minnesota termination and discipline law, see our Minnesota employment law overview.

What does Minnesota’s Whistleblower Act actually prohibit?

The operative language of Minn. Stat. § 181.932, subd. 1 is unusually broad. The statute provides that “an employer shall not discharge, discipline, penalize, interfere with, threaten, restrain, coerce, or otherwise retaliate or discriminate against an employee regarding the employee’s compensation, terms, conditions, location, or privileges of employment because” the employee engaged in a protected activity.

Read that list carefully. It does not stop at termination. The statute reaches discipline, penalties, threats, interference, and any conduct that “retaliates or discriminates” with respect to compensation, terms, conditions, location, or privileges. A demotion, a schedule change, a transfer to a less desirable office, the loss of a discretionary bonus, the removal of a direct report, a sudden change in performance reviews, or a quiet exclusion from meetings can all satisfy the statute if a court connects them to a protected report.

The protected activities that follow the “because” are also wider than most owners realize. They include reporting suspected violations of federal, state, or common law to the employer or to a government body, participating in a public-body investigation, refusing to follow an order the employee has an objective basis to believe is unlawful, reporting healthcare quality concerns that risk public harm, and (for public employees) certain disclosures about state programs and scientific findings. Reports about violations of common law and public policy are inside the statute, not just statutory or regulatory violations.

Who is a “protected” employee, and what is a “report”?

Coverage starts with Minn. Stat. § 181.931, the definitions section. An “employee” is anyone performing compensated work in Minnesota for an employer, with independent contractors expressly excluded. An “employer” is any entity with one or more employees in Minnesota, including state and local government. There is no minimum employee threshold, no industry carve-out, and no probationary exclusion. A two-person company with one Minnesota worker is covered.

The statute’s definition of “report” is the part that surprises owners. Under § 181.931, subd. 6, a report is “a verbal, written, or electronic communication by an employee about an actual, suspected, or planned violation.” Three features of that definition matter:

  • A verbal report counts. There is no writing requirement, and an employee who raises the issue out loud to a manager is in the same protected position as an employee who emails a compliance officer.
  • The violation can be suspected or planned. The employee does not need to wait for the conduct to occur or to confirm that it actually happened.
  • The report can be internal. There is no requirement that the employee go to a government body. Most retaliation claims I see arise from internal complaints, not external ones.

Add § 181.931, subd. 5, which defines “penalize” to include conduct (including post-employment conduct) that “would tend to discourage a reasonable employee from making or supporting a report,” and the statute’s reach starts to come into focus. A negative reference to a future employer, a tightened post-employment confidentiality demand, or a sudden refusal to forward final paperwork can all be reachable conduct after the employment ends.

What does “good faith” mean after Friedlander?

The 2013 legislature added a statutory definition of “good faith,” and the Minnesota Supreme Court decided in 2017 what that definition meant. That decision is the single most important development in Minnesota whistleblower law in recent memory.

Before 2017, Minnesota courts had read into the statute a requirement that the employee report with the “purpose of exposing an illegality.” If the employer already knew about the conduct, or if the employee’s report was made for a non-altruistic motive (such as documenting a position in a brewing dispute), employers could argue the employee was not really a “whistleblower” and was not protected. The Minnesota Supreme Court abrogated that judicially-created rule in Friedlander v. Edwards Lifesciences, LLC, 900 N.W.2d 162 (Minn. 2017), holding that the 2013 statutory amendment defining “good faith” replaced the prior judicially-imposed “purpose of exposing an illegality” requirement with a textual standard tied to the truthfulness of the report.

That standard now lives in Minn. Stat. § 181.931, subd. 4, which provides that “good faith” means conduct that does not violate § 181.932, subd. 3. Subdivision 3 of § 181.932, in turn, provides that the statute “does not permit an employee to make statements or disclosures knowing that they are false or that they are in reckless disregard of the truth.” Reading the two together, the standard is now:

  • A report is in good faith if it is not knowingly false and not made with reckless disregard of the truth.
  • The employee’s purpose, motive, or strategic reason for reporting is no longer part of the test.
  • A report about something the employer already knows is still protected.
  • A report that turns out to be wrong is still protected, as long as the employee was not knowingly or recklessly false.

For employers, the practical implication is that the older defenses (the employee was just covering themselves, the employee was building a case, we already knew about the issue) no longer carry the weight they used to. A report is protected unless the employer can show it was knowingly false or recklessly indifferent to the truth. That is a high bar.

How does an employee prove a retaliation claim, and how does an employer defend one?

Minnesota courts apply the McDonnell Douglas burden-shifting framework to Whistleblower Act claims, most recently reaffirmed by the Minnesota Supreme Court in Hanson v. State, Department of Natural Resources, 974 N.W.2d 252 (Minn. 2022). The framework has three parts.

First, the employee must establish a prima facie case of retaliation. The elements are conduct protected by the Whistleblower Act, an adverse employment action, and a causal connection between the two. Causal connection at this stage is often shown by temporal proximity: a firing, demotion, or discipline that follows close on the heels of a report.

Second, if the employee makes the prima facie showing, the burden shifts to the employer to articulate a legitimate, non-retaliatory reason for the action. This is where contemporaneous documentation matters. Performance reviews predating the report, a documented restructuring decision, a pattern of similar discipline applied to other employees, or a written policy violation all support a legitimate reason. At this stage, the employer must articulate, but need not prove, a non-retaliatory reason.

Third, if the employer articulates a legitimate reason, the burden shifts back to the employee to show the stated reason is pretext for retaliation. Pretext can be shown by inconsistencies in the explanation, departures from past practice, comparators (similarly situated employees who were not disciplined for the same conduct), or evidence the stated reason is factually wrong. Hanson is a useful illustration on the employer side: the plaintiff established the prima facie case but lost at summary judgment because she could not show pretext.

The takeaway for an employer is that the case is rarely won or lost on the question whether a report happened or whether it was protected. It is usually won or lost on whether the employer’s reason for the adverse action is well-documented, applied consistently, and predates or is independent of the report. For the broader playbook on defending an adverse-action decision, see our discussion of common legal defenses against wrongful termination.

What counts as an “adverse action” beyond firing?

The statute’s verbs (discharge, discipline, penalize, interfere, threaten, restrain, coerce, retaliate, discriminate) reach much further than termination. Minnesota courts and the statute’s text reach beyond termination to demotions, transfers to less desirable positions or locations, denial of promotions, reductions in pay or hours, removal from key projects, exclusion from meetings, sudden negative performance reviews after a record of positive ones, the imposition of new performance improvement plans, and constructive discharge through hostile or untenable working conditions, many of which are encompassed by § 181.932 subd. 1’s expansive enumeration of prohibited conduct.

Two underappreciated points: First, post-employment conduct can qualify. Under § 181.931, subd. 5, conduct after the employment ends can be a “penalty” if it would discourage a reasonable employee from making or supporting a report. A retaliatory negative reference, an unreasonable post-employment threat letter, or a contested non-compete enforcement action can be reached. For perspective on the boundary between legitimate enforcement and retaliation, see post-employment obligations.

Second, the action does not have to affect the bottom line directly. Loss of “privileges of employment” is statutory text. Stripping a manager of a parking spot or a private office can be an adverse action if the connection to the report is provable. The relevant question is whether the change is materially adverse to a reasonable employee, not whether it produced a measurable financial loss.

What are the damages and remedies if a court finds retaliation?

Minn. Stat. § 181.935 gives the prevailing employee a wide menu. Paragraph (a) authorizes a civil action to recover “any and all damages recoverable at law, together with costs and disbursements, including reasonable attorney’s fees,” plus “such injunctive and other equitable relief as determined by the court.” Paragraph (c) lists examples of equitable relief: reinstatement, back pay, restoration of lost service credit, compensatory damages, and expungement of adverse records.

Three features of this remedy structure deserve an owner’s attention.

First, attorney’s fees. § 181.935(a) is a fee-shifting statute. A successful plaintiff recovers reasonable attorney’s fees on top of damages. In a small case, fees can exceed the underlying damages by a wide margin. This is the single feature that most often drives employers to settle a marginally defensible claim rather than litigate.

Second, the broad equitable relief. Reinstatement is a real possibility, even where the employer would prefer a clean break. Expungement of records means the employer’s HR file may have to be edited, with the entries replaced. These remedies operate forward in time and can constrain how the company manages a position long after the verdict.

Third, the separate notice-violation penalty. § 181.935(b) imposes a civil penalty of $25 per day per injured employee, capped at $750 per injured employee, on an employer that fails to give notice “as required under section 181.933 or 181.934.” This is a small number, but it is a strict-liability number tied to compliance with the written-reasons request and the DOLI notice rules. Skipping the § 181.933 response window is not just bad practice; it has its own statutory price tag.

How does the § 181.933 written-reasons request fit in?

Minn. Stat. § 181.933 is a related statute that often gets folded into a retaliation case. Subdivision 1 provides: “An employee who has been involuntarily terminated may, within 15 working days following such termination, request in writing that the employer inform the employee of the reason for the termination.” The employer must respond “within ten working days following receipt of such request” with the truthful reason for the termination.

For an employer, this statute creates one obligation and one significant benefit. The obligation is to respond promptly and truthfully when a discharged employee makes a written request. The benefit is in 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.” A § 181.933 response is shielded from defamation liability. For the broader law on defamation exposure between employers and employees, see our piece on business defamation.

The strategic reality is that the § 181.933 statement becomes the central document in any later retaliation case. It locks the employer into a stated reason. Inconsistencies between the § 181.933 statement and later litigation positions are powerful pretext evidence. The right approach is to treat the response as a deliberate drafting exercise: factually accurate, concise, consistent with the contemporaneous personnel file, and reviewed before it is sent.

How does MWA retaliation differ from MHRA reprisal claims?

Minnesota has two separate retaliation statutes that owners frequently conflate. § 181.932 protects reports of legal violations generally. The Minnesota Human Rights Act, Minn. Stat. § 363A.15, protects reprisals for opposing discrimination, filing a charge, testifying, or participating in an MHRA investigation or proceeding.

Three differences matter for compliance:

  • The protected activity is different. An employee complaining about a sales-tax violation triggers § 181.932. An employee complaining about a hostile-environment racial slur triggers § 363A.15. Many situations trigger both (a complaint about wage-and-hour violations affecting women in a department), and a careful complaint usually pleads both.
  • The procedural path is different. MHRA reprisal claims have an administrative-charge option through the Minnesota Department of Human Rights, with corresponding investigation procedures. § 181.932 claims go directly to district court.
  • Remedies overlap but are not identical. Both authorize damages and fee shifting. The MHRA additionally authorizes punitive damages of up to $25,000 under Minn. Stat. § 363A.29, subd. 4. § 181.932 has no parallel punitive-damages provision; the prevailing employee is limited to “any and all damages recoverable at law,” fees, and equitable relief under § 181.935(a) and (c).

The practical implication is that an employer cannot run a retaliation analysis solely under § 181.932 if the underlying complaint touches a protected category under chapter 363A. Both statutes need to be in the analysis from the start.

What internal practices reduce retaliation exposure?

Three operating habits prevent more retaliation claims than any combination of policies.

First, document performance contemporaneously, not retrospectively. The single most effective defense to a § 181.932 claim is a documented performance file that predates the report. The single most damaging fact pattern is a clean file followed by a sudden write-up the week after the employee raised a concern.

Second, separate the report from the decisionmaker when possible. If a manager has been the target of a report or is closely tied to the underlying conduct, that manager should not be the sole decisionmaker on the employee’s discipline or termination. A second-level review by HR or by an independent business leader insulates the decision from the appearance, and often the reality, of retaliatory motive.

Third, treat the § 181.933 response and the at-will discharge memo as a single coordinated drafting exercise. The reason given to the employee, the reason in the personnel file, and the reason any future § 181.933 response would state should be the same reason. For background on the at-will baseline against which all of this operates and on whether an employer can fire an employee who is a whistleblower, see those companion articles.

The Whistleblower Act does not prevent firings. It prevents retaliatory firings. The line between the two is drawn by the documentation, the timing, and the consistency of the employer’s stated reasons.

Can I still fire a whistleblower for performance reasons?

Yes. The Minnesota Whistleblower Act does not freeze a reporting employee in place. What it prohibits is taking adverse action because of the protected report. If the performance issues are documented, predate the report, and would have led to the same outcome regardless, the employer has a real defense. Under the McDonnell Douglas framework Minnesota courts apply, the employer’s burden is to articulate a legitimate non-retaliatory reason. The risk is timing and documentation: a sudden firing two weeks after a § 181.932 report, with no prior write-ups, will face a pretext argument even if the reason is genuine.

Does the report have to be about something the company actually did wrong?

No. The statute protects reports of an ‘actual, suspected, or planned’ violation. The employee does not have to prove a violation actually occurred to be protected, and the employer cannot defeat the claim by later showing the underlying concern was unfounded. What the statute requires is good faith, which after Friedlander means the report was not knowingly false and not made with reckless disregard of the truth. A wrong-but-honest report is still protected.

What if the employee reports the same issue I already know about?

Still protected. Minnesota courts have squarely rejected the argument that a report stops being a ‘whistleblower’ report when the employer already knows the underlying facts. Before 2017, courts had read in a ‘purpose of exposing an illegality’ requirement; the Minnesota Supreme Court abrogated it. Today, an employee’s motive for reporting is not part of the protected-conduct test.

Can I refuse to give a written reason for the firing?

Practically, yes; legally, you should not. Minn. Stat. § 181.933 gives a discharged employee 15 working days to request a written reason for the termination, and the employer has 10 working days to respond with a truthful explanation. The statute also gives the employer a defamation shield for that statement. Refusing to comply triggers a civil penalty under § 181.935(b) and forfeits the defamation safe harbor on what is often the single most contested document in any retaliation case.

Does the law cover reports made to my own managers, or only to the government?

Both. Under § 181.931, subd. 6, a ‘report’ is any verbal, written, or electronic communication by an employee about a violation. The statute does not require the employee to go outside the company. Internal complaints to a supervisor, an HR partner, or a compliance hotline qualify. Employers sometimes assume only reports to a government agency trigger the statute. That assumption has caused more inadvertent retaliation claims than almost any other single misreading of the law.

Are independent contractors covered?

Generally no. Minn. Stat. § 181.931, subd. 2 defines ’employee’ as someone performing compensated work in Minnesota for an employer, and explicitly excludes independent contractors. Misclassification is a separate problem: a worker labeled as a contractor but functioning as an employee may still be covered, and the misclassification itself can be the underlying violation a worker reports. The exemption is also not a license to retaliate against a real contractor for raising legal concerns; other doctrines, including tortious interference and contract claims, may apply.

In Minnesota, retaliation litigation is largely won or lost on records that exist before the dispute starts. The substantive law is favorable to reporting employees, especially after Friedlander, and the McDonnell Douglas framework gives the employer a real defense if (and only if) the contemporaneous record supports a legitimate, non-retaliatory reason. Owners who treat § 181.932 as a paperwork exercise tend to lose. Owners who treat it as an operating discipline (consistent documentation, clean § 181.933 responses, separated decisionmakers) tend to win the cases that matter and avoid most of them. For a fuller discussion of how termination decisions interact with Minnesota’s broader legal framework, our Minnesota employment law overview is the right starting point.