Clearinghouse is the zone where beginners get sweaty palms. It sounds scary, there are a lot of buttons, a lot of English-language terms, and any mistake smells like a fine. I'll walk you through it. After this chapter, you'll stop being afraid of Clearinghouse and start using it like a regular tool β roughly, like email. Because that's basically what it is: email for drug tests.
9.1. What this beast is and why it exists
Drug & Alcohol Clearinghouse is a federal FMCSA database that collects information on every failed drug test and every refusal to test among US CDL drivers. It's been live since January 6, 2020.
The point is simple: a driver who fails a test at one company shouldn't be able to quietly slip over to another one and get behind the wheel. Before 2020, that happened all the time.
How it used to work before Clearinghouse
Here's the classic scenario the industry watched for years. A driver works at Company A, fails a random. Company A lets him go. He writes a rΓ©sumΓ©, leaves Company A off it entirely, and two weeks later he's hired at Company B. Company B is legally required to request data from previous employers β but if the previous employer isn't listed, there's nothing to request. The driver is back behind 80,000 pounds of steel. No rehab. No Return-to-Duty test.
It ended in crashes. Sometimes fatalities.
In 2020, FMCSA closed the hole. Failures are now stored in a centralized database, and any employer can see them when hiring. The driver can't hide anymore.
What goes into the database
- Positive drug test.
- Positive alcohol test (BAC 0.04 or higher).
- Refusal to test (refusal is treated as a failure).
- On-duty use witnessed by observation.
- Completion of a Return-to-Duty program.
- Follow-up test results.
Who has to deal with Clearinghouse
Everyone with a USDOT/MC Authority. Plus MROs (medical review officers), SAP specialists, TPAs, and the drivers themselves.
π« Pause. What's running through your head right now: "company registration, driver registration, consents, limited query, full query, annual, pre-employment, planβ¦ I'm going to drown." Stop that thought. This entire structure boils down to three actions that you repeat for the rest of your career: 1. Once β register the company. 2. With every new hire β run a pre-employment query. 3. Every January β run annual queries on everyone active. The rest is interface details. You learn the interface in two weeks. Let's go.
9.2. How it works at the logic level
Picture Clearinghouse as a locked archive. Inside, there's a folder on every CDL driver in the country. Most folders are empty. Some have records.
To look inside a specific driver's folder, you need to:
- Have a company account in Clearinghouse.
- Buy a query β one query = one look inside.
- Get the driver's consent β without his electronic consent, the folder doesn't open.
- Read what's in there.
That's it. That's the whole mechanism.
Two types of query
- Limited Query β a quick scan. The database answers in one word: "records exist" or "no records." No details shown. Used for annual checks on existing drivers. If you get "records exist," you've got 24 hours to follow up with a Full Query and find out what's actually there.
- Full Query β the complete file: type of violation, date, rehab status. Required before hiring any new driver.
What it costs
Queries are sold in bundles. Ballpark β $1.25 each (a pack of 50 runs $62.50). For a 3β10 truck company, 20β30 queries a year covers everything with room to spare.
9.3. Registering the company in Clearinghouse
π΅ Owner. If the company is new β you do this yourself. Not a dispatcher, not an accountant, not "a friend with experience." Clearinghouse is one of the first steps after you get your MC Authority.
π’ Employed Safety. The first thing you do at a new company is check: is there a Clearinghouse account or not? If not β create one. If yes β take access over from the owner and switch it to current credentials (your corporate email, your phone for 2FA).
What you need before starting
FMCSA Portal account β an account on the main FMCSA portal. If you don't have one β register that first, then Clearinghouse. Pain point: the FMCSA Portal sometimes requires PIN verification that's mailed to the company address via regular mail. That can take 1β2 weeks. Budget that time, don't leave it to the last minute.
Step by step
1. clearinghouse.fmcsa.dot.gov β Register.
2. Role: Employer with a FMCSA Portal account.
3. Corporate email. Not johnny1985@gmail.com. Set up safety@yourcompany.com or at least compliance@. I'll explain why below.
4. Follow the link in the email β create a password β immediately save it in a password manager (1Password, Bitwarden, whatever). A month from now you won't remember it.
5. Authentication Method β the second factor:
- Phone (SMS).
- Authentication App (Google Authenticator).
- Backup Codes β 10 one-time codes.
Take Backup Codes. Print them, put them in a folder labeled "Clearinghouse β access," forget about them. When they run out β generate a new set. This is the most reliable option because it's not tied to a phone that can change or get lost.
6. Role: Employer. Confirm that the company operates under DOT drug & alcohol regulations β Yes.
7. FMCSA Portal login/password β the system will pull your company info automatically.
8. Verify Contact Information and Company Information (USDOT, address, phone).
9. If you're the owner β check "Yes, I am an Owner Operator."
10. Accept terms. Done.
β οΈ A mistake I see constantly. Owner registers Clearinghouse on his personal Gmail. Six months later β changes phones, loses email access, forgets the password. Six months after that β an audit shows up. The company has no access to its federal portal. Recovering it through FMCSA means weeks of correspondence and notarized documents. The audit isn't going to wait. Corporate email from day one. Ten minutes of setup, zero problems down the road.
9.4. Registering the driver
By law, the driver registers in Clearinghouse himself. In practice β reality is different. Half the drivers don't know what Clearinghouse is. The other half know, but they sit at a computer once a year and get nervous at the word "email." You as the Safety do this with him. It's not "you for him" β it's "you next to him, he clicks the buttons."
Why this matters
Without an account, the driver can't give consent for your query. Without consent, the database won't show a result. Without a result, you have no right to put him in a truck. The chain breaks at the first link.
Step by step
1. Clearinghouse β Register β Create Account.
2. Email β the driver's real email, one he actually has access to. Not yours, not his wife's, not the dispatcher's. When the driver leaves for another company β the account stays with him, and he'll need to manage it. If you register it on your email β you've given him a CDL problem that will follow him for years.
3. Password β simple but reasonable. Write it on a slip of paper, hand it to the driver.
4. Authentication β Backup Codes β print them β hand the driver an envelope marked "Clearinghouse β do not lose."
5. Role: Driver.
6. Personal data: full name, phone, address, ZIP.
7. CDL: country, state, number, date of birth.
8. The system cross-checks against the federal CDL database. If it matches β the account is live.
9. If you already created a pending query before registration β it's now sitting in his account. The driver clicks Consent β Yes Submit. A couple of minutes later, you have the result.
Three typical situations
Textbook case. Rookie, first company. You sit down together, 10 minutes of registration, pre-employment query right away, consent right away. Two minutes later you see: "No records found." You hire him.
Normal reality. The driver worked at two or three places, has an account, but forgot the password back around 2022. You recover it via "Forgot Password." During the process, you discover he has a forgotten pending query from a previous employer sitting there β you close it. You run your own query.
Red flag. The driver refuses to give consent. By law, refusing consent is treated as prohibited status β he can't drive a CMV. The refusal is still going to surface for the company on the next query anyway. There's only one solution: either consent, or you part ways. There's no middle ground, and there won't be.
9.5. Pre-employment Query
Required before every hire. No exceptions. The driver doesn't touch a wheel until you have the result in hand. Not "I'll get it tomorrow, let him run in the meantime" β no. Result first β truck second. In that exact order.
The procedure
1. Log in (another backup code burned).
2. Conduct a Query.
3. Driver's info: full name, DOB, country, state, CDL number.
4. System verifies the driver exists.
5. Type: Full Query. For pre-employment β Full only.
6. Certify β Conduct a Query.
7. Request goes to the driver. Driver clicks Consent Yes. You get the result.
What you'll see
- No records found β clean. Hire him. Doesn't cancel anything else β MVR, PSP, pre-employment drug test still happen.
- Records found: Prohibited β cannot hire. He's in prohibited status until Return-to-Duty is completed.
- Records found: Not Prohibited β there were violations, but Return-to-Duty is done. Read the details, weigh it, decide for yourself.
If it comes back Prohibited
Three options, in descending order of common sense:
- Don't hire. The safest path. A person sitting in Prohibited right now is a person who hasn't closed out rehab. You have no reason to step into that story.
- Wait for Return-to-Duty completion. The driver goes to a SAP, completes the program, passes a Return-to-Duty test with a negative result. Clearinghouse status flips to "Not Prohibited." Now you can take him β but remember the next 1β5 years will have follow-up tests on the SAP's schedule. That's administrative load on you.
- Non-CDL position. Rarely relevant for a trucking company.
9.6. Annual Query
Once every 12 months on every active driver. This is a Limited Query β a quick "has anything new popped up this year" check.
When to do it
In a batch, in January. Put a reminder on your calendar: "January 15 β Annual Clearinghouse Queries," and once a year you close the whole fleet in an hour.
You can spread it out across each driver's hire date β but that's five times more work and ten times more chances to forget someone. I always do a January volley.
The procedure
1. Log in.
2. Annual Queries section β the system shows you the list of who's due.
3. Before you run the query, you need a General Consent for Limited Queries in hand β a paper form signed by the driver at hire. Stored in the Driver File. Signed once, valid for the entire employment period. You do not need a separate consent each year.
4. Run the limited query on everyone on the list.
5. If someone comes back "Records Found" β a hard clock starts: 24 hours to:
- Pull the driver off the road.
- Run a Full Query (with consent).
- Get the details and make a decision.
A typical scenario where Annual saves the company
12-truck fleet. January, the Safety runs annuals. 11 drivers β clean. One β Records Found. You dig in: turns out the driver moonlighted a week at another company in October, got caught on their random, failed, quit, and quietly came back to you. If you hadn't run the annual β he'd have been driving for you in prohibited status until the next audit. And at audit that's a fine of up to $19,246 (2025 schedule; the amounts are indexed annually) for every trip a prohibited driver made. And it's not one line item β it's multiplied by however many loads he ran in those months.
That's why annual.
9.7. Query Plan: where queries come from
Physically: if there are no queries on your balance, you can't run a request. The database just won't let you.
Purchasing
1. Clearinghouse β Purchase Query Plan.
2. Plan Size β from 1 to 10,000. The bigger the pack, the lower the per-unit cost.
3. Payment: credit card, PayPal, Amazon Pay, check.
4. Queries hit your balance instantly.
How many to buy
Working formula:
- Annual = number of active drivers Γ 1.
- Pre-employment = projected hires for the year Γ 1.
- Buffer = +20%.
Example. Fleet of 10, planning 5 hires over the year. 10 + 5 + 3 buffer = 18 queries. Buy a pack of 20.
Unused queries don't expire, they carry over to the next year.
π‘ Don't buy queries one at a time "as needed." Stock up once a year for the whole fleet β forget about it. Wasting time on small orders every time is just a dumb hourly leak.
9.8. A driver failed a test. What you do
The situation nobody expects but that eventually happens at every company.
π§° If you're scared β here's the exact sequence. You get a call from the TPA or the clinic: "Driver so-and-so β positive drug test." First 5 minutes. Pull him off the road. Call: "Pull into the nearest TA or Pilot, park the truck, we're sending a replacement." Not "drive to the terminal," not "finish the load." Every mile from the moment of positive is a prohibited driver in motion = a fine of up to $19,246 per violation and personal problems for the driver. No compromises. Within 3 business days. Log the violation in Clearinghouse. Report a Violation section. Type, date, result. Hand the driver SAP contacts. FMCSA requires multiple names to choose from, not one. These are certified specialists who handle return to work. Process suspension or termination per company policy. Most companies terminate β that's legal and I'm not going to judge anyone for it. Some keep the driver and pay for Return-to-Duty if he's valuable. Your call. Document everything in the Driver File. Test result, date, notice to driver, SAP list, company decision. Every step with a date. It's scary the first time. The second time it's just work.
Return-to-Duty Process
If the driver wants to come back, here's his path:
- Evaluation with a SAP.
- Program assigned by the SAP (education/treatment).
- Follow-up evaluation with the SAP.
- If the SAP confirms readiness β Return-to-Duty Test (observed).
- Negative result β status flips to "Not Prohibited."
- Next 12β60 months β follow-up tests on the SAP's schedule.
The driver pays, or the new company that hires him pays. The old company isn't obligated to pay anything.
9.9. Fines
Amounts are indexed annually; the order of magnitude is:
- No pre-employment query β up to $19,246 for the company (for the driver β up to $4,812; 2025 schedule).
- Used a prohibited driver β up to $19,246 per violation (multiplied by number of trips).
- Failed to report a violation within 3 business days β fine plus CSA hit.
- No annual query β fine per driver.
- Company not registered in Clearinghouse β critical audit finding.
At a Safety Audit (especially New Entrant), Clearinghouse is in the top three sections examined. The inspector pulls the query logs and cross-references them with the Driver File. Gaps show up immediately.
π Checklist: Clearinghouse under control
Company:
- [ ] Registered in Clearinghouse.
- [ ] Email is corporate, not personal Gmail.
- [ ] Login/password/backup codes in a password manager.
- [ ] Query Plan purchased for the year with 20% buffer.
New driver:
- [ ] Clearinghouse account created.
- [ ] Full Pre-Employment Query completed before the driver goes on the road.
- [ ] Consent received.
- [ ] Result in Driver File.
- [ ] General Consent for Limited Queries signed and filed in Driver File.
Every January:
- [ ] Annual Limited Queries run on every active driver.
- [ ] Results in Driver File.
- [ ] For every "Records Found" β Full Query within 24 hours and a decision.
Incident:
- [ ] Driver pulled off the road in the first minutes.
- [ ] Violation logged within 3 business days.
- [ ] SAP contacts given to the driver.
- [ ] Everything in Driver File with dates.
β Chapter 9 takeaway
- Clearinghouse is the federal drug & alcohol violations database. Live since January 6, 2020.
- The company must: register β buy a Query Plan β run queries. Without this, you can't hire anyone.
- Full Pre-Employment β before every hire. Limited Annual β once a year on every active driver.
- Without driver consent, you won't get a result. That's why registering the driver is part of your job.
- A prohibited driver on the road = a fine of up to $19,246 per violation. Pulling him off the road is instant.
- Return after a failure goes through SAP + Return-to-Duty Test + years of follow-up tests.
- At a Safety Audit, Clearinghouse is one of the first things checked.
β You've got Chapter 9 ifβ¦
- [ ] You understand what Clearinghouse is and why it was created.
- [ ] You can register a company and a driver.
- [ ] You can distinguish Limited and Full queries and know when to use each.
- [ ] You know the exact sequence of actions for a positive test or refusal.
- [ ] You can distinguish Pre-Employment, Annual, and Return-to-Duty queries.
- [ ] You can buy a Query Plan and size it for the year.
- [ ] You understand the SAP's role and the logic of the Return-to-Duty Process.
π° Clearinghouse is a zero-tolerance zone for mistakes.
Forgot pre-employment β a fine of up to $19,246. Sent a prohibited driver on a run β up to $19,246 per dispatch (2025 schedule; indexed annually). Plus Clearinghouse hits auto-flow into CSA and drag your rating down for years.
Two places where beginners break most often: (1) they skip the January annual query β "eh, I'll do it in February" β and then February comes and they don't; (2) they let a driver hit the road before the pre-employment result is in. I know this pattern. It costs money.
- Company and driver registration in Clearinghouse.
- Pre-employment, Random, Post-accident, Reasonable suspicion, Return-to-Duty, Follow-up tests.
- 30,000+ locations across the US β the driver tests at the nearest center without losing a day.
- Random testing program with automatic driver selection per FMCSA quotas.
- Annual queries and a full document package for Safety Audit.
- Driver onboarding briefings at hire.