Central Cargo Express

Hiring a Driver With a Past Drug or Alcohol Violation: Return-to-Duty and Follow-Up

By Tom Whitaker · 2026-11-19 · 11 min read

The application looks good. Eight years of tractor-trailer experience, a clean MVR, references who pick up the phone. Then the pre-employment Clearinghouse query comes back, and there is a violation on it: a positive drug test from two years ago at another carrier. Some recruiters stop reading at that point and move to the next file. Others want to keep going but have no idea what the rules ask of them.

Both reactions are understandable. The federal rules do not tell you to reject the driver, and they do not tell you to hire the driver. What they do is lay out, in fairly exact terms, what has to be true before that person drives for you and what you owe the program afterward. Most of it lives in 49 CFR Part 40, Subpart O, which Part 382 adopts for truck and bus drivers through §382.309 (return-to-duty testing) and §382.311 (follow-up testing).

This guide is for the person at a small or mid-sized carrier who will actually make the call and then carry the paperwork: the safety manager, the owner, the recruiter who also handles compliance on Fridays.

First, read the query result correctly

A full pre-employment query, run with the applicant's electronic consent, tells you more than "violation: yes or no." The useful question is where the driver stands in the return-to-duty process. There are four practical positions, and each one leads to a different next step.

What the query and SAP records showCan the driver work for you?What you do next
Violation reported, no SAP assessment or treatment completedNo safety-sensitive work at allDecide whether to wait; you cannot shortcut the SAP process
SAP has reported the driver eligible for a return-to-duty testNot yet; a negative RTD test comes firstGet the SAP report, send the driver for the RTD test, report the result
RTD test passed, follow-up testing still in progressYes, once the CDL privilege is reinstatedGet the follow-up plan from the SAP and continue it
RTD and all follow-up tests completedYesNormal hiring; record shows the history until it ages out

The first row is the one that trips people. A driver in prohibited status cannot perform any safety-sensitive function, and §382.503 puts the same restriction on you as the employer: you may not permit it. A driver's promise that the paperwork is "almost done" changes nothing. Until the substance abuse professional (SAP) has evaluated the driver, prescribed education or treatment, and later reported that the driver complied, the process has not moved.

Since FMCSA's second Clearinghouse rule took effect in November 2024, there is an extra layer. When a driver is in prohibited status, the state licensing agency removes the CDL or CLP privilege from the license. Under §382.503(b) that driver cannot operate a commercial motor vehicle until the state reinstates the privilege, which happens after the negative return-to-duty result is reported. So even the third row has a practical check built in: confirm the license shows the CDL privilege again before the first dispatch.

You are allowed to say no

It helps to clear this up early, because recruiters sometimes assume a driver who finished the process has a right to be hired. §40.305(b) says the opposite in plain terms: an employer is not required to return an employee to safety-sensitive duty just because the conditions were met. It is a personnel decision.

That means your company can set its own hiring standard for applicants with a past violation. Some carriers will consider a driver who completed the program and has been testing clean for a year. Some will not consider anyone with an open follow-up plan. Some decide case by case. Any of these can be reasonable. What matters is that the standard is written down, applied the same way to every applicant, and checked against your insurer's underwriting rules before anyone makes an offer. Ask the insurer directly rather than guessing; underwriting guidelines on drug and alcohol history vary and are often stricter than the federal minimum.

Hiring a driver who still needs the return-to-duty test

If you decide to bring on a driver in the second position, your company becomes the employer that closes out the return-to-duty step. The order of operations matters.

  1. Get the SAP's report. The SAP sends the follow-up testing plan directly to the employer's designated employer representative (DER), as §40.307(b) requires. Ask the driver to sign whatever release the SAP needs, then contact the SAP yourself. The plan is not uploaded to the Clearinghouse, so this call is the only way you will see it.
  2. Wait for the SAP's determination. Under §40.305(a), the return-to-duty test cannot happen until the SAP has determined the driver successfully complied with the prescribed education or treatment.
  3. Send the driver for the RTD test. It is drugs, alcohol or both, as the SAP specified. A return-to-duty drug test must be collected under direct observation; §40.67(b) makes that a requirement for the employer, not an option. Tell the collection site the reason for the test so the custody and control form is marked correctly.
  4. Read the result against the standard. The driver needs a verified negative drug result and/or an alcohol concentration below 0.02.
  5. Report the negative result. §382.705(b)(1)(ii) requires the employer to report a negative return-to-duty test to the Clearinghouse by the close of the third business day after you get the result.
  6. Confirm the license. Check that the state has restored the CDL privilege before the driver touches a truck.

What about the pre-employment test? Every new hire still needs one under §382.301. FMCSA's published guidance says a single DOT drug test can satisfy both the pre-employment and the return-to-duty requirement, as long as the test meets the return-to-duty conditions, including direct observation. If you combine them, make sure both purposes are documented so an auditor does not see a new hire with no pre-employment result on file.

Hiring a driver in the middle of follow-up testing

This is the more common case. The driver passed the RTD test at a previous carrier, did a few follow-up tests there, then left. The follow-up plan does not end when the job does. §40.307(e) says the plan "follows" the employee to later employers and through breaks in service, and the regulation's own example is almost exactly this situation: two of six tests done at Employer A, and Employer B is responsible for making sure the remaining four happen.

Your steps:

  • Find out where the plan stands. Contact the SAP for the plan itself. Then, with the driver's written consent, ask the previous employer which follow-up tests were completed and when. The query tells you the driver is in follow-up; it does not tell you how many tests remain.
  • Resume testing right away. There is no grace period for a new hire to settle in. The first follow-up test can be as early as the first week.
  • Keep the schedule to yourself. §40.307(g) prohibits the employer, the SAP and any service agent from giving the driver a copy of the schedule or telling the driver how often or how long testing will go on. The tests have to be unannounced to work.
  • Do not add tests. §40.307(d)(4) bars the employer from imposing extra testing under company authority beyond the SAP's plan. If you think the driver needs more testing, that is a conversation with the SAP, who can modify the plan.

How the 12-month minimum actually counts

The SAP must order at least six unannounced follow-up tests in the first 12 months of safety-sensitive duty after the driver returns. The SAP can order more, and can extend testing for up to another 48 months, so a plan can run as long as five years in total.

The phrase that matters for scheduling is "safety-sensitive duty." Calendar months while the driver is off work, between jobs or laid off do not count. The regulation's second example covers a seasonal layoff: two tests done, three months worked, a four-month layoff, and the employer must still get the remaining four tests done in the next nine months of duty.

Here is how a carrier might lay out the remainder of a plan for a new hire. The dates and counts are an example, not a template:

ItemExample
SAP plan6 drug tests and 2 alcohol tests in the first 12 months of duty; 4 drug tests in each of months 13–24
Done at previous carrier3 drug tests, 1 alcohol test, over 4 months of duty
Left for your carrier3 drug tests and 1 alcohol test within the next 8 months of duty, then the year-two tests
Your schedulingSpread unevenly across the window; avoid a pattern like "first Monday of every other month"

Follow-up tests do not replace random testing. The driver also goes into your random pool like every other covered driver. If a random selection and a scheduled follow-up test land close together, ask your consortium or C/TPA how they record each one so the file shows clearly which test served which purpose.

Closing out the plan

When the driver finishes every follow-up test the SAP prescribed, the current employer has one more reporting duty: §382.705(b)(1)(v) requires a report to the Clearinghouse that the driver successfully completed all follow-up tests. If the driver completes the plan while working for you, that report is yours to file, again within three business days.

Do not assume the record vanishes after that. Under §382.719, a violation stops showing up on employer queries only when the SAP information, the negative RTD result and the follow-up completion are all reported and five years have passed since the violation determination. A driver who finished everything in eighteen months will still show the violation on queries until the five-year mark. That is useful to know when the driver later asks why another carrier hesitated.

Records you will keep longer than usual

A driver with a violation history creates documents that fall in the longest retention bucket of §382.401: five years for driver evaluation and referral records, records of violations and positive results, and other program records. Negative test results generally go in the one-year group, but for this driver the SAP report and follow-up plan should sit with the five-year material.

A short checklist for the file:

  • the signed consent and the full pre-employment query result;
  • the SAP report and follow-up plan (kept in the drug and alcohol file, not the general personnel file, and with restricted access);
  • the previous employer's record of completed follow-up tests;
  • each RTD and follow-up result, with the reason for test marked;
  • Clearinghouse confirmation for every report you filed;
  • your written hiring standard and the note showing how this applicant was evaluated against it.

Where carriers go wrong

From the audits and conversations we see, the same few mistakes repeat:

Letting the driver "ride along" while waiting. A driver in prohibited status cannot perform safety-sensitive functions. That category covers more than driving, including inspecting equipment, loading or unloading and waiting to be dispatched while on duty. A training ride as a second driver is safety-sensitive work.

Telling the driver the schedule. It usually happens innocently, when a dispatcher says "you've got a test coming up next week, so don't take that long run." That defeats the unannounced requirement and violates §40.307(g).

Losing the plan when the safety manager leaves. The follow-up plan lives with the DER. If one person keeps it in an inbox and then leaves the company, the next person has no idea a follow-up test is overdue. Put the plan in the drug and alcohol file and set the testing reminders in a shared calendar or your C/TPA's system.

Treating the employer's own tests as the plan. Adding monthly company-authority tests feels cautious, but the regulation forbids testing beyond the SAP's plan, and non-DOT tests run on DOT forms create their own problems.

Skipping the license check. A negative RTD result does not reinstate the CDL by itself; the state has to act on the reported status. Look before the first dispatch.

For the regulatory text, the full return-to-duty process is in 49 CFR Part 40, Subpart O on eCFR, and FMCSA explains query types and reporting duties on the Drug and Alcohol Clearinghouse site.

Frequently asked questions

Can we hire a driver whose query shows prohibited status if the driver starts the SAP process right away?

You can make a conditional offer, but the driver cannot perform any safety-sensitive work for you until the SAP reports successful compliance, the driver passes a return-to-duty test and the state restores the CDL privilege. In practice that can take weeks or months, depending on the treatment the SAP prescribes.

Who pays for the SAP and the follow-up tests?

The regulations require the employer to give a driver who violates the rules, including an applicant, a free list of available SAPs (§40.287). They do not settle who pays for the evaluation, treatment or follow-up tests. That is a matter for company policy and any applicable agreement, so put your policy in writing and tell applicants before they accept an offer.

Does the follow-up clock keep running while the driver is between jobs?

No. The minimum of six tests is counted over the first 12 months of safety-sensitive duty after return, so time away from covered work does not count toward the plan. A driver who changes carriers or takes a break picks up where the plan left off.

Can we test the driver more often than the SAP's plan because of our company policy?

Not under DOT authority. §40.307(d)(4) prohibits employers from adding testing beyond the SAP's plan. If you believe more testing is needed, contact the SAP, who can modify the plan.

How long will the violation show on our future queries?

Until all of these are reported, the SAP information, the negative return-to-duty test and completion of follow-up testing, and five years have passed since the violation determination, whichever happens last. A driver can be fully back at work and still show the violation on queries for several years.

Keep reading