Key Takeaways
- 49 CFR 382.701(b)(1) requires a query at least once per year for every employee subject to testing.
- The duty attaches to each driver, so a carrier with 200 CDL holders has 200 separate positions in the cycle.
- Where a limited query reports that information exists, a full query is due within 24 hours of the limited one.
- Miss that window and the driver must not perform a safety-sensitive function until the full query comes back clear.
- Query records and everything received in response are kept 3 years from the date of the query itself.
Most fleets run their Clearinghouse queries as one January job and treat the year as covered. The duty was never a fleet duty, and the arithmetic belongs to each driver separately. An investigator reading 1 file does not care what the fleet did in January, because the question on that page is the gap between this driver's own query dates.
Each driver brings their own clock because the regulation attaches the duty to the employee. That duty gives a carrier with 200 CDL holders 200 separate positions to keep track of. One January date cannot cover 200 positions at once.
So the work is to turn one annual event into a rolling schedule. That schedule has 3 inputs, because the rule is short, the deadline after a limited query is tight, and the record you keep is defined to the year. Reading the 3 together is what makes the schedule build itself.
What 382.701 Says About Timing
Timing in 49 CFR 382.701 is set in 2 places and reads more plainly than its reputation. The first of those 2 places, paragraph (a), requires a full query before a driver first performs a safety-sensitive function for you. Paragraph (b)(1) then requires a query of the Clearinghouse at least once per year for every employee subject to testing.
Those are the regulation's own words, and the precise phrase matters when you write policy. The rule says "at least once per year" and does not describe a 365-day window. FMCSA guidance reads that annual duty as running from the previous annual query, which is why a per-driver cycle is the standard way to meet it.
Why the Per-Driver Reading Is the Safe One
Policy written to the fleet calendar leaves gaps that a file review finds immediately. A driver hired in March and queried that month has a March position in the cycle. Rolling them into the following January batch is compliant, and rolling them into the January after that is not. A March driver carried to the second January sits 22 months out, which is the finding an investigator writes.
Because each driver's position moves whenever you query them, the schedule has to be recalculated at the moment of the query. A carrier that records the next due date while completing the current query never has to reconstruct it later. That single habit removes most of the exposure here.
The 24-Hour Rule After a Limited Query
Recalculating the date is simple, and the one deadline inside the rule is tighter. A limited query reports only whether information exists in a driver's Clearinghouse record. Where it reports that information exists, paragraph (b)(3) requires a full query within 24 hours of conducting the limited one.
Missing that window has an immediate operational consequence. The driver must not perform any safety-sensitive function until the full query is complete and the result that comes back shows no prohibition against them. That same limited query also satisfies the annual duty on its own, provided the driver's consent is already on file.
The 4 Timing Rules in One Place
Consent and timing together settle most of the questions a fleet asks:
What triggers it | When it is due | Where it is written |
|---|---|---|
A new driver, before the first safety-sensitive function | Before that function is performed | 382.701(a) |
Every employee subject to testing | At least once per year | 382.701(b)(1) |
A limited query reporting that information exists | A full query within 24 hours | 382.701(b)(3) |
Any completed query | Records kept 3 years from the query date | 382.701(e) |
Reading down the middle column shows how different those 4 deadlines are from each other. One is an event, one is a cycle, one is a countdown in hours, and the last is a retention period. A single annual reminder covers only the second of them. A calendar built on that one reminder therefore satisfies 1 of the 4 timing requirements and leaves the other 3 of them to somebody's memory at the end of a long week.
Put a due date on the training as well as the query.
KC LMS assigns by role, holds a due date on every assignment, and keeps a dated completion record your Part 382 file can produce.
What You Keep, and for How Long
Retention is the fourth of those deadlines and the one most often under-built. Paragraph (e) requires an employer to retain a record of each query and all information received in response for 3 years from the date of the query. That period runs from the query itself and not from the end of any calendar year, so a schedule built around calendar years will expire some records early.
A practical file carries more than the regulation names. Keeping the signed consent beside the query record, with the date it was obtained, answers the question an investigator asks before looking at the query at all. The rule sets no separate period for that consent, so your own retention policy governs it.
Where Supervisor Training Fits the Same Calendar
The same file usually has to answer a second question about training. Under 49 CFR 382.603 every supervisor designated to determine whether reasonable suspicion testing is required must receive at least 60 minutes of training on alcohol misuse. They must receive at least an additional 60 minutes on controlled substances use.
Those 2 hours are a one-time requirement in the rule and a recurring one in practice. Supervisors move, new ones are promoted, and a file showing training for a supervisor who left in 2024 proves nothing at all about the person making that call on the road today. Pairing the training check with the query cycle keeps both answers current in the same review, and a content library refreshed every week keeps the modules themselves from drifting.
What KC LMS Gives a Fleet Compliance Team
Both answers come from the same place, which is a record with a date and a name on it. The Clearinghouse records your queries, and nothing in it tracks whether the supervisor who made a reasonable suspicion call had completed the 2 hours. Your training file is the only place that second answer exists, and it has to be producible for the person who was on duty that day.
KC LMS assigns courses from the attributes your HR record already holds, so a newly promoted supervisor receives the 382.603 modules without anybody maintaining a list. Each assignment carries a due date, completion is recorded against the person with a date, and the reporting reads across person, course and assignment. Certificates hold an expiry date where your policy sets one, and a refresher is stored with the assignment it belongs to.
For a transportation and logistics business, the pattern is the same on both sides of the file. Calculate the next date at the moment you complete the current one, for the query and for the training. DOT drug and alcohol testing compliance stops depending on anyone remembering what January covered.
Frequently Asked Questions
1. How often must an employer query the Clearinghouse for a current driver?
At least once per year, which is the phrase 49 CFR 382.701(b)(1) uses. FMCSA guidance reads that as running from the previous annual query, so each driver holds their own position in the cycle. A fleet-wide January batch meets it only while every driver's previous query falls inside the year.
2. Does a limited query satisfy the annual requirement?
Yes, provided the driver's consent is already on file. A limited query reports only whether information exists in the record. If it reports that information exists, the employer must conduct a full query within 24 hours of the limited one.
3. What happens if the full query is late?
The driver must not perform any safety-sensitive function until the full query is complete and the result shows no prohibition. The consequence attaches to the missed deadline itself, so it applies even where the full query eventually comes back clear.
4. How long must query records be kept?
Three years from the date of the query. 49 CFR 382.701(e) requires a record of each query and all information received in response. The period runs from the query itself, so a retention schedule built around calendar years will expire some records early.
5. How much supervisor training does 382.603 require?
At least 60 minutes on alcohol misuse and at least an additional 60 minutes on controlled substances use, for designated supervisors. The rule states it as a quantity of training rather than a repeating cycle, so keeping it current for the people actually doing the job is a matter of policy.
References
- 49 CFR 382.701, Drug and Alcohol Clearinghouse queries.
- 49 CFR 382.603, Training for supervisors.
- FMCSA. Drug and Alcohol Clearinghouse, February 2025 Monthly Summary Report.
- FMCSA. What is the annual requirement for employee queries?.
- FMCSA. What is the difference between a full and limited query?.