When an employee refuses to complete assigned tasks, you face both a management problem and potential legal exposure. Under Minnesota’s at-will employment rule, you may generally discipline or terminate an employee who will not do the job: absent an employment contract for a specified term, “the employer-employee relationship is generally at-will, which means that an employer may discharge an employee for ‘any reason or no reason.’” Dukowitz v. Hannon Security Services, 841 N.W.2d 147, 150 (Minn. 2014) (quoting Pine River State Bank v. Mettille, 333 N.W.2d 622, 627 (Minn. 1983)). That authority has limits, and the limits are narrower and more specific than most employers expect. An employee acting in good faith may refuse work the employee reasonably believes presents an imminent danger of death or serious physical harm, and an employer “may not discriminate against an employee for a good faith refusal to perform assigned tasks if the employee has requested that the employer correct the hazardous conditions but the conditions remain uncorrected,” Minn. Stat. § 182.654, subd. 11. An employer also may not retaliate against an employee who “refuses an employer’s order to perform an action that the employee has an objective basis in fact to believe violates any state or federal law or rule or regulation adopted pursuant to law, and the employee informs the employer that the order is being refused for that reason,” Minn. Stat. § 181.932, subd. 1(3). And a covered employer owes a reasonable accommodation to a qualified employee with a disability unless it can demonstrate undue hardship, Minn. Stat. § 363A.08, subd. 6; 42 U.S.C. § 12112(b)(5)(A). So the safe path is a deliberate one. Understand why the employee is refusing, document each incident on the day it happens, communicate your expectations directly and in writing, and follow whatever corrective process your own handbook promises. If the refusal persists or involves a legally sensitive claim, consult a Minnesota employment attorney before you take disciplinary action. This article walks you through each step, from diagnosing the refusal to defending a termination decision if it comes to that.

Understand the Reasons

The first step is determining why the employee is refusing. The reason matters because it determines your legal exposure and the appropriate response.

Common causes include lack of task clarity, workload overload, skill gaps, personal circumstances, or deliberate insubordination. It also matters whether the refusal stems from a legally protected reason, such as a safety objection, a request for disability or pregnancy accommodation, a protected absence, or a whistleblower concern. Each of the statutes above bars retaliation in its own terms, so a refusal that satisfies one of them is not a refusal you can treat as ordinary insubordination, Minn. Stat. § 181.932, subd. 1(3); Minn. Stat. § 182.654, subd. 11.

Start by asking directly. Schedule a private conversation and ask open-ended questions. Employees who feel heard are more likely to surface the real issue rather than escalate. See the next section on structured communication for how to run that conversation.

If the employee frequently misses important work tasks rather than outright refusing them, the diagnostic approach is similar but the corrective path may differ.

Document the Behavior

Document each refusal in writing on the day it occurs. Include the date, the specific task assigned, the nature of the refusal (what the employee said or did), and any explanation offered. Preserve emails, messages, and notes from any related meetings.

Thorough documentation serves two purposes. First, it gives you a factual record for performance reviews, corrective action plans, and, if necessary, termination. Second, it supplies the record behind the “legitimate, nondiscriminatory reason” an employer must articulate once an employee makes a prima facie showing of discrimination, McDonnell Douglas Corp. v. Green, 411 U.S. 792, 802 (1973).

Keep the documentation objective and fact-based. Avoid characterizations like “bad attitude.” Instead, record what was observed: “On April 1, 2026, employee declined to complete the Johnson account report due by end of day, stating it was not her job.”

For a deeper look at managing employees who refuse to acknowledge mistakes, the same documentation discipline applies.

Communicate Directly

Address the refusal directly rather than working around it. Avoidance sends the message that the behavior is tolerated.

Here are four steps to structure the conversation:

  1. Initiate a Private Conversation: Meet one-on-one in a confidential setting. Avoid addressing the refusal publicly, which invites defensiveness and can affect team morale.
  2. Practice Active Listening: Let the employee explain without interrupting. Acknowledge their concerns. You do not have to agree with their position to show that you are taking it seriously.
  3. Provide Constructive Feedback: Identify the specific task that was not completed and the concrete impact on the team or client. Use direct, specific language rather than general statements about attitude or professionalism.
  4. Collaborate on Solutions: Ask the employee what obstacles are preventing task completion and work through them together. This approach often surfaces fixable problems (unclear priorities, missing resources, or interpersonal friction) and creates a record that you made reasonable efforts to support performance.

One caution about that meeting if a medical issue surfaces. Under 42 U.S.C. § 12112, a covered employer “shall not make inquiries of an employee as to whether such employee is an individual with a disability or as to the nature or severity of the disability, unless such examination or inquiry is shown to be job-related and consistent with business necessity,” but the same section provides that a covered entity “may make inquiries into the ability of an employee to perform job-related functions.” Ask about the ability to do the work, not about the diagnosis.

Employees who refuse to communicate properly present a related challenge and may need escalating interventions before the task refusal can be addressed at its root.

Assess Job Responsibilities

Before escalating discipline, confirm that the assignment was reasonable. In Minnesota, a written job description is not automatically the outer limit of what may be assigned, McGowan v. Executive Express Transportation Enterprises, Inc., 420 N.W.2d 592 (Minn. 1988). There the Minnesota Supreme Court affirmed a misconduct disqualification where a delivery driver refused to pick up her supervisor’s personal prescription, observing that in a small business “all of the duties of every employee cannot be anticipated or spelled out” and that “[t]he request by the employer was entirely reasonable.” The current statutory test for employment misconduct asks whether the conduct “is a serious violation of the standards of behavior the employer has the right to reasonably expect of the employee,” Minn. Stat. § 268.095, subd. 6(a), which the Legislature narrowed to that single test effective October 1, 2019, Minn. Laws 2019, 1st Spec. Sess., ch. 7, art. 7, §§ 9, 11.

The McGowan court also drew the outer line: “We do not hold that every employee is required to perform every personal errand an employer may request or face disqualification for misconduct. From the record here, however, one can conclude that the requested errand was within the expected job duties of the employee.” McGowan decided a benefits disqualification rather than the lawfulness of discipline, so read it as a description of what a decision-maker found reasonable on that record, not as a rule that a job description never limits an assignment.

The contract point runs the same direction. Minnesota employment of indefinite duration is at will, so the employer “can summarily dismiss the employee for any reason or no reason,” Pine River State Bank v. Mettille, 333 N.W.2d 622, 627 (Minn. 1983), and the same opinion states that “[a]n employer’s general statements of policy are no more than that and do not meet the contractual requirements for an offer,” 333 N.W.2d at 626. Whether a contractual limit on what may be assigned exists is a question of what the parties actually agreed to. A written employment agreement or a sufficiently definite handbook provision is the usual form such a limit takes, though Pine River itself addressed handbook job-security and disciplinary provisions rather than the scope of assigned duties. The same opinion answers the “that is not in my job description” objection: “In the case of unilateral contracts for employment, where an at-will employee retains employment with knowledge of new or changed conditions, the new or changed conditions may become a contractual obligation.” The terms in place at hire are not a fixed ceiling on what may be assigned.

Review the employment contract and job description anyway. Clear expectations make discipline easier to defend even where the law does not require them, and if the job description is outdated or ambiguous, updating it costs little.

If the employee refuses to work overtime when needed, wage-and-hour law fixes what overtime costs and does not limit how much of it you may assign. The Fair Labor Standards Act requires one and one-half times the regular rate for hours over 40 in a workweek, 29 U.S.C. § 207(a)(1), and the Department of Labor’s regulation states that “there is no absolute limitation in the Act (apart from the child labor provisions and regulations thereunder) on the number of hours that an employee may work in any workweek,” 29 C.F.R. § 778.102. The same regulation adds that the Act “does not generally require, however, that an employee be paid overtime compensation for hours in excess of eight per day, or for work on Saturdays, Sundays, holidays or regular days of rest,” so the federal trigger is the workweek total rather than a long day. Minnesota’s overtime statute uses a 48-hour weekly threshold, Minn. Stat. § 177.25, subd. 1, and the FLSA does not excuse noncompliance with a state law “establishing . . . a maximum work week lower than the maximum workweek established under this chapter,” 29 U.S.C. § 218(a), so an employee covered by the FLSA is paid on the federal 40-hour rule, 29 U.S.C. § 207(a)(1), and the higher state threshold adds nothing for that employee. Two Minnesota rules do limit the assignment itself. A hospital or licensed health care facility may not discipline a nurse solely for declining additional consecutive hours beyond a normal work period of 12 or fewer consecutive hours when working them may, in the nurse’s judgment, jeopardize patient safety, subject to an emergency exception, Minn. Stat. § 181.275, subds. 2, 3. That prohibition “does not apply to a nursing facility, an intermediate care facility for persons with developmental disabilities, a licensed boarding care facility, or a housing with services establishment,” Minn. Stat. § 181.275, subd. 2. And no employer may work a minor under the age of 16 more than 40 hours a week or more than eight hours in any 24-hour period, Minn. Stat. § 181A.04, subd. 4. Health care employers should also note that Minn. Stat. § 177.25, subd. 2 allows the employer and employee to agree, before the work is performed, to a 14-day work period in place of the seven-day workweek, with overtime owed past eight hours in a day or 80 hours in the period.

Evaluate Performance Issues

When refusals are part of a broader performance pattern, evaluate four areas:

  1. Performance Metrics: Compare actual output against established benchmarks. Identify whether the gap is task-specific or part of a wider performance trend.
  2. Feedback Mechanisms: Assess whether the employee has received clear, timely feedback in the past. Employees who have not received regular feedback have a stronger argument that performance issues were not communicated.
  3. Skill Gaps: Determine whether the refusal reflects inability rather than unwillingness. If the employee lacks the skills to complete the task, training may be the more effective intervention.
  4. Work Environment: Examine whether team dynamics, workload distribution, or organizational culture are contributing factors. If multiple employees are struggling with similar tasks, the problem may be systemic rather than individual.

Explore Employee Support Options

Offering support before escalating discipline is good management practice and useful legal protection. It demonstrates that you made reasonable efforts to set the employee up for success.

Identify Underlying Issues

Employers who approach refusal with curiosity rather than immediate discipline tend to resolve the issue faster and with less legal exposure. Ask:

  1. Open Communication: Create a setting where the employee can surface concerns without fear of retaliation.
  2. Assess Workload: Determine whether the task is achievable given the employee’s current responsibilities and available resources.
  3. Identify Skill Gaps: Consider whether training or additional support would enable task completion.
  4. Check for Accommodation and Leave Rights: Medical conditions, pregnancy, and family circumstances can move the situation out of the discipline track entirely.

The Americans with Disabilities Act can require a reasonable accommodation, but only for a “qualified individual,” meaning one “who, with or without reasonable accommodation, can perform the essential functions of the employment position,” and only from an employer with “15 or more employees for each working day in each of 20 or more calendar weeks in the current or preceding calendar year,” and only where the accommodation would not “impose an undue hardship on the operation of the business.” 42 U.S.C. § 12111(5)(A), (8); 42 U.S.C. § 12112(b)(5)(A). The 2008 amendments to the ADA also direct that “[t]he definition of disability in this chapter shall be construed in favor of broad coverage of individuals under this chapter, to the maximum extent permitted by the terms of this chapter,” 42 U.S.C. § 12102(4)(A), so more refusals sit inside the accommodation framework than older sources suggest.

The Family and Medical Leave Act does something different. It entitles an eligible employee to “a total of 12 workweeks of leave during any 12-month period” for a birth, an adoption or foster placement, care for a spouse, son, daughter, or parent with a serious health condition, or a serious health condition of the employee that makes the employee unable to perform the functions of the position, 29 U.S.C. § 2612(a)(1), and on return to restoration to the same job or “an equivalent position with equivalent employment benefits, pay, and other terms and conditions of employment,” 29 U.S.C. § 2614(a)(1). For a private employer, the Act applies only to one who “employs 50 or more employees for each working day during each of 20 or more calendar workweeks,” and only to an employee with at least 12 months and 1,250 hours of service, 29 U.S.C. § 2611(2)(A), (4)(A)(i); a public agency is a covered employer regardless of size, 29 U.S.C. § 2611(4)(A)(iii). An employer may not use FMLA leave “as a negative factor in employment actions, such as hiring, promotions or disciplinary actions,” 29 C.F.R. § 825.220(c). The obligation runs both ways: for a foreseeable birth or placement the employee must give “not less than 30 days’ notice,” 29 U.S.C. § 2612(e)(1).

Pregnancy has its own track. Since June 27, 2023, the federal Pregnant Workers Fairness Act has made it unlawful for an employer with 15 or more employees, 42 U.S.C. § 2000gg(2)(B)(i), to “not make reasonable accommodations to the known limitations related to the pregnancy, childbirth, or related medical conditions of a qualified employee, unless such covered entity can demonstrate that the accommodation would impose an undue hardship,” and to “require a qualified employee to take leave, whether paid or unpaid, if another reasonable accommodation can be provided,” 42 U.S.C. § 2000gg-1. Minnesota’s own pregnancy accommodation statute adds requirements, as the next section describes.

Provide Additional Resources

Where the refusal stems from capability gaps, offering concrete resources (training programs, mentorship, peer support, or mental health services through an employee assistance program) demonstrates good faith and often resolves the issue without disciplinary escalation.

If the employee refuses to collaborate with teammates, consider whether team dynamics or interpersonal conflict are driving both the collaboration problem and the task refusal.

Implement Corrective Actions

If the refusal continues after you have investigated the cause, communicated expectations, and offered support, implement corrective action through a structured process:

  1. Verbal Warning: Confirm in writing (even if the conversation was verbal) that a warning was given, what behavior was addressed, and what is expected going forward. Provide a copy to the employee.
  2. Written Warning: Issue a formal written warning that identifies the specific instances of refusal, the prior verbal warning, the expected behavior, and the consequences if the conduct continues.
  3. Final Written Warning or Suspension: Depending on your company policy and the severity of the situation, escalate to a final written warning or brief suspension. This step signals that termination is the next consequence.
  4. Termination: If refusal continues, termination is generally defensible, provided the refusal was not protected conduct and you applied your own policy consistently.

Understand what writing that sequence down does legally, because it is the opposite of what most employers assume. In Pine River State Bank v. Mettille, 333 N.W.2d 622, 627 (Minn. 1983), the Minnesota Supreme Court held that “personnel handbook provisions, if they meet the requirements for formation of a unilateral contract, may become enforceable as part of the original employment contract.” The bank there fired an at-will loan officer without following the disciplinary policy in its own handbook, and the court held that the bank “breached its employment contract with Mettille by not affording him the job termination procedures of its handbook.” 333 N.W.2d at 631. The line between binding and not binding runs within a single handbook: “An employer’s general statements of policy are no more than that and do not meet the contractual requirements for an offer,” while “[t]he provisions of the handbook section entitled ‘Disciplinary Policy’ do, however, set out in definite language an offer of a unilateral contract for procedures to be followed in job termination.” The cost is concrete. The court noted that “[i]t may well be that had the bank complied with its handbook procedures it could, in due course, have terminated Mettille, but the fact is that termination did not occur in this way,” and it affirmed lost wages to the date of trial because “the bank’s disciplinary procedures confer some degree of substantive protection to the employee.”

You keep your flexibility by drafting for it. The same opinion states that “[l]anguage in the handbook itself may reserve discretion to the employer in certain matters or reserve the right to amend or modify the handbook provisions.” 333 N.W.2d at 627. Boilerplate may not be enough: in Hall v. City of Plainview, 954 N.W.2d 254 (Minn. 2021), the court analyzed handbook provisions and disclaimers one at a time and held that a general “no contract” disclaimer did not unambiguously defeat a specific handbook promise, pointing instead to a disclaimer that expressly named the handbook’s grievance and termination procedures as the model of clarity.

One more practical note on a lawful discharge. It does not by itself disqualify the employee from unemployment benefits, because a discharged applicant is ineligible “only if” the discharge was for employment misconduct or aggravated employment misconduct, Minn. Stat. § 268.095, subd. 4. Minn. Stat. § 268.095, subd. 6 makes its definition of employment misconduct exclusive and excludes “simple unsatisfactory conduct” and “conduct an average reasonable employee would have engaged in under the circumstances,” and a single incident is an express factor.

Employees who refuse to participate in required training should also be routed through the corrective process, particularly where the training is legally mandated. Minnesota’s training mandates are hazard-specific. An employer must train an employee before initial assignment to a workplace where the employee may be routinely exposed to a hazardous substance or harmful physical agent, and must repeat that training at intervals no greater than one year, under Minn. Stat. § 182.653, subd. 4b, with parallel requirements in subdivisions 4c through 4f for harmful physical agents, regulated waste, farming operations, and infectious agents. The same section gives you the record you will want: “Every employer shall have the right to request that their employees sign statements that they have received appropriate training under this subdivision, once training has been completed.” For employers in the industry classifications the commissioner lists, subdivision 8 requires a written workplace accident and injury reduction program that describes “how safe work practices and rules will be enforced” and is reviewed and documented at least annually, and Minn. Stat. § 182.676 requires a joint labor-management safety committee for employers of more than 25 employees. Federal OSHA separately requires information and training on hazardous chemicals in the employee’s work area, 29 C.F.R. § 1910.1200(h).

Harassment prevention training sits in a different category for Minnesota employers. The Minnesota Human Rights Act makes harassment because of a protected characteristic an unfair employment practice, Minn. Stat. § 363A.08, since it defines “discriminate” to include harassment, Minn. Stat. § 363A.03, subd. 13, and imposes no training obligation, and the EEOC’s regulation says only that an employer “should take all steps necessary to prevent sexual harassment from occurring,” 29 C.F.R. § 1604.11(f). The training remains a sound liability-management practice here, and refusing it is a policy problem rather than a compliance problem.

Understand Employment Laws

Several legal frameworks under Minnesota employment law intersect with task refusals:

  1. Employment Contracts: Minnesota employment of indefinite duration is at will, so the employer “can summarily dismiss the employee for any reason or no reason.” An assigned task is measured against a contractual scope only where a written employment agreement or a sufficiently definite handbook provision sets one, per Pine River State Bank v. Mettille, 333 N.W.2d 622, 627 (Minn. 1983).
  2. Workplace Policies: Confirm that your policies address insubordination and that the employee knew about them, because that knowledge is what the decision-maker looks for later. In Stagg v. Vintage Place Inc., 796 N.W.2d 312, 317 (Minn. 2011), the Minnesota Supreme Court upheld a denial of unemployment benefits on a record showing the employer “had an absenteeism and tardiness policy of which Stagg was aware and that Stagg was aware that he was expected to follow that policy,” and in Schmidgall v. FilmTec Corp., 644 N.W.2d 801, 806 (Minn. 2002) the court stated that “an employee’s decision to violate knowingly a reasonable policy of the employer is misconduct.” Stagg also separates the two forums: “whether an employer follows the procedures in its employee manual says nothing about whether the employee has violated the employer’s standards of behavior,” and handbook-as-contract questions are “necessarily brought in a different forum.”
  3. Protected Rights: Federal and state law protect employees who refuse work in the narrow circumstances described below, who decline to carry out an order they have an objective basis in fact to believe is illegal, or who exercise rights under the National Labor Relations Act, the FMLA, the ADA, Minnesota’s leave statutes, or anti-discrimination law. A refusal with a protected basis calls for legal counsel before any disciplinary action.
  4. Your Own Corrective Process: A handbook’s disciplinary procedures that are definite in form, distributed to employees, and accepted by continued employment become part of the employment contract, so an employer that discharges an employee without following them breaches that contract as a matter of law even though the employment is at will. Pine River State Bank v. Mettille, 333 N.W.2d 622, 627, 631 (Minn. 1983).

In Minnesota, several statutes can convert a task refusal from insubordination into legally protected conduct.

Unsafe work. Under the Minnesota Occupational Safety and Health Act, Minn. Stat. § 182.654, subd. 11, “An employee acting in good faith has the right to refuse to work under conditions which the employee reasonably believes present an imminent danger of death or serious physical harm to the employee,” and an employer “may not discriminate against an employee for a good faith refusal to perform assigned tasks if the employee has requested that the employer correct the hazardous conditions but the conditions remain uncorrected.” The same subdivision supplies a floor for what counts: “A reasonable belief of imminent danger of death or serious physical harm includes but is not limited to a reasonable belief of the employee that the employee has been assigned to work in an unsafe or unhealthful manner with a hazardous substance, harmful physical agent or infectious agent.” It also answers your next practical question, which is what to do with the person today. An employee “who has refused in good faith to perform assigned tasks and who has not been reassigned to other tasks by the employer shall, in addition to retaining a right to continued employment, receive pay for the tasks which would have been performed” if the employee requests a commissioner inspection and the commissioner determines the assigned tasks would have placed the employee in imminent danger. Reassignment to other tasks is the move the statute itself contemplates, and it takes the pay obligation off the table. Since 2023, the remedies have grown: an administrative law judge may order, in addition to the relief in Minn. Stat. § 182.669, reinstatement or front pay, restored fringe benefits and seniority, back pay, and compensatory damages equal to the greater of $5,000 or twice actual damages, including punitive damages. A refusal outside those limits is not protected by that provision, though Minn. Stat. § 182.654, subd. 9 separately provides that “[n]o employee shall be discharged or in any way discriminated against because such employee has filed any complaint or instituted or caused to be instituted any proceeding or inspection under or related to this chapter,” which reaches the employee who reports a hazard rather than refusing a task.

Federal law is narrower, and it starts from the other direction. The protection comes from a regulation interpreting section 11(c) of the Occupational Safety and Health Act, 29 U.S.C. § 660(c): 29 C.F.R. § 1977.12(b)(1) states that “as a general matter, there is no right afforded by the Act which would entitle employees to walk off the job because of potential unsafe conditions at the workplace,” that hazardous conditions “will ordinarily be corrected by the employer, once brought to his attention,” and that an employer “would not ordinarily be in violation of section 11(c) by taking action to discipline an employee for refusing to perform normal job activities because of alleged safety or health hazards.” A refusal is protected under 29 C.F.R. § 1977.12(b)(2) only where the employee, “with no reasonable alternative, refuses in good faith to expose himself to the dangerous condition,” a reasonable person would conclude “that there is a real danger of death or serious injury and that there is insufficient time, due to the urgency of the situation, to eliminate the danger through resort to regular statutory enforcement channels,” and “the employee, where possible, must also have sought from his employer, and been unable to obtain, a correction of the dangerous condition.” The Supreme Court upheld that regulation in Whirlpool Corp. v. Marshall, 445 U.S. 1, 19 (1980), noting that the regulation “does not require employers to pay workers who refuse to perform their assigned tasks in the face of imminent danger.” Subsection (a) of the same regulation adds that requesting information from OSHA, participating in enforcement proceedings, and cooperating with an inspector are separately protected. A complaint must be filed with the Secretary of Labor “within thirty days after such violation occurs,” 29 U.S.C. § 660(c)(2).

Refusing an illegal order. The Minnesota Whistleblower Act, Minn. Stat. § 181.932, subd. 1(3), bars an employer from retaliating against an employee who “refuses an employer’s order to perform an action that the employee has an objective basis in fact to believe violates any state or federal law or rule or regulation adopted pursuant to law, and the employee informs the employer that the order is being refused for that reason.” Both elements matter, and so does the breadth of the prohibition: since a 2023 amendment the opening clause bars an employer from discharging, disciplining, penalizing, interfering with, threatening, restraining, coercing, or otherwise retaliating against the employee “regarding the employee’s compensation, terms, conditions, location, or privileges of employment,” so a write-up, a schedule change, or a transfer can be the prohibited act. A later amendment in 2025 rewrote only the clause covering state-employee disclosures, so the refusal clause reads today as quoted. Clause (1) of the same subdivision separately protects the employee, “or a person acting on behalf of an employee,” who “in good faith, reports a violation, suspected violation, or planned violation of any federal or state law or common law or rule adopted pursuant to law to an employer or to any governmental body or law enforcement official,” so an internal complaint that never leaves the building still triggers the statute, on a good-faith standard rather than clause (3)’s objective-basis-in-fact standard. The statute has an outer boundary you can rely on: subdivision 3 provides that the section “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,” and subdivision 4 provides that it “does not diminish or impair the rights of a person under any collective bargaining agreement.” One industry carve-out appears on the face of the statute: the revisor’s note records that clauses (1) and (3) “were found preempted by the federal Airline Deregulation Act to the extent that they relate to air carrier routes and services in Botz v. Omni Air Int’l, 286 F.3d 488 (8th Cir. 2002).”

On August 12, 2026, the Minnesota Supreme Court affirmed dismissal of both a whistleblower refusal claim and a common-law claim because the employee did not allege facts showing that the order she refused would actually have violated the law she identified, noting that it has never interpreted the phrase “an objective basis in fact to believe.” Wredberg v. Canvas Health, Inc., No. A24-1897 (Minn. Aug. 12, 2026). The court was explicit about the limits of that reasoning. Given the parties’ agreement and the absence of briefing on the phrase, it “assume[d] for the purposes of this case only” and expressly did “not decide” whether the whistleblower claim “is contingent on her alleging that her employer ordered her to actually violate the law.” Whether an actual violation is required is therefore open. The element you can rely on is the statutory one: the employee must have an objective basis in fact for believing the ordered action violates an identified state or federal law, and must inform you that the order is being refused for that reason.

Accommodation and leave. A refusal tied to a disability accommodation request is different, because the request itself is protected activity, Heisler v. Metropolitan Council, 339 F.3d 622, 632 (8th Cir. 2003), and a Minnesota employer with 15 or more part-time or full-time employees for each working day in each of 20 or more calendar weeks in the current or preceding calendar year must start an informal, interactive process and provide a reasonable accommodation for a qualified employee with a disability unless it can demonstrate undue hardship, Minn. Stat. § 363A.08, subd. 6. That interactive-process duty was added to the Minnesota Human Rights Act in 2021 and is the step employers most often skip before disciplining a refusal. The refusal itself is protected only as far as the duty reaches: the Act defines a “qualified disabled person,” for employment purposes, as one who “with reasonable accommodation, can perform the essential functions required of all applicants for the job in question,” Minn. Stat. § 363A.03, subd. 36, and the accommodation duty itself runs to a “job applicant or qualified employee with a disability,” Minn. Stat. § 363A.08, subd. 6, so you may still act on a refusal to perform an essential function that no reasonable accommodation covers. If you decline the accommodation, the statute gives you the test you will be measured against, listing five undue-hardship factors: the size of the business, the type of operation and workforce composition, the nature and cost of the accommodation, the reasonable ability to finance it at each site, and “documented good faith efforts to explore less restrictive or less expensive alternatives.” Subdivision 5 of the same section extends the identical accommodation duty to pregnancy and childbirth.

Minnesota’s pregnancy accommodation statute is more specific still. Minn. Stat. § 181.939, subd. 2 requires reasonable accommodations for health conditions related to pregnancy or childbirth, provides that an employer may not “claim undue hardship for the following accommodations: (1) more frequent or longer restroom, food, and water breaks; (2) seating; and (3) limits on lifting over 20 pounds,” and bars discipline “for asserting rights or remedies under this subdivision.” An employee who has requested a pregnancy-related limit on lifting over 20 pounds is exercising a statutory right, and you may not claim undue hardship as to that accommodation. The same statute states the limits: you are not required “to create a new or additional position,” to discharge an employee, to transfer another employee with greater seniority, or to promote an employee. Subdivision 1 covers another interruption an employer may misread as refusal, requiring reasonable break times to express milk without reduced compensation, and subdivision 3 requires notice of these rights at hire and in any employee handbook.

Two Minnesota leave statutes reach absences that can look like refusals to work. Minn. Stat. § 181.9447, subd. 6 makes it “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,” and adds that “[a] person need not explicitly refer to sections 181.9445 to 181.9448 or the rights enumerated herein to be protected from retaliation.” And since November 1, 2025, Minn. Stat. § 268B.09, subd. 1 has provided that an employer “must not discharge, discipline, penalize, interfere with, threaten, restrain, coerce, or otherwise retaliate or discriminate against an employee for requesting or obtaining benefits or leave, or for exercising any other right under this chapter,” with a commissioner-issued penalty of $1,000 to $10,000 per violation payable to the employee. Minnesota’s paid leave law defines an employer as one “having any individual in covered employment,” Minn. Stat. § 268B.01, subd. 18, with no 50-employee floor and no 75-mile worksite rule, so it reaches small employers the FMLA’s thresholds never covered, 29 U.S.C. § 2611(2)(B)(ii), (4)(A)(i).

Retaliation bars that sit alongside these. The FMLA makes it unlawful for an employer “to interfere with, restrain, or deny the exercise of or the attempt to exercise, any right provided under this subchapter,” and unlawful “to discharge or in any other manner discriminate against any individual for opposing any practice made unlawful by this subchapter,” 29 U.S.C. § 2615; it also protects a coworker who files a charge, gives information, or testifies in an FMLA inquiry, and it preserves greater state leave rights, 29 U.S.C. § 2651(b). The ADA bars discrimination against an individual who opposed an unlawful practice or filed a charge, testified, assisted, or participated in an ADA proceeding, and separately makes it unlawful “to coerce, intimidate, threaten, or interfere with any individual in the exercise or enjoyment of . . . any right granted or protected by this chapter,” which reaches an employee who merely asks for an accommodation or supports a coworker’s request, 42 U.S.C. § 12203. Minnesota’s parallel is Minn. Stat. § 363A.15, which makes intentional reprisal an unfair discriminatory practice against a person who “opposed a practice forbidden under this chapter” or participated in a proceeding, and lists the acts that count: “refuse to hire the individual; depart from any customary employment practice; transfer or assign the individual to a lesser position in terms of wages, hours, job classification, job security, or other employment status; or inform another employer that the individual has engaged in the activities listed in clause (1) or (2).” Departing from a customary employment practice is the clause employers most often trip over, because it can make otherwise routine discipline unlawful.

Acting together with coworkers. The National Labor Relations Act protects a task refusal only when it is concerted. 29 U.S.C. § 157 gives employees the right “to engage in other concerted activities for the purpose of collective bargaining or other mutual aid or protection,” so a group of employees who stop work together over a condition of employment is protected even without a union and even without first making a demand, NLRB v. Washington Aluminum Co., 370 U.S. 9 (1962). One employee acting alone is covered when the refusal honestly and reasonably invokes a right in a union contract, NLRB v. City Disposal Systems, Inc., 465 U.S. 822 (1984). Section 8(a)(1) is what makes discipline for that activity unlawful, since it is an unfair labor practice “to interfere with, restrain, or coerce employees in the exercise of the rights guaranteed in section 157,” and section 8(a)(4) separately bars retaliation against an employee who filed charges or gave testimony, 29 U.S.C. § 158. Two limits matter. Concerted activity can lose protection, because “[a]n employee may engage in concerted activity in such an abusive manner that he loses the protection of §7,” and a no-strike clause can make an otherwise concerted refusal unprotected. And the Act’s definitions exclude supervisors, independent contractors, agricultural laborers, domestic workers, and a person employed by a parent or spouse, and exclude government employers entirely, 29 U.S.C. § 152. Separately, NLRA section 502, 29 U.S.C. § 143, provides that quitting work “in good faith because of abnormally dangerous conditions” is not a strike, but Gateway Coal Co. v. United Mine Workers, 414 U.S. 368 (1974) requires “ascertainable, objective evidence” of those conditions.

What is not out there. Minnesota does not recognize a general wrongful-termination tort, Dukowitz v. Hannon Security Services, 841 N.W.2d 147, 150-51 (Minn. 2014). Employment is at will, and the common-law wrongful-discharge claim is the narrow one recognized in Phipps v. Clark Oil & Refining Corp., 408 N.W.2d 569, 571 (Minn. 1987), which covers an employee “discharged for refusing to participate in an activity that the employee, in good faith, believes violates any state or federal law or rule or regulation adopted pursuant to law.” A common-law wrongful-discharge claim outside that scope “is cognizable only if we recognize a new cause of action,” Wredberg v. Canvas Health, Inc., No. A24-1897 (Minn. Aug. 12, 2026). The Minnesota Supreme Court has limited that action “to discharges resulting from an employee’s good-faith refusal to violate the law” and has said that neither Phipps nor its companion case “recognizes a broader cause of action that arises every time an employee’s termination results from an employer’s violation of a clear mandate of public policy,” Dukowitz v. Hannon Security Services, 841 N.W.2d 147, 150-51 (Minn. 2014), a limit the court reaffirmed in Wredberg. Dukowitz also tells you where the real exposure lives, noting that “the Legislature has explicitly furnished a civil remedy for retaliation in a variety of analogous situations, including when an employer discharges an employee for seeking workers’ compensation benefits or for reporting an employer’s violation of state or federal law,” and naming Minn. Stat. §§ 176.82, subd. 1 and 181.932, subd. 1. Check the specific statute that covers the conduct in front of you rather than reasoning from public policy in the abstract. Federal protection for refusing an illegal order is likewise sector-specific rather than general, sitting in industry statutes such as the one covering a railroad employee who refuses “to violate or assist in the violation of any Federal law, rule, or regulation relating to railroad safety or security,” 49 U.S.C. § 20109, and the one covering a commercial driver who “refuses to operate a vehicle because . . . the operation violates a regulation, standard, or order of the United States related to commercial motor vehicle safety, health, or security,” 49 U.S.C. § 31105.

Document Performance Issues

When documenting for legal purposes, ensure records are:

  • Contemporaneous: Created at the time of the incident, not reconstructed later.
  • Specific: Tied to particular tasks, dates, and observable behavior, not general characterizations.
  • Consistent: Applied uniformly across similarly situated employees.
  • Preserved: Kept in the personnel file and backed up, with copies of any written warnings delivered to the employee.

Consistency matters because it removes the comparison an employee uses to prove pretext: under McDonnell Douglas Corp. v. Green, 411 U.S. 792, 804 (1973), an employer “may justifiably refuse to rehire one who was engaged in unlawful, disruptive acts against it, but only if this criterion is applied alike to members of all races,” and Minnesota courts apply that framework to disparate treatment claims under the Human Rights Act, Henry v. Independent School District #625, 988 N.W.2d 868 (Minn. 2023). Uniform treatment lowers the risk without barring a claim, because a prima facie case may also be established by direct evidence of discriminatory motive, Sigurdson v. Isanti County, 386 N.W.2d 715, 720 (Minn. 1986). Scope your uniformity practice to everyone, because a unanimous Supreme Court held in 2025 that “the standard for proving disparate treatment under Title VII does not vary based on whether or not the plaintiff is a member of a majority group,” Ames v. Ohio Department of Youth Services, 605 U.S. 303 (2025).

Documentation is what carries your side of the framework. Under McDonnell Douglas, once the employee makes a prima facie showing, “[t]he burden then must shift to the employer to articulate some legitimate, nondiscriminatory reason for the employee’s rejection,” and dated records of the assignment, the refusal, and the warnings are what meet it.

Write those records knowing the employee can read them. In Minnesota, the written warnings and discipline notices a corrective action process generates are part of the employee’s personnel record under Minn. Stat. § 181.960, subd. 4. The employee may request in writing to review that record under Minn. Stat. § 181.961, twice a year while employed and once a year after separation, and you must respond within seven working days if the record is in Minnesota and 14 if it is not, without charging a fee for the copy. An employee who disputes what a notice says may submit a written position statement of up to five pages, and under Minn. Stat. § 181.962 that statement “must be included along with the disputed information for as long as that information is maintained,” and must also go to anyone who later receives a copy of the disputed information.

Regular performance reviews that reference these documented incidents provide a paper trail demonstrating that performance concerns were communicated over time, not invented after the fact to justify a termination decision.

Seek Professional Guidance

When a task refusal implicates a legally sensitive issue (safety complaints, accommodation or pregnancy requests, protected leave, protected class membership, or concerted activity), consult a Minnesota attorney for business owners with employment experience before proceeding with discipline. The cost of early legal guidance is a fraction of the cost of defending a retaliation or discrimination claim.

For straightforward insubordination handled through a documented process that matches your own handbook, HR guidance is typically sufficient. For anything more complicated, err on the side of legal consultation before acting.

Can I fire an employee for refusing to complete assigned tasks?

Usually yes, and with fewer preliminaries than most employers assume. Minnesota employment of indefinite duration is at will, which the Minnesota Supreme Court described in Pine River State Bank v. Mettille as meaning that the employer can summarily dismiss the employee for any reason or no reason, so warnings and progressive discipline are not legal prerequisites to termination. The obligation comes from your own handbook instead. Where a handbook sets out a definite disciplinary procedure, that procedure can become part of the employment contract, and the employer in Pine River was held to have breached its employment contract by not affording the employee the job termination procedures of its handbook. Two statutes limit what you may do about the refusal itself. Minn. Stat. § 181.932, subd. 1(3) protects an employee who refuses an order the employee has an objective basis in fact to believe violates state or federal law and who tells you that is the reason, and Minn. Stat. § 182.654, subd. 11 gives an employee who has refused in good faith to perform assigned tasks under conditions of imminent danger a right to continued employment.

What if an employee refuses a task they say is unsafe or illegal?

Both protections are conditional rather than general, so run the elements before treating the refusal as insubordination. Under Minn. Stat. § 182.654, subd. 11, an employee acting in good faith may refuse work the employee reasonably believes presents an imminent danger of death or serious physical harm, and you may not discriminate against that employee for the refusal if the employee asked you to correct the hazardous condition and it remains uncorrected. Federal law is narrower. 29 C.F.R. § 1977.12(b)(1) states that, as a general matter, the Occupational Safety and Health Act affords employees no right to walk off the job because of potential unsafe conditions at the workplace, and that an employer would not ordinarily violate section 11(c) by disciplining an employee who refuses normal job activities over alleged hazards. On the illegality side, Minn. Stat. § 181.932, subd. 1(3) protects the refusal only where the employee has an objective basis in fact to believe the ordered action violates a specific law and informs you that the order is being refused for that reason.

How should I document an employee's refusal to work?

Record each incident in writing on the day it occurs. Note the date, the specific task assigned, the exact nature of the refusal, and any explanation the employee gave. Preserve related emails and meeting notes. Deliver written warnings through documented channels and keep copies. Write each notice knowing the employee can read it, because notices of warning, discipline, or termination are part of the personnel record under Minn. Stat. § 181.960, subd. 4, the employee may request a review of that record under Minn. Stat. § 181.961, and a disputed entry travels with the employee’s written position statement under Minn. Stat. § 181.962. Consistent, contemporaneous documentation is your strongest evidence if the situation leads to termination or litigation.

What is progressive discipline and when does it apply to task refusal?

Progressive discipline is a structured, step-by-step approach to corrective action, typically a verbal warning, a written warning, a final written warning or suspension, and then termination. Minnesota law does not require it, because employment of indefinite duration is at will and the employer can summarily dismiss the employee for any reason or no reason under Pine River State Bank v. Mettille, absent a handbook or policy that makes those steps binding, which Pine River held can occur. What it does is create an obligation you take on voluntarily, because handbook provisions stated in definite language, distributed to employees, and accepted by continued work may become enforceable as part of the employment contract under Pine River State Bank v. Mettille. Follow the steps you publish, or reserve discretion and the right to amend in the handbook text itself.

When should I involve HR or an employment attorney?

Involve HR as soon as a refusal is documented and a corrective conversation has been held. Consult an employment attorney before terminating an employee who has raised safety concerns, requested accommodation, taken or requested leave, acted together with coworkers over working conditions, or belongs to a protected class. Any of those factors can complicate what looks like straightforward insubordination. Early legal guidance is far less costly than defending a retaliation claim after the fact.