Annual Clearinghouse query requirements

Annual FMCSA Clearinghouse query requirements apply to every employer of CDL drivers. The employer must query the Drug and Alcohol Clearinghouse at least once a year for each driver it employs, under §382.701(b), and must run a full query before a new driver performs any safety-sensitive function, under §382.701(a). The annual query can be a limited query, which tells you only whether the Clearinghouse holds anything on the driver. If it does, you have 24 hours to run a full query with the driver's electronic consent, and if you miss that window the driver cannot drive until the full query comes back clean. An owner-operator is the employer of a CDL driver and queries themselves, through a consortium or third-party administrator. Below: who has to query, the two kinds of query, how the year is counted, the 24-hour rule, what to keep, and the mistakes that show up in reviews.

Who has to query

The obligation sits on the employer, and it covers every driver "subject to controlled substance and alcohol testing under this part", which is Part 382. That means every driver who holds a CDL or a commercial learner's permit and operates a commercial motor vehicle that needs one. A driver who only ever drives a 20,000-pound straight truck on a regular licence is not in Part 382 and does not get queried. A driver who is in the pool for random testing is in the pool for the annual query, and the two lists should be identical.

An owner-operator is both. §382.705(b)(6) says an employer who employs themselves as a driver "must designate a C/TPA" to carry out the employer's reporting duties for their own testing, and the same C/TPA is how the owner-operator's queries are run. You register as an employer, designate the C/TPA, and the C/TPA queries you. Under §382.705(c) the employer keeps "ultimate responsibility" regardless of who does the work, so an owner-operator whose C/TPA forgot is an owner-operator with a missed query.

Drivers themselves have no query obligation. A driver who never registers can still be the subject of a limited query, because that consent is on paper, but cannot be the subject of a full query until they register, which is where pre-employment goes wrong for a lot of small carriers.

Pre-employment: a full query, before the driver drives

§382.701(a)(1) says an employer must not employ a driver to perform a safety-sensitive function "without first conducting a pre-employment query". Driving is a safety-sensitive function, so the query comes before the first trip, not within 30 days like the driving record inquiry in §391.23(a). Under §382.701(a)(2) this one has to be a full query, and a full query releases the record to the employer, which is why it needs the driver's specific consent given inside the Clearinghouse under §382.703(d).

The sequence is the practical problem. The employer requests the query, the driver logs in to their own Clearinghouse account and consents, then the result appears. A consent request that has not been answered is a query that has not been run, and requests can take most of a day to reach the driver's account. Send it before the orientation date, not on it.

The pre-employment query also does the job the old previous-employer letters used to do. §391.23(e) still requires an investigation of the driver's drug and alcohol history for the last three years, but since 6 January 2023 the Clearinghouse query satisfies it for employers regulated by FMCSA, under §382.413(b). Two exceptions remain. If the driver is partway through a follow-up testing plan, you ask the previous employer for the plan directly. And if the previous employer was regulated by another DOT agency, such as a transit or rail operator, the Clearinghouse does not hold that history and you write to them under §382.413(c).

Annual: a limited query is enough, until it is not

§382.701(b)(1) requires a query "at least once per year" for every employed driver in the testing pool. §382.701(b)(2) lets that query be a limited one. A limited query returns one of two answers: no information exists, or information exists. It does not say what the information is. That is the trade. It is cheaper in consent, because the driver signs a paper or electronic consent that the employer holds, and that consent "may be effective for more than one year". Many carriers take a multi-year limited-query consent at hire and never think about it again, which is fine as long as the consent itself is on file.

The two kinds of query, side by side:

How is the year counted? The rule says "at least once per year" and does not define the year. The safe reading is the strict one: the next query is due no later than 365 days after the previous one, counted from the date of the last query rather than from the calendar, and the pre-employment full query starts the clock for a new hire. A carrier that runs every driver on the same day each January is compliant. A carrier that ran the queries in March one year and the following April has a gap for every driver, and the gap is visible in the Clearinghouse's own query history, which is what an investigator will look at.

A full query satisfies the annual requirement too. If you ran a full query on a driver for any reason, that is the year's query. There is no need to run a limited one on top.

The 24-hour rule

§382.701(b)(3) is the paragraph that turns a limited query from a formality into something with a clock on it. If the limited query shows that information exists, the employer "must conduct a full query, in accordance with paragraph (a)(2) of this section, within 24 hours of conducting the limited query". The clock starts when the limited query is run, not when somebody reads the result.

The consequence of missing it is in the same paragraph. If the full query is not done within 24 hours, the employer "must not allow the driver to continue to perform any safety-sensitive function" until the full query is done and shows no prohibition under §382.701(d). Read that carefully. Inside the 24 hours the driver can keep working. After it, the driver is off safety-sensitive duty by operation of the rule, whatever the record turns out to say, until the full query clears them. A driver whose record shows a completed return-to-duty process, with the negative test and the follow-up plan done, is not prohibited and can drive. A driver whose record shows a violation with no return-to-duty is prohibited under §382.701(d) and cannot.

The full query needs the driver's electronic consent inside the Clearinghouse, and the driver is the one person in the process with no deadline. A driver who refuses consent cannot perform safety-sensitive functions under §382.703(c), but a driver who is simply unreachable for a day has run out the clock for you. Run limited queries on a day when drivers are reachable, not on a Friday afternoon.

One more clock, in the employer's favour. Under §382.701(c), if information about a driver is entered within 30 days after you queried them, FMCSA notifies you. After that, nothing arrives until you query again, which is the reason the annual query exists.

What to keep, and for how long

§382.701(e) requires an employer to keep "for 3 years a record of each query and all information received in response to each query". Since 6 January 2023 the same paragraph says an employer with a valid Clearinghouse registration meets that requirement through the Clearinghouse itself, because the query history is stored there. That is a genuine relief and a small trap. The history is there for as long as your registration is valid. Let the registration lapse, or lose access to the account when the person who set it up leaves, and the record is somewhere you cannot reproduce it from.

The consent is separate. §382.703(a) requires the employer to keep the driver's written or electronic consent to limited queries for three years after the last query it was used for. The Clearinghouse does not hold this one, because it was given outside the Clearinghouse. It lives with your other Part 382 records, and it is the item most often missing when an investigator asks to see the basis for a limited query. Full-query consent is recorded inside the Clearinghouse and shows on the query record.

Where the records go matters as much as how long. Query results that contain violation information are drug and alcohol records, and §382.405 restricts who may see them. They do not belong in the driver qualification file, which is a file you hand to a reviewer. A note that the query was run and its date can go in the DQ file without harm; the result stays with the Part 382 records. The retention guide has the full schedule, and the DQ file guide covers what that file is and is not for.

Clearinghouse-II and the state licensing agency

Since 18 November 2024 the Clearinghouse has been wired into the CDL itself. Under §382.725(a)(2) a state licensing agency must check the Clearinghouse before it issues, renews, transfers or upgrades a CDL or learner's permit, and under §383.73(q) a state that is told a driver is prohibited must begin its downgrade procedure and complete it on the driver's record within 60 days. The driver's commercial privilege comes off the licence, and under §382.503(b) the driver may not drive a commercial motor vehicle until the state reinstates it, which happens when the Clearinghouse reports the driver is no longer prohibited.

What this means for a carrier is that a prohibited driver now shows up in two places: the Clearinghouse, and the driving record you pull for the annual review under §391.25. It does not mean the driving record replaces the query. The downgrade can take up to 60 days, the driving record is pulled once a year, and a driver can be prohibited and still hold a valid-looking CDL for weeks. The query is the current answer. The driving record is the confirmation, later.

Common mistakes

• Counting the year from January. The rule is once per year, and the query history in the Clearinghouse shows the date of the last one. A carrier that queried everyone in March and then in the following April has a gap on every driver. Count from the last query.
• Running the pre-employment query after the first trip. The driver was needed, the request was sent, and the driver started work while it waited for consent. §382.701(a)(1) says "without first conducting", and the query record shows the date the result came back, next to the first log.
• Asking for a full query on a driver who has not registered. The request sits unanswered. Nothing in the Clearinghouse tells the employer why. Ask at the interview whether the driver has an account, and if not, have them create one before the start date.
• Assuming the C/TPA did it. A C/TPA queries the drivers it has been told about, on the schedule it has been given. A driver added in June who was never sent to the C/TPA has no query, and under §382.705(c) that is the employer's problem.
• Not keeping the limited-query consent. The query is in the Clearinghouse; the consent for it is not. A limited query with no consent on file is a query the employer cannot show it was entitled to run.
• Reading "information exists" as "prohibited". It is not. A driver who completed return-to-duty years ago has a record, and a limited query on them will always come back with information. The full query is what tells you whether they are prohibited, and it has to be run within 24 hours every time.
• Losing the account. The registration is tied to a personal login. When that person leaves, so does access to the query history. Add a second administrator before you need one.

Do you need software for this?

Not for the query. The query runs on the federal portal and nowhere else, and no software can run it for you; a C/TPA can, and for an owner-operator must. What is left over is arithmetic. Which driver is due, from what date, and whether the 24 hours after a limited query have passed. With three drivers that is a wall calendar and a folder for the consent forms, and it is compliant. Somewhere around five drivers, with hires and departures across the year, the dates stop lining up and the one that gets missed is the driver who was hired in a busy month. That is the part Ledger Road tracks: each query's date, the next one counted from it, and the 24-hour clock when a limited query finds something. The spreadsheet guide covers where that line falls for the rest of the records.