Compliance
Clearinghouse Annual Query: The Yearly Check Carriers Forget
By Editorial Team · Updated July 9, 2026 · 12 min read · Editorial standards
On this page 8 sections
You ran the full query the day you hired her. Fifteen months later she’s still on your board, hauling loads every week, and nobody ever ran another Clearinghouse check. That silent gap is a violation, and it’s the one auditors love because it shows up cold in your records. The pre-employment query gets all the attention, but the clearinghouse annual query is the recurring obligation that actually trips carriers up. Here’s who needs one, why a cheaper limited query usually covers it, and the 24-hour deadline that turns a routine check into an emergency.
What is the clearinghouse annual query, and who has to run it?
Every FMCSA-regulated employer must run at least one query in the Drug and Alcohol Clearinghouse for each CDL driver it employs at least once every 12 months. That rule lives in 49 CFR 382.701(b), and it applies whether the driver has been with you a decade or joined last quarter. There is no exemption for long-tenured, clean-record drivers, and no credit for the pre-employment query you already ran. The annual obligation is separate and continuous for the entire time a driver stays on your roster.
The mechanism is a rolling 12-month window measured per driver, not a single company-wide date. If you queried a driver on August 3, you have until the following August 3 to run the next one. Carriers get burned by treating this as an annual event they do once every January. Run it that way and any driver hired in October quietly blows past their individual 12-month mark before your next batch. The fmcsa clearinghouse annual query is a per-driver clock, and the safest practice is to track a next-due date on each driver’s qualification file.
Who counts as a driver you “employ”? Anyone who operates a commercial motor vehicle requiring a CDL for you, including owner-operators. If you are an owner-operator with no other employees, FMCSA requires you to designate a consortium/third-party administrator (C/TPA) to run queries on your behalf, because you can’t be your own querying employer. This obligation is one slice of your broader DOT compliance program for trucking companies, and it sits right alongside your random testing and driver qualification files.
Limited query vs full query: what’s the difference?
A limited query tells you only whether information exists in a driver’s Clearinghouse record; a full query tells you what that information actually is. That single distinction drives everything about how you run the annual check, what consent you need, and whether the driver has to touch a computer. Understanding the mechanism first saves you from over-buying full queries you don’t need or, worse, running the wrong consent type.
A limited query clearinghouse search returns a yes-or-no signal: either the record is clean or “information exists.” It does not show you the violation, the substance, the date, or the return-to-duty status. A full query returns the underlying details, including any unresolved prohibition that would bar the driver from operating. Because a limited query exposes no protected detail, FMCSA lets it run on a general consent the driver signs outside the system. A full query, which surfaces sensitive violation data, requires the driver’s specific electronic consent inside their own Clearinghouse account.
| Limited query | Full query | |
|---|---|---|
| What it shows | Only whether any information exists in the driver’s record | The specific violations, return-to-duty status, and any active prohibition |
| Consent type | General consent signed outside the Clearinghouse (paper or e-sign you retain) | Electronic consent the driver grants inside the Clearinghouse |
| Driver login needed? | No | Yes, the driver must register and consent in the Clearinghouse |
| When it’s used | Satisfies the once-a-year check for current drivers under 382.701(b) | Required pre-employment, and within 24 hours after a limited query shows information exists |
| Typical cost | Per-query fee from your prepaid query plan (verify current pricing) | Per-query fee from your prepaid query plan (verify current pricing) |
Query fees are purchased in advance through a query plan on the FMCSA Clearinghouse site. Pricing has held at a low per-query rate for years, but confirm the current amount when you buy, since fees can change. For a deeper walkthrough of query types and how they fit the hiring flow, see our guide on how to run an FMCSA Clearinghouse query.
Why the annual query can be a limited query, and what consent you need
You can satisfy the annual requirement with a limited query, and doing so is both cheaper and easier on the driver because it never requires them to log in. The reason sits in the consent rules at 49 CFR 382.703. A limited query runs on general consent the driver signs once, outside the Clearinghouse, authorizing you to check whether information exists in their record. That consent can be a standalone paper form or an electronic signature you capture and store, and it can be worded to cover queries over a defined period so you aren’t chasing a new signature every year.
This is where the annual query differs sharply from the pre-employment process. The pre-employment full query demands the driver’s specific electronic consent granted inside their Clearinghouse account, driver by driver, every time. The annual limited query needs none of that in-system interaction, which is exactly why it’s the right default for current employees. If you want the full picture of the different consent types and when each applies, our explainer on Clearinghouse requirements and driver consent breaks them down side by side.
The record-keeping catch bites carriers here. The general consent is not optional paperwork you can skip because the query “came back clean.” You must retain the signed general consent and a record of each query you run. Retention is generally at least three years under Part 382, though you should verify the current rule for your record type before you dispose of anything. Missing consent for a query you ran is its own finding, separate from failing to run the query at all.
How to run the annual query, step by step
Running the annual query is a short procedure, but each step has a gotcha that turns a five-minute task into a compliance gap. Here is the sequence, what’s federally required versus merely smart, and the mistake that catches carriers at each stage.
Build a per-driver query calendar
What you do: List every CDL driver you employ and record the date of their last Clearinghouse query. Set each driver’s next-due date at 12 months out.
Required or smart? The 12-month cadence is federally required by 382.701(b). The calendar itself is smart practice, but without it you have no defensible way to prove you met the deadline for every driver.
The gotcha: Treating the annual query as one company-wide event. A driver hired mid-year hits their individual 12-month mark on their own schedule, and a single January batch will let them lapse.
Collect general consent for limited queries
What you do: Have each driver sign a general consent authorizing limited queries, either on paper or by e-signature, and file it.
Required or smart? Required by 382.703 before you can run a limited query. Wording the consent to cover a period rather than a single query is smart and saves annual re-signing.
The gotcha: Running the limited query first and backfilling consent later. The consent must exist before the query, and an auditor will check the dates.
Register and fund a query plan
What you do: Register your company in the FMCSA Clearinghouse, designate your querying user, and buy a prepaid query bundle. Owner-operators without employees must appoint a C/TPA to do this.
Required or smart? Registration and a funded query plan are prerequisites to running any query. Verify the current per-query fee at purchase.
The gotcha: Assuming your C/TPA automatically runs annual queries. Confirm in writing who owns the annual cadence, because the legal obligation stays with you as the employer.
Run the limited query
What you do: Enter the driver’s information and run the limited query against your consent on file. Read the result: clean, or “information exists.”
Required or smart? Running at least one query per driver per year is the core federal requirement. Choosing a limited query over a full query is your call and is the cheaper, lower-friction option.
The gotcha: A limited query that shows information exists is not the finish line. It starts a clock, covered next.
On a hit, run a full query within 24 hours
What you do: If the limited query shows information exists, obtain the driver’s electronic consent and run a full query within 24 hours.
Required or smart? Federally required by 382.701(b). If you cannot complete the full query within 24 hours, you must not allow the driver to perform safety-sensitive functions until the full query is done and shows the driver is not prohibited.
The gotcha: Letting the driver keep running loads while you sort out the full query. Once a limited query flags information and the 24-hour window passes without a completed full query, that driver has to come off safety-sensitive duty.
Retain consent and query records
What you do: File the signed general consent, the query result, and the date, for each driver.
Required or smart? Required. Retention is generally at least three years under Part 382; verify the current rule for your record type.
The gotcha: Purging on your own schedule. Keep the paper trail long enough to survive an audit, because “we ran it” without a record reads the same as never running it.
What happens if a limited query returns a hit?
A limited query that reports “information exists” triggers a mandatory full query within 24 hours, and until that full query clears the driver, they may have to stop driving. This is the single most misunderstood part of the annual process. The limited query is designed to be a cheap tripwire, not an answer. When it trips, 382.701(b) requires you to escalate immediately: get the driver’s electronic consent, run the full query, and read what the record actually contains.
If the full query is completed within 24 hours and shows no prohibition, the driver continues normally. If you can’t complete it within 24 hours, the driver cannot perform safety-sensitive functions until the full query is finished and comes back clean. A full query that reveals an unresolved prohibition means the driver is barred from operating a commercial motor vehicle until they complete the return-to-duty process with a substance abuse professional. For the mechanics of how violations, return-to-duty, and prohibited status work inside the database, see our overview of the FMCSA Drug and Alcohol Clearinghouse.
What the annual query does not tell you
The annual query is airtight on one thing and blind on another. It confirms whether a driver has a federal drug or alcohol program violation on record. It says nothing about how that driver behaved for the carriers who employed them. A perfectly clean Clearinghouse record sits comfortably next to a history of no-shows, loads abandoned at a truck stop, equipment returned trashed, and a resignation by text message on a Friday. None of that is a testing violation, so none of it reaches the Clearinghouse, the MVR, or the PSP.
That behavior gap is what a peer-sourced driver-review database is built to cover. Alongside your required annual query, you can search a driver by name and read what past carriers reported about reliability, dispatch cooperation, and whether they’d rehire. CDLScan lists more than 1 million driver reviews and runs around 20,000 searches a week; the search itself is free, with a full report starting at $2.75. It doesn’t replace your Clearinghouse query, MVR, or PSP check, and it is not a federal record. It’s the added behavior layer those required checks were never designed to capture.
Frequently asked questions
How often do I have to run a clearinghouse annual query? At least once every 12 months for each CDL driver you employ, per 49 CFR 382.701(b). The 12-month window is measured individually from each driver’s last query date, not as a single company-wide date, so track a next-due date per driver.
Can the annual query be a limited query, or does it have to be a full query? The annual check can be a limited query. A limited query only reveals whether information exists in the driver’s record, and it runs on a general consent the driver signs outside the Clearinghouse, so it’s the cheaper and lower-friction option for current employees.
What is a limited query clearinghouse check, and how is its consent different? A limited query clearinghouse search returns only a yes-or-no on whether any information exists, without the violation details. Because it exposes no sensitive data, it runs on a general written consent the driver signs outside the system, unlike a full query, which needs the driver’s electronic consent inside the Clearinghouse.
What happens if a limited query comes back showing information exists? You must obtain the driver’s electronic consent and run a full query within 24 hours under 382.701(b). If the full query is not completed within 24 hours, the driver cannot perform safety-sensitive functions until it is done and shows the driver is not prohibited.
Do I need the driver to log in for the annual query? Not for a limited query. It runs on the general consent you already hold, so the driver never touches the Clearinghouse. The driver only needs to log in and grant electronic consent if a hit forces you to run a full query.
How long do I keep the general consent and query records? Retain the signed general consent and a record of each query, generally for at least three years under Part 382. Retention periods can vary by record type, so verify the current rule before you dispose of anything.
Does the annual query replace the pre-employment full query? No. They are separate obligations. The pre-employment full query is a one-time requirement before hiring, with in-system electronic consent, while the annual query is a recurring 12-month check that can be satisfied with a limited query on general consent.
What are the clearinghouse annual query requirements for owner-operators? The clearinghouse annual query requirements still apply to owner-operators, but a driver who employs themselves cannot be their own querying employer. FMCSA requires owner-operators without other employees to designate a consortium/third-party administrator (C/TPA) to run the annual query on their behalf.