FMCSA Clearinghouse Queries: Pre-Employment and Annual Checks

A new CDL driver finishes orientation on Friday, the recruiter has a signed consent form in the file, and dispatch books a Monday run. Nobody notices that the full query is still "pending driver consent" because the driver never created a Clearinghouse login. In another terminal, an annual batch of limited queries flags three drivers with records, and one of them is still under a load the next afternoon. Both carriers believed they were compliant.

Neither problem is a misunderstanding of the rule. Both are hand-off failures between safety, recruiting and dispatch: the regulation sets a clock, and no system enforced it. This guide turns 49 CFR 382.701 and its neighbouring sections into a working sequence with owners, time limits and a dispatch hold, so that a driver's eligibility is decided by a query result rather than by whoever remembers to check.

• Inside this guide: what limited and full queries return, the two kinds of driver consent, the pre-employment and annual sequences, what a prohibited status means for dispatch and the CDL, and the records an investigator will ask to see.
• Practical extras: a query-budget example in dollars, a note on why India has no equivalent register, an eligibility rule written as SQL, a timed failure trace and an evaluation table for compliance software.

Limited and full queries return different answers, at the same price

A limited query tells an employer only whether the Drug and Alcohol Clearinghouse holds information about a driver; a full query releases that information. Pre-employment checks always require a full query, while the annual check may start with a limited one.

Section 382.701(a) bars an employer from using a driver in safety-sensitive functions without first running a pre-employment query, and paragraph (a)(2) requires that query to be a full query. Paragraph (b) requires a query at least once a year for every employed driver and allows a limited query in its place, with the driver's consent. FMCSA guidance sets a flat $1.25 per query and charges once when a limited query is followed by a full one.

The fee is trivial; the timing is not. Queries are bought in advance as a query plan in the employer's own Clearinghouse account, so a plan balance of zero on a Friday afternoon is a common reason a pre-employment check stalls until Monday.

Two consents, two places, and what happens when a driver refuses

Treat consent as two separate records with two separate owners. The general consent for limited queries lives in your files; the specific consent for a full query exists only as an action the driver takes in the Clearinghouse.

Section 382.703(a) bars any query without the driver's written or electronic consent and requires the employer to keep that consent for three years from the date of the last query. Section 382.703(b) adds that before any information is released, the driver must give consent electronically through the Clearinghouse. FMCSA guidance confirms that drivers are not obliged to register, but a driver must register to grant that electronic consent, including for every pre-employment query.

Drug and alcohol clearinghouse queries rest on two consents under 49 CFR 382.703: a general written or electronic consent kept by the employer for 3 years after the last limited query, and a specific electronic consent the registered driver grants inside the Clearinghouse before each full query releases any violation record.

• Refusal to consent: Section 382.703(c) prohibits the employer from using a driver in safety-sensitive functions who refuses either consent.
• Hiring-side refusal: Section 391.23(f)(2) separately bars a motor carrier from letting an applicant operate a commercial motor vehicle if the applicant refuses consent to the Clearinghouse query.
• Multi-year general consent: Section 382.701(b)(2) allows the limited-query consent to cover more than one year, so one form signed at hire can support every annual check for the length of employment.
• Notification consent: Under 382.703(e), the same consent lets FMCSA tell the employer about information added to the driver's record within 30 days after the query.

Pre-employment sequence from offer letter to first dispatch

A driver becomes dispatchable only when three independent results are in: a full query showing no prohibition, a verified negative pre-employment drug test, and the previous-employer history the Clearinghouse does not hold. Run them in parallel, but release the driver only on the last of the three.

Section 382.301(a) requires a verified negative controlled substances result from the medical review officer or C/TPA before a driver first performs safety-sensitive functions, subject to the narrow exception in 382.301(b). Section 391.23(e)(4) says that since 6 January 2023 the Clearinghouse query covers previous FMCSA-regulated employers, but drug and alcohol history from employers regulated by another DOT mode must still be requested from those employers directly.

1. Offer accepted: Recruiting collects the general consent, the CDL number and issuing state, and asks the candidate to register in the Clearinghouse the same day.
2. Full query requested: The safety team runs the pre-employment full query; the Clearinghouse sends the consent request to the candidate's account.
3. Collection and test: The candidate attends the collection site; the result is verified by the medical review officer.
4. Other-mode history: If the application lists employers that tested the driver under another DOT agency's rules, such as FAA, FRA, FTA or PHMSA, within three years, the carrier sends release requests to them.
5. Release to dispatch: The driver record changes to "eligible" only when all three results are filed and the full query shows no prohibition under 382.701(d).

Owner-operators who employ themselves still need someone to report on them. Section 382.705(b)(6) requires an employer who is also the driver to designate a C/TPA to carry out the reporting duties for its own violations. Our carrier onboarding packet covers the authority and insurance checks a broker runs on that owner-operator's company, which are separate from the driver's Clearinghouse status.

Running the annual query on a rolling 365-day clock

The annual requirement is per driver and rolling, not a calendar-year event. FMCSA's revised guidance of 9 March 2023 measures it as at least once within 365 days of the last query, and a follow-on query after a record-change notice restarts the clock.

Most fleets run limited queries in monthly batches grouped by the driver's last query date, which spreads the work and keeps any "information found" results to a handful at a time. The critical rule sits in 382.701(b)(3): when a limited query shows information exists, the employer must complete a full query within 24 hours, and until it does, the driver may not perform safety-sensitive functions.

-- Drivers due for their annual query in the next 30 days (illustrative schema)
SELECT d.driver_id, d.cdl_no, d.cdl_state,
       q.last_query_date,
       q.last_query_date + INTERVAL '365 days' AS annual_due_by
FROM   driver d
JOIN   (SELECT driver_id, MAX(query_completed_date) AS last_query_date
        FROM clearinghouse_query GROUP BY driver_id) q ON q.driver_id = d.driver_id
WHERE  d.status = 'ACTIVE_CDL'
  AND  q.last_query_date + INTERVAL '365 days' <= CURRENT_DATE + 30;

-- Dispatch hold rule evaluated every 15 minutes
-- hold = (limited_result = 'INFO_FOUND')
--        AND full_query_result IS NULL
--        AND now() >= limited_completed_ts + INTERVAL '24 hours'
-- release only when full_query_result shows no 382.701(d) prohibition

A conservative fleet applies the hold at the moment the limited query returns "information found" rather than at hour 24, because a driver halfway through a 600-mile run cannot be pulled off the road in minutes. The regulation sets the outer limit; your dispatch rule can be stricter.

A missed 24-hour window traced through dispatch

The trace below follows one annual batch at a regional carrier. The query itself worked; the failure was that the result never reached the system that assigns loads.

1. Mon 06:10: Batch AQ-2611 runs 22 limited queries; three drivers (D-1147, D-2083, D-3310) return "information found". Consent requests for full queries go to their Clearinghouse accounts.
2. Mon 10:55: D-1147 and D-3310 grant consent; full queries show resolved records with completed return-to-duty and follow-up testing, so both remain eligible.
3. Tue 06:10: The 24-hour limit for D-2083 passes with no consent. The safety team's tracker turns red, but the transport management system still shows the driver as available.
4. Tue 07:30: Dispatch assigns load 77-5521 to D-2083; the truck leaves the yard at 07:52. At 09:40 the safety manager sees the conflict and the driver is stopped at a fuel island; the load is re-powered with a 3-hour delay.
5. Controlled state: The Clearinghouse result now writes an eligibility flag to the TMS driver profile, and the TMS refuses a load assignment while the flag is "hold". The safety manager alone can clear it, with a reference to the full query.

Annual clearinghouse queries under 49 CFR 382.701(b)(3) need a full query within 24 hours whenever a limited query reports information, so fleets that let the safety log, not the transport management system, decide driver availability risk dispatching a driver who is barred from safety-sensitive work after hour 24.

The same pattern of a compliance status held in one system and an assignment made in another is behind many hours-of-service violations. Our guide to HOS dispatch locks and gate controls describes how a driver availability flag can block a tender before it leaves the planning screen.

What a prohibited status means for dispatch and the driver's CDL

A prohibited status ends the driver's safety-sensitive work immediately at your company and, since November 2024, also starts a process that removes the commercial driving privilege from the licence itself.

Section 382.701(d) forbids an employer from using a driver whose query shows a listed violation, such as a verified positive, adulterated or substituted test, an alcohol result of 0.04 or higher, or a refusal, unless the driver has completed the substance abuse professional (SAP) process and a negative return-to-duty test. The employer may also take on a driver whose follow-up testing is still in progress, provided it manages that follow-up testing itself.

• State licensing check: Section 382.725(a)(2) requires the state CDL official to obtain the driver's Clearinghouse record on or after 18 November 2024 when the driver applies for a CDL or commercial learner's permit.
• Licence downgrade: Under 383.73(q), the state must complete and record a downgrade on the CDLIS driver record within 60 days of receiving notice that the driver is prohibited.
• Reinstatement path: The same paragraph requires the state to make the driver eligible for reinstatement when FMCSA reports that the prohibited status has ended.
• Record availability: Section 382.719(a) keeps violation information available to employers until the return-to-duty steps are reported, follow-up testing is complete and five years have passed since the violation.

Prohibited drivers found by a drug and alcohol clearinghouse query lose more than one job: 49 CFR 382.701(d) bars every employer from using them in safety-sensitive work, and 383.73(q) requires the state to downgrade the CDL on the CDLIS record within 60 days of FMCSA's notice.

Records, registrations and roles an investigator asks to see

Keep the evidence trail in two places: the Clearinghouse account, which now satisfies the query record requirement, and your own files, which still hold consents, authorised users and the dispatch decisions taken on each result.

Section 382.701(e) requires a three-year record of each query and its results, and states that from 6 January 2023 an employer with a valid Clearinghouse registration meets that requirement. Registration lasts five years under 382.713(a), and FMCSA may cancel the registration of anyone who has not queried or reported in two years. Authorised users must be verified annually under 382.711(b)(2).

Reporting duties run the other way and are just as dated. Section 382.705(b)(1) requires the employer to report items such as an alcohol result of 0.04 or higher, a negative return-to-duty result and a refusal by the close of the third business day after obtaining the information, while medical review officers report verified drug results within two business days.

Query budget and idle-truck cost, with India as a contrast case

For a 240-driver fleet the query fees are a few hundred dollars a year; the money at risk is in trucks parked while a full query waits for consent, and in loads moved by a driver who should have been held. The figures below are illustrative.

India has no counterpart to the Clearinghouse: we found no national register that an employer can query for a driver's drug and alcohol violations. Indian fleets rely on licence checks and their own testing, measured against the Motor Vehicles Act, 1988, Section 185 threshold of 30 mg of alcohol per 100 ml of blood detected by breath analyser. The rupee column therefore shows a contrast, not an equivalent obligation.

The comparison shows where effort belongs. A single idle day costs more than the entire annual query budget, so the return on a consent-chasing workflow, registration help at orientation and an automated hold comes from avoided downtime and avoided violations, not from savings on the $1.25 fees.

Which eligibility checks stay as fixed rules and where software assists

Whether a driver may drive is a yes-or-no rule that should be computed from query results and dates, never inferred. Software and AI earn their place in chasing people, reading letters and matching identities, with a named person confirming the output.

Evaluating a Clearinghouse workflow before you buy or build one

Judge any compliance tool or consortium service by whether it closes the gap between a query result and a load assignment. A dashboard that shows the right status to the safety team but not to dispatch leaves the original failure in place.

This page differs from our article on the customs query document workflow, which deals with answering questions raised by a customs authority; the shared word "query" is the only overlap. Use the table below as a demonstration script for vendors or as acceptance criteria for an internal build.

If your current TMS cannot hold a driver eligibility flag, or your safety and recruiting records sit in separate tools that never reach dispatch, write those requirements down and send them through our project request form. More transport compliance and dispatch guides are collected in the logistics and supply chain section.