Three weeks after a fatal crash in rural Tennessee, a plaintiff's firm sent a discovery request to a brokerage I know. The request listed twenty-three categories. Category four was something like: "all documents identifying the specific vehicle, including VIN, license plate, and unit number, used to transport the subject shipment." The brokerage had the carrier's MC number, the authority printout from SAFER, an insurance certificate, a carrier packet with a W-9, and a rate confirmation. They had nothing — zero — in category four.
The carrier had thirty-two trucks on their MCS-150 filing. Which one moved the load? Nobody knew. And in discovery, "I don't know" is the same as "I didn't check."
What Plaintiff's Counsel Actually Asks For
Post-Montgomery v. Caribe Transport II, the subpoena language has gotten sharper. Plaintiff's firms that work truck-accident cases have been refining their requests for years, and they know exactly where the documentation holes are. The carrier-entity level is mostly covered now — good brokers have the MC pull, the authority age, the insurance on file. But the equipment level is where they find the vacuum.
The specific questions they're drilling on now:
- What vehicle actually moved this shipment?
- When did you last physically document that vehicle's condition?
- Did you know the carrier was operating equipment with recent out-of-service violations?
- Did the unit that caused the crash appear anywhere in your pre-load records?
That last one is the killer. Under 49 CFR § 396.13, a driver is required to review the prior vehicle inspection report before operating a commercial vehicle. The carrier is supposed to certify defects are repaired. Most brokers read that as "the carrier's problem" — and from a compliance standpoint, it is. But from a negligent-selection standpoint after a crash, whether you had any information about the specific vehicle before tendering is a legitimate question about your due diligence.
If the answer is "we had nothing on the truck, only on the company," you're fighting on uneven ground.
The SAFER Snapshot Tells You Nothing About Which Truck Showed Up
A carrier with a Satisfactory rating, a clean crash indicator, and 11 power units on their MCS-150 filing is a carrier you might reasonably approve. I'd approve them — pending their insurance and authority age. But the Satisfactory rating tells you the operation passed a compliance review. It doesn't tell you anything about which of those 11 trucks is going to show up at your shipper's dock at 0600.
Take MC-1247893, DOT-3567102. Thirty-two unit dry van operation, Satisfactory safety rating, 3.1% OOS rate, authority since 2021. Solid on paper. You vet them, approve them, and give them a load. What you don't know is that unit 28 — an '09 Peterbilt with VIN starting 1XPWD49X09D — had a Level I inspection six weeks earlier that flagged brake adjustment issues. The driver signed off. The carrier certified the fix. The load moved. Then, four months later, that same Peterbilt is involved in a rear-end collision on I-40 and someone dies.
Plaintiff's counsel pulls the vehicle inspection records from FMCSA. They find the Level I from six weeks before your load. Then they pull your carrier file and show the jury: you approved the carrier, you had no information about this specific vehicle, and you didn't ask. Whether that gets you to a verdict depends on state law and the jury — but it's an uncomfortable position. It's much more comfortable if your file has a photo of that truck, timestamped, from the pre-tender Verifi™ check, showing the actual plate and unit number.
The Four Things a Per-Unit Record Closes
When you have a photo record pinned to the specific VIN — not just a photo of a truck, but a photo tagged to the actual unit card in the carrier's fleet — you close four gaps simultaneously.
You prove which truck was on your load. The plate in the pre-tender Verifi™ shot matches the plate on the crash report. That's not nothing. That's a direct line from your vetting record to the actual equipment.
You establish a timeline for the equipment's condition. "On August 5, 2026, at 7:14 AM, the driver submitted a photo of unit number 28 showing the exterior, cab, and CDL." That's evidence of what the truck looked like at time of tender. It's not a DOT inspection, but it's documentation.
You catch VIN substitution before the load moves. This matters most in the double-broker scenarios — the fraudulent carrier shows up with a truck that doesn't match the carrier's fleet at all. If you have photos from the last time you moved freight with this carrier, pinned to the VINs on their equipment list, a truck that's never been photographed or has a VIN that doesn't match their MCS-150 filing is an instant red flag. You catch it before the load moves, not in discovery.
You build a durable equipment record. The single most useful thing about pinning photos to a VIN is that the record doesn't reset when you run a new screening on the same carrier. Screen MC-1247893 today, photograph their unit 28, and six months from now when you tender them a load again, that photo is sitting on the unit card already. Your team doesn't have to re-document what you already documented. The history accumulates.
The FMCSR Section That Makes This Matter Most
49 CFR Part 396, Vehicle Inspection, Repair, and Maintenance, is the regulatory home for equipment condition. Subpart A covers periodic inspections, § 396.13 covers driver pre-trip responsibilities, and § 396.17-23 sets the inspection interval requirements. None of those sections require a broker to inspect a carrier's equipment. But they create the factual context in which a jury evaluates your choices.
If the regulations require the carrier and driver to document equipment condition, and you as the broker have access to that kind of documentation via a pre-tender photo capture but chose not to use it, "I didn't know the equipment was defective" starts to sound less like an honest statement and more like a choice to remain uninformed. Plaintiff's counsel will make that argument. You want to have a record that undercuts it.
What This Looks Like in Practice
The workflow isn't complicated. Before you tender to any carrier — especially one you haven't moved freight with in the last 90 days — run a Verifi™. The driver gets a link, submits photos of the truck and trailer and their CDL, and the GPS pins the location. That submission lands on the screening record.
Now, with Fleet Intelligence unit photos, the photos you collect over time don't just live on individual screening records. You can pin them to the specific truck or trailer on the carrier's fleet roster by VIN. So when unit 28 of MC-1247893 has been photographed on three loads over six months, those photos accumulate on unit 28's card. The next time anyone on your team opens that carrier's screening, they see the history of that specific piece of equipment — what it looked like, when it was last documented.
That's the record that answers category four on the discovery request. "All documents identifying the specific vehicle" — here's a timestamped photo of the truck, the trailer, the plate, and the driver's CDL, from the pre-tender Verifi™, pinned to the unit in our fleet records.
How I Document This
For any carrier I use more than twice:
1. Run a Verifi™ on the first load. Get photos of the power unit, the trailer, the cab, and the plate — plus the CDL. Pin the truck photos to the unit card in the fleet roster by VIN. Pin the trailer the same way.
2. On subsequent loads, if I'm using the same carrier but can't confirm it's the same equipment, run Verifi™ again. If the truck is in the fleet roster and already has photos, a Verifi™ photo that matches is confirmation. A truck that's never been in their roster — and shows up anyway — is a call before the load moves.
3. Keep the carrier-entity vetting separate from the unit documentation. SAFER and the MC pull go in the carrier file. The Verifi™ submissions and the unit photos go in the fleet record. They're two different layers of the same defense — the company-level record and the equipment-level record.
4. For any load over $50,000 in cargo value or any load involving a carrier I've used fewer than three times, the Verifi™ is non-negotiable. That's the bar I've set for myself. Below that threshold on both factors with a well-documented carrier, I'll sometimes skip it. But I never skip it when either condition is true.
If your documentation stops at the MC number, your carrier file is incomplete. That's not a criticism — it's where most of the industry still is. But plaintiff's counsel has figured out where the gap is. The question is whether you close it before a load goes sideways, or explain it afterward.
---
_[Fleet Intelligence unit photos are live on DOTScreener now — open any screening, click a unit card in the Fleet section, and add a photo. It pins to the VIN and shows up every time you screen that carrier.]_
— 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
Your Carrier Has a Satisfactory Rating. That's Not the Green Light You Think It Is.
A Satisfactory safety rating means a carrier passed a compliance review — at some point. It doesn't mean they're safe right now. Here's what to check instead of stopping at the headline.
Broker GuidesOne Approval Event. Fourteen Months. A Lot Can Go Wrong in Between.
Your carrier approval is a snapshot, not a subscription. After Montgomery, the question in a deposition isn't just 'did you vet this carrier?' — it's 'was that vetting current when you tendered this load?' Here's why continuous monitoring and re-filed Carrier Selection Records are a better answer than a 14-month-old carrier packet.
Broker GuidesYour Carrier Agreement Isn't Evidence. Here's How to Make It One.
Most carrier agreements are PDFs with a scanned signature and no chain of custody. A plaintiff's attorney has four questions for that document — and a blank PDF in a folder answers none of them. Here's what an actual evidentiary record of carrier approval looks like.