The Pre-Trip Attestation Chain Brokers Don't Think About — Until Discovery Starts

A flatbed hauling steel coil goes through an intersection in rural Indiana. Loaded. Driver fault. The sedan in the cross lane gets pinned under the trailer. The sedan driver dies.

The carrier — MC-1247893 / DOT-3891047, northern Illinois, 34 months of authority, clean SAFER snapshot — carries BIPD. Their insurer starts working it. The plaintiff's attorney files against the carrier and, three weeks later, adds the broker to the suit. The broker is our office. We tendered the load two days before the crash.

Discovery opens. Subpoenas go to the carrier. In the boxes that come back: 90 days of driver vehicle inspection reports, sorted by truck and trip date.

Three consecutive trips before the crash. Same tractor. Same driver. DVIR entry each time: "Air brake pressure loss, approximately 60 mph sustained grade." Carrier signed back: "Defects corrected." What actually happened: shop reset the slack adjuster. Didn't replace the brake lining. Didn't pull the drum. The pressure drop was still there on the next trip, and the next. The driver signed the pre-trip attestation every time: "I have reviewed this report and I acknowledge defects noted were corrected."

Third trip after that: the crash.

The plaintiff's attorney took my deposition. One question that I still think about: "Before tendering this load, did you ever request or review the carrier's pre-trip inspection records?" The answer was no. The follow-up: "Were you aware that federal regulations require drivers to review and sign maintenance defect records before each trip?" Also no. I didn't even know what 49 CFR § 396.13 was.

That's the problem. Not that I should have reviewed their DVIRs. I wasn't going to do that, and nobody expects me to. The problem is that I didn't understand the chain — what it meant that the signal was there in the VM BASIC data, and what a reasonable broker might have done about it before tender.

What § 396.13 actually requires

The regulation is short. Before operating a commercial motor vehicle, the driver must review the driver vehicle inspection report (DVIR) required by § 396.11 from the prior trip. If the report notes defects or deficiencies, the driver must sign the DVIR and acknowledge that the defects have been repaired or that repair isn't necessary for safe operation.

That's the whole thing. Review the last inspection report. If there were defects, sign that they're fixed (or acknowledged). Then drive.

The practical result is that every time a carrier has a defect on a truck and that truck goes back on the road, there's a document with a human signature that says "I saw this problem and I was told it's fixed." The carrier keeps those documents for at least three months under § 396.11(c). When plaintiffs' lawyers subpoena maintenance records, the pre-trip attestation chain is in the box.

The three-regulation chain

These three sections of Part 396 create a paper trail that functions like a chain of custody for mechanical knowledge:

§ 396.3 is the foundation: carriers must "systematically inspect, repair, and maintain" every vehicle they operate. All parts and accessories must be "in safe and proper operating condition at all times." This is the duty. Violation of it is the negligence.

§ 396.11 is the post-trip record: drivers must complete a written inspection report at the end of every day of operation covering specified systems — service brakes, parking brakes, steering, tires, lights, coupling devices, and more. If defects are found, the carrier certifies they were corrected before the vehicle goes back on the road. Three-month retention minimum.

§ 396.13 is the pre-trip attestation: before the next trip begins, the next driver (or the same driver) reviews that post-trip report and signs it. Their signature confirms they know what the report said and whether the repairs happened.

Together: defect documented by the driver → carrier certifies repair → next driver confirms they reviewed the repair record → vehicle operates. If the defect wasn't actually fixed and a crash happens, discovery reveals that two to three people signed documents saying it was. That's not a gap in the record. That's a documented decision chain with names on it.

What this has to do with you after Montgomery

You're not in that chain. You didn't sign anything. The driver did, the carrier maintenance manager did, the dispatch supervisor probably authorized the run. You're the broker who tendered the load two days earlier.

So why does it matter to you?

Montgomery v. Caribe Transport II, LLC, decided May 14, 2026, unanimous, answers that. The Supreme Court held that the FAAAA does not preempt state-law negligent-selection claims against freight brokers. Before Montgomery, most circuits — particularly the 7th and 11th — held that those claims were preempted. That door is now open in every state court in the country.

Negligent selection turns on what you knew and what you should have known about the carrier at the time you hired them. The § 396.13 chain is evidence of what the carrier knew about their own equipment's condition. It proves that someone inside that organization had knowledge of a recurring defect and made an operational decision anyway.

The question for the broker isn't "did you see the DVIR?" You didn't. You couldn't. The question is: "Did the available signals suggest a maintenance problem? Did you look at those signals? Did you ask anything about it? And if not — why not?"

If the carrier's Vehicle Maintenance BASIC was at the 74th percentile the day you tendered — meaning worse than 74% of comparable carriers on maintenance violations found during roadside inspections — and you tendered the load without noting the score or asking a single question about their maintenance practices, that's an explanation you need to give under oath. "I didn't know what that number meant" is not a great answer when the carrier had a documented brake defect chain on the same truck.

The VM BASIC as a proxy for what you can't see

You're not going to request 90 days of DVIRs before every load. That's not the industry, it's not practical, and it's not what regulators require of brokers. But the VM BASIC in CSA is doing that aggregation for you — imperfectly, with lag, but it's doing it.

The Vehicle Maintenance BASIC percentile reflects the rate at which roadside inspectors found vehicle maintenance violations on that carrier's trucks. Brake defects, tire violations, lighting failures, coupling issues. When a carrier is at the 65th percentile or above, that means inspectors who randomly stopped their trucks found maintenance violations at a higher rate than 65% of their peer carriers. Those inspection records are real. They're documenting the same kind of equipment condition that the pre-trip attestation chain is supposed to prevent.

A high VM BASIC doesn't mean a carrier's pre-trip chain is broken. Plenty of carriers with elevated VM scores run tight operations that got hit on a technicality. But a carrier at the 70th percentile-plus on VM, with an OOS rate on vehicle violations above 4%, and authority under 24 months — that's a combination that tells you their maintenance culture has been documented as deficient by the people who actually looked at their trucks. That's what should be prompting a question at load tender, not silence.

What to ask, and why it's not about getting an answer

Two questions I ask now when a carrier flags on VM metrics. Neither is regulatory. Neither is required. Both end up in the carrier file.

First: "What's your brake inspection interval — how often do you pull drums?" The actual answer matters less than whether anyone in dispatch can give one. A carrier running a tight PM program has an answer. If the person on the phone says "I'd have to check with maintenance," that's information. Not a dealbreaker, but information.

Second: "Walk me through what happens when a driver writes up a defect on the inspection report." Again, not a gotcha. What I'm listening for: do they know what § 396.11 requires? Do they have a process, or is this a dispatching house that views maintenance as someone else's problem?

Neither question proves anything about whether that carrier's trucks are safe. But asking them and logging what you were told creates a record that says: I saw the signal. I asked about it. Here's what they told me. I made a decision with that information in hand.

That's the difference between a vetting record that holds up in deposition and one that doesn't.

How I document this

Whenever the Vehicle Maintenance BASIC is above the 60th percentile or the vehicle OOS rate exceeds 4%, my carrier vetting note includes:

• VM BASIC percentile and the date I pulled it
• Vehicle OOS rate — I calculate this myself from the inspection count and violation count in FMCSA L&I, not just the BASIC score, because the score's lag can run 60 days
• Whether I called dispatch and what maintenance questions I asked
• A verbatim summary of what they told me — not a cleaned-up paraphrase, the actual substance of the answer
• The tender decision and what it was based on

If I approved the load despite elevated VM scores, I note what else I saw that supported the decision: high inspection count (statistically reliable signal), no recent OOS violations, satisfactory rating, long authority tenure. Something concrete.

If I declined, I note what the combination looked like and why it tipped the decision.

What I don't do is pull SAFER, see a marginal VM score, and move on without recording that I saw it. That's the gap that shows up when discovery starts. Not fraud. Not bad intent. Just silence where a signal existed — and after Montgomery, silence is something a jury in state court gets to fill in.

The pre-trip attestation is a 30-second ritual at a truck stop. The driver reviews a form, signs their name, and drives. Ninety-nine times out of a hundred, nobody ever looks at that form again. The hundredth time, it's in a box of subpoenaed records and a plaintiff's attorney is using it to show what a carrier knew about a defect on a truck you put on the road.

You can't control that chain. But you can control whether your vetting record shows you looked at the available signals and asked the right questions before you tendered.

— Mason Lavallet

Founder, DOTScreener.com