Imagine spending weeks away from home. You’ve slept in truck stops, sat at docks, put up with construction zones that never seem to end, and dealt with enough four-wheelers to question the state of humanity. Finally, you’re home. You’ve got groceries to buy, laundry piled up, and maybe a family that would actually like to see you without a steering wheel in front of your face.
Then the phone rings. It’s the company. You’ve been selected for a random drug test. They need you to head to a collection site.
Congratulations. Your home time has apparently become a branch office.
For some drivers, the demand is a minor inconvenience. For others, the collection site is a serious drive, the call comes at the worst possible moment, or the timing collides with another job or obligation. And for a driver who misunderstands the notification or refuses, the consequences can go well beyond losing an afternoon.
Now a truck driver is asking federal regulators to change the rules. Nathan Weidert filed a petition asking the Federal Motor Carrier Safety Administration to prohibit employers from notifying CDL holders about, or administering, random drug tests while they’re off duty. FMCSA lists the petition as received June 10, 2026. It remains pending.
That last sentence is important: there is no new federal ban on off-duty random drug testing. Not today. This is a request to change the rules, not a rule that has already taken effect.
What the petition is actually asking
Weidert’s request targets the timing of an employer’s random-testing notification and the administration of the test when a CDL holder is off duty. It does not call for eliminating random drug tests, excusing impaired driving, or allowing drivers to skip an otherwise valid testing program.
Those are very different ideas, even if they all get dumped into the same argument whenever somebody mentions drug testing.
Under federal rules, drivers in covered safety-sensitive positions are subject to unannounced random testing. Motor carriers have testing obligations, and randomness is part of the program’s purpose. The issue in dispute is whether those obligations should reach into a driver’s scheduled time off when it may be possible to conduct the test during working time instead. The debate over how testing works is broader than notification timing; I also covered hair follicle testing and drug-screening policy in trucking.
It sounds simple until you consider how truck schedules actually work. Not every driver clocks out at 5 p.m. on Friday and returns at 8 a.m. Monday. Some stay out for weeks. Some are seasonal. Some work irregular schedules, switch carriers, or have long gaps between assignments. Carriers also have random-selection periods to manage and cannot simply ignore selected drivers.
Still, drivers have a reasonable question: if the company can plan maintenance, dispatch, and paperwork, why can’t it plan the notification around the period when somebody is actually working?
Selection, notification, and collection are not the same event
There are three different moments in this process, and it’s worth separating them. First, a driver’s name is selected through a random-testing program. Second, the driver is notified. Third, the specimen is collected. A company’s obligation to operate a legitimate random program doesn’t automatically answer every question about the timing of the second step. FMCSA’s published guidance makes that clear by describing circumstances in which a carrier can hold the notification until the driver returns to work. That’s not a universal permission to postpone a test forever. It’s evidence that the agency already recognizes the distinction.
Imagine two drivers are selected on the same day. One is sitting at home for a scheduled three-day break before the next dispatch. The other is a seasonal employee who may not return for months. Those situations don’t create identical scheduling problems, and treating them as identical can create unnecessary conflict. The important question is whether a carrier has a documented process that accounts for the driver’s actual schedule while still meeting federal testing requirements. A good policy should prevent surprises, not manufacture them.
What FMCSA says right now
Here is where the answer gets uncomfortable for anybody hoping the current regulation already guarantees uninterrupted home time.
FMCSA’s published guidance under 49 CFR 382.305 explicitly says an employer may notify a driver of selection for a random controlled-substances test while the driver is off duty. The agency says that if the employer chooses to notify the driver during that time, it must make sure the driver proceeds immediately to a collection site. It also says employers should clearly explain that practice to drivers in advance.
The same guidance offers another option. An employer may hold the selected driver’s name and notify the driver when they return to work, provided the driver returns before the next random-testing selection is made. In other words, the agency acknowledges that some off-duty interruptions can be avoided without automatically abandoning the test.
FMCSA also says time spent traveling to and from the collection site and providing the specimen must be recorded as on-duty time for hours-of-service purposes. That detail matters, even though recording time on duty doesn’t magically give someone their family afternoon back. It’s another reason the bigger question of driver control over the clock matters; I raised related concerns in my look at FMCSA’s sleeper-berth flexibility experiment.
There is another distinction people often miss. Federal rules treat random alcohol tests differently. Random alcohol testing is limited to the period when a driver is performing safety-sensitive duties, just before those duties, or just after them. The fact that an off-duty random *drug* test can be permitted does not mean an off-duty random *alcohol* test is automatically valid.
We need to keep those two programs straight. Mixing them together creates bad advice, and CDL holders are the ones stuck dealing with the fallout.
On-duty time is not the same thing as getting your afternoon back
Here’s an easy detail to miss in a heated Facebook argument: FMCSA’s guidance says the travel and collection time associated with an off-duty random controlled-substances test must be recorded as on-duty time for hours-of-service compliance. That means it isn’t supposed to vanish from the driver’s record as though the trip never happened. But this guidance alone does not settle wage payment, expense reimbursement, or whether a particular employer’s handling of that trip was reasonable. Those questions can depend on the employment arrangement and other applicable law.
This matters especially for drivers who are paid by the mile. A run to a collection site can take an hour or much longer, yet there may be no freight moving and no obvious line item on the settlement sheet. The company sees a compliance appointment. The driver sees time, fuel, transportation arrangements, and plans suddenly rearranged. If a carrier expects a driver to respond immediately, it should already know how that instruction is logged, who is paying any applicable costs, and whom to call when a collection site is closed or unavailable. Finding those answers after a dispute starts is spectacularly bad timing.
The experience behind Weidert’s request
According to reporting by *Overdrive*, Weidert’s case did not begin with a driver who simply didn’t feel like going for a test. He was near the end of a seasonal work arrangement and had no more work scheduled with that employer. The employer selected him for a random test, and the ensuing dispute resulted in a refusal being reported to the federal Drug and Alcohol Clearinghouse.
That is not a small administrative inconvenience. A reported refusal can disrupt a driver’s ability to perform safety-sensitive work and trigger a formal return-to-duty process. When your CDL is how you earn a living, a database entry is not something you can casually shrug off.
There is also an important update. *Overdrive* reported that Weidert eventually obtained a correction to his Clearinghouse record after FMCSA examined the specific facts, including that he was actively working for another employer when the first employer directed him to test. The agency determined that, under those circumstances, he could not reasonably have complied.
That individual correction does not establish a general rule that home-time testing is illegal. It does, however, show how much can be at stake when a poorly timed instruction turns into an alleged refusal.
For a driver who has to spend months untangling a record, being told everything worked out eventually probably feels about as reassuring as a dispatcher saying the receiver will unload you ‘any minute now.’
A corrected record does not mean the system worked perfectly
It’s tempting to look at Weidert’s eventual record correction and say the process sorted itself out. It did resolve the particular case described in reporting, but that is not the same as saying the original disruption was harmless. A driver dealing with a contested refusal isn’t simply waiting for a paperwork typo to be fixed. They may be trying to explain an employment problem to a new carrier, gather messages from an old employer, or understand why their ability to work has been challenged.
The difference between a fair system and a technically fixable system matters. A fair system should make expectations unmistakable before a driver’s career is in jeopardy, especially when the employer knows the driver has already started another job or is far from the collection site. Corrections and appeals are important safeguards, but prevention is better. Nobody wants a six-month argument about a test notification to become the most memorable part of their home time.
Why carriers aren’t completely wrong to be concerned
This argument deserves more than pretending every carrier is sitting in an office devising ways to ruin a driver’s weekend.
Random drug testing is a federal compliance requirement. A carrier needs a defensible program, selection procedures, and records. The program cannot become so predictable that drivers know exactly when they’ll be tested. A driver who disappears for long stretches or is nearing the end of an assignment can complicate the calendar.
A company may also worry that waiting for someone to return from time off could push the test beyond the applicable selection period. Those are operational concerns worth discussing, not reasons to abandon driver protections.
But there is a difference between saying, ‘We must maintain a lawful random-testing program,’ and saying, ‘Therefore, your only two days at home belong to us whenever it’s convenient.’
FMCSA’s own guidance already recognizes waiting until a driver returns as an available approach in certain circumstances. That should be the starting point for a practical conversation. If a driver is coming back in a few days, could notification wait? If the schedule is uncertain, could the carrier document why it could not? If a testing-site trip truly must happen during off time, should there be a clear procedure for recording the time and communicating expectations?
Those are questions a rulemaking process could examine. They are also questions responsible carriers can think about now.
What a sensible carrier policy could look like
You don’t need a giant corporate legal department to understand why clear instructions help. A carrier could put its random-testing policy in writing, explain whether off-duty notification is possible, tell drivers what immediate reporting means, and identify a compliance contact who can answer questions after business hours. Dispatch, safety, and the testing administrator should be working from the same playbook. Otherwise the driver gets one answer from dispatch, a different answer from safety, and perhaps a third from somebody who last looked at the regulation in 2014.
There should also be a way to document a real obstacle without turning every obstacle into a refusal allegation. Maybe a driver is on an airplane, working a lawful shift for another employer, or two hours from the nearest open collection site. I’m not suggesting those facts automatically excuse a test; that is precisely why professional review matters. I’m saying a structured process is safer than a panicked phone call followed by an irreversible assumption. The federal program is serious enough to deserve more than improvised text messages.
Home time isn’t the same as sitting idle
A strange thing happens in trucking: the longer you’ve been away, the easier it becomes for outsiders to treat your time at home as an empty space on the schedule.
It’s not empty. That time is when drivers take care of the rest of their lives. They see children, spouses, parents, friends, and doctors. They buy groceries and fix the lawn mower and try to remember what it feels like to sit in a room that doesn’t vibrate.
When a driver is told to report for a test during a scheduled break, the company may be thinking about a collection-site appointment. The driver may be thinking about the six weeks it took to earn that afternoon.
The frustration isn’t necessarily about the test itself. Plenty of drivers support strict standards and would rather not share the road with anybody impaired. The frustration is that the company can choose the moment, the driver may have almost no discretion, and a misunderstanding can threaten the license they spent years protecting.
For independent contractors and owner-operators, the exact compliance arrangement can differ. Some use consortiums or testing pools. That doesn’t erase the broader point: compliance procedures need to account for the odd hours and long absences that define this work.
The hidden cost of taking someone off their own clock
Every carrier says driver retention matters. Usually that means talking about compensation, equipment, or home-time schedules. What often gets left out is how drivers are treated once they get home. A good paycheck loses some of its shine if a scheduled break always comes with the possibility of another surprise demand. Respect can be remarkably practical: accurate dates, clear expectations, notice when possible, and a safety department that knows the difference between a compliance question and a driver being difficult.
It’s also worth looking beyond the stereotypical over-the-road schedule. A local driver might be caring for a relative on a day off. A regional driver might be two states away visiting family. A husband-and-wife team might finally have a rare day when neither person is in the truck. None of these situations creates a personal exemption from the rules, but all of them make the stakes more obvious. If federal policy can allow a compliant way to avoid interrupting those hours, why would a company choose inconvenience as its default?
And yes, drivers have responsibilities here, too. Keep contact information current, understand the company’s written policy, and don’t ignore legitimate communications because you’re annoyed. The point is mutual clarity. Carriers shouldn’t have to guess whether someone will return, and drivers shouldn’t have to guess whether their break belongs to them. That’s a management issue long before it becomes a Washington issue.
A practical middle ground is worth debating
If FMCSA decides to take up Weidert’s petition, it will have to balance the safety purpose of random testing against the cost of treating off-duty drivers as permanently available employees.
My preference would be a serious examination of policies that preserve random selection while avoiding unnecessary interruptions in genuine off-duty periods. Selection and notification do not always have to be treated as the same moment, as existing FMCSA guidance demonstrates.
That doesn’t mean a carrier should be forced to miss every testing deadline or that a selected driver can decide to show up whenever they feel like it. It means the federal government should be willing to answer a basic question: why should a driver’s personal time be the default solution to an employer’s scheduling problem?
A reasonable system might distinguish a driver returning tomorrow from one who won’t work again for months. It might require clearer company policies, careful documentation of unavoidable exceptions, and meaningful protection against erroneous refusal reporting. Any of those ideas would need to be tested against existing rules before they could become law.
For now, drivers should be especially careful not to mistake the petition for a current exemption. If you’re notified, don’t assume you can simply ignore the instruction because you’re at home. Ask for clarification promptly, preserve the communication, and get qualified help if the situation becomes a dispute.
The point isn’t to turn every home-time call into a legal battle. It’s to prevent a driver from losing months of livelihood over a process that could have been handled more intelligently.
If you get that call: questions worth asking immediately
Let’s make this practical. If you’re notified of a random test during home time, first find out exactly what kind of test you’re being directed to take and where. Confirm the collection site’s location and hours, and ask who the testing contact is if there is a conflict or the location cannot accommodate you. If the instruction is by phone, ask for written confirmation; if it’s by text or email, keep a copy. The goal is not to manufacture an argument. It’s to make a clear, accurate record of what both sides understood.
If you genuinely cannot comply with the instruction as given, communicate that promptly rather than simply disappearing. Explain the concrete obstacle without assuming you have a legal exemption. A dispute about a random test can quickly involve technical rules, Clearinghouse reporting, and serious consequences, so get qualified advice rather than trusting a comment from somebody whose cousin once drove a box truck. None of these steps guarantees a particular outcome, but careful communication is a much stronger position than silence.
Finally, look at the bigger picture once the immediate situation is handled. Was the company’s policy available before the call? Did it explain what an off-duty selection could mean? Did the carrier record on-duty travel and collection time properly? Was the collection location actually open? Those are reasonable operational questions that help identify whether the problem was an unusual exception or a predictable mess waiting to happen to the next driver.
The bigger issue isn’t the collection cup
This petition puts a familiar trucking problem into one simple question: when does a driver stop belonging to the job?
The industry talks constantly about recruiting drivers, retaining drivers, and improving quality of life. Those discussions sound wonderful in a conference room. They mean considerably less if somebody’s first day home can be casually interrupted because the company didn’t want to wait until Monday.
The answer may not be an absolute ban on every off-duty notification. There are enough different schedules and employment situations in trucking that writing an inflexible rule could create new problems. But the current framework deserves scrutiny, particularly when one bad interaction can turn into a Clearinghouse nightmare.
Drug testing is a safety program. It should stay one. Respecting time off shouldn’t have to be treated as a threat to that goal.
The question I would put to drivers is simple: have you ever been called for a random test during home time, and if so, how did your carrier handle it? I suspect the answers would tell us plenty about which companies treat home time like a promise—and which ones treat it like a suggestion.

