You Vetted the Carrier. Nobody Vetted the Driver.

A carrier in the Chicago market — call them MC-3847291, DOT-2891047, three years on the books, dry van authority, nothing alarming in the BASICs — put a driver behind the wheel of a loaded reefer in late 2024. The broker who tendered that load had done everything right at the carrier level. SAFER was clean. BASIC scores were below threshold across the board. Cargo insurance verified against FMCSA's L&I system, not just the certificate. The T-call went smooth, rate confirmed, pickup scheduled for 0600.

The driver had a clearinghouse prohibition. The carrier had completed their annual general awareness query earlier that year — checked the box, technically compliant on paper. But this driver's prohibition came in three weeks after that query ran, and dispatch put him back in the truck without running an updated check first. Nobody caught it before pickup. Nobody caught it at all, until there was a crash, a death, and a plaintiff's attorney subpoenaing every document in the broker's file.

I tell that story because it identifies the specific blind spot in how most brokers think about carrier vetting. Everything you check is at the entity level. The human being actually operating twelve tons of equipment on a public highway is invisible to your process.

Carrier qualification is not driver qualification

When you pull a SAFER snapshot, check BASIC scores, verify insurance, and confirm authority age, you're vetting the carrier as an organization. You're building a picture of their safety patterns, their compliance history, their inspection record. That's real information and it matters. But it says nothing about the specific driver dispatch assigns to your load.

49 CFR Part 391 puts driver qualification squarely on the carrier. Section 391.11 sets the baseline: a carrier cannot use a driver who doesn't meet minimum qualifications — valid commercial driver's license, current medical examiner's certificate, no disqualifying medical condition, no record of violations falling under § 391.15. Section 391.15(b) lists what disqualifies a driver: DUI, leaving the scene of an accident, using a motor vehicle to commit a felony, certain drug convictions, and a few others. None of those events show up in your SAFER pull. None move the BASICs until they accumulate into a pattern visible at carrier level. They live in the driver's qualification file and, since 2020, in the FMCSA Drug & Alcohol Clearinghouse — both of which you cannot access without the driver's consent or a post-accident subpoena.

The carrier's driver qualification file, per 49 CFR § 391.51, is supposed to contain: an employment application, an MVR inquiry run at hire and annually thereafter, the medical examiner's certificate, a certificate of road test or equivalent, and annual reviews of the driving record. Every driver, every carrier, every load. You trust it exists. You never see it. If it has gaps — and some do, especially at smaller carriers that treat compliance as paperwork to be done when an auditor schedules a visit — those gaps become your problem the moment you tendered to that carrier and the driver hurt someone.

What the Clearinghouse gives you (and what it doesn't)

The Drug & Alcohol Clearinghouse fixed a real problem. Before 2020, a CDL driver could fail a drug test at one carrier, get fired, walk across the street, and get hired at the next one without disclosure. No national record. No visibility. The clearinghouse ended that by requiring carriers to check the system before employing any CDL driver (the pre-employment full query under 49 CFR § 382.301) and to run a general awareness query on every active CDL driver once per year (§ 382.701). The pre-employment full query shows all violations and prohibitions on record. The annual query only shows whether a new violation has been added since the last check.

What this means in practice: a carrier that ran its annual query in January and added a driver in March — with a prior prohibition — might have cleared that driver without a full pre-employment check if internal compliance is loose. A carrier that ran a full pre-employment query correctly might still have a driver pick up a new violation in November, six months after the annual general awareness query ran, and dispatch that driver in December without any updated check. The system requires annual queries, not continuous monitoring.

As a broker, you can't run a clearinghouse query on a specific driver without that driver's consent. That's not a workaround I'm aware of, and it's not something you can demand in a carrier agreement and actually enforce at dispatch. What you can see in aggregate is the Controlled Substances/Alcohol BASIC. A carrier with a documented pattern of clearinghouse violations will eventually see that move. But a carrier with one active prohibition on one driver who hasn't been caught yet? Below the noise floor. Invisible in the BASIC until it shows up in an inspection — usually after something goes wrong.

The T-call that actually does something

Three minutes with dispatch beats a lot of database checks. I've written about that before. But the T-call only creates a paper trail if you're asking questions that produce a record.

Two questions worth adding to every T-call before load tender — especially on loads over $50,000, anything temperature-sensitive, high-value, or running a tight lane:

"Who's the assigned driver, and can I get the CDL number for my file?"

"Has your clearinghouse annual query been completed for this driver for the current calendar year?"

You're not going to catch every prohibited driver by asking those questions. A carrier that's already ignoring a clearinghouse prohibition isn't going to tell you honestly on the phone. But you're building a record that the question was asked. You exercised a step. You demonstrated reasonable care. If a crash happens six hours later and discovery opens your file, the question of whether you inquired about driver qualification has an answer.

Some carriers push back on the CDL number question. They think it's overreach, or they're not used to being asked. My response: you're asking for the CDL number of the person operating your shipper's $115,000 load of pharmaceutical returns on I-80 at 2 AM. That's not overreach. That's proportionate. And the carriers that actually have a clean compliance program — the ones you want to be working with — don't balk at this. They know their drivers' CDL numbers. They can answer in thirty seconds.

If dispatch can't give you a driver name because the load hasn't been assigned yet, that's fine. Ask again when they call to confirm the driver before pickup. Make it a standard handoff question. It doesn't have to be adversarial. "Hey, before we finalize — who's the driver and can I grab that CDL number?" becomes routine fast.

Post-Montgomery and the duty of reasonable care

Before Montgomery v. Caribe Transport II, LLC, broker defense strategy often leaned on preemption: the FAAAA preempts state-law negligent-selection claims, full stop, so carrier-level vetting was the ceiling and also the floor. That door closed on May 14, 2026. The Supreme Court was unanimous. Freight brokers are exposed to state negligent-selection liability, and the question now is what "reasonable care" actually requires.

I'm not a lawyer, and I won't tell you what legal standard will apply in a given state after a given crash. But I've watched enough discovery play out to know how the analysis runs. A plaintiff's attorney building a negligent-selection case against a broker looks at the carrier file. They look at the T-call notes. They look at what questions you asked and what answers you documented. If the notes are blank — just "T-call done, rate confirmed" — the attorney has room to argue that reasonable care meant something more, and that you didn't do it.

Driver qualification is a specific, documentable step. Asking the question doesn't guarantee the carrier gives you a true answer. But a broker who never asked, who has no record of any inquiry into who was actually driving, is in a different position than one who documented the T-call, captured a driver name and CDL number, and noted whether the clearinghouse query status was confirmed.

That's not an exhaustive defense. It's one additional layer of documented care. Post-Montgomery, layers are what the paper trail is made of.

Older authority and driver qualification gaps tend to correlate

Here's a pattern I've noticed — and I want to be clear this is observation, not a stat I can point you to a study for. Carriers with authority under eighteen months are often still building their compliance program. Their driver qualification files are often the least complete part of it, because carriers prioritize getting trucks running over running background checks the way a mature carrier does. The DQ file, the annual MVR pulls, the clearinghouse query cadence — these are things some new-entrant carriers treat as "get to it when we're bigger."

That's the same population where asking about the driver's CDL number at dispatch time does the most work. If the dispatcher says "I'm not sure we have that number handy," that's information. It might not be disqualifying — small dispatch operations often don't have a centralized file in front of them on a phone call — but it's a flag worth noting and worth asking a follow-up question about.

If a carrier can't tell you who's driving your load and can't confirm that driver's clearinghouse status, that's not a hard no by itself. But it's a data point. It goes in the file, right next to the SAFER snapshot and the insurance verification, as evidence of what you knew and what you couldn't confirm when you made the dispatch decision.

How I document this

After the T-call, before load confirmation, these fields get logged in the load file:

That's five lines. On a load that ends up in litigation, those five lines are evidence of a process. If they're missing, the absence is what gets argued.

If your TMS doesn't have a custom field for it, use the notes section. If you're on a spreadsheet, add a column. The medium doesn't matter. The timestamp and the content matter.

One more thing: if the driver changes between confirmation and pickup — which happens — document the update. Don't just update the driver name. Log it as a change, with a timestamp, showing that you re-ran the question on the new driver before the truck moved. That's a slightly different scenario than a first-time dispatch, and the record should reflect it.

The carrier vetting process you've built covers a lot. The specific human behind the wheel on a specific day has always been the gap in it. You can't close that gap completely from the outside. But you can put a flag at the edge of it that shows you knew the gap existed and you did something about it.

— Mason Lavallet

Founder, DOTScreener.com