Discharge Series, Part 5: Drugs/Alcohol Use - Failed a Drug Test? Here's What It Actually Means for Your Unemployment Claim

A Positive Test Doesn't Always Mean You're Disqualified

Early in my career, I watched a colleague make a determination that stuck with me. A claimant had tested positive for illegal drugs and was let go as a result, and my colleague disqualified him for misconduct on that basis alone. There was one problem: the employer had no drug policy. No rule against drug use, nothing the claimant had ever agreed to or been warned about. The claimant's job also wasn't a safety-sensitive one, more like a cashier than a truck driver. The case worked its way all the way up to that state's supreme court, which reversed the decision, found the claimant eligible for benefits, and specifically noted that a safety-sensitive role might well have changed the outcome. A positive test for illegal drugs, with no employer policy addressing drug use and no safety risk tied to the job, wasn't misconduct.

That case reflects one state's law at one point in time. Drug and alcohol rules vary considerably from state to state: some states apply the ordinary misconduct standard, others have written specific testing statutes directly into their unemployment law. So take the principle, not the outcome, as the national lesson: a positive test, on its own, doesn't automatically end your claim.

I bring that up because it captures something people don't expect: getting fired over a drug or alcohol test doesn't automatically end your unemployment claim. Just like every other topic in this series, the employer still has to prove you committed misconduct, meaning they have to show you knowingly broke a real workplace rule or showed genuine disregard for your job duties. A positive test, a refusal, or an accusation of being impaired at work is the start of that argument, not the end of it.

What Actually Happened?

"Fired for drugs or alcohol" covers four different situations, and which one applies to you changes how a state will look at your claim.

• Positive test: random, "reasonable suspicion" (your employer had a specific reason to think you were impaired that day), or post-incident (given after an accident or workplace incident)

• Test refusal: you declined a test your employer asked you to take

• Alleged on-the-job impairment: accused of being impaired or under the influence while working, based on observation rather than (or in addition to) a test

• Off-duty conduct: your employer found out about something you did off duty, on your own time

Figure out which one fits before you read further. The rules genuinely differ by scenario.

Why the Employer Still Has to Prove It

Standing rule of this series: the burden of proof is on the employer, not you. That doesn't change here, but this topic has more state-by-state statutory variation than most others in the series, so it's worth being precise about where the general rule ends and state-specific exceptions begin.

A positive test alone is rarely enough. Depending on the state, the employer may need to show the testing followed the applicable law and the employer's own policy: a certified lab, confirmation of an initial positive screen (a fast on-site "instant cup" screen is not the same thing as a confirmed lab result), and a documented chain of custody, the paper trail showing exactly who handled your sample, when, and how, so nothing got mixed up along the way. In certified workplace testing programs, a lab positive is also typically reviewed by a Medical Review Officer (MRO), a licensed physician, before it's reported to the employer, specifically to catch legitimate explanations like an active prescription. If the employer skipped that review, or is relying on an unconfirmed screening result, that can seriously weaken their case.

One more distinction that matters throughout this topic: testing positive for a drug and being impaired at work aren't necessarily the same thing. Some substances, marijuana in particular, can remain detectable for days or weeks after any impairment has worn off. If your employer says you were fired for being "under the influence," the state may look for actual observations of impairment, not just a lab result. If you were fired simply for violating a zero-tolerance testing policy, though, actual impairment may not matter; the policy violation itself can be enough.

If there was no test at all (you were accused of being impaired at work based purely on how you looked or acted), the employer's case usually rests on specific, documented observations: things like slurred speech, odor, unsteady behavior, or erratic performance, ideally noted by more than one person at the time it happened, not reconstructed afterward. A vague "seemed off" from a single supervisor, without any contemporaneous documentation, is often the weakest version of this argument. That doesn't mean it can't succeed; it means the specifics of what was actually observed and recorded matter more here than in almost any other scenario in this article.

Refusing a test is usually treated like failing one, but the circumstances still matter: was the test authorized by a written policy or a state/federal testing requirement, did that policy apply to you, and if "reasonable suspicion" was required, did the employer actually have it? Some states have found that a refusal isn't disqualifying when the suspicion behind the request doesn't hold up. Trying to substitute, dilute, or tamper with a sample can also be treated as a refusal under some state laws or employer policies.

If your employer's own handbook promises a warning, an Employee Assistance Program referral, or a last-chance agreement before termination on a first positive test, and they skip straight to firing you instead, that's the employer not following its own rules, and that can undercut a misconduct finding. On the flip side, if you'd previously signed a last-chance agreement making continued employment conditional on staying clean, a later positive test is much more likely to be treated as misconduct: the agreement itself can supply the "knowing violation" the employer needs.

Off-duty conduct raises a different question: what connection did it have to your job? If it happened entirely off the clock and didn't affect your work, the employer may have a harder time showing misconduct connected to your employment. But a clearly communicated drug-free policy, a safety-sensitive position, licensing requirements, or other job-specific obligations can create that connection even when the actual use happened away from work.

Being upfront can still work in your favor. Say you've had a couple of drinks after your shift, then get an emergency call to come back in, and you tell your employer that before you show up. If they require you to come in anyway and then discharge you over it, several states have found that cuts against a misconduct finding: willfulness is central to the standard, and an employer that knowingly walked into the situation after being told has a harder time proving it. That said, it's not a blanket safe harbor: an employer can still have a lawful rule requiring you to be fit for duty.

Prescription medication taken as prescribed isn't misconduct just because it shows up on a screen. If there's a real issue, it's more likely to be observable impairment on the job, or failing to comply with a legally permissible safety-sensitive fitness-for-duty policy, not the mere existence of a valid prescription. (This is part of why the MRO review mentioned above exists: to catch exactly this situation before a positive result ever gets reported to your employer.)

Medical marijuana is genuinely messy right now, and it's worth being upfront about that instead of promising an outcome. There are really three separate questions buried in it: whether your state's law permits the use, whether employment law protects it, and whether your state's unemployment law treats the discharge as misconduct, and those don't always line up the same way. States are all over the map: some have found that off-duty, legal medical use isn't misconduct even under a zero-tolerance policy; others have sided with the employer regardless of what state marijuana law allows; a few states have written medical marijuana protections directly into their unemployment statutes. And recreational marijuana being legal in your state doesn't mean your employer has to permit it, or that violating a workplace testing policy can't affect your unemployment eligibility: legalization and employment law are two different questions. If this is your situation, don't assume either outcome. Pull together your registry card or medical documentation and let the state make the call.

Safety-sensitive and DOT-regulated jobs (commercial driving and other roles regulated by the Department of Transportation) add federal testing rules on top of state law. A verified DOT positive or refusal can require your immediate removal from safety-sensitive duties, and federal rules generally treat a refusal the same as a positive result for that purpose. But that federal consequence isn't the same thing as an automatic unemployment disqualification: DOT rules don't themselves decide your UI claim, and your employer isn't federally required to fire you over it. The state still applies its own unemployment law to the discharge, though the employer's case is considerably stronger when a federally regulated safety requirement is involved.

What the Adjudicator Is Really Trying to Determine

Strip away the details, and most of these cases come down to the same handful of questions: What exactly were you discharged for: a positive test, a refusal, impairment, or off-duty conduct? What did the employer's policy actually prohibit, and did you know about it? Did the testing comply with that policy and applicable law? Is the result reliable? And is there a real connection between what happened and your ability to do the job?

What to Do Right Now

• Write down the exact reason your employer gave for the discharge: "failed drug test," "reported to work impaired," "refused testing," and "violated the drug-free workplace policy" aren't necessarily the same issue, and the distinction matters

• Get the specifics on your test: which lab, whether it was an instant screen or a confirmed lab result, whether an MRO reviewed it, and whether you can request the chain-of-custody paperwork

• Find your employer's actual written policy. Did you see it, sign it, or acknowledge it before this happened?

• If this was a refusal, pin down exactly what you were asked to do and under what circumstances

• If prescription medication is involved, gather proof of a valid prescription taken as directed

• Keep a written timeline of events (when you were tested, what you were told, any conversations with HR or supervisors) and note any witnesses

• File your claim no matter what reason your employer gives. Let the state make the determination; don't disqualify yourself before anyone official does

Bottom Line

"Fired for drugs or alcohol" is not one single outcome. In most cases, the employer still has to prove what happened, follow their own rules, and connect it to your ability to do the job, but a handful of states have written specific drug- and alcohol-testing statutes that change that analysis for certain positive tests or refusals. Don't assume you're out of luck, and don't assume you're in the clear, before you've actually seen a determination.

✍️ How this is made: I use AI to help draft these articles from my own outline and 30+ years of UI expertise. Every fact, correction, and final edit is mine.

John Partlow has spent 30+ years working in unemployment insurance: 20 years inside Tennessee's state UI agency and 10+ years helping states modernize their systems. He built Unemployment Unlocked to translate that experience into plain-English guidance for claimants navigating the system. Read more about John →