Managing Problem Employees: MN Legal Playbook

What does Minnesota’s at-will rule actually let you do?

In Minnesota, employment is at-will by default: absent an enforceable contract, collective-bargaining agreement, definite handbook or policy promise, or other legal limitation, either you or the employee can end the relationship at any time, for any reason that is not illegal, and without advance warning. There is no general requirement to show “good cause” or to run progressive discipline before firing. What at-will does not do is override the specific state and federal statutes that put certain reasons off-limits.

That distinction is the whole game. Minnesota has not adopted a broad good-cause standard, but it has layered on a series of targeted protections: the Minnesota Human Rights Act (“MHRA”), the Whistleblower Act, earned sick and safe time, and the wage-payment rules, among others. Each one carves out a specific reason you cannot act on, or a specific step you must follow. So the practical question is rarely “can I fire this person?” It is “is my actual reason one of the few the law forbids, and have I built a record that shows it?” For the mechanics, see how at-will firing works in Minnesota.

What handbook language protects you instead of binding you?

A handbook protects you only when it does two things: states clearly that employment stays at-will, and keeps discipline discretionary. The trap is the opposite kind of language, the kind that promises specific steps. Minnesota courts have long recognized that definite, mandatory handbook language can create a binding unilateral contract, Pine River State Bank v. Mettille, 333 N.W.2d 622 (Minn. 1983), so a policy stating “we will issue three written warnings before termination” can convert your discretion into an obligation you have to honor before firing.

This is where good intentions backfire. A well-meaning progressive-discipline policy, written as a promise, becomes a contract term the employee can enforce. The fix is not to abandon policies; it is to write them as guidance, not guarantees. Keep an at-will disclaimer, use permissive words (“may,” “in its discretion”) rather than mandatory ones (“will,” “must”), and avoid committing to a fixed sequence of steps you will follow every time. In my experience, the handbooks that cause litigation are the detailed ones drafted years ago and never revisited. For a closer look, see what belongs in an employee handbook.

How do you build a documentation trail that holds up?

Documentation is what turns a firing from one person’s word against another’s into a defensible decision. If the employee later claims the real reason was discrimination or retaliation, Minnesota and federal courts ask a predictable question: did the employer have a legitimate, nondiscriminatory reason, and was that reason genuine or a pretext? Contemporaneous, specific, fact-based records are how you answer it.

Three qualities separate useful documentation from the kind that hurts you. It should be contemporaneous (written when the problem happened, not reconstructed the week you decide to fire), specific (dates, facts, and business impact, not adjectives like “bad attitude”), and consistent (comparable employees were treated the same way). Inconsistency is its own exposure: if you fired this person for something you tolerated in others, the gap becomes the evidence of pretext. In my practice, the single most common defect I see is a clean personnel file followed by a sudden termination, with nothing in between. A documented workplace investigation carries far more weight than after-the-fact memory.

What does a performance improvement plan (“PIP”) do legally, and where do employers go wrong?

A performance improvement plan (“PIP”) has no independent legal force in an at-will state: you do not need one to fire, and completing one does not obligate you to keep anyone. Its value is evidentiary. A genuine PIP documents that a performance concern was real, communicated, and given a chance to improve, which undercuts a later claim that the stated reason was a cover story.

Two traps turn a helpful tool into a liability. First, a PIP written like a contract binds you: if it promises a defined period or specific steps in mandatory language, it can become the same kind of unilateral commitment a handbook can. Keep it framed as an expectation, not a guarantee of continued employment. Second, timing creates the appearance of retaliation. If you launch a PIP days after an employee reported a safety problem or filed a complaint, a court weighing a reprisal claim under the MHRA will look hard at that sequence, because reprisal turns on the employer’s motive and timing. The cleaner your earlier documentation, the less a coincidence of timing can be spun into a motive. See the legal side of performance management.

Which protected classes limit how you discipline or fire?

You may not discipline or fire because of a protected characteristic. The Minnesota Human Rights Act reaches further than federal law: under Minn. Stat. § 363A.08, it is an unfair employment practice for an employer to discharge or discriminate against an employee because of “race, color, creed, religion, national origin, sex, gender identity, marital status, status with regard to public assistance, familial status, membership or activity in a local commission, disability, sexual orientation, or age.” Federal Title VII covers a shorter list.

The gap matters. Title VII, at 42 U.S.C. § 2000e-2, bars discrimination based on “race, color, religion, sex, or national origin,” so several categories (creed, marital status, status with regard to public assistance, familial status, and local-commission activity) are protected in Minnesota but not under that federal statute. Disability deserves special attention. A “performance problem” is sometimes an unaddressed medical condition. The Americans with Disabilities Act (“ADA”), 42 U.S.C. § 12112, and the MHRA require you to reasonably accommodate a known disability, so disciplining an employee whose struggles trace to a disability, before you have considered accommodation, can turn a performance issue into a discrimination claim. When performance drops suddenly, it is worth asking whether something has changed. For more, see disability discrimination and accommodation in Minnesota.

Which employee actions are protected from retaliation?

Beyond protected status, the law shields specific employee actions, and disciplining someone because of one is unlawful even when that person is also a poor performer. In Minnesota the core protected actions are reporting suspected illegality, opposing discrimination, using protected leave, discussing pay, and seeking workers’ compensation. The mistake to avoid is treating a protected complaint as insubordination.

The most common protected actions include:

• Whistleblowing. Under Minn. Stat. § 181.932, an employer may not “discharge, discipline, penalize . . . or otherwise retaliate or discriminate against an employee” because the employee, in good faith, reports a suspected violation of law, including a report made internally to you. A whistleblower can bring a private lawsuit for damages and attorney’s fees under Minn. Stat. § 181.935.
• Opposing discrimination. The MHRA’s reprisal section, Minn. Stat. § 363A.15, protects an employee who “opposed a practice forbidden under this chapter” or filed or assisted in a charge. Federal Title VII, 42 U.S.C. § 2000e-3, runs parallel.
• Discussing wages. Under Minn. Stat. § 181.172, you cannot take adverse action against an employee for disclosing or discussing wages. An employee stirring up pay conversations is exercising a protected right, not committing misconduct.
• Off-duty lawful products. Under Minn. Stat. § 181.938, you generally cannot discipline for off-premises, off-hours use of lawful consumable products, including cannabis. That same statute preserves your right to act “on the basis of the . . . employee’s past or present job performance” and to address on-the-job impairment, so it protects the conduct, not the performance.
• Workers’ compensation. Under Minn. Stat. § 176.82, it is unlawful to fire or threaten to fire an employee for seeking workers’ compensation benefits after a workplace injury.

Read alongside Minnesota’s retaliation rules for employers, the pattern is consistent: when an employee has recently done something protected, slow down and confirm your reason predates it and stands on its own.

How do sick-time and leave rules limit disciplining an absent employee?

When an employee is “always absent,” some of those absences may be legally protected, and holding them against the employee is where employers get caught. Minnesota’s earned sick and safe time (“ESST”) law bars you from counting protected sick time against an employee, and the federal Family and Medical Leave Act (“FMLA”) bars interference with protected leave. Sort the protected absences from the unprotected ones before you treat attendance as the problem.

Minnesota’s ESST rules are specific about attendance systems. Under Minn. Stat. § 181.9447, it is unlawful for “an employer’s absence control policy or attendance point system to count earned sick and safe time . . . as an absence that may lead to or result in retaliation or any other adverse action.” So the familiar “ten attendance points and you are out” system cannot count protected sick time toward that total. Federally, the FMLA, 29 U.S.C. § 2615, makes it unlawful to “interfere with, restrain, or deny” an eligible employee’s exercise of leave rights. The practical step: before disciplining for absenteeism, separate the protected absences (sick time, FMLA, and Minnesota’s paid-leave program) from the unprotected ones, and build your case only on the latter. See earned sick and safe time compliance and Minnesota paid family and medical leave obligations.

How do you handle insubordination and communication breakdowns?

Refusing a lawful, reasonable instruction, or a persistent failure to communicate, is a legitimate and documentable basis for discipline in an at-will workplace. You do not have to tolerate an employee who will not do the job or work with the team. The one caveat: make sure what looks like disruption is not legally protected group activity.

The line runs between individual insubordination and collective complaint. The National Labor Relations Act (“NLRA”), 29 U.S.C. § 157, gives covered, nonsupervisory private-sector employees, in both union and non-union workplaces, the right to “engage in other concerted activities for the purpose of collective bargaining or other mutual aid or protection.” An employee raising wages, hours, or working conditions with or on behalf of coworkers is engaged in protected activity, even if the delivery is abrasive. An employee who refuses assignments, misses meetings, or will not respond to management for reasons unrelated to protected concerted activity or other protected rights generally is not protected on that basis. Document the specific conduct and its business impact, and keep the record on job performance rather than the employee’s opinions. For a related situation, see an employee who will not communicate.

How do you make the final termination decision?

Before you act, run the decision through a short checklist that pulls the prior sections together. A clean termination in Minnesota is one where the reason is legitimate and documented, consistent with how you have treated comparable employees, not based on a protected class or protected activity, and where any handbook or PIP promises have been honored. If all of that holds, the at-will rule does the rest.

In practice, most defensible terminations answer five questions yes. Is the reason a genuine, documented business reason? Have comparable employees been treated the same way? Is the reason free of any protected characteristic under the MHRA? Is it independent of any recent protected activity or leave? And have you followed whatever your own handbook or PIP actually commits you to? Keep the reason you give truthful and consistent, too: in Minnesota, a false or shifting explanation that the departing employee is compelled to repeat to prospective employers can support a defamation claim under the compelled self-publication doctrine the Minnesota Supreme Court recognized in Lewis v. Equitable Life Assurance Society, 389 N.W.2d 876 (Minn. 1986), though courts apply it narrowly. One more distinction matters: if the real driver is an eliminated position or an economic cut rather than the individual’s performance, you are looking at a layoff, which follows different notice and selection rules. See when a cut is really a layoff. When those questions are answered honestly and the file supports them, the decision is usually straightforward.

When is the final paycheck due after you fire someone?

Minnesota’s final-pay clock for a discharge is fast, and missing it carries a penalty. Under Minn. Stat. § 181.13, when you discharge an employee, their earned, unpaid wages are “immediately due and payable upon demand of the employee.” The demand must be in writing, and if you do not pay within 24 hours of that written demand, you owe a penalty equal to the employee’s average daily earnings for each day you are late, up to 15 days.

The rule rewards being ready. Because the penalty runs from a written demand, having the final check prepared when you deliver the termination lets you hand it over on the spot and close the question. A resignation follows a different, slower rule: under Minn. Stat. § 181.14, when an employee quits, final wages are due by “the first regularly scheduled payday following the employee’s final day of employment,” unless that payday falls less than five calendar days after the final day, in which case payment may wait until the second regularly scheduled payday but no later than 20 calendar days after the final day. So the same dollars are due almost immediately when you fire someone but not until the next payday when they quit. Do not let a dispute over the reason for the firing delay the paycheck; the wage obligation and the performance dispute are separate matters. For the details, see Minnesota’s final-paycheck rules.

What does severance with a release buy you?

Severance is optional in Minnesota: no statute requires it. What you buy with it is a signed release of legal claims, which lowers the risk of a later lawsuit. But a release is only worth what it can enforce, and two rules control whether it actually waives the claims that matter most in a termination.

First, age claims. To waive federal age-discrimination claims for an employee 40 or older, the release must meet the Older Workers Benefit Protection Act (“OWBPA”), 29 U.S.C. § 626: it must be written to be understood, specifically reference age-discrimination rights, advise the employee in writing to consult an attorney, and give defined periods to consider and to revoke the agreement. Second, Minnesota discrimination claims. Under Minn. Stat. § 363A.31, a release of MHRA claims may be “rescinded within 15 calendar days of its execution,” and the employee must be told in writing of that right. A severance agreement that ignores either rule can take the employee’s money and still leave the door open to the very claims you were trying to resolve. For structure, see structuring a severance agreement.

Managing a problem employee well is less about the moment you decide to act and more about the record you build before it. In Minnesota, the at-will rule gives you real latitude, but the value is in using it deliberately: document honestly, apply your standards consistently, keep protected status and protected activity out of the decision, and have the final paycheck ready. Do those things and most terminations are defensible; skip them and even a justified firing can turn expensive. If you are weighing a specific situation and want a second set of eyes before you act, email [email protected] with a short description and any relevant documents. You can also see our broader employment-law practice area for related issues.