Which Clearinghouse Query Do You Owe, and What Happens If You Miss It?
ON THIS PAGE8 sections
- Which query do I owe, and what does each one return?
- Do I still have to call the previous employers?
- How do I actually run this, step by step?
- What happens to the driver’s license now?
- Does the April 2026 identity verification change apply to me?
- What the Clearinghouse cannot tell you
- What does non-compliance cost?
- Frequently asked questions
There are two Clearinghouse queries and they are not interchangeable. The pre-employment query has to be a full query. 49 CFR 382.701(a)(2) says the employer “must conduct a full query under this section, which releases information in the Clearinghouse to an employer and requires that the individual driver give specific consent” (49 CFR 382.701). The annual query does not. It may be a limited query, which tells you only whether information exists.
That distinction produces the bottleneck every recruiter eventually hits. Specific consent is given by the driver electronically, inside the Clearinghouse, and drivers are not required to register there. FMCSA’s guidance says both things in one breath: “Drivers are not required to register for the Clearinghouse. However, a driver will need to be registered to provide electronic consent in the Clearinghouse if a prospective or current employer needs to conduct a full query of the driver’s Clearinghouse record — this includes all pre-employment queries” (FMCSA-D&A-CLEAR-382.703-FAQ003, January 8, 2019).
So the truck is loaded, the driver is in the parking lot, and the query is waiting on an account he has never opened. Nothing in Part 382 lets you start him anyway.
Which query do I owe, and what does each one return?
A full query releases the record; a limited query only tells you a record exists. That is the whole difference, and it drives the consent you need, where you collect it, and what you must do within 24 hours when the answer comes back wrong.
| Full query | Limited query | |
|---|---|---|
| Satisfies pre-employment duty | Yes, and only this | No |
| Satisfies annual duty | Yes | Yes — 382.701(b)(2) |
| What it returns | The information in the driver’s record | Whether information exists, nothing more |
| Consent required | Specific consent, given electronically inside the Clearinghouse, before each query | General consent, collected outside the Clearinghouse |
| Consent duration | One query | May be multi-year, but must state the timeframe |
| If it returns a hit | You have the detail already | Full query within 24 hours (382.701(b)(3)) |
Two errors are common enough to name. A limited query does not clear a driver for hire: run one pre-employment and you have satisfied nothing. And limited-query consent does not have to be renewed annually: the rule says the driver “may give consent to conduct limited queries that is effective for more than one year.”
Do I still have to call the previous employers?
For their drug and alcohol history, no, if they were FMCSA-regulated. 49 CFR 391.23(e)(4) now reads: “As of January 6, 2023, employers subject to § 382.701(a) of this chapter must use the Drug and Alcohol Clearinghouse to comply with the requirements of this section with respect to FMCSA-regulated employers” (49 CFR 391.23). FMCSA states the negative side plainly: “Inquiries not conducted under § 382.701(a) will not satisfy these inquiry requirements” (Clearinghouse FAQ).
Two carve-outs survive, both in 49 CFR 382.413.
Follow-up testing plans still come from the previous employer. Where an employee subject to follow-up testing “has not successfully completed all follow-up tests, employers must request the employee’s follow-up testing plan directly from the previous employer” (382.413(b) exception). The Clearinghouse shows you a driver is mid-plan. It does not hand you the plan.
Non-FMCSA DOT modes still require a manual inquiry. 382.413(c) requires you to request the information “directly from those employers regulated by a DOT Agency other than FMCSA.” An applicant who spent two years testing under FAA or FRA rules has history that never reached this database. 49 CFR 40.25 says the same from the other side.
And the query does not replace the pre-employment controlled substances test. 49 CFR 382.301(a) still bars safety-sensitive work until you hold a verified negative result from the MRO or C/TPA. Pre-employment alcohol testing stays optional under 382.301(d), but if you do it, you do it for all covered employees.
How do I actually run this, step by step?
| Step | What you do | Status |
|---|---|---|
| 1 | Register the company and keep the registration alive | Required |
| 2 | Collect both consents, and know which is which | Required |
| 3 | Run the pre-employment full query before any safety-sensitive function | Required |
| 4 | Run the annual query on a rolling 365-day clock | Required |
| 5 | Act on change notifications for 12 months after each query | Required in effect |
| 6 | Report your own violations by the close of the third business day | Required |
| 7 | Retain query and consent records for 3 years | Required |
Register the company and keep the registration alive
What you do: register before you query or report anything, as 49 CFR 382.711(a) requires of every employer and service agent. Then re-verify your authorized users every year, which 382.711(b)(2) requires in terms (49 CFR 382.711).
Status: required.
The gotcha: the registration expires quietly. 49 CFR 382.713(a) makes it valid for five years, and 382.713(b) says FMCSA “will cancel Clearinghouse registrations for anyone who has not queried or reported to the Clearinghouse for 2 years” (49 CFR 382.713). A three-truck carrier with no turnover can go two years without touching the system, then find on the morning of a hire that the account is gone. Treat the annual query as the activity that keeps you alive.
Collect both consents, and know which is which
What you do: build two artifacts. A general consent for limited queries, signed outside the Clearinghouse, stating the timeframe it covers. And, for each full query, the driver’s specific consent given electronically inside the Clearinghouse. 49 CFR 382.703(a) is absolute on the threshold: no employer may query “without first obtaining that driver’s written or electronic consent” (49 CFR 382.703).
Status: required.
The gotcha: the specific consent lives on the driver’s side of the system and you cannot manufacture it. If he is not registered, there is nothing for him to click. Ask on the phone screen, before the road test and before the physical, whether the applicant has a Clearinghouse account. Treat it the way you treat the driver application under 391.21: a document that has to be complete before anything downstream moves.
Refusal is not a stalemate. 382.703(c) bars a safety-sensitive function where the driver refuses consent, and 49 CFR 391.23(f)(2) closes the hiring-side loop: on refusal for the pre-employment query, “the prospective motor carrier employer must not permit the driver to operate a commercial motor vehicle.”
Run the pre-employment full query before any safety-sensitive function
What you do: run the full query before the driver performs a safety-sensitive function, not before he drives. 382.701(a)(1) bars employing a driver “to perform a safety-sensitive function without first conducting a pre-employment query of the Clearinghouse.”
Status: required.
The gotcha: safety-sensitive is broader than driving. The definition at 49 CFR 382.107 reaches time waiting to be dispatched, time inspecting, servicing or conditioning the vehicle, and time attending a vehicle being loaded or unloaded (49 CFR 382.107). Put a new hire on the yard doing pre-trip work Monday and run the query Tuesday, and you were outside the rule on Monday.
One workaround exists and it is not discretionary. FMCSA’s FAQ: if a technical issue prevents queries, “FMCSA will post a notification on the home page informing employers that they may hire a driver using only the procedures set forth in 49 CFR 391.23(e). If no such notification is on the home page, the requirement to conduct pre-employment queries… is in effect” (Clearinghouse FAQ). Check the home page, and run the query once service is restored.
Run the annual query on a rolling 365-day clock
What you do: query at least once per year for every employee subject to Part 382 testing, as 382.701(b)(1) requires. A limited query is enough.
Status: required.
The gotcha: two, and both are calendar problems.
The clock is rolling. FMCSA describes the duty as “at least once within a 365-day period based on the date the employer conducted the last query, or another 12-month period determined by the employer,” tracked “on a rolling 12-month (365-day) basis.” A driver queried on March 3 is due by March 3, not December 31. Carriers who run everyone each January are compliant by accident and eventually miss the driver hired in February.
And a hit on a limited query lights a 24-hour fuse: “the employer must conduct a full query… within 24 hours of conducting the limited query” (382.701(b)(3)). That is one day to obtain electronic specific consent from a driver who may be 900 miles away. If it does not come, 382.703(c) applies and he comes off safety-sensitive functions.
Act on change notifications for 12 months after each query
What you do: treat the post-query notification email as a work item with a 24-hour clock, routed to a monitored inbox rather than one recruiter’s.
Status: required in effect. The follow-on query FMCSA directs is a full query; skip it and you are running a driver whose record you have not read, which is how carriers land on the wrong side of 382.701(d). If the driver refuses the consent that full query needs, 382.703(c) applies.
The gotcha: the printed rule and current agency practice do not match, and the printed rule is the shorter of the two. 49 CFR 382.701(c) provides for notification if information is entered “during the 30-day period immediately following an employer conducting a query.” FMCSA’s FAQ describes what the system now does: “As of March 8, 2023, an employer will be notified via email if a driver they have queried has new information… recorded in their Clearinghouse record within 12 months of a pre-employment or annual query,” where the previous behavior was 30 days after pre-employment queries only. Build on the 12-month practice, or your monitoring will read silence as clean for eleven months it never covered.
On receipt, FMCSA directs the employer to “complete a full follow-on query within 24 hours,” and if the driver refuses consent, “the employer must remove the driver from safety-sensitive functions until a full query is conducted and the results obtained.” A follow-on query also satisfies the annual requirement and resets the 365-day clock from its own date.
Report your own violations by the close of the third business day
What you do: report what 49 CFR 382.705(b) puts on you, by the close of the third business day after you obtain the information (49 CFR 382.705).
Status: required.
The gotcha: carriers routinely believe they must report positive drug tests. They do not. The MRO does, on a shorter clock.
| Report | Who reports it | Deadline |
|---|---|---|
| Verified positive, adulterated or substituted result; MRO refusal determinations | MRO | Within 2 business days of the determination (382.705(a)(1)) |
| Alcohol confirmation test of 0.04 or greater | Employer | Close of the third business day (382.705(b)(1)) |
| Refusal to test that does not require an MRO determination | Employer | Close of the third business day (382.705(b)(1)(iii), (iv)) |
| Negative return-to-duty test result | Employer | Close of the third business day |
| Completion of the follow-up testing plan | Employer | Close of the third business day |
| Actual knowledge of prohibited use | Employer | Close of the third business day after obtaining actual knowledge (382.705(b)(4)) |
Actual knowledge is a defined term, not a hunch. 49 CFR 382.107 limits it to four sources: direct observation by the employer, information from the driver’s previous employer or employers, a traffic citation for driving a CMV while under the influence, or the employee’s own admission (49 CFR 382.107). A rumor from dispatch is not on that list.
An actual-knowledge report is also an evidence package. 382.705(b)(5) requires witnesses with contact information, a description of the violation, evidence supporting each fact alleged (“affidavits, photographs, video or audio recordings, employee statements”) and a certificate of service showing you gave the employee everything you reported. Assembling that inside three business days is why carriers who have done it once keep a template.
You may designate a C/TPA, but 382.705(c) says the employer “retains ultimate responsibility for compliance with this section.” One express exception sits in the same paragraph: an employer does not retain that responsibility where the C/TPA is designated under 382.705(b)(6) — the owner-operator case, an employer who employs himself as a driver, who must designate a C/TPA and still queries himself.
Retain query and consent records for 3 years
What you do: keep a record of each query and everything received in response for three years (382.701(e)), and the consent record for three years from the last query (382.703(a)).
Status: required, but lighter than most carriers assume.
The gotcha: this gets over-filed. The rule text itself closes the point. The last sentence of 382.701(e) reads: “As of January 6, 2023, an employer who maintains a valid registration fulfills this requirement” (49 CFR 382.701). FMCSA’s FAQ says the same operationally — employers “may choose to maintain separate copies of their Clearinghouse queries in a driver qualification file or driver investigation history file or other location but are not required to do so as of January 6, 2023” (Clearinghouse FAQ) — though the same FAQ page dates the registration-satisfies-retention position to January 6, 2020 a few answers earlier. Follow the regulation, and do not build a policy that turns on the FAQ’s date.
One thing you do still file by hand. 49 CFR 391.53(b)(2) requires a copy of the response received from each previous employer investigated under 391.23(d) and (e), and that copy goes in the driver investigation history file, not the driver qualification file. For employers regulated by a DOT mode other than FMCSA, no Clearinghouse record exists to stand in for it, so the response itself is the record. Those are separate files with separate access rules. Our driver qualification file checklist covers what belongs in the DQ file and what does not.
What happens to the driver’s license now?
Since November 18, 2024, prohibited status reaches the CDL itself, on a 60-day State clock. For its first years the Clearinghouse was a hiring gate. Now it is a licensing event.
The rule is Clearinghouse II, “Controlled Substances and Alcohol Testing: State Driver’s Licensing Agency Non-Issuance/Downgrade of Commercial Driver’s License,” 86 FR 55718, published October 7, 2021, effective November 8, 2021, compliance date November 18, 2024. Four things started that day.
The State must downgrade. On notification that a holder is prohibited under 382.501(a), the State must “initiate established State procedures for downgrading the CLP or CDL. The downgrade must be completed and recorded on the CDLIS driver record within 60 days of the State’s receipt of such notification” (49 CFR 383.73(q)). Sixty days, not thirty.
Those 60 days are a real second chance. 383.73(q)(1) requires the State, on notice before the downgrade is recorded that the driver is no longer prohibited, to “terminate the downgrade process without removing the CLP or CDL privilege from the driver’s license,” where State law allows.
The State must query before issuing. 49 CFR 382.725 changed “may” to “must” on the same date: licensing officials must obtain the record when a driver applies for a CDL or CLP, and “by applying… a driver is deemed to have consented” (49 CFR 382.725). 49 CFR 384.235 mirrors the duty into the State compliance rules.
Roadside enforcement got a hook. 49 CFR 392.15 now bars a CLP or CDL holder from operating a CMV “if prohibited by § 382.501(a).”
One consequence lands squarely on your desk: coming back is two gates, not one. Completing the return-to-duty process clears the federal prohibition, but 49 CFR 382.503(b) says the driver may not drive “until the State Driver Licensing Agency reinstates the CLP or CDL privilege to the driver’s license.” Verify the license, not only the query result, before dispatching a returning driver, which means an MVR from every licensing state. And note that a violation does not age off at five years: 49 CFR 382.719(a) requires four conditions together, walked through in how a driver leaves prohibited status.
Does the April 2026 identity verification change apply to me?
Probably not, and the way this was reported is worth correcting. FMCSA’s notice: “Starting April 27, 2026, users who register for certain Clearinghouse accounts will need to prove their identity using a secure web application. This update applies to new registrations for the following user roles: Employer Without a Portal Account; Consortium/Third-Party Administrator (C/TPA); Medical Review Officer (MRO); Substance Abuse Professional (SAP); Assistants invited to register under another registered entity” (FMCSA Clearinghouse news).
Read the limits in that sentence.
New registrations only. Existing registrants are not covered. FMCSA says only that “in a later phase, FMCSA will prompt existing Clearinghouse users to complete the identity verification process. We will provide instructions on this when it is ready to implement.” No date and no compliance deadline has been announced. If a vendor tells you your existing account has a deadline, ask them to show you where FMCSA published it.
Five roles, and the employer role is qualified. The list says “Employer Without a Portal Account.” FMCSA states that “employers of CDL drivers that register with the U.S. Department of Transportation (DOT) will have their identity verified through the DOT registration process.” Most motor carriers register through the FMCSA Portal and sit outside this change.
Drivers are not in scope. FMCSA states that “driver accounts have been verified from the inception of the Clearinghouse by validating license information,” and the press release of April 27, 2026 notes that CDL holders “are already verified through state systems.”
If you do fall in scope: log in via Login.gov, select the role, scan the on-screen QR code, follow the link to the FMCSA Identity Verification mobile app, scan a government-issued ID and take a selfie. The Clearinghouse then pulls your first, middle and last name into the registration, and “this information cannot be edited by the user.” The press release names IDEMIA as the provider.
One clarification worth carrying into any conversation about this: a separate, earlier identity verification program attached to FMCSA registration itself was incorporated into the Unified Registration System in April 2025, and it applies to new applicants for a USDOT number (FMCSA fact sheet, April 2025). Different program, different scope, and several secondary write-ups have merged the two.
What the Clearinghouse cannot tell you
It carries one category of fact: a drug or alcohol violation somebody was legally required to report. That is narrow and specific, and the database is excellent at it.
Work Steps 1 through 7 correctly and here is your file on a new hire: a full query returning either nothing or a violation record, a verified negative pre-employment test, an MVR from each licensing state, and whatever the PSP report shows in crashes and roadside inspections. Every one of those records exists because an event crossed a reporting threshold.
The behavior that costs carriers money mostly sits under that line. A driver let go for showing up unfit but never tested produces no Clearinghouse record, because actual knowledge under 382.107 requires direct observation, a previous employer’s report, a DUI citation or an admission, and a supervisor’s suspicion is none of those. A driver who walked off a load or went dark for three days generates nothing here at all. That is the same blindness behind the real cost of a bad driver hire.
That gap is what a first-party behavioral layer covers. On cdlscan, carriers write reviews of drivers they actually employed, so observations that never became reportable events (reliability, communication, how the equipment came back, whether the driver finished the contract) still leave a trace tied to a period of employment. Our overview of how carrier-written driver reviews work covers the format, and what carriers see in a DAC report covers the employment-side record.
Be exact about the boundary. The Clearinghouse query is federally required and nothing replaces it. Peer review is an additional layer on top of the mandatory record, run after the required checks are complete, never in place of one. If you intend to rely on third-party information about a candidate 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 the applicable obligations with your own counsel.
What does non-compliance cost?
The rule does not print a number, and neither will we. 49 CFR 382.727 subjects an employer, employee, MRO or service agent who violates Subpart G to “the civil and/or criminal penalty provisions of 49 U.S.C. 521(b)(2)(C)” (49 CFR 382.727). No dollar figure appears there, and FMCSA’s civil penalties are adjusted for inflation. Pull current amounts from Appendix A to 49 CFR Part 386.
Same discipline on fees. 49 CFR 382.721 authorizes a “reasonable fee” and sets no amount, with one hard exception: “No driver may be required to pay a fee to access his or her own information in the Clearinghouse” (49 CFR 382.721). Current query-plan pricing lives on the Clearinghouse site, alongside FMCSA’s monthly summary reports if you want current volume figures.
Frequently asked questions
The applicant is not registered in the Clearinghouse. Can I hire him anyway?
Not into safety-sensitive work. Drivers are not required to register, but FMCSA guidance is explicit that a driver must be registered to give the electronic consent every full query requires, including all pre-employment queries. Without the query you cannot start him, and 391.23(f)(2) bars you from letting a driver who refuses consent operate a CMV.
Do I have to report a positive drug test?
No. The MRO reports verified positive, adulterated and substituted results and refusal determinations within 2 business days under 382.705(a)(1). Your list under 382.705(b) is alcohol confirmations of 0.04 or greater, refusals, actual knowledge, negative return-to-duty results and follow-up completion, each by the close of the third business day. Routine negative pre-employment results are not reported at all.
My C/TPA handles all of this. Am I covered?
Operationally yes, legally no. 382.705(c) permits an employer to designate a C/TPA and states that the employer “retains ultimate responsibility for compliance with this section.” The one exception in that paragraph is the owner-operator: under 382.705(b)(6) an employer who employs himself as a driver must designate a C/TPA, and 382.705(c) says he does not retain that responsibility for the reporting the C/TPA is designated to do. He still queries himself.
Do query records go in the driver qualification file?
Not necessarily. 382.701(e) requires three years of retention, and FMCSA’s position is that a valid registration satisfies that duty because the system stores the query history. Copies in a DQ file or investigation history file are optional. The exception is 391.53(b)(2): responses from employers regulated by a DOT mode other than FMCSA are not in the Clearinghouse and must be retained in the driver investigation history file.
A driver says his record is wrong. What can he do?
Petition FMCSA, but 382.717(a)(1) limits it to administrative errors — he may not contest the accuracy of a test result, a refusal or other violation information. Three narrow exceptions sit at 382.717(a)(2), including the DUI non-conviction route below. 49 CFR 382.717 gives FMCSA 45 days from a complete petition to inform the driver of its decision in writing, 14 days where expedited treatment is granted, and 30 days to complete an administrative review, which constitutes final agency action (49 CFR 382.717).
A driver’s DUI charge was dismissed. Does the actual-knowledge report come off?
Not automatically. FMCSA states that a report of actual knowledge based on a DUI in a CMV “will remain in the Clearinghouse for 5 years, or until the driver has completed the return-to-duty process, whichever is later, regardless of whether the driver is ultimately convicted.” A Notice of Enforcement Policy issued March 8, 2023 says FMCSA will not enforce return-to-duty requirements against a driver whose citation ends in non-conviction, but adds that the driving prohibition applies between the report and that determination, and that “non-conviction” does not include pleading guilty to a lesser charge such as reckless driving.
General compliance information for motor carrier hiring and safety staff, not legal advice. Regulatory text, deadlines and agency guidance cited here were checked against law.cornell.edu/cfr, govinfo.gov, clearinghouse.fmcsa.dot.gov and fmcsa.dot.gov in July 2026. Agency practice and the regulations change; verify any section before building policy on it. Last reviewed 2026-07.