Your Carrier File Gets Deposed. Not You. The File.

A broker I know sat for four hours of deposition last November. He had a SAFER snapshot in his carrier file — printed, filed, everything where it was supposed to be. Except the only date on it was written in the upper corner with a Sharpie, because that was how his office had always done it. Opposing counsel picked it up, held it for a moment, and asked: "You wrote this date yourself, correct? There's no system-generated timestamp on this document?" He said yes. The next twenty minutes were about whether he could actually prove he'd done the check before the load moved, or whether the date in the corner could have been written after the fact.

He had done the check. He was telling the truth. But he couldn't prove it to a standard that held up under cross. His attorney told me later that exchange cost them six figures at settlement because the defense couldn't definitively establish timeline.

That is the gap this post is about. Not whether you did the diligence. Whether your file can prove you did it, to someone who is paid to doubt you.

This Is Now a Legal Document, Not a Compliance Habit

Before May 14, 2026, brokers in the Seventh and Eleventh Circuits had a reasonable argument that FAAAA preemption blocked state-law negligent-selection claims entirely. That ended with Montgomery v. Caribe Transport II, LLC. The Supreme Court held, unanimously, that the FAAAA does not preempt state negligent-selection claims against freight brokers. Every carrier file you build from here forward is a potential exhibit in state court litigation. That's not a threat — it's just the legal landscape now.

What that means practically: the standard for your diligence documentation isn't "did I check the boxes?" It's "can I hand this file to a defense attorney at 9 PM on a Friday and have them walk into court Monday morning with a defensible story?" Most carrier files I've seen fail that test — not because the broker skipped steps, but because the record of those steps doesn't hold up under three basic lines of cross-examination.

Four Questions Opposing Counsel Will Ask

Defense attorneys prep you for depositions. Plaintiffs' attorneys prep the file. When a carrier file lands in discovery, here's the sequence of questions that gets asked — in various forms, across several hours.

When exactly did you check? Not "the morning of." Not "before the load moved." A specific time. "9:47 AM on March 4th" is defensible. "Morning of" is not. If your vetting record doesn't contain a corroborable timestamp — one that was generated by a system, not written in by a human after the fact — you're relying on testimony to fill the gap. Testimony can be challenged. System timestamps are much harder to dispute.

What did it show at the time you checked? A SAFER snapshot that exists in your file today might look different from what SAFER showed the day of the load. Carriers update. Ratings change. BASIC scores move. A screenshot with no embedded timestamp, no URL with a date parameter, and no metadata proves only that you ran the check at some point. Plaintiffs' lawyers know this. The question "isn't this the same SAFER page, but printed after the crash?" is a real deposition question. The answer "no, here's the system-generated export from 10:03 AM on the day of tender" ends that line of inquiry. The answer "I believe so, but I can't be certain" does not.

What was your decision threshold? This one catches brokers off guard. Your file might show that you checked a carrier's BASIC scores. What it often doesn't show is what score was acceptable versus disqualifying. If you approved a carrier with a 72nd-percentile Unsafe Driving BASIC, the question is: what was your cutoff? Was it 80%? 75%? Did you write it down anywhere? If your SOP says "review BASIC scores" but doesn't define pass/fail, then your approval of a borderline carrier looks like a judgment call made with no criteria — which is exactly the characterization that supports negligence. A written threshold — even an imperfect one — converts that judgment call into a documented policy decision.

Did you deviate from your threshold, and what did you write down? This is the one most brokers have absolutely nothing on. You had a policy. You made an exception. Maybe the carrier had one red flag but was referred by someone you trusted, or the load was time-sensitive, or the flag turned out to be a data error you verified by phone. None of that helps you in deposition if it's not in the file. An undocumented exception looks like the policy didn't exist — or worse, that you knew about the problem and moved the load anyway.

The Timestamp Problem

I'm not asking you to become a forensic archivist. But I want to be specific about what "corroborable timestamp" actually means, because this comes up constantly.

A screenshot you take on your phone has EXIF metadata. A PDF exported from a vetting platform typically embeds creation date in the document properties. An email you send yourself with the SAFER URL at time of check has a sent timestamp. A CarrierWatch or QCMobile export often includes a "report generated" date in the header. These are system-generated. They can be verified by someone other than you.

A Sharpie date in the corner cannot.

A handwritten note in a folder cannot.

A comment in your TMS that says "checked FMCSA, all clear" with no supporting attachment can be challenged on the grounds that it doesn't specify what you found.

The fix isn't complicated. If your platform generates a dated export, save it. If it doesn't, send yourself the URL in an email at time of check — the email timestamp is corroborable. If you're pulling SAFER directly, the snapshot URL contains enough identifying information that an IT forensics professional can confirm what version of the page it represents if metadata supports the date.

I'm not saying you need to run your vetting through a blockchain. I'm saying your documentation needs to be something that an independent party could look at and say: "this was generated at this time, and it shows this." That's a realistic bar. Most brokers just haven't been building to it.

The Exception Record You're Not Writing

Every broker has loads where the carrier cleared every standard check but triggered one question mark — a three-month-old authority that got a strong reference from a partner broker, a high OOS rate from a period when the carrier was managing a fleet expansion, a lapsed insurance certificate that turned out to be a refiling delay the insurer confirmed by phone.

You moved those loads. You had good reason to. And you have nothing in your file about any of it.

That exception record is the most important thing most brokers never write, and it's the thing that would protect them most if the exception turned out to be wrong.

A one-paragraph note — written before the load moves, not after — that says: "Carrier MC-1247893 / DOT-3567102 shows a 71st-percentile Vehicle Maintenance BASIC. Spoke with dispatch (call logged at 11:14 AM) to confirm recent repair shop relationship and review current PM schedule. Driver count is two; both drivers appear active in Clearinghouse with no prohibitions. Approved at 11:30 AM under the following rationale: single BASIC flag, low inspection frequency, no OOS violations in past 12 months. Load value $62,000, standard dry van." That is not a long note. It took me three minutes to type that. In discovery, it is the difference between "the broker reviewed available data and made a documented decision" and "the broker saw a red flag and moved the load anyway."

The Regulatory Floor Is Lower Than You Think

49 CFR § 371.3 tells brokers what they must keep: transaction records — carrier name, bill of lading number, compensation, freight charges. That's it. Three-year retention. No requirement to keep SAFER screenshots, BASIC score exports, or exception notes.

The floor is low by design — it was written in a different era. The problem is that some brokers read "I'm only legally required to keep transaction records" as permission to document nothing beyond what § 371.3 demands. That's backwards thinking. The regulation defines the minimum the government requires. The negligence standard — now fully available to plaintiffs in state court — asks something much harder: did you exercise reasonable care in selecting this carrier? That question is answered by everything you did, documented or not. You want documentation on your side of that answer.

How I Document This

Every carrier approval in DOTScreener generates a timestamped record: the data source, the score or status at time of pull, and the date/time of the query. That gets attached to the carrier record in a format that can be exported as a PDF with embedded creation date.

For anything that requires a phone call — a borderline BASIC, a reference check, a question about an ownership change — I type a brief note into the file before the truck rolls. Time, who I spoke with, what they said, what I decided and why. If I'm approving a carrier despite a flag, I note the flag, the additional verification I ran, and the conclusion. Thirty seconds.

The SAFER URL goes in the record too. Not a screenshot. The URL, copied and timestamped by email to myself when the session is active. If I ever need to establish that I ran a check at 10:03 AM on a specific date, the email server log is my witness.

None of this is complicated. It's just not what most brokers are doing, because until May 14, 2026, they had a reasonable argument that the paper trail was a formality. It's not a formality anymore.

How I Document This (Short Version)

• System-generated PDF export with embedded creation timestamp for every SAFER/L&I pull
• Any borderline approval gets a one-paragraph written rationale before the load is tendered — what the flag was, what I verified, what I decided
• Phone calls logged with time and summary before the truck picks up
• § 371.3 transaction records retained for 3 years minimum; vetting records same
• Exception documentation includes: the specific concern, the additional verification step, the outcome, and the timestamp of the decision

That's it. It doesn't take long. It just has to happen before the load moves, not after.

— Mason Lavallet

Founder, DOTScreener.com