How to Handle Insubordination in a Professional Setting

Table of Contents

• What Counts as Insubordination in the Workplace
  • Insubordination vs. Professional Disagreement
• Examples of Insubordination in the Workplace
• Step 1: Stay Calm and Assess the Situation Before You Respond
• Step 2: How to Document Employee Insubordination Correctly
  • What to Include in an Incident Report
• Step 3: Address the Behavior in Private With a Script
• Step 4: Use an Insubordination Disciplinary Action Template
  • Progressive Discipline: Verbal Warning to Termination
  • What Belongs in the File at Each Step
  • When Insubordination Is Not the Right Label
  • The Timing Rule
• Step 5: Coach the Employee and Clarify Expectations
• When to Involve HR and How to Protect Your Company
• The Managerial Failure Audit: Is Your Leadership Part of the Problem?
• Handling Insubordination in Remote and Hybrid Teams
  • What Digital Insubordination Actually Looks Like
  • Put Directives in Writing
  • Set Response-Time Standards Before You Need Them
  • Camera, Channel, and Meeting Norms
  • When to Move From Chat to Video
  • The Hybrid Exception
• Frequently Asked Questions

Last Updated: September 19, 2026

What Counts as Insubordination in the Workplace

Insubordination at work is a refusal to follow a lawful, reasonable directive from someone with the authority to give it. This guide from Your Life’s Path explains how to handle insubordination in a professional setting without escalating the conflict or exposing your company to legal risk.

The line is clearer than most managers think. A direct order gets refused, and the refusal is willful. That’s it. Late work, a bad attitude, or a heated debate usually isn’t insubordination on its own.

Behavioral research from COSE’s workplace conduct guidance points to a shift toward prevention. Organizations now try to spot the personality drivers behind conflict before it hardens into open defiance.

That matters because most “insubordination” cases start as something smaller.

Insubordination vs. Professional Disagreement

Insubordination is a willful refusal to obey a lawful and reasonable work directive. Professional disagreement is an employee voicing a different view while still doing the work.

The difference comes down to three things:

• Was there a clear, lawful order?
• Did the employee understand it?
• Did they refuse to comply, or just push back first?

Managers on r/managers discussion threads raise a fair point. Highly educated employees often challenge directives as part of their job. Treat that as defiance and you punish good thinking.

Examples of Insubordination in the Workplace

Examples of insubordination in the workplace range from open refusal to quiet non-compliance. Some are obvious. Others hide in plain sight.

Common cases include:

• Flatly refusing a task: “No, I’m not doing that.”
• Walking out of a meeting after being given an assignment
• Publicly arguing with a supervisor in front of the team
• Ignoring a direct order and doing the opposite
• Repeatedly missing deadlines after clear instructions
• Badmouthing a manager to clients or coworkers
• Refusing to follow a safety or compliance rule

The pattern matters more than any single moment. One sharp comment is a bad day. A repeated refusal to comply is a conduct issue you have to act on.

Step 1: Stay Calm and Assess the Situation Before You Respond

Staying calm is the first move, and it’s the one most managers skip. React in the moment and you hand the employee the upper hand.

Take a breath. Then ask yourself three questions:

1. Was my instruction clear and reasonable?
2. Did the employee actually refuse, or just disagree?
3. Is this a one-time event or a pattern?

Answer those honestly before you say a word. Your response sets the tone for everything that follows.

If you’re angry, wait. A ten-minute pause beats a ten-month cleanup.

Step 2: How to Document Employee Insubordination Correctly

Knowing how to document employee insubordination correctly protects you, the employee, and the company. Good records turn a “he said, she said” argument into a clear, defensible file.

Stick to facts, not feelings. Write what was said and done, not how it made you feel.

What to Include in an Incident Report

A solid incident report covers the basics:

• Date, time, and location of the incident
• Names of everyone present
• The exact directive given, word for word if you can
• The employee’s exact response
• Any prior related incidents
• Your immediate action

Keep it neutral. “Employee said, ‘I’m not doing that'” beats “Employee was disrespectful.” One is evidence. The other is opinion.

Careerminds’ guidance on progressive discipline stresses moving away from on-the-spot reactions toward a structured, documented process. That structure is what keeps you compliant.

Step 3: Address the Behavior in Private With a Script

Address the behavior in private, and use a script so you don’t wing it. Public confrontations create witnesses, drama, and legal exposure.

Here’s a script you can adapt:

“I want to talk about what happened in Tuesday’s meeting. When I asked you to take on the client report, you said you wouldn’t do it. I need to understand your side. Can you walk me through it?”

Then listen. Don’t argue.

After they respond, restate the expectation:

“Here’s where we land. That report is part of your role. I need it by Friday. If something’s blocking you, tell me now so we can solve it.”

Close with the consequence, calmly:

“If this happens again, we’ll move to a formal warning. I’d rather we fix it here.”

The script keeps you steady and keeps the focus on conduct, not personality.

Step 4: Use an Insubordination Disciplinary Action Template

An insubordination disciplinary action template keeps your response consistent and fair. It also shows any future reviewer that you followed due process. The template matters less for the employee in front of you and more for the reviewer who reads the file six months from now.

A simple progressive path works for most cases:

Step	Action	When to Use	Documentation Required
1	Verbal warning	First minor refusal	Manager’s same-day note, no employee signature required
2	Written warning	Repeated or serious refusal	Signed acknowledgment or witnessed delivery
3	Final written warning	Pattern continues after step 2	Signed acknowledgment plus HR review
4	Performance improvement plan	Behavior tied to role expectations	Defined metrics, 30/60/90-day checkpoints
5	Termination	No change after all steps	Full file review with HR and legal before delivery

Progressive Discipline: Verbal Warning to Termination

Start at the lowest step that fits the offense. A single rude comment does not jump to termination. Move up only when the behavior repeats or worsens. Each step gets documented. Each step gives the employee a clear chance to correct course.

That is the whole point of progressive discipline. It is fair to the employee and defensible for you.

What Belongs in the File at Each Step

A common pattern among HR practitioners is that files fail not because the manager was wrong, but because the record is thin. At each step, the file should contain:

• The original directive, in writing if possible
• The employee’s response, quoted rather than paraphrased
• The date the employee was told the expectation and the consequence
• Any prior related coaching or warnings, with dates
• The employee’s signature or a note that they declined to sign
• The name of any witness or HR representative present

If the employee refuses to sign, write “Employee declined to sign” and date it. Do not forge, pressure, or skip the step.

Take The Official DiSC® Assessment Online Now! →

When Insubordination Is Not the Right Label

Before you escalate, rule out the categories that look like insubordination but are legally protected or procedurally different:

• Protected concerted activity. Under the National Labor Relations Act, employees in non-supervisory roles generally have the right to discuss wages, hours, and working conditions with each other. A group complaint about pay or safety is not insubordination, even if the tone is sharp.
• Safety refusals. An employee who refuses a task they reasonably believe is imminently dangerous may be protected under OSHA. Route these to safety leadership, not discipline.
• Reasonable accommodation requests. A refusal tied to a disability, religious practice, or medical restriction is an accommodation conversation, not a conduct issue.
• Whistleblower reports. Retaliating against an employee for reporting suspected illegal activity can trigger liability under federal and state whistleblower statutes.

If any of these are in play, stop the disciplinary track and involve HR before your next conversation. Mislabeling protected activity as insubordination is one of the most common and most expensive mistakes managers make.

The Timing Rule

Deliver each step within a few business days of the triggering event. A warning issued three weeks after the incident reads as retaliation or as a manufactured paper trail. Same-week delivery, same-day notes.

Step 5: Coach the Employee and Clarify Expectations

Coaching is where most managers stop too early. A warning changes nothing if the employee still doesn’t know what “good” looks like.

Use corrective coaching to reset expectations:

• Restate the specific behavior you need to change
• Explain why it matters to the team and the work
• Agree on what success looks like
• Set a check-in date to review progress

This is where behavioral insight pays off. Employees who understand their own communication style tend to handle feedback better. Tools like SHRM’s HR guidance on insubordination reinforce that clear, consistent expectations are the backbone of any corrective process.

A DiSC Management Profile can give you that read on how each team member prefers to receive direction, and our Virtual Workshops walk managers through applying it in real conversations.

When to Involve HR and How to Protect Your Company

Involve HR early when the behavior could lead to termination, when the employee has a protected characteristic, or when you’re unsure about legal risk. HR protects the company and keeps the process consistent.

Bring HR in when:

• The behavior is severe or repeated
• The employee threatens legal action
• A policy violation is involved
• You’re considering termination
• The employee has raised a complaint of their own

Document everything you send to HR. Keep the file clean and factual.

The Managerial Failure Audit: Is Your Leadership Part of the Problem?

Sometimes the manager is part of the problem, and a honest audit will show it. That’s uncomfortable, but it’s worth the look.

Ask yourself:

• Was my instruction actually clear?
• Did I give the employee the tools and time to comply?
• Have I been consistent with the whole team?
• Am I reacting to the person, not the behavior?

If you answered “no” to any of these, fix your side first. Insubordination can be real, but it can also be a symptom of unclear leadership.

Handling Insubordination in Remote and Hybrid Teams

Remote and hybrid teams make insubordination harder to spot. There is no hallway moment, no read on tone, no body language to check. Most guides still assume an office, which is why digital insubordination is the biggest gap in the current literature.

The core problem is ambiguity. In an office, a manager can walk over and confirm a directive was heard. In a distributed team, silence is the default and silence is not consent.

What Digital Insubordination Actually Looks Like

Watch for patterns, not single events:

• Ignoring direct messages or meeting invites from a manager while responding to peers in the same window
• Slow-walking assignments past agreed deadlines without flagging a blocker
• Public pushback in shared channels that would never happen in a one-on-one
• Going silent after a direct written request, then resurfacing days later as if nothing happened
• Turning off the camera in every meeting after being asked to keep it on for client calls
• Declining or no-showing to scheduled one-on-ones repeatedly
• Editing shared documents to reverse a decision that was already made

One missed message is not insubordination. A documented pattern of ignoring a specific manager’s directives while complying with everyone else’s is.

Put Directives in Writing

The single most effective prevention step is to move directives out of chat and into a durable channel. A direct message can be edited, deleted, or buried. A task in your project management tool, an email with a clear subject line, or a shared doc with a timestamp creates a record.

A workable format for a written directive:

Task: Update the Q3 client report with the revised figures.
Owner: [Employee name]
Deadline: Friday, 5:00 p.m. local time.
Blocker protocol: If you cannot meet this, reply by Wednesday with the specific blocker.
Consequence: This is a required deliverable for the client meeting.

That format removes the two most common defenses: “I did not know it was urgent” and “I did not know it was my job.”

Set Response-Time Standards Before You Need Them

Most remote conflicts trace back to mismatched expectations about responsiveness. Publish the standard, apply it to everyone, and enforce it evenly.

A common baseline that works for many teams:

• Chat: Reply within four business hours during the workday
• Email: Reply within one business day
• Direct manager requests: Acknowledge within two hours, even if the answer is “I will get to this tomorrow”
• After-hours: No expectation of response unless the role has an on-call rotation

When the standard is written and applied to the whole team, “I did not see it” stops being a defense and becomes a documented performance issue.

Camera, Channel, and Meeting Norms

Camera policies are a frequent flashpoint. Decide the rule for your team and state it in writing:

• Client-facing calls: camera on unless there is a documented reason
• Internal team meetings: camera optional, but active participation required
• One-on-ones: camera on for the manager, employee’s choice unless performance is under review

Apply the same rule to yourself. A manager who asks for cameras on and then joins every call audio-only has no standing to enforce the policy.

When to Move From Chat to Video

Text strips tone. A neutral message can read as hostile, and a hostile message can read as neutral. When a written exchange starts to escalate, move it to a live conversation within one business day. Do not keep trading paragraphs.

After the live conversation, send a short written summary: what was discussed, what was agreed, and what happens next. That summary becomes the record.

The Hybrid Exception

Hybrid teams create a specific risk: an employee who is compliant in the office and non-compliant on remote days. Track behavior by day and channel, not by overall impression. If the pattern is real, it will show up in the log. If it is not, you have saved yourself from a false accusation.

Frequently Asked Questions

What qualifies as insubordination at work?

Insubordination is a willful refusal to follow a lawful, reasonable direct order from a supervisor. It requires intent, not just a mistake or a question. An employee who asks for clarification is not being insubordinate. An employee who flatly refuses to complete an assigned task after being told to do so is. HR experts recommend defining insubordination clearly in your employee handbook, including examples, so any disciplinary action you take is consistent and legally defensible.

What is the difference between insubordination and a simple disagreement?

A disagreement is a difference of opinion about how to approach a task. Insubordination is a refusal to comply with a directive after the disagreement has been heard. Highly educated or specialized employees often push back as part of their professional role, and managers who cannot tell the two apart risk punishing healthy debate. The test: did the employee ultimately follow the directive, or did they refuse? If they followed it, you have a disagreement, not insubordination.

Can an employer fire an employee for insubordination?

Yes, in most U.S. states employment is at-will, so an employer can terminate for insubordination. However, firing without documented progressive discipline invites legal risk. SHRM and employment attorneys consistently advise a formal, documented process: verbal warning, written warning, performance improvement plan, then termination. If the insubordination involved a protected activity like reporting harassment, termination could be seen as retaliation. Involve HR before you act.

How do I document employee insubordination without it looking retaliatory?

Stick to observable facts, not interpretations. Write what was said, when, and who witnessed it. Avoid words like “hostile” or “disrespectful” unless you quote the exact language. Record the direct order given, the employee’s response, and the impact on work. Date every entry and keep copies in a secure file. Consistent documentation across all employees, not just the one you are frustrated with, is what protects you from a retaliation claim.