Clearinghouse annual queries: what carriers track in 2026

You hire a driver on Monday and dispatch them Tuesday. Your safety manager runs the usual license and medical checks, but the Drug and Alcohol Clearinghouse query sits in a separate queue with its own consent form and receipt. Six months later, an auditor asks for proof that every employed driver received an annual limited query within the last 365 days. If your team treats Clearinghouse work as “HR paperwork” instead of a dated compliance record, those two moments—the hire and the audit—are where the file falls apart.

The Clearinghouse rules live in 49 CFR part 382, not inside the qualification file list at § 391.51. That separation matters operationally: consent, query results, and follow-up full queries belong in controlled Part 382 files, while your qualification workflow still needs visible due dates so reviewers see one timeline for each driver.

Key takeaways

• Run a pre-employment full query with driver consent before the driver performs safety-sensitive functions, as required by § 382.701.
• Run a limited query at least once every 365 days for each driver you employ; if the limited query indicates information exists, run a full query within 24 hours.
• Store consent and query receipts where only authorized safety staff can retrieve them; track last query date and next due date beside MVR and medical tasks in your qualification process.
• A missed annual query is a documentation problem you can see coming—if you calendar it the same way you calendar annual MVR reviews.

The annual limited query is not a reminder on a sticky note—it is a record you must produce, with dates that match what FMCSA expects under Part 382.

Why annual Clearinghouse queries slip past busy safety teams

Mid-size fleets often execute the pre-employment full query cleanly because onboarding checklists are front and center. The annual limited query is easier to defer. Drivers stay employed for years, dispatchers rotate, and the spreadsheet that held query dates moves with a departed safety coordinator. § 382.701(b) requires at least one limited query in every 365-day period for each employed driver, not once per terminal and not once per company spreadsheet row labeled “fleet.”

Picture a regional carrier hiring three drivers in one week. Each needs a full query before safety-sensitive work; that query shows violation detail if any exists. Six months later, each still needs the limited query on its own anniversary. When a limited query indicates information in the Clearinghouse, you must run a full query within 24 hours—a handoff that fails if only one person knows the login. Both query types require consent filed with the receipt; a refusal means you cannot run the query and cannot use that driver in safety-sensitive functions until the situation is resolved under your policy and Part 382.

The practical fix is to treat query anniversaries like license expirations: one date field per driver, updated the day the receipt lands, reviewed in the same meeting where you scan annual MVR due dates. Our Clearinghouse query basics guide defines query types without mixing them into § 391.51 tabs.

If your safety team already meets weekly on file status, add two columns: last limited query and next limited due. Drivers who transferred from an affiliate need a new row, not an inherited “green” cell from another entity. When FMCSA updates consent language, replace stored forms prospectively for new queries—do not assume a five-year-old PDF still matches program requirements.

Where Clearinghouse records live versus qualification file work

Carriers store Clearinghouse consent and receipts with the controlled drug-and-alcohol file while showing last query and next due on the qualification dashboard. That mirrors FMCSA’s split between Part 382 and Part 391. Dispatch may need to know a driver is not cleared for safety-sensitive work, but terminal staff should not browse detailed violation histories unless your access policy explicitly allows it. Role-based access keeps hiring decision makers and safety staff on the retrieval path while others see status flags you control.

Owner-operators and leased drivers who perform safety-sensitive functions under your USDOT number follow the same query rules. Each employment relationship gets its own queries and receipts; another carrier’s receipt does not satisfy your file. Pair Clearinghouse tasks at hire with pre-employment inquiries and § 391.51 onboarding so new staff learn which portal answers which regulation.

Terminal managers may ask whether a driver is “Clearinghouse cleared.” Define what you share: a status flag and due date, not query result PDFs on a shared drive. The Clearinghouse query glossary entry helps align language between safety, HR, and dispatch so questions do not turn into improvised file browsing.

Showing Clearinghouse query proof when investigators sample drivers

When a review moves beyond roadside credentials, investigators may ask for proof that required queries ran for named drivers. They expect consent, query type, run date, and results that align with employment periods. Opaque PDF names force reviewers to guess; a cover sheet per driver prevents that waste even when the underlying queries were timely.

Answer Clearinghouse questions from Part 382 files first. If the sample also opens driver qualification files, that is a separate checklist—application, MVR history, medical evidence, road test documentation under § 391.51. Mixing both stories in one email thread confuses which rule you are satisfying. If a driver leaves mid-cycle, retain query documentation for the employment window FMCSA expects for Part 382 records, and note employment end dates on your cover sheet.

Investigators may sample drivers who worked only part of the review period. Your cover sheet should tie each query to employment start and end so nobody has to reconstruct timelines from inbox subjects. Practice that narrative once before you need it under a deadline.

Common Clearinghouse mistakes and what to fix this week

Teams often treat a hire-day limited query as the annual query—it is not. Others calendar anniversaries from hire date but miss drivers who transferred from an affiliate without a new query row. Storing consent once without checking updated FMCSA consent language is another gap; review Clearinghouse program materials when compliance bulletins change. Software that marks drivers “compliant” on qualification items alone can hide overdue limited queries unless query due dates sit beside MVR dates on the report safety managers already read.

This week, export every employed driver with last limited query date, sort oldest first, and schedule anyone within 30 days of the 365-day window. Confirm pre-employment full queries for hires in the last 90 days. Build one sample packet—consent plus receipts—as you would hand it to an auditor; if you struggle to follow it, reorganize before someone else asks.

Keep the cycle visible after hire

Clearinghouse compliance is recurring work, not a launch-day project. Calendar limited queries with the same discipline as driver qualification files, and teach new safety staff where consent and receipts live before audit season. When you want a structured starting point, continue with our Clearinghouse query basics guide—then map those steps to the dates already on your driver list.

Sources

• 49 CFR 382.701 — Database queries
• 49 CFR 391.51 — General requirements for driver qualification files
• 49 CFR 391.25 — Annual inquiry and review of driving record
• FMCSA — Drug and Alcohol Clearinghouse