"They're being insubordinate" is one of the most common complaints managers bring to HR, and one of the most frequently mishandled. Not every disagreement counts. Not every refusal counts. And the difference between an employee who's insubordinate and an employee who has raised a legitimate concern often comes down to how HR investigates, documents, and decides. Get it wrong and you face a wrongful termination or retaliation claim. Get it right and you have a defensible employment action.
The Four Elements That Make Conduct Insubordination Most labor arbitrators and employment courts apply a similar four-part test. First, the directive must be clear: the employee has to understand exactly what they were asked to do. Vague instructions don't qualify. Second, the directive must be reasonable and within the employee's job scope. Being told to do something outside your role or position is not insubordination to refuse. Third, the directive must be lawful; an employee can refuse to falsify records or commit a safety violation. Fourth, the refusal must be willful, not inability.
A missed deadline is not insubordination if the employee tried. A refusal to work unsafe hours is not insubordination if the directive violated OSHA rules. An argument about the right approach to a project is not insubordination if the employee ultimately complied.
What Insubordination Looks Like in Practice Clear cases: "No, I'm not doing that" in response to a reasonable work assignment. Walking off a shift without permission. Repeated refusal to attend meetings after being told they're required. Refusing to comply with a documented performance improvement plan.
Gray cases: challenging a manager's decision in a meeting, expressing disagreement forcefully, questioning the ethics of an instruction, raising safety concerns, or engaging in protected activity like filing a grievance . These are not insubordination and treating them as such risks a retaliation claim.
Can You Fire an Employee for Insubordination on the First Offense? Legally, yes in most at-will states. Practically, it depends on severity and past practice. A blatant refusal to follow a core safety directive might justify immediate termination. A heated exchange about an assignment usually calls for a documented conversation first. Inconsistent application is the fastest way to turn a defensible termination into a wrongful termination case.
How HR Should Investigate Insubordination Claims Start with the facts, not the characterization. Ask the manager: what exactly did you ask the employee to do, what did they say or do in response, and what was the context. Interview the employee separately. Review any relevant written communications. Check whether the employee had raised concerns (safety, legal, harassment) that might reframe the refusal as protected activity.
Document everything. An insubordination termination without a clear written record of the directive, the refusal, and the investigation is almost impossible to defend in an at-will employment challenge, particularly if the employee is in a protected class.
Building an Insubordination Response That Protects Both the Company and the Employee The strongest HR response treats insubordination like any other conduct issue: through a structured, documented process that separates investigation from decision. Managers should not be making termination calls on their own in the moment. Centralized intake, a standardized investigation protocol, and calibrated discipline across similar cases produce defensible outcomes. See harassment and hostile work environment for related investigations, and just-cause termination for how courts evaluate these decisions. The NLRB publishes guidance on when conduct that looks insubordinate is actually protected concerted activity under Section 7.
AllVoices' HR case management platform gives employee relations teams the structured documentation and audit trail that insubordination cases require, keeping investigation notes, directives, witness statements, and disciplinary decisions in one reviewable record.