Post-Incident Drug Testing: What OSHA Actually Allows (And What Gets You Cited)

Here is a scenario that plays out every week in small businesses across the country. A forklift driver clips a shelf rack. No one is hurt. A few boxes fall. The supervisor, following company policy, immediately sends the driver for a urine drug test. The driver comes back clean. Two weeks later, OSHA shows up for an unrelated inspection, reviews your procedures, and issues a citation for discouraging injury reporting.

If that surprises you, you are not alone. Thousands of employers discovered — often the hard way — that OSHA's 2016 recordkeeping rule overhauled the legal landscape around post-incident drug testing. The rule is still widely misunderstood, and the misunderstanding is expensive.

Where This All Started: 29 CFR 1904.35

In May 2016, OSHA published a final rule amending 29 CFR 1904.35, the recordkeeping regulation governing employee rights around injury reporting. The headline change was straightforward: employers cannot retaliate against workers who report work-related injuries or illnesses.

But buried in the rule's preamble and enforcement guidance was a provision that sent safety managers scrambling. OSHA declared that certain post-incident drug and alcohol testing programs could constitute implicit retaliation — not because the employer said "we'll punish you for reporting," but because the structure of the testing policy itself could deter an employee from coming forward.

The agency's logic: if an employee knows that reporting any injury, regardless of cause, will trigger a drug test, they may choose not to report a minor injury at all. That chilling effect, even if unintentional, violates the spirit of the recordkeeping rule. OSHA can and does cite employers under Section 11(c) of the OSH Act — the anti-retaliation provision — when they believe blanket testing is being used as a de facto deterrent.

The Bright Line: What You Can Test For

OSHA was careful not to ban all post-incident testing. The agency drew a line based on one key question: is there a reasonable possibility that drug or alcohol use contributed to the incident?

If the answer is yes, testing is permissible. In fact, it is a perfectly legitimate safety practice. If a worker is driving erratically and then crashes a company vehicle, you can test. If a machine operator is slurring words and then activates a press incorrectly, you can test. If the behavior before the incident gives you genuine cause to believe impairment played a role, document that cause and send the employee for testing.

What you cannot do — at least not without risking a citation — is test automatically after every workplace injury, no matter how minor or how unlikely drug use is to have played a part. The classic example OSHA has used in enforcement guidance: an employee reports a bee sting. If your policy says every injury triggers a drug test, sending that person to the lab is not a safety measure. It is a policy that, on its face, discourages reporting.

The same logic applies to injuries caused by equipment failure, a hazard nobody could have anticipated, or a third party's actions. If the incident has nothing to do with the employee's physical condition or judgment, blanket testing crosses the line.

State Laws Add Another Layer

For employers who operate in states with their own OSHA-approved plans — California, Michigan, Minnesota, Washington, and about two dozen others — the analysis gets more complicated. Some states have their own drug testing statutes that interact with their safety plans in unexpected ways. A policy that is defensible under federal OSHA rules may still create exposure under a state's employment law, or vice versa.

Several states — Colorado, Arizona, New Jersey, New York, among others — have now legalized recreational marijuana. Impairment from cannabis is a real safety concern, but a positive urine test for THC does not prove impairment at the time of an incident. Urine screens detect metabolites that can remain present for days or weeks after use. If you are in a legal-marijuana state and you test positive post-incident, terminating an employee on that basis alone carries significant wrongful-termination risk unless your state law specifically protects employers in that scenario. Some do. Some don't. You need to know which situation you are in before you rely on a urine test as the basis for any adverse action.

What a Defensible Drug Testing Policy Looks Like

The goal is a policy that genuinely promotes safety without creating the appearance — or the reality — of retaliation. Here is how most employment attorneys and safety consultants recommend structuring it for a small business.

Your policy should state, in plain language, that testing will be conducted when there is reasonable suspicion of impairment, when the nature of the incident reasonably suggests impairment may have been a factor, or when required by a client contract or federal regulation (like Department of Transportation rules for drivers). It should also make clear that reporting an injury will not, by itself, trigger testing.

Train your supervisors in reasonable suspicion recognition. This is not optional. A supervisor who cannot articulate why they sent someone for a test — slurred speech, unsteady gait, the smell of alcohol, erratic behavior — has not met the "reasonable possibility" standard. The observation needs to be documented contemporaneously, before the test, not after a positive result comes back and someone is looking for justification.

Review your existing policy language. If it says something like "any injury requiring medical treatment will result to post-incident drug testing," you have a problem. That language is precisely what OSHA's enforcement guidance targets. Replace it with cause-based language.

If you operate under DOT regulations — any business with drivers holding a commercial license operating vehicles over 26,001 pounds, for instance — federal DOT rules require specific post-accident testing. Those rules supersede the OSHA guidance for covered operations. But DOT's rules are also cause-based in most circumstances; they are not a blanket "test everyone" scheme.

The Documentation Question

Whatever your policy says, the enforcement reality is that documentation is your defense. If you tested an employee post-incident and you want to be able to show OSHA the decision was reasonable, you need a written record of the specific facts that supported testing. What did the supervisor observe? When? What did the incident look like? Why was impairment a plausible contributing factor?

If you cannot reconstruct that narrative from your own records, you cannot rebut an allegation of retaliation. The test result itself — positive or negative — is not the point. The point is whether you had a legitimate, documented basis for requiring the test before you knew the result.

Keep incident investigation records separate from drug testing records. OSHA does not have access to drug test results during a routine inspection, but they can examine your testing policy, your supervisor training records, and the pattern of who you have tested and when. A pattern of testing only workers who report injuries — but never testing workers for any other reason — is a red flag.

A Program That Protects You Without Punishing Reporters

Post-incident drug testing is a legitimate tool. When used correctly, it protects your workforce and gives you defensible grounds to take action when impairment genuinely contributed to an incident. When used as a blanket policy, it turns a safety tool into a liability.

The fix is not complicated. Revise the policy language. Train the supervisors. Document the cause. Make sure your employees know — through the policy and through your culture — that reporting a bee sting is not going to send them to a lab. The goal of the OSHA rule was never to stop drug testing. It was to stop employers from using the threat of drug testing to keep injury numbers artificially low.

A clean OSHA 300 log that was built by discouraging reporting is not something to be proud of. A clean log built on genuine hazard control is. Your drug testing program should support the latter.

---

Further Reading:

• OSHA 29 CFR 1904.35 — Employer Obligations to Inform Employees
• OSHA Enforcement Guidance on Retaliation and Drug Testing (October 2016)
• DOT Post-Accident Testing Requirements — 49 CFR Part 40