An Employee Just Refused a Task as Unsafe. What OSHA's 1977.12 Says You Can and Can't Do Next

The job is running late and the customer is on the phone. You ask one of your guys to climb into the pit under the lift and finish the brake line, or to go up on the roof edge and pull the last of the old flashing, or to reach into the conveyor and clear the jam so the line can restart. He looks at the job, looks at you, and says he is not doing it. It isn't safe.

What happens in the next ten minutes matters more than almost anything else you will do that week, and most owners handle it on instinct. Some push harder. Some write the employee up at the end of the shift for insubordination. Some shrug and do the task themselves. Very few know that OSHA has a specific regulation describing when a refusal like that is protected, and that the answer turns on facts you can check right there on the shop floor.

This post answers one question: when an employee refuses a task because they believe it is dangerous, what does 29 CFR 1977.12 actually say about whether you can discipline them, and what should you do instead? It does not re-explain retaliation law generally. For that, our post on OSHA's anti-retaliation rule covers the broader picture of Section 11(c).

There is no general right to walk off the job

Start with the part owners rarely hear, because it is the part that surprises employees too. The regulation says plainly, in 1977.12(b)(1), that as a general matter nothing in the Occupational Safety and Health Act entitles employees to walk off the job because of potential unsafe conditions. The expected path when someone sees a hazard is that they report it, the employer fixes it, and if the employer doesn't, the employee can ask OSHA to inspect under Section 8(f) of the Act or go to another agency with authority over the problem.

The same paragraph goes on to say that, under ordinary circumstances, an employer would not normally violate Section 11(c) by disciplining an employee who refuses normal job duties over alleged safety concerns. That sentence is why some owners believe they are always within their rights to write up a refusal. They are reading half the rule.

The exception that decides most real refusals

Paragraph (b)(2) carves out the situation that actually matters. It recognizes that an employee can end up facing a choice between not doing the assigned task and exposing themselves to serious injury or death. When an employee, with no reasonable alternative, refuses in good faith to expose themselves to that condition, they are protected against later discrimination.

The regulation then sets out what has to be true for that protection to attach. Read together, there are four conditions.

The first is good faith. The employee has to actually believe the danger is real. A refusal used as cover for avoiding unpleasant work, or as leverage in an unrelated dispute, does not qualify.

The second is that a reasonable person would agree. The test is not whether you, or an inspector, or an engineer would later conclude the job was safe. It is whether a reasonable person, in the circumstances the employee was facing at that moment, would conclude there was a real danger of death or serious injury. That is judged from where the employee was standing, with the information they had, not with hindsight.

The third is urgency. There has to be insufficient time, because of the urgency of the situation, to get the danger eliminated through regular enforcement channels, meaning a complaint and an inspection. A hazard that is serious but will not hurt anyone before OSHA could look at it generally points toward reporting rather than refusal.

The fourth is that the employee asked you first. Where possible, the employee must have sought a correction of the condition from the employer and been unable to get it. This is the condition that most directly involves you. If the employee tells you what is wrong and you fix it, the refusal question usually disappears.

Notice what the regulation does not require. The employee does not have to be right. They do not have to cite a standard, use the word "OSHA," or put anything in writing. A mechanic who says "I'm not going under that car, the lift arm is slipping" has told you enough.

What to do in the moment

Because the protection turns on what a reasonable person would have concluded and whether you were given a chance to fix things, the first few minutes after a refusal are where you either resolve the problem or create a retaliation claim.

Stop the task, not the conversation. Don't assign the same job to someone else while the concern is unresolved. If the hazard is real, you have just moved it to a different person, and the second employee's injury would be on you. If the first employee raised it in front of others, reassigning it quietly sends a message about what happens to people who speak up.

Ask what they see. Get specific. Which part of the lift, which section of the roof edge, which guard is missing, what did the gas meter read. Often the employee has noticed something you haven't, because they are closer to it. Sometimes the concern turns out to rest on a misunderstanding that can be cleared up by showing them the lockout already in place or the anchor point that was installed last month.

Look at it yourself, or have someone competent look. Many OSHA standards already describe the conditions an employee is worried about. A conveyor that can restart while someone is reaching in is a lockout/tagout issue under 1910.147. An unprotected edge six feet or more above a lower level on a construction job is a fall protection issue under 1926.501. If your own review finds the condition the employee described, you have your answer.

Fix it, or offer a genuinely safe alternative. The regulation's language about "no reasonable alternative" cuts both ways. If you can lock out the equipment, bring in a harness and anchor, rent the right lift, or assign the employee to other work while the job is made safe, do it. An employee who is offered a real, safe alternative and still refuses is in a different position from one who is simply told to get on with it.

Write down what happened. A short note is enough: what the employee said, what you checked, what you found, what you did, and when the task resumed. If you ever have to explain your decision to OSHA, a record made that day is far more persuasive than a recollection assembled months later.

Where discipline goes wrong

The riskiest moment is not the refusal itself. It is the performance conversation two weeks later, or the schedule cut, or the decision not to call someone back after a slow period. Section 11(c) protects against discrimination because of protected activity, and a well-founded refusal under 1977.12(b)(2) is protected activity. An employee who believes they were punished for it can file a complaint with OSHA, and the statute gives them 30 days from the adverse action to do so.

That does not mean you can never discipline an employee who once refused a task. It means any later action has to stand on its own facts, documented consistently with how you treat everyone else, and far enough removed from the refusal that the connection is not obvious. If you find yourself thinking of a refusal as the reason someone is "not a team player," that thought is the connection an investigator would look for.

It is also worth knowing that a number of states run their own OSHA-approved plans, and some of those states have work refusal protections written more broadly than the federal regulation. If you operate in a state plan state, check your state's rules rather than assuming the federal text is the whole story.

Making refusals rarer, not riskier

The businesses that handle this well are rarely the ones with the most carefully drafted discipline policy. They are the ones where employees raise concerns early, before a task is assigned under deadline pressure. A pre-task conversation about the job, a habit of stopping briefly to ask what could go wrong, and a genuine practice of acting on near-miss reports all reduce the number of times an employee ends up at the point of saying no.

When a refusal does happen, treat it as information. The employee is telling you that, from where they stand, the job as assigned could hurt them. Sometimes they are wrong, and a few minutes of explanation settles it. Sometimes they are right, and the refusal has just prevented the injury, the claim, and the inspection that would have followed.

None of this guarantees how OSHA or a court would view a particular situation, and a disputed refusal involving discipline is worth discussing with employment counsel before you act. What 1977.12 gives you is a clear set of questions to ask in the moment. Ask them before you decide, not after.