Who this is for: fleet managers, compliance assistants, owner-operators
Limited vs. Full Clearinghouse Query — What's the Difference?
A limited query tells you if a driver has a Clearinghouse record (yes or no) without showing details. A full query shows the complete violation record. Pre-employment requires a full query. Annual queries use limited queries first.
Limited query
A limited query indicates whether a driver has a record in the Clearinghouse — it returns a "record exists" or "no record found" response. It does not show the details of any violation. Limited queries do not require driver consent. They are used for the annual query requirement for current drivers.
Full query
A full query returns complete information about any Clearinghouse violations, including the type of violation, the date, the test result, and the driver's current status (prohibited or returned to duty). A full query requires the driver's electronic consent. Full queries are required for pre-employment and whenever a limited query returns "record exists."
Query cost and frequency
The Clearinghouse charges a per-query fee. Employers receive a set number of free queries per year; beyond that, additional queries are billed. Check the current fee schedule at clearinghouse.fmcsa.dot.gov. Plan your query schedule to meet all requirements while staying within budget.
When each query type is used
Pre-employment always requires a full query — limited queries are not permitted for this purpose. Annual queries always start with a limited query. If the limited query returns "record exists," you must then run a full query. The two-step approach for annual queries conserves full query fees for the cases where they are actually needed, while still satisfying the annual review requirement for drivers with no record. A driver with no violations will never require a full query on an annual basis unless their status changes.
When a limited query becomes a full query obligation
Once an annual limited query returns "record exists," running the full query is not optional — it is required. Knowing a driver may have a violation and not following up with a full query is worse than not running the query at all; it creates documented knowledge of a potential problem without action. Run the full query promptly, review the result, and take the appropriate action based on whether the driver is prohibited or has a resolved status.
Common mistakes with query type
Two errors come up in compliance reviews. First: using a limited query for pre-employment instead of a full query. A limited query doesn't satisfy the pre-employment requirement. If you run a limited query pre-employment and it returns a record, you've now documented awareness of a potential problem without taking the required step — that's worse than not querying at all. Second: running a full query for annual purposes without first obtaining driver consent. Full queries require consent. Running one without it is a Clearinghouse violation in its own right. Use the right query type for each required purpose, and document what was run and when.
Saving documentation that identifies the query type
The Clearinghouse portal labels query results with the query type — "pre-employment full query" and "annual limited query" appear in the results output. When you save or print the result for the DQ file, save the page that includes this label, not just a generic confirmation. A stack of query documents with no indication of which type was run creates ambiguity about whether required query types were actually completed — which matters in a compliance review when someone is checking whether pre-employment was done as a full query, not a limited one.
Frequently Asked Questions
Can a carrier run a full query instead of a limited query for the annual requirement?
Yes. Full queries satisfy the annual requirement. Some carriers run full annual queries for all drivers to get complete violation detail, accepting the higher fee. This is acceptable but requires driver consent for each full query, since full queries are not consent-free like limited queries.
What if a driver's consent for a full query expires before I run it?
Driver consent in the Clearinghouse portal has a limited validity window — typically 30 days from when the driver grants it. If you don't run the query within that window, the consent lapses and you'll need to request it again. For pre-employment queries, initiate the consent request early and run the query promptly once consent is received.
Does a "no record found" result on a limited query mean the driver has never had any drug or alcohol violation?
"No record found" means the driver has no violations in the Clearinghouse since January 6, 2020. It does not cover violations from before that date, which must be investigated through previous employer safety performance inquiries under 49 CFR 391.23. A clean Clearinghouse result is necessary but not sufficient for establishing a complete pre-employment history.
If we run a limited query and it returns "record exists," how quickly must we follow up with the full query?
The regulation does not specify a deadline for running the full query after a limited query shows a record, but best practice is to act immediately — request driver consent the same day. The driver should not continue to perform safety-sensitive functions while you wait. If the full query then shows a prohibited status, the driver must be removed from operation immediately.