A Defense Lawyer's Pre-Suit Checklist for the Broker Who's Never Been Sued

Most freight brokers who are really good at carrier documentation got that way after getting sued. They sat through depositions, watched what their files couldn't answer, and rebuilt from scratch. One bad experience, fixed forever.

If you haven't been sued yet, you haven't had that education. And that creates a specific kind of complacency: nothing has gone wrong, therefore my process must be fine. Those two things are unrelated. You've been lucky. That's not the same as being protected.

I want to give you the deposition education without the deposition. So here's what I'd want in your carrier file if I were the transportation defense attorney you call the morning after a fatality on a load you brokered.

Data vs. Evidence of Judgment

A SAFER printout shows that on a given date, a carrier had active authority, a Satisfactory rating, and no BASIC alerts. That's data.

Evidence of judgment would be: a broker reviewed the carrier's vehicle OOS rate, noted it was at 17% against a national roadside average of roughly 20%, observed the carrier had 31 inspections over 22 months with a declining OOS trend over the last six, and approved the carrier based on positive trajectory plus three years of authority and a clean crash history — documented in a note attached to the approval record.

See the difference? The first proves you looked. The second proves you thought.

After Montgomery v. Caribe Transport II, LLC, the negligent-selection standard is "ordinary care." Ordinary care isn't just running the check. It's making a reasonable judgment based on what the check shows, and the file needs to reflect that judgment. What you saw. What you weighed. What you concluded and why.

Most carrier files have the first kind. Defense lawyers need the second kind.

Seven Things That Actually Matter in Your File

Here's what a transportation defense attorney actually needs in your carrier file to build a negligent-selection defense. Not compliance theater — a real defense.

A per-load date stamp. Not the onboarding date, not a quarterly monitoring pull. The date you ran your checks for this specific load. This is the single most important element in the file, and it's the first thing opposing counsel attacks. A SAFER printout dated four months before the load moved is worse than no printout at all — it proves your verification was already outdated. The review has to be current at the time of tender, and the file has to prove it.

A complete safety data pull, not just the rating. Most carrier files show the FMCSA safety rating: Satisfactory, Conditional, or Not Rated. What they don't show is what else the broker actually looked at. Was the Unsafe Driving BASIC in the file? The OOS rate? The crash count and whether any crashes had preventability determinations? The date of the carrier's last compliance review? If the plaintiff's expert puts the carrier's record on a projector and says "this broker should have known about the 73rd percentile Vehicle Maintenance BASIC," you need a file that shows you looked at Vehicle Maintenance on the day the load moved. If it's not in the file, it didn't happen.

Insurance verified against FMCSA L&I — not just the certificate. The ACORD 25 certificate is issued by the insurer and can reflect information that's days or weeks stale. FMCSA's Licensing & Insurance database shows the current filing, including any pending cancellation notices. Both should be in the file. The ACORD shows what the insurer reported. The L&I record shows what's currently active with the agency. They can and do diverge, and the gap is a plaintiff's exhibit.

A note explaining any flags or exceptions. This is the one element that's almost universally missing from the broker files I've reviewed, and it's the one a defense lawyer needs most. If a carrier had an Unsafe Driving BASIC at 59% and you approved them anyway, the file needs to show why. The presence of a red flag with no explanation is a plaintiff's exhibit. The same red flag with a documented, reasonable explanation is the foundation of your defense.

Your written approval standard. What threshold did you apply to this carrier? If you have a written carrier selection policy — and post-Montgomery you should — the file needs to show the carrier was evaluated against it and what the outcome was. A carrier that meets your standard cleanly: noted. A carrier that meets it with a caveat: the caveat goes in the file.

The reviewer's identity. Not an unsigned printout. A name. When the deposition question is "who made this decision," the file should have an answer.

The carrier's own representations. Most broker-carrier agreements include language where the carrier represents compliance with applicable federal safety regulations. That signed BCA is part of the file. Under 49 CFR § 371.7, brokers can't operate in a way that deceives carriers or shippers — but the flip side is carriers represent their own fitness when they sign up. Document that the BCA is signed and current.

The Exception Record Is Where Cases Are Won

This deserves more than a line item. Documentation of your judgment calls — specifically the ones where you approved a carrier despite a flag — is what separates a defensible file from an indefensible one. Most broker files have neither.

Here's a real-world scenario with fictional numbers that illustrates the problem. You're looking at MC-1589234 / DOT-4023761. The carrier is 22 months in authority, dry van, $1M BIPD confirmed on L&I. Clean snapshot. But their Vehicle Maintenance BASIC is at 71%. Not in alert — the threshold is 80% — but above average, and trending up from 58% three months earlier. You need the load covered and this is your best option for the lane.

A broker who approves this carrier and writes a note that says "Vehicle Maintenance BASIC at 71%, flagged for review. Pulled underlying violations: three brake lamp violations from one inspection event in 2025, no brake system OOS. No repeating mechanical pattern. Approved for current load. Re-review flagged in 30 days." has a defensible record. You saw it, you looked at what was behind it, you made a judgment, and you documented it.

A broker who approves this carrier because 71% isn't in alert, logs nothing, and moves on has a gap. Not because they were careless — they weren't — but because when a plaintiff's expert tells the jury this carrier's Vehicle Maintenance BASIC was elevated and trending upward, there's nothing in the file that shows you did anything other than miss it. The expert's narrative fills the silence.

Write the exception note in plain English. Not legal language, not jargon. The language you'd use explaining the decision to a new broker on your team, because that's roughly the language a jury understands. "Carrier authority is 16 months. Below our 18-month standard. Approved based on owner-operator with prior CDL history at previous carrier per dispatch call on [date], 14 inspections with zero OOS in 14 months, insurance verified directly with underwriter at [insurer name]. File contains phone log and insurer email confirmation." That note, on that date, is what a defense lawyer builds the "reasonable broker" story from.

Carriers you deny don't need a note. The denial is the record. Carriers you approve despite flags absolutely do.

The Monitoring vs. Vetting Confusion

I'm going to say something that will annoy some brokers: most carrier vetting records aren't vetting records. They're monitoring records mislabeled as vetting records.

The difference matters. A monitoring record says: as of this date, the carrier had active authority and no new alerts. A vetting record says: before this load moved, I reviewed the following specific data about this carrier and reached the following determination.

Both are useful. They're not the same job. Monitoring tools — Carrier411, Highway, others — are excellent at watching your roster for status changes and fraud indicators. But the output of a monitoring tool is not per-load vetting documentation. When a plaintiff's attorney asks "what did you check before you tendered this load," "our monitoring tool showed the carrier was clean" describes a process that isn't in your file and probably isn't what a court will accept as evidence of ordinary care.

This is the gap that shows up most often in post-Montgomery deposition transcripts. Brokers describe their monitoring process as their vetting process, and then discover that monitoring records — even thorough ones — don't answer the per-load question: what did you specifically review, on the day this load moved, about this specific carrier?

The Regulatory Foundation You Should Be Citing

FMCSA's Safety Measurement System BASICs are built on specific Parts of the Federal Motor Carrier Safety Regulations. When you review a BASIC, you're reviewing inspection-level enforcement of those regs. The Vehicle Maintenance BASIC reflects violations of 49 CFR Part 393 (parts and accessories) and Part 396 (inspection, repair, and maintenance). The Driver Fitness BASIC reflects violations of Part 391 (driver qualifications), including § 391.11's requirement that drivers be physically and otherwise qualified. The HOS Compliance BASIC reflects Part 395 (hours of service).

This matters for your documentation because it anchors your review to the regulatory framework, not just to a percentile number. When your note says "reviewed Part 395 compliance indicators for this carrier, HOS BASIC at 42nd percentile, no alert, approved" — you're speaking the language that maps to the standard of care, not just the score.

The strongest per-load records I've seen reference the specific violation categories behind elevated BASICs rather than just the percentile number. That's the difference between reviewing a score and demonstrating that you understood what the score was measuring.

How I Document This

My per-load approval record includes:

• System-generated date and timestamp (not handwritten, not reconstructable after the fact)
• Carrier MC# and DOT#, legal entity name as it appears on authority
• FMCSA safety rating with date of last compliance review, pulled from the SAFER snapshot that day
• All seven BASIC percentiles from the SMS carrier page, or notation that data is marked insufficient with the inspection count
• Vehicle OOS rate and driver OOS rate, with inspection count and timeframe context
• FMCSA L&I active insurance confirmation, including policy number, insurer name, coverage limits, and effective/expiration dates
• Flag or exception notation for any data point outside standard — with reasoning
• Approval or denial decision, with the name of the person who made it
• Reference to the signed BCA on file and the date it was executed

If I approved a carrier despite a flag, that flag is in the record with a written explanation. If a month from now a plaintiff's attorney pulls that record and reads it, I want them to see a professional who understood what they were looking at and made a documented judgment call — not someone who ran the same checklist on every carrier and never looked up.

That's what ordinary care looks like in a file. Not the absence of red flags. The evidence that you saw what was there and acted reasonably on it.

The broker who's never been sued still has every opportunity to build this process. The one who's been sued once usually has. Build it now.

— Mason Lavallet

Founder, DOTScreener.com