What a Plaintiff's Lawyer Sees When They Subpoena Your Carrier File

The File That Decides the Case

The load was a 38,000-pound reefer run — $92,000 of pharmaceutical product on a Chicago-to-Nashville lane. MC-1247893 / DOT-3566422, eight months of operating authority. A pedestrian was struck at a rest stop outside of Cookeville. The carrier had a vehicle OOS rate of 31% at dispatch. Your file has one screenshot from six weeks earlier and a W-9.

The plaintiff's lawyer gets your carrier file in discovery and spends about four minutes finding what she needs.

That's how negligent carrier selection cases work now — and after the Supreme Court's Montgomery v. Caribe Transport II decision in May 2026, it's not a regional risk or a one-circuit exception. The Court held unanimously that the FAAAA doesn't preempt state-law negligent-selection claims against freight brokers. That means plaintiffs' counsel in every state can now name the broker. The contingency math has changed. Your carrier file is exhibit A.

I've been thinking about this from the other side. What does your documentation look like to someone whose job is to find the hole in it?

Question One: When Did You Pull This Data?

The first thing a competent plaintiff's lawyer checks in your carrier file is the timestamp. Not the date of the accident. The date of your last verification.

If your SAFER screenshot is from March 3rd and the load dispatched April 11th, that's a 39-day gap. The expert witness they hire doesn't need to show that anything actually changed in those 39 days. The gap itself is the argument. "Ladies and gentlemen, the broker's last verification of this carrier was 39 days before the accident."

If your file has undated screenshots — and most of them do — you have a different problem. An undated screenshot saved to a generic "carrier docs" folder is legally indistinguishable from something you assembled after the fact. I'm not saying you did that. I'm saying it can be made to look like you did.

The timestamp isn't a technicality. It's the spine of your defense. Without it, there's no "when I looked at this carrier, here's what I saw." There's just a pile of documents with no clear chain.

What They Read in Your SAFER Print

Assuming you printed a SAFER company snapshot at all — and 49 CFR § 390.15 requires you to investigate a carrier's safety record before using them, which a SAFER print goes directly toward satisfying — here's what a plaintiff's attorney is looking at.

The Crash Indicator BASIC. Not whether the percentile is elevated. Whether you noticed it and what you did with it. If MC-1247893 was sitting at the 75th percentile on the Crash Indicator and your file shows approval with no annotation, the question is already written for cross: "Did you see this score?" "Yes." "And you approved them anyway?" "Yes." "And you wrote nothing down." That isn't a question.

The vehicle OOS rate. FMCSA's safety fitness threshold under 49 CFR § 385.9 is 34% for vehicle OOS. A carrier at 31% is close enough that a jury will want to know why you didn't notice. Maybe you had a legitimate reason — carrier has 300 power units and a blitz quarter skewed the number, you noted it, you confirmed current inspections. That's a defensible file. An empty file is not.

Authority grant date. If your carrier had been operating for eight months at dispatch, any plaintiffs' expert will testify that the industry practice — not the regulation, the practice — is to apply additional scrutiny to carriers under 18 months of authority. That distinction matters in tort. Industry practices become the standard of care. If you dispatched a lane worth over six figures to an 8-month-old authority with no additional vetting notes, that's the second gap they'll find.

The MCS-150 filing date. 49 CFR § 390.19 requires carriers to file a biennial MCS-150 update. If the most recent filing in your SAFER print is 30 months old, you had notice that this carrier was potentially out of compliance with a federal reporting requirement. Did you flag it? Did you call the carrier to confirm status? Or did you look past it because the SAFER page loaded without errors?

The Gap That Kills Most Files

Here's where most brokers are actually most exposed, and I don't think they realize it.

Initial vetting looks okay in the majority of carrier files. SAFER snapshot, ACORD 25, W-9. Some version of an onboarding check. The question a plaintiff's lawyer asks — the one that tends to produce the longest silence in deposition — is:

"When is the last time you verified this carrier's safety status before the day of the accident?"

Not when you onboarded them. When you last confirmed them before this specific load.

If your process is "we check carriers when we onboard them and then use them on future loads," you are one freight claim away from a very expensive deposition. Carriers' situations change. Insurance lapses. Ratings get downgraded. Officers turn over. A clean carrier in Q1 can have two OOS orders and a BASIC flag by Q4.

49 CFR § 371.3 requires brokers to maintain records of each freight transaction, but it doesn't set an ongoing monitoring cadence. That sounds like good news. It isn't. The absence of a regulatory floor means plaintiff's experts will testify to an industry best practice standard, and without documented re-vetting intervals, your one-time check looks like you did the minimum and walked away.

"You checked once at onboarding, never looked again, and your carrier had a new OOS order issued 90 days before the accident — is that accurate?"

If the answer is yes, the jury is already doing math.

The Insurance Certificate Problem

The ACORD 25 is in almost every carrier file. It is also almost useless standing alone.

An ACORD 25 certificate is issued by the carrier's insurance agent at a point in time. It reflects coverage as of issuance. It says nothing about what happened to that policy afterward. Policies get cancelled. Coverage gaps open and sometimes close without a broker ever knowing. The certificate you pulled at onboarding 14 months ago is a historical document, not proof of current coverage.

The L&I database — FMCSA's live insurance filing record — is the actual source of truth. It reflects active policy filings, pending cancellations, and lapse history. If your carrier's L&I record shows a 19-day coverage lapse four months before the accident, and your file has nothing documenting that you ran an L&I check at dispatch, you had a static certificate and no live verification.

The deposition question writes itself: "If your carrier's insurance had lapsed the day before you dispatched this load, would your current process have detected that?" For most brokers, the honest answer is no.

What a Re-Filed Carrier Selection Record Actually Protects

There's a practice that I think will be standard in five years: generating a fresh carrier vetting record tied to each dispatch event, not just at onboarding.

The logic is straightforward. You're not being sued for your onboarding process. You're being sued for a decision you made on a specific day, about a specific carrier, for a specific load. Your defense needs to answer that question. A timestamped, load-linked record — showing what you checked, when you checked it, what the data showed, and why you approved — is the answer. A folder of undated screenshots is not.

What DOTScreener calls a Carrier Selection Record is exactly this: a permanent, timestamped document attached to a dispatch event that captures the carrier's safety data as it existed at the time of tender. If discovery comes two years later, you pull the record for that load. It has a date-and-time stamp. It shows what the BASIC percentiles were that day, what the OOS rate was, what the insurance status was. That's not "I thought I checked them." That's documentation.

Continuous monitoring fits into this same logic. If you're actively watching carriers in your approved pool — flagging insurance changes, BASIC movements, new OOS orders — and that monitoring history is in your file, you've shown a jury that you weren't just checking a box at onboarding and moving on. You were actively watching. Every re-verification event is evidence of a process, not a one-time action.

How I Document This

For every dispatched load, the carrier file I maintain includes:

A timestamped SAFER company snapshot pulled on the day of dispatch or the day before — not the onboarding screenshot recycled indefinitely. A current L&I database check with the pull date and active coverage confirmation. A note on any elevated BASIC percentiles: what the number was, what I saw in the underlying violation data, and why I still approved or what additional steps I took. A brief entry if I'm dispatching a carrier under 18 months of authority, explaining what I did beyond the baseline check.

And a Carrier Selection Record tied to the load event, not floating in a general folder with no date.

The question I ask myself when I'm building the file is this: if a plaintiff's expert reads this document two years from now, will it be clear what I knew, when I knew it, and that I made a reasonable decision based on what I had? If the answer is no, the file isn't done.

The Bottom Line

Plaintiff's lawyers are good at their jobs. They'll find the gap between your last verification and the accident date. They'll find the stale ACORD. They'll find the elevated BASIC you didn't annotate. They're not looking for proof you're a bad broker. They're looking for one moment where your process broke down, one lane where you moved too fast, one load where the file doesn't match what you claim your process is.

The defense isn't having a perfect carrier. The defense is a reasonable, documented process that shows you made a thoughtful decision with the information available.

If your carrier files don't show that today, you know what to fix.

— Mason Lavallet

Founder, DOTScreener.com