How Plaintiff Attorneys Attack Freight Brokers After Fatal Truck Accidents
A field guide to the other side's playbook. Here's exactly what a plaintiff's firm subpoenas after a fatal crash, the negligent-selection theory they build, the 'you should have known' argument that wins, and the documentation gaps they exploit — written so you can close them before you're ever named.
The best way to understand how to defend a freight brokerage is to understand how a skilled plaintiff's attorney attacks one. So this article is written from the other side of the table. I'm going to walk through, step by step, what a competent plaintiff's firm does after a fatal crash involving a carrier you brokered — what they request, what theory they build, and where they find the gaps that turn a brokerage into a defendant with a checkbook.
None of this is secret. It's standard practice in the personal-injury bar, discussed openly at their conferences and in their trade publications. The only people who seem surprised by it are the brokers on the receiving end. Let's fix that.
The opening move: name everyone with a balance sheet
After a catastrophic crash, the carrier and driver are obvious defendants — but the carrier often carries only the federal minimum insurance, and a catastrophic-injury or wrongful-death claim blows through that limit immediately. The carrier may be a two-truck operation with no real assets. The driver has nothing.
So the plaintiff's attorney looks *up the chain* for a defendant with deeper pockets and better insurance: the broker, the shipper, the 3PL. This is not personal. It's arithmetic. The damages are enormous, the carrier's coverage is small, and the plaintiff's job is to find solvent defendants. A freight broker — especially a mid-size or large one with real insurance — is an attractive target the moment the carrier's coverage runs dry.
The legal vehicle is **negligent selection**: the theory that the broker failed to exercise reasonable care in choosing a competent, safe carrier, and that this failure was a cause of the plaintiff's harm. That's the case they're going to build. Here's how.
What they subpoena — the document requests
Within the first wave of discovery, expect requests for essentially your entire relationship with the carrier and the load. A representative list:
- The carrier's qualification/onboarding file — everything you collected when you set the carrier up.
- Your carrier-selection and vetting policies — written procedures, if any exist.
- The load file — rate confirmation, BOL, dispatch notes, communications.
- Every communication mentioning this carrier — emails, texts, chat messages, CRM notes, call logs.
- Monitoring records — anything showing whether and how you tracked the carrier's safety status over time.
- The carrier's safety data as you possessed or accessed it — and metadata showing *when* you accessed it.
- Records for other carriers available on the lane — to show a safer option existed.
- Your training materials — how your people are taught to vet carriers.
- Insurance and indemnity agreements — to map coverage and contribution.
Read that list again and ask yourself, honestly: *for the last carrier I tendered to, what comes out of the file in response to each item?* The brokers who sleep well are the ones whose answer is "a clean, dated record." The brokers who get hurt are the ones whose answer is "a packet from onboarding and a lot of emails."
The theory: "you should have known"
With the documents in hand, the plaintiff builds the negligent-selection case on a foundation of *foreseeability* — the legal idea that you're responsible for harms a reasonable person in your position should have anticipated. The argument has three beats:
Beat one — the danger was knowable. The carrier's FMCSA safety record on the tender date showed [a Conditional rating / Alert-status BASICs / a high OOS rate / a crash pattern / lapsing insurance]. All of it was free and public.
Beat two — a reasonable broker would have looked. The standard of care for a professional freight broker includes checking the publicly available safety data before entrusting a carrier with a load. (Expect a plaintiff's expert — often a former broker or compliance professional — to testify to exactly this.)
Beat three — you didn't, or can't prove you did. This is the kill shot. Either there's no record that you checked the safety data, or the record shows you checked only at onboarding eighteen months earlier and never again. Therefore you breached the standard of care, and that breach put a dangerous carrier on the road that killed the plaintiff.
Notice how much of this turns on *documentation* rather than on what you actually did. Even a broker who *did* glance at the data loses beat three if there's no contemporaneous record of it — because, as plaintiff's attorneys say to juries in plain English, **"if it isn't written down, it didn't happen."** The absence of a record isn't neutral. It's affirmative evidence of neglect in the story they tell.
The gaps they exploit
Across the brokerages that get hurt in these cases, the same handful of gaps recur:
1. **No written selection standard.** If you can't produce a policy, the plaintiff gets to define the standard of care for you — through their expert — and they'll define it as high as the facts allow.
2. **Onboarding-only vetting.** You checked the carrier once, when you set them up, and never looked again. Safety profiles decay; the carrier that was clean at onboarding was in Alert status by the tender date, and you didn't catch it.
3. **No timestamp.** You have *a* record, but it doesn't establish *when* you checked — so the plaintiff argues it was created after the fact, or that it reflects today's data rather than the data on the tender date.
4. **Screenshots and ad hoc notes.** A screenshot saved to someone's desktop, a note in an email — these are easy to attack as incomplete, cherry-picked, or unverifiable. They're better than nothing but they're not a system.
5. **No carrier attestation.** When the carrier lied about its insurance or its safety practices, you have nothing showing you obtained — and reasonably relied on — the carrier's own representations.
6. **Inconsistent practice.** Your best operators document; your busiest ones don't. The plaintiff finds the undocumented load and uses it to argue your "process" is fiction.
Closing the gaps before you're named
The defense to all of this is built *before* the crash, and it's almost entirely about creating durable, contemporaneous evidence of reasonable diligence. Concretely:
- A written carrier-selection standard that defines what gets checked before every tender — so the standard of care is *yours*, not the plaintiff's expert's invention.
- Screening at tender, not just onboarding — capturing the carrier's safety picture as it exists at the moment of the decision, every time.
- Timestamps and an audit trail — proving *what* was checked, *when*, and *by whom*, so the record can't be dismissed as after-the-fact.
- Carrier attestations — the carrier's own signed representations about insurance, drivers, and safety, so that if they lied, the story is "we reasonably relied on their representation," not "we should have somehow known."
- Consistency — the same process on every load, so there's no undocumented tender for the plaintiff to find.
- Retention — keeping the records long enough to outlast the litigation window, which can run years.
Every one of those is a direct counter to a specific move in the plaintiff's playbook. A written standard counters beat two. A timestamped tender-date screen counters beat three. Carrier attestations counter "you should have known." Consistency counters the cherry-picked undocumented load.
This is exactly what I built DOTScreener to produce — and I built it knowing this playbook, because the whole industry needs a defense that's as systematic as the attack. Every screening creates a **timestamped report** of the carrier's live FMCSA safety data, captures the **carrier's attestation**, and lands in an **audit log** showing who ran it and when — the documented diligence that turns "if it isn't written down it didn't happen" from a weapon against you into a shield.
The plaintiff's bar has a playbook. Now you have it too. The brokers who read the other side's strategy and build the record in advance are the ones who get *dismissed* from the case instead of writing the check.
— Mason Lavallet
Founder, DOTScreener.com
---
Sources
- [Restatement (Second) of Torts § 411 — Negligent Selection of an Independent Contractor](https://www.law.cornell.edu/wex/negligent_hiring)
- [49 U.S.C. § 14501(c) — FAAAA preemption and the motor-vehicle safety exception](https://www.law.cornell.edu/uscode/text/49/14501)
- [FMCSA SAFER Company Snapshot](https://safer.fmcsa.dot.gov/CompanySnapshot.aspx) — the public data plaintiffs reconstruct
- [FMCSA Safety Measurement System (CSA BASICs)](https://csa.fmcsa.dot.gov/)
- [Transportation Intermediaries Association (TIA) — Carrier Selection Framework / broker best practices](https://www.tianet.org/)
Automate your carrier vetting
DOTScreener runs every check in this article automatically — live FMCSA data, documented decisions, tamper-evident audit trail.
Start Free Trial