It came at 11:52 PM on a Wednesday. An insurance adjuster — professional, almost apologetic — asked if I'd brokered load number L-48291 out of Indianapolis about three weeks prior. Dry van, 42,000 pounds of consumer electronics, billed by the shipper at $290,000, headed to a distribution center outside Atlanta.
I said yes.
He told me the carrier, Summit Ridge Transport out of Memphis (MC-1247893 / DOT-3568204), had a fatal accident that afternoon. A family of four in a minivan. The company driver ran a red light at highway speed. Three deaths. The driver survived.
"We're coordinating with multiple parties," the adjuster said. "Our client will need a copy of your carrier qualification file and any documentation related to your selection of Summit Ridge Transport."
That sentence. Right there. That's the sentence that decides whether the next 18 months of your professional life are uncomfortable or catastrophic.
I had a file. Not a perfect one, but a real one. The call still wasn't fun. But I wasn't scrambling to remember if I'd ever verified insurance before that load.
Most brokers are scrambling.
What the adjuster is actually doing
The adjuster isn't just being thorough. They're starting the subrogation chain. Their client — the plaintiff's attorney representing the families — will sue the carrier. But since Montgomery v. Caribe Transport II (U.S. Supreme Court, May 2026), the plaintiff's attorney knows they can also sue the broker in state court for negligent carrier selection. The FAAAA doesn't preempt that claim anymore. Justice Barrett's unanimous opinion ended the shield that brokers in the 7th and 11th Circuits had used for years.
So that adjuster call is two things at once: mapping the carrier's liability and mapping yours. Your file is evidence in both cases.
The formal discovery letter comes 60 to 90 days after the suit is filed. When it does, it asks for everything you have on that carrier going back three years. Under 49 CFR § 371.3, you're already required to keep records of each brokered transaction — the carrier's name and address, the amounts paid, the shipment records — for three years. That's the regulatory minimum. What the plaintiff wants is everything above that minimum: your vetting records, your approval decision, the insurance verification, any monitoring alerts you received, and what you did with each one.
The gap between what § 371.3 requires you to keep and what you actually need to survive a negligent-selection lawsuit is where brokers get destroyed. The regulation was written for rate transparency and commission disclosure, not for a three-fatality discovery fight.
The first 48 hours
The moment you confirm the accident is real, you have exactly one job: preserve everything and audit what you have.
Do not delete anything. Do not "clean up" the TMS record or move the load to a closed archive. Do not touch the email thread with the carrier's dispatcher. Any deletion after you're on notice of potential litigation is spoliation — tampering with evidence — and it carries its own penalties in civil court, separate from the underlying negligence claim.
Then pull the file. Here's what you're looking for:
When was the authority verification done? Did someone run an MC pull before booking this specific load, or only at the time of carrier onboarding months ago? There's a difference. If you approved Summit Ridge in February and have been booking loads through them since without re-verifying authority, your February pull is what the record shows. The plaintiff's expert will check whether Summit Ridge's authority was ever flagged, voluntarily surrendered, or reinstated in that window.
What's the SAFER snapshot date? The FMCSA SAFER system has a timestamp on any print or export you saved. If your only record shows an onboarding pull from eight months ago with nothing since, you'll be explaining a gap that covers the period when Summit Ridge's Vehicle Maintenance BASIC crossed the intervention threshold.
Did you verify insurance at load time? Not just the COI. The FMCSA L&I database shows insurance filing history — actual filings, lapses, reinstatements. A COI from onboarding doesn't tell you whether that policy was still active on the day your load moved. Insurance can lapse between approvals. The plaintiff's expert will pull the L&I filing history and overlay the dates against your file. If your most recent insurance verification was four months before the accident, that's a question you'll be answering under oath.
What did your monitoring show? If you had any continuous monitoring on Summit Ridge and received an alert that you didn't act on, that alert is now the most dangerous document in your file. An ignored flag isn't a mark of diligence. It's proof you had notice and kept booking.
The § 371.3 floor isn't a vetting standard
Brokers sometimes confuse regulatory recordkeeping with legal due diligence. They're not the same thing at all.
49 CFR § 371.3 requires you to maintain records of each transaction: who the carrier was, what you paid them, the shipment basics. Three years of retention. That's the floor. It was written for freight bill auditing and commission transparency, not for a courtroom fight over whether you should have known a carrier had a pattern of maintenance violations.
Post-Montgomery, the legal standard of care in a negligent-selection suit is what a reasonable, competent broker in your market would have done to qualify this carrier. That's a jury question, and juries don't grade on a curve when there are three fatalities and a $2M-plus damages claim staring at them.
What does a reasonable broker do? Runs the MC against SAFER. Looks at the BASIC scores. Checks the crash register. Verifies operating authority. Verifies insurance against the L&I filing history — not just a COI. Gets a signed carrier agreement. Documents all of it with timestamps. And then monitors the carrier between loads, not just at onboarding.
If Summit Ridge's Vehicle Maintenance BASIC had crossed the intervention threshold six weeks before your load and you had no monitoring in place, you didn't know. Now you're explaining that ignorance to a jury while the plaintiff's attorney holds up a screenshot showing exactly when the alert would have fired.
The document that actually kills you
The item that destroys most brokers in discovery isn't a bad document. It's a missing one.
Specifically: the gap between onboarding date and load date. A carrier gets approved in January. You verify their authority, pull their SAFER snapshot, get a COI, have them sign your carrier agreement. Everything looks right. Then you book them in March, July, and again in August without touching the file.
In August, three people die.
The plaintiff's attorney pulls your records. They see the January onboarding documents and ask: "What did you verify before the August load?" The answer, for most brokers, is nothing. There's an onboarding packet and then silence for seven months.
That silence is the exposure. You didn't do anything wrong at onboarding. But the legal question isn't whether you were diligent once. It's whether you were diligent at the time of the load. A carrier can deteriorate significantly in seven months. A BASIC can shift from green to red. An insurance policy can lapse and be reinstated twice. A Conditional rating can be issued. All of that can happen while your file sits unchanged from January.
The fix isn't running a full onboarding packet every time you book a carrier. Nobody has time for that. The fix is continuous monitoring with a documented load-time verification step: a current authority check before dispatch, an insurance status pull against L&I, and an automated flag on any material changes since the last load. That process creates a record showing what you knew on the day you booked — not what you knew in January.
What my file showed that night
The reason I had something to hand the adjuster on that Wednesday call isn't that I'm naturally organized. It's that the vetting process I use creates records automatically.
When I approve a carrier in DOTScreener, it files a Carrier Selection Record — a timestamped document capturing the carrier's authority status, insurance filing history, BASIC profile, and crash record at the moment of approval. That record doesn't get overwritten. It stays, with a date on it.
When a carrier is on Continuous Monitoring, DOTScreener watches for changes: insurance status, BASIC threshold crossings, authority flags, OOS events. When something changes, it generates a new Carrier Selection Record with a new timestamp showing what I knew and when.
What I had for Summit Ridge: the February approval record, and a monitoring alert from six weeks prior when their Vehicle Maintenance BASIC ticked up. I had documented a re-verification call to their insurance agency and a note that I'd requested a re-signed carrier agreement before the next load. I had both the agreement and the call log.
Not every broker gets to hand over a file like that. Most don't have monitoring at all. Their file is the January onboarding packet and seven months of silence.
The adjuster and I had a two-minute conversation. He got the file the next morning.
The plaintiff's attorney still named me in the initial filing — that's standard. But they withdrew the claims against me within 90 days once they saw what I had. The file did the talking.
How I document this
At carrier approval:
- Pull the SAFER company snapshot and save it with a date-stamped filename
- Pull the FMCSA L&I insurance history — not just the COI — and save it separately
- Verify operating authority with a dated record, separate from the onboarding date
- Get a signed carrier agreement with indemnification and insurance warranty language
- File the Carrier Selection Record in DOTScreener at approval time
Before each load on an existing carrier:
- Run a current authority check (takes 30 seconds; do it every time)
- Pull insurance status against L&I, not just the COI on file
- Review any Continuous Monitoring alerts since the last load before booking
When a monitoring alert fires:
- Document what the alert showed: what BASIC, what percentile change, what date
- Document what action you took: additional verification, re-signed agreement, declined load, or escalated to a compliance review
- Do not book without an updated vetting action timestamped in the file
When the accident call comes:
- Preserve everything immediately — nothing gets archived, deleted, or "cleaned up"
- Pull the complete vetting history before you return any calls
- Don't volunteer information beyond confirming the load relationship until you've spoken with your attorney
- Know what your file says before you describe it to anyone
That last point matters more than any of the others. The adjuster who called me at 11:52 PM was professional and polite. But he was working. The question he asked — "what documentation do you have" — has one good answer and a lot of bad ones. The good answer is knowing exactly what's in your file before you pick up the phone.
Your file should be able to speak for itself. If you're not sure what it says, find out before they ask.
---
— Mason Lavallet
Founder, DOTScreener.com
Automate your carrier vetting
DOTScreener runs every check in this article automatically — live FMCSA data, documented decisions, tamper-evident audit trail.
Go deeper
Related Articles
The Oversize Carrier Vetting Gap That FMCSA Won't Fill For You
FMCSA authority doesn't say a word about whether a carrier's state oversize permits are current. Most brokers don't ask. Here's what to check before you tender a permit load.
Broker GuidesNot Rated Isn't a Safety Rating. It's the Absence of One.
The majority of active motor carriers in FMCSA's system are 'Not Rated' — and most brokers treat that as a neutral signal. It isn't neutral. It's the absence of a formal evaluation, and it tells you almost nothing about whether the carrier is safe.
Broker GuidesYour Carrier's OOS Rate Looked Fine. The OOS Order Is Why You're Getting Sued.
Most brokers check the OOS rate in SAFER and call it done. But a carrier's historical OOS rate doesn't tell you whether they're currently under an active out-of-service order. Those are completely different things, and only one of them matters at load tender.