The Carrier Vetting Checklist a Plaintiff's Attorney Hopes You Never Build

The call came on a Tuesday, eight months after the load had delivered without incident. A broker in Ohio picked up and the voice on the other end was a plaintiff's attorney's paralegal. There'd been a crash in Missouri — a carrier he'd booked on a flatbed load of steel coil. One fatality. The attorney wanted his carrier vetting records for MC-1847293 / DOT-3821044.

He hadn't thought about that load since it delivered. The carrier had been on his approved list. He'd done a full packet when he onboarded them two years earlier. He figured he was fine.

He wasn't fine. The discovery process revealed a carrier whose BASIC scores had deteriorated significantly in the fourteen months since his team had last looked at them, whose insurance had lapsed briefly four months before the crash and reinstated, and whose MCS-150 hadn't been updated in over a year. None of it was visible in the file he'd put together at onboarding — because all of it happened after.

The verdict was $2.1 million. The broker's E&O didn't cover negligent selection. His carrier was broke. He was on the hook.

What Montgomery Actually Changed

I want to be precise about this, because I've heard brokers misread the Supreme Court's decision from May 14, 2026. Montgomery v. Caribe Transport II, LLC didn't create a new legal theory. Negligent carrier selection existed as a state tort claim long before. What the Court decided — unanimously, Justice Barrett writing — was that the Federal Aviation Administration Authorization Act doesn't preempt state-law negligent-selection claims against freight brokers.

That matters because the 7th and 11th Circuits had been dismissing these cases on preemption grounds. Brokers in those circuits had relative shelter from negligent selection suits. That shelter is gone. Every state is now open for a plaintiff to argue that a broker negligently selected a carrier, under state tort law, and that the broker owes damages for harm caused by that carrier.

The underlying standard hasn't changed, but the exposure has dramatically increased. More plaintiffs will bring these claims. More of them will survive motions to dismiss. More brokers will be sitting across a deposition table from an attorney who has already pulled their carrier file.

If you operate as a broker in the United States in 2026, this is your reality. "I've never been sued" is not a vetting strategy.

The Five Things That Determine Whether Your File Survives

I'm not going to tell you this is a magic shield. There is no document you can create that makes you immune to being sued. But there's a real difference between a carrier file that falls apart under deposition and one that gives you a defensible answer to every question an attorney can reasonably ask. These are the five things that separate the two.

1. How You Found the Carrier

This is the first thing a plaintiff's attorney asks, and most brokers are surprised by how much it matters. "We pulled them from the load board" is a worse answer than "we pulled them from a safety-ranked search filtered by OOS rate and authority age." Not because load board sourcing is illegal, but because it's an undifferentiated pool with no documented safety filter applied before the booking decision.

Under any reasonable standard of ordinary care, a broker exercising due diligence in carrier selection should be able to explain why this carrier and not another. What criteria led to the selection? Was safety data part of the decision? Or did the carrier just respond to the posting first?

The method of selection is documented in what FMCSA calls a "carrier selection record" — a concept implied by the recordkeeping requirements under 49 CFR § 371.3, which require brokers to maintain records of each transaction including the carrier name, authority, and compensation. The regulation sets a floor, not a ceiling. A plaintiff's expert will argue that a reasonably careful broker does more than the floor.

If your carrier sourcing method produces a documented record — "identified through a search ranked by safety metrics, filtered to active authority, OOS rate below X, minimum 12 months tenure" — that record is part of your defense. If your sourcing method produces nothing, you're explaining improvisation.

2. Insurance Status at Tender, Not Just at Onboarding

The COI you collected at onboarding is not insurance verification at tender. I've said this before and I'll say it again until brokers internalize it. A COI is a snapshot. Insurance is a continuous obligation. 49 CFR Part 387 requires carriers to maintain financial responsibility — $750,000 minimum BIPD coverage under § 387.9 for most general freight — at all times. The regulation does not care that your COI was current six weeks ago.

The FMCSA Licensing & Insurance database reflects current insurance status and lapse history. A plaintiff's attorney can pull that in twenty minutes. If coverage lapsed between your COI date and the crash date, and you have no record of verifying current status at or near tender, you have a gap in your file. That gap is the thing they build the case around.

The verification you need at tender is a check against L&I status dated close to the load — not a reprint of the original COI. If you're using a monitoring tool that watches insurance status and alerts you to changes, you need that tool's output in the carrier's record, timestamped. If you're doing it manually, you need a dated notation.

3. Authority Status and Safety Data Documented to the Load Date

SAFER snapshots go stale. A screenshot you took at onboarding, even with a good timestamp, tells a plaintiff's attorney what the carrier's record looked like then. It tells them nothing about the day the load moved.

For your carrier file to hold up, each booking needs documentation that reflects safety status close to that booking date. That means BASIC percentiles, OOS rate, crash history, authority status — pulled or confirmed within a reasonable window of when the load ran. The specific window isn't defined by regulation, but "within the last 30 days for frequently-used carriers" and "fresh for first-time bookings" are defensible positions. Months-old data is not.

This doesn't mean you pull a fresh full file on every load. For a carrier you book weekly, a monitoring system that tracks for changes and notes the absence of flags is more useful than repeatedly reprinting the same SAFER snapshot. What you need is a dated record of the safety state at the time of booking, however you capture it.

MC-1847293 is a carrier I'll use as an example. If that carrier's Unsafe Driving BASIC went from the 40th percentile to the 78th percentile over six months, and your last documented safety pull predated that shift, you've defended a carrier that your own data sources would have flagged. A reasonably careful broker checks. The file should prove you checked.

4. What Changed Since the Last Time You Looked

This is the one that gets brokers on approved-list carriers more than any other. The approved list becomes a false confidence. Carriers get approved, go into the list, and the mental model shifts to "cleared" rather than "cleared as of [date] — needs re-verification before next booking."

Three categories of change can turn a previously acceptable carrier into a liability:

Insurance lapse or policy change — already covered above.

Safety record deterioration — a carrier that was clean 18 months ago can accumulate Unsafe Driving violations, fail a roadside inspection that dings their Vehicle Maintenance BASIC, or get into a crash that appears in the Crash Indicator. None of this shows up in your file if you're not watching.

Ownership or authority change — a carrier that gets sold or changes officers may carry over a safety rating that no longer reflects the people running the trucks. MCS-150 updates trigger when the carrier self-reports. If they don't update, SAFER doesn't automatically reflect the change.

A monitoring system that watches for triggers — insurance status changes, authority revocations, BASIC score movements, MCS-150 date gaps — turns this from a manual re-check you'll never remember to do into an automated alert you can document. The alert, and your response to it, is the record.

5. The Carrier Agreement — Signed, Verified, and Attributed to a Real Human

Your carrier agreement is only as good as the proof that an authorized person at the carrier actually agreed to it. An email with a PDF attachment that has a typed name at the bottom isn't proof of who signed. It's a document that could have been completed by anyone who had access to that email address.

Under deposition, the question is "can you identify the specific individual at that carrier who agreed to these terms, and can you verify that they had authority to bind the carrier?" A carrier agreement signed electronically with verified identity — a government-issued ID matched to the signer, a timestamped audit trail — answers that question. A PDF emailed back to you does not.

When something goes wrong, carriers sometimes claim the agreement wasn't authorized. A broker without verified signatory records is in a worse position than one who has them. The agreement is the foundation of your defense on contributory negligence and limitation of liability arguments — if the agreement itself is in dispute, you've lost your foundation before the case starts.

The Carrier Selection Record: Why Each Load Needs Its Own

49 CFR § 371.3 requires brokers to maintain records for each transaction. Most brokers satisfy this minimally — carrier name, authority number, compensation, check. That's the regulatory floor. It's not a litigation defense.

What the record actually needs to contain, for each load, is a snapshot of the decision:

• How the carrier was identified
• What safety data was visible at the time of booking (dated)
• What insurance status was at or near tender (dated)
• Whether anything had changed since the last booking of this carrier
• Who authorized the booking and when

When you have that record, the deposition answer to "what was the state of this carrier's file on the day of the crash" is a document you hand across the table. Not a reconstruction you're building under cross-examination.

DOTScreener builds this record at the screening level — the Carrier Selection Record captures the safety data state at the time of the screen, timestamps the monitoring context, and documents the selection rationale. For brokers who re-screen carriers before each load or maintain continuous monitoring with re-filed CSRs, the record follows the load rather than sitting static in an onboarding folder.

That's not marketing. That's what the document needs to do to be useful when you actually need it.

The Pre-Load Window Is the Only Window You Control

Here's the part that brokers miss. After the load moves, your options shrink fast. If something goes wrong on that load, everything you do after the fact looks like damage control. The only moment where you can actually exercise due diligence is before you tender — when you still have the ability to choose a different carrier.

The plaintiff's attorney knows this. They'll frame every gap in your file as a choice you made before the load moved: you chose not to verify insurance, you chose not to re-check safety data, you chose to rely on an old COI. Each "you chose" is a negligence argument.

The checklist above isn't a post-incident checklist. It's a pre-tender checklist. By the time something goes wrong, the file either holds up or it doesn't. You built it before the load moved, or you didn't build it at all.

How I Document This

Here's the file structure I use on every carrier booking. Not every item is equal weight — the ones that matter most in litigation are the dated insurance verification and the dated safety snapshot. But all of them belong in the record.

Carrier identification: Source of selection noted (search parameters, safety filters applied, or referral source if applicable).

Authority verification: SAFER screenshot or monitoring system notation, dated to within 30 days of the load. Operating Status must show "Authorized for Property (For Hire)" or equivalent.

Insurance verification: L&I database check dated within the week of the load for frequently-used carriers, same-day for first-time bookings. BMC filing type noted (91 or 91X). Any monitoring alert history for this carrier noted.

Safety snapshot: BASIC percentiles, OOS rate, crash indicator, authority age — as of a date within 30 days of the load. For monitored carriers, the monitoring system's last-alert-free notation suffices with a timestamp.

Carrier agreement: Signed agreement on file with verified signatory identity. If electronically signed with ID verification, the audit trail reference noted.

Approval decision: Who approved the booking, when, and any exceptions noted (new authority, WARN result, elevated BASIC scores above threshold).

That's the file that survives a deposition. Not because it's bulletproof — nothing is — but because every reasonable question gets a reasonable, dated answer.

The broker in Ohio had done some of this work. He'd done the onboarding right. What he hadn't built was the per-load record, and that's where he got exposed. The crash happened on a load, not at onboarding.

Build the file for the load.

— Mason Lavallet

Founder, DOTScreener.com