A refusal is one of the most misunderstood moments in a workplace testing program. Most employers think of a positive result as the hard case and a refusal as the simple one. In practice, a refusal is often messier to document, because it isn’t a lab finding. It’s a judgment call about behavior, made in real time, by whoever happens to be running the collection that day.
Getting that documentation right matters just as much as getting a positive result right. Under DOT rules, a verified refusal carries the same consequences as a verified positive. If the paperwork is thin, inconsistent, or written after the fact instead of in the moment, the whole determination becomes easy to challenge.
What actually counts as a refusal
A refusal isn’t limited to an employee flatly saying “no.” Under 49 CFR 40.191, a list of specific behaviors during the testing process all qualify as a refusal, including:
- Not showing up for a directed test within a reasonable time
- Leaving the collection site before the process is finished
- Not providing a specimen
- Refusing to permit an observed or monitored collection when one is required
- Providing an insufficient specimen with no medical explanation on record
- Declining a directed additional test
- Failing to cooperate with any part of the collection process, such as refusing to empty pockets, becoming confrontational in a way that disrupts the collection, or not following basic instructions during the procedure
- Admitting to the collector or the Medical Review Officer that the specimen was adulterated or substituted
An MRO-verified adulterated or substituted result is also treated as a refusal in its own right, separate from any behavioral refusal at the collection site.
This list matters because it reframes what employers are actually documenting. A refusal case usually isn’t about proving someone said no. It’s about establishing, with specific facts, which of these defined behaviors happened and when.
Why the documentation has to happen in the moment
The single biggest mistake in refusal cases is writing the account after the fact, once the situation has already escalated into a dispute. Memory fades fast, and a written statement produced days later, shaped by hindsight and whatever the employee has since claimed, carries much less weight than a contemporaneous record.
Good practice is simple and the same every time: the collector or the person overseeing the collection writes down what happened immediately, while it’s fresh, in plain factual language. Not “the employee was being difficult.” Instead: “the employee left the collection site at 10:42 a.m. after being told the specimen provided was insufficient, before providing an additional specimen, despite being informed that leaving would be treated as a refusal.”
That kind of specificity is what holds up. Vague characterizations of attitude or tone don’t establish much on their own. A clear timeline of observable conduct does.
What a complete refusal record should include
A defensible refusal file generally has a few consistent pieces:
A written, timestamped account from the collector or observer. This should describe exactly what was said and done, in the order it happened, without editorializing.
Confirmation that the employee was informed of the consequences. Part of what makes a refusal determination solid is showing the employee understood, at the time, that the behavior in question would be treated as a refusal. This doesn’t require a lecture. A short, direct statement from the collector, documented as having been made, is usually enough.
The Custody and Control Form or equivalent paperwork, noting the refusal and any remarks section completed by the collector.
Any medical documentation, if the claimed issue was an inability to provide a sufficient specimen. The shadow testing procedure and medical evaluation requirements exist precisely because “I couldn’t” and “I wouldn’t” need to be told apart, and that determination has its own documented process rather than being left to the collector’s impression.
A record of who made the final determination. Typically this is the Designated Employer Representative, often informed by the collector’s account and, where applicable, the MRO’s review. The determination should be traceable to a specific person and a specific date, not left ambiguous.
Reporting obligations don’t stop at the internal file
For DOT-covered employers, documenting the refusal internally is only half the job. Employers and MROs are required to report certain refusal violations to the FMCSA Drug and Alcohol Clearinghouse under 49 CFR 382.705. The categories that must be reported largely mirror the behaviors above: not appearing for a directed collection, leaving before it’s complete, not providing a specimen, refusing an observed or monitored collection, declining a directed additional test, not cooperating with the collection process, and admitting to adulteration or substitution.
This is a separate step from updating an internal personnel file, and it’s easy for a smaller program to treat it as an afterthought once the immediate situation is resolved. Building Clearinghouse reporting into the same checklist that triggers the internal documentation process, rather than treating it as a follow-up task someone remembers later, keeps programs from missing it.
Common mistakes that weaken a refusal determination
A few patterns show up repeatedly in refusal disputes:
Treating a difficult or confused employee as an automatic refusal. Confusion about instructions, nervousness, or a genuine medical issue with providing a specimen is not automatically the same as refusing. The distinction matters, and conflating them is how an otherwise solid program ends up on the losing end of a challenge.
Letting the written account wait. Even a day’s delay changes how a statement reads and how much weight it carries.
Inconsistent application across employees. If one employee’s hesitation is treated as a refusal and a similar situation with someone else isn’t, that inconsistency becomes the central issue in any dispute, not the underlying conduct.
No clear record of who decided, and when. A refusal determination without a named decision-maker and a date looks improvised, even when the underlying facts are solid.
Confusing DOT and non-DOT procedures. A refusal on a non-DOT test doesn’t carry DOT consequences and isn’t a Clearinghouse-reportable event in the same way. Employers running both DOT and non-DOT testing need separate, clearly understood procedures for each.
Collection method and the documentation burden
The way a specimen is collected shapes how much documentation burden sits on the collector in the first place. An observed urine collection, for instance, involves more procedural steps (clothing instructions, positioning, visual monitoring) and correspondingly more ways a disputed detail can arise. A straightforward oral fluid collection using a cotton swab drug test tends to involve fewer moving parts during the collection itself, which can mean fewer disputed-conduct scenarios to document in the first place, though the documentation standard for whatever does happen stays the same either way.
None of this changes the core principle: whatever the collection method, the record has to describe specific, observable conduct, made at the time it happened, by the person who was actually there.
The bottom line
A refusal determination is only as strong as the written record behind it. That record needs to describe specific behavior, be written at the time it happened, show that the employee understood the consequences, and be followed through with any required Clearinghouse reporting. Programs that build this into a consistent, repeatable process going into every collection, rather than improvising it only when something goes wrong, are the ones that hold up when a refusal gets questioned.
Sources
- U.S. Department of Transportation, Office of Drug and Alcohol Policy and Compliance: 49 CFR 40.191, What is a refusal to take a DOT drug test, and what are the consequences?
- FMCSA Drug and Alcohol Clearinghouse: Reporting Test Refusals
Written and reviewed by Sarah, MouthSwabDrugTests.com
