Insubordination in the Workplace
Insubordination is an employee's deliberate refusal to carry out a lawful and reasonable instruction given by someone with the authority to give it. It is treated as misconduct, and depending on severity and context it may be grounds for discipline up to dismissal.
The definition has three parts, and all three have to hold.
The three tests
- The instruction was lawful. An instruction to do something illegal, or to breach a regulatory obligation, is not one an employee is required to follow. Refusing it is not insubordination.
- The instruction was reasonable, and within the scope of the employee's role. "Reasonable" covers whether it was within their duties, whether it was safe, and whether it was practically achievable.
- The person had authority to give it, and the refusal was deliberate rather than a misunderstanding, an inability, or a question asked in good faith.
What is not insubordination
This is where most employers get into difficulty:
- Disagreement. An employee who argues the instruction is wrong, then does it, has not refused.
- Raising a safety concern, or declining work they reasonably believe is unsafe.
- Refusing something unlawful, or that would breach a regulatory duty.
- Inability, where the person lacks the skill, tools, access or time — a capability matter, not a conduct one.
- A misunderstanding, where the instruction was ambiguous or was never actually received.
- Whistleblowing or raising a grievance, which is protected activity, not defiance.
Treating any of these as misconduct is the single most common way a disciplinary process collapses on review.
Severity varies
A one-off refusal in a heated moment is not the same event as a pattern of ignoring direction, and neither is the same as public defiance that undermines a manager's authority in front of a team. The response should be proportionate: coaching and a documented conversation at one end, a formal process at the other.
Handling it properly
- Establish the facts before characterising them — what was asked, by whom, when, in what terms, and what exactly was said or done in response.
- Check the three tests above honestly.
- Follow your own procedure. The employee handbook and any collective agreement set the process, and departing from your own stated process is a problem even where the underlying conduct is real.
- Put the allegation to the employee and let them respond before any decision.
- Document everything contemporaneously — the instruction, the refusal, the meeting, the response, the outcome.
- Be consistent. Treating the same conduct differently across people is how a defensible decision becomes an indefensible one.
Why the record matters
Almost every disputed disciplinary outcome turns on what was documented at the time, not on what people remember afterwards. Warnings issued, conversations held, the employee's response and the decision all belong on the employee record, dated, rather than in a manager's inbox.
Avant One℠ HR keeps disciplinary records against the employee record alongside performance history and contract terms, so a process is evidenced from the system.
Frequently asked questions
Is refusing to do something unsafe insubordination?
No. An employee who reasonably believes the work is unsafe, or who is asked to do something unlawful, is not required to comply, and refusing is not misconduct.
Can an employee be dismissed for insubordination?
Depending on severity and on following the correct process, yes — but the three tests must hold and the employer's own disciplinary procedure, and any applicable collective agreement, must be followed.
Is arguing with a manager insubordination?
Not by itself. Disagreement expressed and then followed by compliance is not refusal. The question is whether the instruction was ultimately carried out, and how the disagreement was expressed.
What is the difference between insubordination and poor performance?
Insubordination is a conduct issue — the employee could do it and chose not to. Poor performance is a capability issue — they tried and fell short. The two require different processes, and confusing them undermines both.