Clearinghouse Violation Removal: How a Driver Leaves Prohibited Status

A Clearinghouse violation does not fall off after five years. It comes off employer view when four conditions are satisfied together: the SAP has reported to the Clearinghouse, an employer has reported the driver’s negative return-to-duty test, the driver’s current employer has reported that all follow-up tests are complete, and five years have passed since the violation determination (49 CFR 382.719(a)). Miss any one and the violation stays visible to querying employers indefinitely — 382.719(b) says so in one sentence.

That structure catches carriers in a specific way. Two of those four conditions are things you report, not the driver. A driver can finish the entire return-to-duty process, pass the test, and still sit in prohibited status because nobody at your company filed the result inside three business days.

What puts a driver into prohibited status in the first place?

A verified positive drug test, an alcohol test of 0.04 or greater, a refusal to test including adulterating or substituting a specimen, or any other violation of a DOT drug or alcohol prohibition (49 CFR 40.285(b)). The consequence is immediate and total: no safety-sensitive function, including driving a CMV (49 CFR 382.501(a)).

It follows the driver to every DOT-regulated employer. 49 CFR 40.285(a) is written to the employee: you “cannot again perform any DOT safety-sensitive duties for any employer until and unless you complete the SAP evaluation, referral, and education/treatment process.” FMCSA said the same about the annual query — if it shows a violation, the employer is barred from letting the driver perform safety-sensitive functions until the return-to-duty requirements are met, regardless of where the violation occurred (81 FR 87686, 87697).

The driver has to tell you. Under 49 CFR 382.415 a driver in violation must notify all current employers in writing before the end of the business day following the day he received notice of the violation, or before performing any safety-sensitive function, whichever comes first. He is not required to notify the employer that administered the test or documented the circumstances that gave rise to the violation — so for a driver who also works for another carrier, that notice is how you are supposed to find out.

One caution about a date in the CFR: the November 18, 2024 amendment to 49 CFR 382.501 was a punctuation correction, a semicolon changed to a comma (89 FR 90608, 90611). The substantive change that day was the State downgrade requirement, covered below.

What do you owe the driver on the day of the violation?

One thing, and it is small, free, and auditable: a list of substance abuse professionals. Under 49 CFR 40.287 you must give each employee who violates a DOT drug and alcohol regulation — “including an applicant or new employee” — a listing of SAPs readily available and acceptable to you, with names, addresses and telephone numbers, at no charge. The obligation survives a firing, and its absence is an easy audit finding because the inspector only has to ask for a copy.

What you do not owe is the process itself. 49 CFR 40.289(a) states you are not required to provide a SAP evaluation or any recommended education or treatment, and 40.289(c) leaves payment “for employers and employees to decide,” subject to labor agreements and health plans. No federal rule assigns the bill to either side. Get the fee from the SAP.

One condition attaches only if you offer a return: 40.289(b) requires you, before the driver performs safety-sensitive duty again, to ensure the SAP met the qualifications of 49 CFR 40.281 and that the driver successfully complied with the SAP’s recommendations.

What does the SAP actually do, and what can the SAP not do?

The SAP evaluates, refers, re-evaluates, writes the follow-up testing plan, and recommends continuing care — five functions, and none of them is deciding whether the driver gets his job back (49 CFR 40.291(a)). The rule is explicit on the posture, too: 40.291(b) tells the SAP “you are not an advocate for the employer or employee,” and that the function is to protect the public interest in safety.

Six credentials qualify under 49 CFR 40.281(a): licensed physician (MD or DO), licensed or certified social worker, licensed or certified psychologist, licensed or certified employee assistance professional, state-licensed or certified marriage and family therapist, or a drug and alcohol counselor certified by an organization listed by DOT. Verify it — 40.281(e) requires the SAP to provide documentation of current qualification on request to employers and C/TPAs “who are using or contemplating using” the services.

The rest of subpart O shuts down the negotiations carriers and drivers try to open.

Two practical notes. Remote evaluation is allowed, but the technology “must permit real-time audio and visual interaction” between SAP and employee (49 CFR 40.291(a)(1)(i)), and the SAP must stay inside the geographic limits of the credential (40.281(f)). And “successful compliance” does not mean treatment is finished: under 49 CFR 40.301(c)(2) a SAP may find compliance “even though the employee has not yet completed the full regimen.” If the follow-up evaluation goes the other way, you are forbidden to return him to safety-sensitive duties (40.301(d)(2)).

How does a driver get from prohibited to driving again?

Five steps, in this order. Two of them are your reporting duties, and both run on short clocks.

What is your follow-up testing obligation after he returns?

At minimum six unannounced tests in the first 12 months of safety-sensitive duty after the return, on a plan the SAP writes and you execute (49 CFR 40.307(d)). The SAP may require more, and may require additional testing during the following 48 months, but may never set the first-year minimum below six.

The division of labor is precise, and both sides get it wrong in predictable ways.

The plan is written only after the successful-compliance determination and goes directly to the DER (49 CFR 40.307(a)-(c)). Execution is not optional: under 49 CFR 40.309(a)-(b) you may not allow the driver to continue performing safety-sensitive functions unless follow-up testing is conducted as the SAP directed, and tests must be unannounced, with no discernible pattern and no advance notice. Two counting rules produce most of the audit findings: a random-pool test cannot be substituted for a follow-up test (40.309(c)), and a cancelled follow-up test does not count and must be recollected (40.309(d)).

The plan also travels. 49 CFR 40.307(e) states that follow-up testing requirements “follow the employee” to subsequent employers and through breaks in service. In the rule’s own example, a driver completes two of six tests with Employer A and quits: he must complete the four remaining tests during the next ten months of safety-sensitive duty, and Employer B is responsible for ensuring that he does. A layoff pauses the plan rather than erasing it.

When the plan is finished, report it. Completion of all follow-up tests is a Clearinghouse reporting item on the same three-business-day clock (49 CFR 382.705(b)(1)(v)), and it is the third of the four conditions in 382.719(a). Skip it and the violation never leaves employer view, no matter how many years pass.

What if you are hiring a driver who is mid-process?

You may hire him, but only on a specific legal hook, and only if you take the testing plan on. Under 49 CFR 382.701(d) a driver who has not completed all follow-up tests may still be used if he completed the part 40 subpart O process, achieved a negative return-to-duty test result, and “the employer assumes the responsibility for managing the follow-up testing process associated with the testing violation.”

Getting the paperwork is a separate step from the query, and this is the part carriers miss. Under 49 CFR 391.23(e)(4)(i) you must request the follow-up testing plan directly from the previous employer; the Clearinghouse query does not supply it. If the previous employer does not have the return-to-duty information — say it declined to hire him after a positive pre-employment test — 49 CFR 40.25(b)(5) tells you to seek that documentation from the driver himself.

Three more checks belong in the same sitting:

• Ask the direct question. 49 CFR 40.25(j) requires you to ask whether the applicant tested positive or refused on a pre-employment test with a prospective employer in the past two years. If he admits it, he may not perform safety-sensitive functions for you until he documents completion of the return-to-duty process.
• Cover the other DOT modes. The Clearinghouse only holds FMCSA-regulated testing. You must still run the traditional 49 CFR 40.25 inquiry to employers regulated by other DOT operating administrations (40.25(a)(2)-(3); 382.413(c)).
• File it in the right place. Safety performance history obtained under 391.23(e) goes in the driver investigation history file under 49 CFR 391.53, not the driver qualification file. Access is limited to people involved in the hiring decision or who control access to the data, and your insurer may see that file except the alcohol and controlled substances data. Our driver qualification file checklist keeps the two apart.

And 49 CFR 382.723(b) limits your use of Clearinghouse information to determining whether a prohibition applies, barring you from divulging it to anyone not directly involved in that determination.

Can a violation be removed if it should not be there?

Only through a narrow petition process that cannot touch the accuracy of the test. 49 CFR 382.717(a)(1) says petitioners “may request only that administrative errors be corrected” — data entry errors, a duplicate report of a positive result — and “may not contest the accuracy of test results, test refusals, or other violation information.”

Exactly three grounds support actual removal or addition of documentary evidence, and two of them turn on the employer’s paperwork:

That is a live risk on your side: a sloppily documented actual-knowledge or refusal report is removable on its face, so your file on the underlying event has to be right when you enter it.

Timelines: FMCSA informs the driver in writing within 45 days of a complete petition, or within 14 days where expedited treatment is granted; administrative review is completed no later than 30 days after the request and is the final agency action (49 CFR 382.717(d), (e)(2), (f)(4)). If information is corrected or removed, FMCSA notifies any employer that already accessed it (382.717(g)). Note that nothing fully disappears — 49 CFR 382.719(d) preserves FMCSA’s ability to use removed information for research, auditing or enforcement.

What do you have to keep, and for how long?

How the SAP report reaches you matters as much as how long you keep it. Under 49 CFR 40.311 you must receive SAP written reports directly from the SAP, on the SAP’s own letterhead, signed and dated, and ensure no third party changed them; a report forwarded on a service agent’s letterhead does not meet the rule. The successful-compliance report has eleven required elements, including the follow-up testing plan and the continuing care recommendations (40.311(d)). Where the driver has no current employer, the SAP gives the reports to him directly, and to the gaining DOT-regulated employer when he lands a safety-sensitive job (40.311(f)).

Violations of these subparts carry civil and/or criminal penalties under 49 U.S.C. 521(b)(2)(C) (49 CFR 382.727). The amounts are inflation-adjusted; pull them from FMCSA’s current civil penalty schedule rather than a remembered number.

What the Clearinghouse record cannot tell you

It records four things about the return-to-duty process and nothing about the person. Work every step above correctly and you will know whether a prohibition applies, the date of the initial assessment, the date the SAP found successful compliance, and whether the tests were reported.

It will not tell you whether the driver notified his employers on the day 382.415 required or waited to be caught, whether he showed up for follow-up tests without a chase, or how three previous carriers experienced him over eighteen months. None of that becomes a reportable event, so none of it enters a federal system — the same blind spot behind the real cost of a bad driver hire and the reason the PSP report, the MVR and your CSA data can all come back thin on a driver you have questions about.

That gap is what a first-party behavioral layer is for. On cdlscan, carriers write reviews of drivers they actually employed, so observations that never became reportable events still leave a trace tied to a period of employment; our overview of how carrier-written driver reviews work covers the format.

The boundary, plainly: this sits on top of the mandatory record, never in place of it. The Clearinghouse query, the return-to-duty documentation, the follow-up testing plan and the safety performance history investigation are legally required and nothing here substitutes for any of them. Run them exactly as written, then look the candidate up as an additional input. If you intend to rely on third-party information as a factor in a hiring decision, ask the provider which category of information they consider it under the Fair Credit Reporting Act and confirm with your own counsel which obligations attach; the FTC’s guidance on using consumer reports is where that starts.

Frequently asked questions