"We Vetted the Carrier" Is Now a $604 Million Sentence

In July 2026, a Dallas County jury returned a $604 million verdict against a freight broker, a carrier, and a driver over a 2021 fatal crash. The broker has said it will appeal, and the number may not survive. The reason it happened at all will.

This was the first major trial since the Supreme Court, in May 2026, ruled 9–0 that negligent-selection claims against freight brokers are no longer federally preempted (Montgomery v. Caribe Transport II). For fifteen years the FAAAA preemption shield made most of these cases go away early. It is gone. Every load you broker is now a claim a plaintiff can take to a jury, judged on one question: the care you took when you selected the carrier — and whether you can prove it.

It didn't turn on whether the carrier was safe. It turned on what the broker could prove it knew.

Strip the case down and the fight was not really about trucking. The broker's defense was that it did vet: the carrier held a Satisfactory FMCSA rating and had delivered hundreds of loads without incident when it was selected. The plaintiff answered with safety-performance data the broker said it never had in front of it. The jury was left to decide what the broker actually saw, and when.

That is a records question, not a safety question. And it is the question every broker will now face the morning after an incident.

Your Vetting File Is Now the Entire Exhibit

Here is how carrier vetting is documented across most of the industry today: someone pulls the FMCSA record, glances at authority and insurance, maybe screenshots it into a shared drive or a compliance tool, and books the load. The "record" of that decision is a mutable row in a database, an editable document, a timestamp that may or may not reflect when the check actually happened.

In front of a jury, opposing counsel's move is a single sentence: "Prove nothing changed since dispatch." You cannot — not cleanly. To prove that an internal, editable record is authentic and contemporaneous, you have to forensically vouch for every system that touched it: access logs, backups, admin trails. That is expensive, disruptive, and it drags your entire IT estate into discovery — per incident.

And in the age of AI-assisted discovery, the old hedge — keep the record thin, hope the damaging fragment stays buried — is no longer caution. It is exposure. A plaintiff's engine reads everything.

Tamper-Proof Logging Is Not Proof of an Event

This is where good, well-intentioned compliance programs go wrong. Vendors now sell "immutable" and "tamper-evident" logging as the answer. It is not the answer, and the difference is the whole game.

A self-produced log — however unalterable — is still a record the defendant made about itself. It is documented. It is not proven. Proven means something specific: a record whose authenticity does not depend on trusting the party that made it. A signed, timestamped snapshot of the carrier's status as it existed at the moment of dispatch, bound to who checked it and when, and independently verifiable — by your insurer, by opposing counsel, by the court — without taking your word for anything.

We Have Watched This Exact Movie Before

In the late 2000s, the enterprise security industry sold laptop encryption. Everyone had it. Then companies started losing laptops anyway — and the press releases from that era read, almost verbatim: "We lost X million records, but the laptop may have been encrypted."

May have been. The problem wasn't the encryption. Every product shipped a feature letting a local administrator turn encryption on or off — and that change left no evidence of the drive's status at the moment it was lost. IT could not prove to Legal that the drive was encrypted when the laptop walked out the door. The market moved, fast, from "we encrypt your data" to the only thing that actually mattered: "we can prove the drive was encrypted when it was lost."

Montgomery has every one of the same hallmarks. The check happens. The systems that record it can be changed. And when it matters most, no one can prove what was true at the moment that counts.

The Morning After

The forgery problem makes it more urgent, not less: carrier identity fraud and double-brokering — increasingly powered by AI-generated documents and cloned DOT profiles — now cost the industry hundreds of millions a year. The carrier packet itself is forgeable. Which means the record can't just be stored; it has to be signed at the source, captured the moment the check runs.

The general counsel's real question is no longer "do we have a vetting process?" It is the one that gets asked the morning after a crash: an incident happened an hour ago — is the evidence already secured, in a form we can prove? Evidence like that cannot be manufactured after the call comes in. It was sealed at the moment it mattered, or it is gone.

"We vetted the carrier" used to be a sentence you said in a deposition. Post-Montgomery, it's a sentence you have to be able to prove — and, as Dallas just showed, the cost of not being able to runs to nine figures.

---

Measured, not trusted. A vetting record that only asserts what you checked is a record you are asking a jury to trust. A record that carries a verifiable measurement of what the authoritative source served, at the moment you checked it, signed and owned by you, is a record you can prove. Good care was never about a flawless carrier or perfect data — only about attention to a process actually delivered, measured, and provable.

Steven Sprague — Rootz
August 2026