A driver who does not report for a required random test can create more exposure than a positive result if the record is incomplete. Document test refusals as a defined DOT event, not as a vague note that says “no show” or “declined.” When an auditor asks what happened, your file must show the test requirement, the driver’s actions, the employer’s response, and the time sequence without guesswork.
For DOT-regulated employers, a refusal can trigger immediate removal from safety-sensitive functions and a return-to-duty process. That outcome is serious. The documentation behind it needs to be equally disciplined.
What Counts as a DOT Test Refusal?
A refusal is not limited to a driver saying, “I will not test.” Under DOT rules, certain conduct during the testing process may also be treated as a refusal. The exact definition differs between drug and alcohol testing, and the collection site, medical review officer, breath alcohol technician, or employer may each have a role in identifying or reporting the event.
Common examples include failing to appear at the collection site within the required time after notification, leaving before the testing process is complete, failing to provide a sufficient specimen without an adequate medical explanation, or declining a directly observed collection when one is required. A verified adulterated or substituted drug-test specimen is also treated as a refusal.
For alcohol testing, a refusal may include failing to sign required certification, failing to provide enough breath, leaving before the process is complete, or failing to remain available after an alcohol test requires confirmation. A driver who refuses to cooperate with any part of the process may create a refusal issue, but do not label conduct a refusal casually.
The operational rule is simple: record the facts first. Apply the DOT classification only after the appropriate party has made or supported that determination under your process.
Why “No Show” Is Not Enough
“No show” is an internal shorthand, not an audit-ready record. It does not establish when the driver was notified, what instructions were given, whether the driver was reachable, whether a legitimate delay occurred, or whether the test was actually required under the applicable DOT testing program.
A clean record should answer practical questions quickly. Which random selection produced the test requirement? Was the driver in the eligible pool snapshot? When was the selection run? Who notified the driver? When was the collection appointment scheduled? What did the driver say or do? Who made the final refusal determination? When was the driver removed from safety-sensitive work?
That sequence matters because a refusal is not merely a payroll or attendance problem. It is a DOT testing record with direct consequences for dispatch, driver qualification, and future return-to-duty administration.
Build the Record From the Random Pull Forward
The strongest documentation starts before the driver is notified. Preserve the selection record that created the testing obligation. For a random test, retain the locked eligible-driver pool, the date and time of the selection, the documented random-number method, the selected-driver result, and the applicable testing rate or program context.
If the roster changes later, do not overwrite the historical selection pool. An auditor should be able to see who was eligible when the pull occurred, not just who is on the roster now. This is where spreadsheet workflows often fail: a live list is edited, a driver disappears or changes status, and the employer cannot recreate the original selection event.
Next, document notification. Record the date, time, method, and person making the notification. Include the instructions given to the driver, such as where to report, the required reporting window, and whether the driver was instructed to stop performing safety-sensitive functions pending the test.
Use facts, not conclusions. “Driver notified by phone at 9:12 a.m. to report to ABC Collection Site by 10:12 a.m.; driver stated, ‘I’m not going,’” is usable. “Driver refused test” without supporting detail is not.
Keep a Clear Event Timeline
A refusal file should read like a timeline, not a collection of disconnected emails. Capture each status change as it happens: selected, notified, scheduled, arrived, collection issue reported, refusal pending review, refusal determined, and removed from safety-sensitive duties.
Timestamped status histories are especially useful when different people handle selection, dispatch, collection-site communication, and driver management. They establish who knew what and when. They also reduce the temptation to reconstruct events days later from memory.
A platform such as DTSMS Online can preserve the selection snapshot, notification status, and result history in one workflow. The point is not software for its own sake. The point is having one defensible record rather than a text message, a paper custody form, and three separate spreadsheet notes.
Separate Facts From the Determination
Do not ask a dispatcher to make a medical or regulatory conclusion from a phone call. Dispatch can document that the driver did not report. A collection site can document that the driver left, failed to provide a specimen, or declined a required step. A medical review officer may determine whether a shy bladder or shy lung situation has an adequate medical basis. Your designated employer representative must then act on the reported determination.
This distinction protects both the company and the driver. A driver delayed by a crash, a clinic closure, or an instruction error may not have refused a test. On the other hand, an employer should not let an unsupported explanation erase a documented failure to comply.
Record the source of each fact. If the collector reports that the driver left before completing the collection, retain the collector’s statement or written report. If the driver provides an explanation, preserve it exactly and note when it was received. If the MRO or other authorized party provides a determination, record the date, the source, and the action taken.
What Your Refusal Documentation Should Include
A complete file generally needs more than one form. Keep the supporting records together, whether in a secure electronic system or a controlled compliance file. At minimum, preserve these distinct elements:
- The random-selection record and eligible-pool snapshot that established the testing requirement.
- Notification details, including the method, exact time, instructions, and the person who notified the driver.
- Collection-site, BAT, collector, or MRO documentation describing the event and any required determination.
- The driver’s explanation, statement, or lack of response, recorded without editorial comments.
- The employer’s final action, including removal from safety-sensitive duties, the decision date, and the person authorizing it.
- Follow-up records for SAP referral, return-to-duty testing, and follow-up testing when applicable.
Keep the original language where possible. Do not rewrite a collector’s report into a softer version for an internal note. Do not delete an early entry because later information changes the outcome. Add the later information as a new, dated record. Write-once histories hold up better than cleaned-up narratives.
Act Promptly After a Refusal Is Determined
Once a DOT refusal is determined, the employee cannot continue performing DOT safety-sensitive functions. For a CDL driver, that means no driving and no other covered safety-sensitive work until the required evaluation and return-to-duty steps are completed.
Your documentation should show the removal action clearly. Note when dispatch access was restricted, when the supervisor was informed, and whether the driver was taken off the schedule. If the driver is an owner-operator or works remotely, document how the company communicated the restriction and how it controlled future assignments.
Employment consequences are a separate business decision, subject to company policy, contracts, and applicable employment law. DOT rules require removal from safety-sensitive duties and the return-to-duty process. They do not require every employer to make the same termination decision. Keep your policy consistent, and do not confuse a personnel decision with the DOT compliance action.
Avoid the Documentation Failures Auditors Notice
The most common failures are simple: selecting from an unverified pool, having no proof of notification, overwriting roster data, recording a result without a source document, or leaving the driver marked “active” after a refusal determination. Each gap creates a question that your company should not have to answer from memory.
Another avoidable failure is backdating. If a decision is made two days after the event, record the decision two days after the event. The historical timeline can show the incident date and the determination date separately. Accurate timing is more defensible than a record that looks artificially neat.
Review your workflow before the next random pull. Confirm who notifies drivers, who receives collection-site reports, who can change a test status, and who confirms removal from duty. If those responsibilities are unclear, the documentation will be unclear when a refusal occurs.
A refusal record should not depend on a compliance manager remembering a difficult morning six months later. Build the evidence as the event unfolds, preserve the selection trail, and let the timestamps speak for your process when DOT asks.
