Insubordination is when an employee flat-out refuses to follow a manager's lawful, fair order. It's one of the hardest people problems a small-team leader faces. The line between "a defiant employee" and "someone who just disagreed with me" is thinner than most founders think. Get it wrong and you either let bad behavior slide, or you punish someone for something they were legally allowed to do.
This guide breaks down what counts as insubordination, 10 real examples, what it is not, why it happens, and a calm step-by-step way to handle it — plus a write-up template you can copy today.
What Is Insubordination?
Insubordination is the willful refusal to obey a direct, lawful, and fair order from someone who has the right to give it. The key word is willful. An honest mistake, a mix-up, or a good-faith question isn't insubordination — a flat, chosen "no" is.
The Society for Human Resource Management (SHRM) uses a three-part test. For a behavior to count as insubordination, all three must be true:
- A manager gives a clear order. It can be spoken, written, in a job description, or fairly implied. "Please send the client the invoice by end of day" counts.
- The employee gets and grasps the order. They take it in — by nodding, replying, or simply by having taken on the role the task belongs to.
- The employee refuses to do it. This can be a flat "no," a refusal without words, or a delay so long it adds up to a refusal.
If any one of the three is missing, you likely don't have insubordination. No clear order? Then it's a communication gap. The employee didn't get it? That's a training issue. They tried and failed? That's a performance problem, not defiance.
That gap matters, because insubordination is one of the few behaviors that can justify fast, serious disciplinary action — sometimes even firing on a first offense if it's bad enough. So before you reach for a warning, make sure all three boxes are truly checked.
Insubordination vs. Disagreement: Where's the Line?
Here's the trap. A team member pushes back on a call, and it feels like defiance. But disagreement — even blunt, awkward disagreement — is not insubordination. You want people who challenge ideas. The difference is what happens after the call is made.
| Situation | Insubordination? | Why |
|---|---|---|
| "I think this plan is a mistake, here's why" — then does the work anyway | No | Voicing an opinion, then complying |
| "I'm not doing that" — refuses the lawful task outright | Yes | Willful refusal of a reasonable order |
| Asks a clarifying question before starting | No | Seeking to understand, not refusing |
| Rolls eyes, mutters, but completes the task | Gray area | Attitude, not refusal — coach it, don't write it up |
| Publicly tells the team to ignore your instruction | Yes | Refusal plus undermining authority |
| Refuses a task that's unsafe or illegal | No | Legally protected (more below) |
The clean test: Did they disagree, or did they disobey? Disagreement voiced through the right channel is healthy. Disobeying a lawful order, after the call stands, is where insubordination begins. If you want a culture where people feel safe to speak up, spell it out in your employee handbook so the rule is written down, not assumed.
10 Examples of Insubordination at Work
Insubordination isn't always a shouting match. More often it's quiet, repeated, or dressed up as something else. Here are 10 real examples founders and first-time managers run into.
- Flat refusal of a reasonable task. "That's not my job" — when it clearly is, and the request is lawful.
- Ignoring direct instructions. You ask for the report by Friday; they simply don't do it and offer no reason.
- Openly defying a decision. After a call is made, they tell teammates, "We're not actually going to do that."
- Refusing to follow a clear policy. Skipping a required safety step, expense rule, or security check on purpose.
- Walking out of a meeting or off a shift. Leaving mid-task in protest after being asked to stay.
- Verbal abuse toward a manager. Cursing at, insulting, or threatening a supervisor during a work interaction.
- Deliberately doing the opposite. Being told to pause a campaign and launching it anyway.
- Undermining authority behind the scenes. Telling reports to ignore a manager's orders, or spreading that "leadership doesn't know what they're doing" to derail a decision.
- Refusing a fair schedule or location change that falls within their agreed role and contract.
- Chronic, willful lateness after clear direction. Ignoring a manager's plain order to show up on time, with no good reason. (This shades into an attendance policy issue, but when it's a direct "I heard you and I won't," it's insubordination.)
Notice the pattern: in every case there's a clear order, the person got it, and they chose not to comply. Attitude alone — a bad mood, a sigh, one snide comment — doesn't make the list. Behavior does.
What Is Not Insubordination
This is the part that gets small businesses into legal trouble. Some refusals aren't just allowed — they're protected by law. Punishing an employee for these can turn an ordinary people problem into a wrongful-firing or retaliation claim.
Refusing an unsafe order. Under OSHA's right-to-refuse rules, an employee can refuse work they truly believe puts them in danger of serious injury or death, when there's no time to fix it through normal channels. That refusal is not insubordination.
Refusing an illegal or unethical order. "Backdate this contract" or "don't report that injury" — saying no to breaking the law or faking records is protected, not defiant.
Whistleblowing and protected complaints. Reporting harassment, bias, wage theft, or safety issues is shielded. The EEOC's guidance on retaliation makes clear you can't punish someone for raising a good-faith complaint — and dressing up payback as "insubordination" is a well-known red flag to investigators.
Refusing something outside the job. If a task isn't fair or falls well outside the role, saying no isn't insubordination — it's a scope talk.
Honest mix-ups. If the order was vague or the employee truly didn't grasp it, there's no willful refusal. That's on the clarity of the order, not the person.
When in doubt, ask one question before you act: Was this refusal protected by law? If you can't answer with confidence, pause and check with an HR advisor or employment lawyer before you punish anyone.
Common Causes of Insubordination
Insubordination rarely shows up out of nowhere. On small teams especially, it's usually a symptom. Finding the root cause helps you fix the real problem instead of just punishing the surface behavior.
- Unclear expectations. If nobody wrote down who owns what, "that's not my job" is a role-design gap as much as a defiance problem.
- A sense of unfairness. An employee who feels passed over for a raise, promotion, or credit may start to hold back help.
- Weak or uneven management. When rules apply to some people and not others, resentment builds and orders stop landing.
- Poor communication. Orders given as vague hints, or changed all the time, breed the kind of confusion that looks like refusal.
- Personal stress. Burnout, health issues, or trouble at home can spill into a short fuse at work.
- A real values clash. Sometimes the person thinks the order is wrong — and now and then they have a point worth hearing before it hardens into open defiance.
None of these excuse insubordination, but each points to a fix. A clash about direction is solved very differently from burnout or a broken pay talk. Diagnose before you discipline.
How to Handle Insubordination: Step by Step
When insubordination happens, your goal is to fix the behavior fairly, write everything down, and protect the business — without blowing a bad moment up into a bigger one. Work through these steps in order.
1. Cool down first
Never discipline in the heat of the moment. If an employee just refused you in front of the team, step away, let the adrenaline drop, and deal with it in private once you can be fair. Reacting live almost always makes it worse.
2. Confirm it's really insubordination
Run the three-part test again. Was there a clear, lawful order? Did they get it? Did they willfully refuse? And — the big one — was the refusal protected by law? If any box is unchecked, treat it as the problem it really is (a training gap, a safety concern, a mix-up), not as insubordination.
3. Talk in private and listen
Have a calm one-on-one. State what happened as fact: "I asked you to X, and you said Y." Then ask why. You may find a fair reason — or confirm it was plain refusal. Either way, the talk itself is part of your record.
4. Follow progressive discipline
Most cases call for a step-by-step response, not a jump straight to firing. A typical path runs: verbal warning → written warning → final warning → firing. Match the response to the offense. A first-time refusal usually starts with a verbal warning; gross insubordination (threats, sabotage) can justify skipping steps.
5. Write everything down
This one is a must. Note the date, what was asked, what the employee did, who saw it, and what you chose to do. If you give a formal warning, put it in the employee's personnel file. A steady paper trail is what protects you if things ever lead to firing or a legal claim.
6. Set clear expectations going forward
End with what you need to see change, by when, and what happens if it doesn't. Vague warnings don't work. If the behavior is part of a bigger pattern, a performance improvement plan sets clear goals and a timeline everyone can point to.
7. Be consistent
Hold everyone to the same standard. If one person gets a written warning for refusing a task and another gets a pass, you've cut your own authority off at the knees — and handed a bias claim to anyone you discipline later. Consistency is the whole game.
Insubordination Write-Up Template
When a spoken talk isn't enough, log the incident with a formal write-up. Copy the template below, fill in the brackets, keep it to the facts, and have both people sign. Store the signed copy in the employee's file.
EMPLOYEE DISCIPLINARY WRITE-UP — INSUBORDINATION
Employee name: ____________________________
Job title: ________________________________
Manager / supervisor: _____________________
Date of incident: _________________________
Date of this write-up: ____________________
LEVEL OF ACTION (check one):
[ ] Verbal warning (documented) [ ] Written warning
[ ] Final written warning [ ] Termination
1. DESCRIPTION OF THE INCIDENT
State the facts only — what was asked, what the employee did.
Avoid opinions or labels.
Example: "On [date], [manager] instructed [employee] to [task].
[Employee] responded, '[exact words]' and did not complete the task."
__________________________________________________________________
__________________________________________________________________
2. THE INSTRUCTION GIVEN
What lawful, reasonable order was refused?
__________________________________________________________________
3. WITNESSES (if any)
__________________________________________________________________
4. PRIOR RELATED WARNINGS
Date(s) and type of any previous warnings on this issue.
__________________________________________________________________
5. COMPANY POLICY VIOLATED
Reference the relevant handbook section.
__________________________________________________________________
6. EXPECTATIONS GOING FORWARD
Specific behavior required, by when.
__________________________________________________________________
7. CONSEQUENCES IF UNRESOLVED
What happens if the behavior continues.
__________________________________________________________________
EMPLOYEE COMMENTS (optional):
__________________________________________________________________
Employee signature: __________________ Date: __________
(Signature confirms receipt, not necessarily agreement.)
Manager signature: ___________________ Date: __________
One note that trips people up: an employee's signature confirms they got the write-up, not that they agree with it. If someone won't sign, write "Employee declined to sign" and date it with a witness present. That refusal doesn't void the document. For related cases, our disciplinary action guide and employee termination letter template cover the next steps if the behavior gets worse.
How to Prevent Insubordination
The best way to handle insubordination is to make it rare in the first place. Most of it traces back to unclear expectations or a strained relationship — both of which you can get ahead of.
Write expectations down. Vagueness is where "that's not my job" lives. A clear employee handbook, written roles, and a set chain of command remove the excuses before they start.
Explain the why. People say yes more readily when they know the reason behind an order. "Do it because I said so" invites pushback; "here's why this matters to the client" earns buy-in.
Fix small issues early. A missed deadline or a sharp comment handled kindly today keeps a pattern from hardening into open defiance. Regular one-on-ones are your early-warning system.
Set clear standards for new hires. Use the probation period to set norms and give feedback while the stakes are low and the relationship is still forming.
Build real trust. People rarely defy managers they respect and feel heard by. Strong employee relations — fairness, follow-through, real listening — do more to prevent insubordination than any policy.
For small teams with no HR person, the hard part is keeping all of this in order: roles, warnings, signed documents, review notes. A lightweight HR tool like Tiny Team keeps employee records, documents, and discipline notes in one place, so nothing key lives only in your head or a lost email thread. It's free for teams up to 10, and a flat $79/month for up to 50 — with no per-person billing as you grow.
Frequently Asked Questions
Can you be fired for insubordination on the first offense?
Yes, it's possible. Most employers use progressive discipline for minor cases, but serious ("gross") insubordination — such as threats, sabotage, or refusing a key safety order — can justify firing on a first offense. Because most U.S. jobs are at-will, an employer can usually fire for true insubordination, as long as the refusal wasn't protected by law and you've logged it the same way you would for anyone else.
What's the difference between insubordination and misconduct?
Insubordination is one type of misconduct: the willful refusal to follow a lawful, fair order from someone with authority. Misconduct is the wider bucket — it covers things like theft, harassment, or policy breaks that don't involve refusing a direct order. All insubordination is misconduct, but not all misconduct is insubordination.
Is refusing to do something unsafe insubordination?
No. Under OSHA's right-to-refuse rules, an employee who truly believes a task puts them in danger of serious injury — with no time to fix it through normal channels — is protected when they refuse. The same shield applies to refusing illegal or unethical orders. Punishing someone for a protected refusal can open you up to a retaliation claim.
How do I document insubordination the right way?
Log the facts: the date, the exact order given, what the employee said or did (their words, if you can), any witnesses, and the step you took. Keep it to the facts, with no labels or heat. Have the employee sign to confirm they got it, and store the signed write-up in their personnel file. A steady paper trail is your best protection if things get worse.
Is disagreeing with my boss insubordination?
No. Voicing a different view — even a strong one — through the right channel is not insubordination. It only becomes insubordination if you refuse to carry out a lawful, fair order after the call has been made. Healthy workplaces expect people to disagree, then commit once a call is made.
What should I do if an employee refuses to sign a write-up?
An employee doesn't have to sign, and refusing doesn't make the write-up void. Note "Employee declined to sign" on the form, date it, and have a witness there if you can. The signature only confirms the employee got the document — not that they agree with it — so a refusal to sign changes nothing about whether the record holds up.
