Compliance
DOT Drug & Alcohol Testing Program: An Employer's Guide
By Editorial Team · Updated June 19, 2026 · 11 min read · Editorial standards
On this page 9 sections
The day you put your first CDL driver in a truck, you owe the federal government a working drug and alcohol testing program — not a binder, not an intention, but a running system with a random pool, a collection site, and a medical review officer behind it. Most new carriers learn this the hard way, during an audit or after a roadside that turns into a compliance review. This guide walks through what a compliant program actually requires under 49 CFR Parts 382 and 40, and how a small or new fleet stands one up without missing a piece.
What a compliant DOT testing program actually requires
A DOT drug and alcohol testing program is the documented system FMCSA-regulated employers must operate to test CDL drivers for prohibited substances, built on the six test types, a random pool, certified collections, and a medical review officer. It isn’t a single test or a vendor invoice — it’s a standing program you maintain for as long as you employ safety-sensitive drivers, governed by 49 CFR Part 382 for FMCSA-specific rules and 49 CFR Part 40 for the procedures every DOT mode follows.
At a minimum, a program has to include: a written policy you distribute to drivers, enrollment of every CDL driver in a random-testing pool, access to a collection site that follows Part 40, a lab certified by the Department of Health and Human Services (HHS), a qualified medical review officer (MRO) to verify results, and a process to query and report to the FMCSA Clearinghouse. Miss any of those and the program isn’t compliant, no matter how many tests you run. The DOT Office of Drug and Alcohol Policy and Compliance (ODAPC) publishes the governing guidance and the Part 40 procedures that tie it all together.
The six test types you have to run
Every DOT testing program must cover six distinct testing situations: pre-employment, random, post-accident, reasonable suspicion, return-to-duty, and follow-up. Each one is triggered by a different event, and skipping any category is a finding waiting to happen. Here’s the full set in one place.
| Test type | When it’s triggered | What’s tested |
|---|---|---|
| Pre-employment | Before a new driver performs any safety-sensitive function | Drugs (negative result required before dispatch) |
| Random | Unannounced, spread through the year by random selection | Drugs and alcohol |
| Post-accident | After a qualifying crash (fatality, or citation plus injury/tow-away) | Drugs and alcohol, within the rule’s time windows |
| Reasonable suspicion | When a trained supervisor observes signs of use | Drugs and alcohol |
| Return-to-duty (RTD) | Before a driver returns after a violation; directly observed | Drugs and alcohol, negative required |
| Follow-up | Unannounced plan set by the SAP after RTD | Drugs and alcohol |
A few of these trip up new carriers. Post-accident has strict timing — alcohol testing should happen within 8 hours and drug testing within 32 hours, and you must document why a test wasn’t done if you couldn’t get one. Reasonable suspicion requires that the supervisor making the call has completed the mandated training (at least 60 minutes on drugs and 60 on alcohol). And return-to-duty and follow-up tests are managed by a substance abuse professional, not by you alone — for how that path works, see our guide to the DOT substance abuse professional.
Random testing rates and managing the random pool
FMCSA sets the minimum annual random testing rates, and for the current year they are 50% of the average number of driver positions for controlled substances and 10% for alcohol. These rates aren’t fixed forever — FMCSA can raise or lower them based on industry-wide positive rates and publishes the figure in the Federal Register each year — so you confirm the current rate rather than assuming. What stays constant is the obligation to test that share of your average driver count across the calendar year.
Running the random program correctly means more than hitting the percentage. The selections have to be genuinely random — drawn by a scientifically valid method (usually a computer-based generator), with every driver in the pool having an equal chance each time. You can’t steer selections, skip a name, or save them all for December. Key rules to manage:
- Spread selections reasonably across the year. FMCSA expects testing in each quarter, not bunched at year-end.
- Every CDL driver stays in the pool, including new hires (added on enrollment) and owner-operators who drive.
- A selected driver must report immediately to the collection site once notified — random means unannounced.
- Keep the records that prove your selection method and completion rate; this is exactly what an auditor asks for.
This is the single hardest piece to run alone, which is why most small fleets don’t.
Joining a consortium/third-party administrator (C/TPA)
A consortium/third-party administrator (C/TPA) is a service agent that manages all or part of your DOT testing program — most commonly the random pool — on your behalf, and joining one is how nearly every small carrier meets the random-testing requirement. A one- or five-truck operation can’t generate a statistically valid random pool from its own handful of drivers, so the C/TPA combines drivers from many small employers into one large pool and pulls random selections from it.
A typical C/TPA in trucking handles the heavy lifting: maintaining the random pool and running selections, scheduling and coordinating collections, arranging the HHS-certified lab and the MRO, helping with Clearinghouse reporting, and keeping the records. For an owner-operator who employs himself or herself as a driver, designating a C/TPA isn’t just convenient — it’s effectively required, because you can’t randomly select or report on yourself.
What a C/TPA does not do is absorb your liability. 49 CFR Part 382 keeps ultimate responsibility for compliance on the employer. If the C/TPA misses a quarter or botches a report, FMCSA penalizes you. So when you shop for a DOT drug testing consortium, vet it the way you’d vet any compliance vendor: confirm it follows Part 40, ask how it documents random selections, and get clarity on who reports what to the Clearinghouse.

Collection sites, the lab, and the MRO
A Part 40-compliant program runs specimens through a certified collection site, an HHS-certified laboratory, and a medical review officer who verifies every result before it counts. These three links form the chain of custody, and each one is governed by specific procedures in 49 CFR Part 40 so a result holds up.
Here’s how the pieces fit:
- Collection site. A facility with a trained collector who follows the federal custody-and-control form process, handles split specimens, and observes the directly-observed collections the rules require (such as return-to-duty and follow-up tests). Your C/TPA usually has a network of these so a driver can get tested near wherever they are.
- HHS-certified laboratory. Only labs certified under the HHS National Laboratory Certification Program may analyze DOT specimens. They test for the standard DOT panel and report results to the MRO — never directly to you.
- Medical review officer (MRO). A licensed physician trained in substance-abuse testing who reviews every non-negative lab result, contacts the driver, and decides whether there’s a legitimate medical explanation. The MRO is the gatekeeper between a lab positive and a verified violation. A positive you act on is a positive the MRO has confirmed — and the MRO, not the employer, reports verified positives to the Clearinghouse.
You don’t analyze specimens or judge results yourself. Your job is to make sure the program has each of these qualified parties and that they’re talking to each other correctly.
How the program ties into the FMCSA Clearinghouse
Your testing program feeds directly into the FMCSA Drug & Alcohol Clearinghouse: violations and return-to-duty results are reported into it, and you query it before hiring and once a year for every current driver. The testing program and the Clearinghouse aren’t separate compliance tasks — they’re two ends of the same system. Tests generate the data; the Clearinghouse stores and surfaces it.
The reporting splits across parties: the MRO reports verified positive, adulterated, or substituted results; you report alcohol tests of 0.04 or higher, refusals, actual-knowledge violations, and negative return-to-duty results; and the SAP reports return-to-duty process steps. On the query side, you run a pre-employment full query before a new driver works and an annual query on every current driver. We cover that database in depth in the Drug & Alcohol Clearinghouse employer guide, and the click-by-click mechanics in how to run an FMCSA Clearinghouse query.
The practical takeaway: a clean pre-employment query plus a negative pre-employment test is what clears a driver to start. If a query comes back showing an unresolved violation, that driver is in prohibited status and can’t drive until they finish the return-to-duty process — for the driver’s side of that, see what happens if you fail a DOT drug test.
What the testing program never sees
A DOT testing program is built to catch one thing — prohibited drug and alcohol use — and it’s silent on everything else about whether a driver is a good hire. That’s not a flaw; it’s the program’s scope. But it leaves a gap that costs carriers real money, and it’s worth being honest about where the gap sits.
A driver can pass every pre-employment test, sail through a year of random selections, and carry a spotless Clearinghouse record while still being the hire who no-shows after orientation, ghosts dispatch on a hot load, or walks off and abandons a truck at a truck stop. None of that is a testing violation, so none of it touches your program or the federal record. The driver’s last three dispatchers know exactly how they performed; your testing file never will.
That reliability layer is what a peer-sourced driver-review database like cdlscan.com is built to add. Once your required testing and Clearinghouse checks are clear, you can search a driver by name and read what previous carriers actually reported — the no-shows, the abandoned loads, the rehire-worthiness signals a compliance file can’t carry. CDLScan holds more than 1,000,000 driver reviews, runs around 20,000 searches a week, and the search is free — cheap insurance against a bad truck-driver hire that typically costs an employer somewhere between $8,000 and $50,000.
Frequently asked questions
What does a DOT drug and alcohol testing program require? A compliant program needs a written policy, every CDL driver enrolled in a random-testing pool, the six required test types (pre-employment, random, post-accident, reasonable suspicion, return-to-duty, follow-up), a Part 40-compliant collection site, an HHS-certified lab, a medical review officer, and Clearinghouse querying and reporting. It runs under 49 CFR Parts 382 and 40.
What are the DOT random drug testing rates? FMCSA sets minimum annual random rates and publishes them each year. They are currently 50% of the average number of driver positions for controlled substances and 10% for alcohol. Always confirm the current figure with FMCSA, since the rates can change based on industry positive rates.
Do I have to join a consortium (C/TPA)? You’re not required by name to join one, but a small fleet realistically can’t maintain a valid random pool alone, so nearly all do. An owner-operator who drives effectively must designate a C/TPA, because you can’t randomly select or report on yourself. The C/TPA runs the program; you keep the legal responsibility.
What is a C/TPA in trucking? A consortium/third-party administrator is a service agent that manages all or part of your DOT testing program — typically the random pool, collection scheduling, lab and MRO coordination, and Clearinghouse reporting support. It combines drivers from many small employers into one large random pool. Under Part 382, the employer still retains ultimate compliance responsibility.
What is a medical review officer (MRO)? An MRO is a licensed physician trained in substance-abuse testing who reviews every non-negative lab result, interviews the driver about possible legitimate medical explanations, and decides whether the result is a verified violation. Labs report to the MRO, not to you, and the MRO reports verified positives to the Clearinghouse.
How is the testing program connected to the Clearinghouse? The program generates the data the Clearinghouse stores. Verified positives, alcohol violations, refusals, and return-to-duty results are reported into it, and you query it before hiring and annually for current drivers. A clean query plus a negative pre-employment test is what clears a new driver to start.
Which tests are directly observed? Return-to-duty and follow-up tests are always directly observed under Part 40, meaning a collector watches the specimen being provided. Certain other situations can also require observed collections. Routine pre-employment and random drug tests are not directly observed unless a specific trigger applies.
Does a clean testing program mean a driver is a safe hire? No. The program only confirms a driver hasn’t a reportable drug or alcohol violation. It says nothing about reliability — no-shows, abandoned trucks, or rehire eligibility — which is why employers pair the required testing with a peer-review check at cdlscan.com before they put someone in a truck.