The Defect Was Already in the Log. Nobody Checked.

The brake job was in the log. The driver had written it up two Tuesdays before the crash — right air chamber, audible leak at brake application. The line item in the DVIR read "defect noted." The next entry, same day, read "corrected" with the carrier's maintenance supervisor's initials.

The shop never touched it. No repair order. No parts receipt. No shop labor entry. Nothing.

Six days later, a fully loaded flatbed blew through a traffic backup on I-55 at 64mph and hit four stopped vehicles. The carrier was MC-1247893 / DOT-3567102. Eighteen months of authority, Satisfactory safety rating, Vehicle Maintenance BASIC sitting at the 71st percentile the last time anyone looked — which was at carrier onboarding, eleven months before the crash.

The discovery subpoena asked for all DVIRs for that specific truck going back 90 days. Plaintiff's counsel had them in hand before the carrier's insurer finished acknowledging the claim. The signed-off "corrected" notation with no supporting documentation told the whole story: the carrier's maintenance program existed on paper and nowhere else.

Then came the deposition of the brokerage's compliance manager.

"Did you ever ask this carrier how they handled defects reported in their driver vehicle inspection reports?"

She hadn't. Most brokers don't. Most brokers have never heard the acronym DVIR.

What 49 CFR § 396.11 and § 396.13 Actually Require

Under 49 CFR § 396.11, a commercial motor vehicle driver is required to complete a written inspection report at the end of every day of driving. The report has to cover specific systems: service brakes, parking brakes, steering, lights, tires, horn, windshield wipers, rear vision mirrors, coupling devices, wheels, emergency equipment. If the driver finds a defect or deficiency, they have to note it. The carrier then has to certify either that the defect was repaired or that the defect doesn't need repair before the next trip — meaning a burned-out marker light might not ground a truck, but a brake issue does.

That's the post-trip side.

§ 396.13 covers the pre-trip side. Before operating that vehicle, the next driver — or the same driver starting their next day — must review the previous DVIR. If defects were noted, the driver must make sure the carrier has signed off that they've been addressed. The driver signs the new DVIR to acknowledge the review. The carrier retains both DVIRs for three months.

So what you get, if the carrier is following the rules, is a document chain: post-trip report with defect noted → repair certification by the carrier → pre-trip acknowledgment by the next driver. Three months of that chain, for every truck, for every trip.

If the carrier isn't following the rules, you get something different: blank forms, rubber-stamped "no defects" on trucks that haven't been looked at, or "corrected" notations with nothing behind them. Which is exactly what the discovery subpoena in that I-55 case produced.

Why the DVIR Chain Matters in a Crash Case

When a crash is caused or contributed to by a mechanical failure — brake failure, tire blowout, steering defect, anything equipment-related — the first document any competent plaintiff's attorney subpoenas is the DVIR file for that truck. The reason is simple: if the defect was in the log and the carrier signed off that it was corrected when it wasn't, that's not negligence. That's falsification of a federal record. The case shifts from "they made a mistake" to "they knew and they lied."

Even if it doesn't rise to falsification, a DVIR file that shows repeated defect entries on the same system — the same brake chamber, the same tire position, the same turn signal — builds a picture of deferred maintenance. The carrier knew about the problem. They kept running the truck anyway. They just kept checking "corrected" and moving freight.

That picture is devastating in front of a jury. It's even more useful for settlement negotiation, which is where most of these cases actually end.

What's equally damaging, in a different way, is a carrier that simply doesn't have DVIRs. No records means either they weren't maintaining the trucks at all, or they were destroying records — neither of which plays well. Courts treat missing records with an adverse inference in many jurisdictions: if you had the records and they showed what you claim, you'd have kept them.

The Broker's Position in This Picture

Here's where most brokers tune out: "That's the carrier's problem. We don't maintain trucks. We're not responsible for their maintenance records."

True, strictly speaking. You're not. You don't own the truck. You don't employ the driver. You don't sign the DVIR.

But post-Montgomery v. Caribe Transport II, LLC — the Supreme Court's unanimous May 2026 decision holding that FAAAA preemption doesn't block state-law negligent-selection claims — the question isn't whether you maintained the truck. The question is whether your decision to select that carrier was reasonable given what you knew or should have known.

And if you selected a carrier running at the 71st percentile in Vehicle Maintenance with no follow-up inquiry and no re-check since onboarding, and that carrier's mechanical failure caused a fatal crash, the plaintiff doesn't need you to have signed the DVIR. They just need to show you chose a carrier the data was already warning you about, and you either didn't notice or didn't care.

"Did you review the carrier's BASIC scores before this load?" If the honest answer is "I checked at onboarding," the follow-up is obvious: "So you didn't check them the day you tendered?" That's the gap. Not the DVIR itself. The DVIR is the carrier's problem. Your problem is the selection decision and whether you documented why you made it.

What Reasonable Inquiry Looks Like

I'm not saying brokers need to audit carrier maintenance shops. That's absurd, it's not your job, and no jury will expect it. What they will expect — what "reasonable care" looks like in plain terms — is that you asked some questions when the data suggested you should.

If a carrier's Vehicle Maintenance BASIC is sitting at the 68th percentile or higher, that's a signal. Not necessarily a hard stop, but a signal worth acting on. The reasonable response is an inquiry. A phone call. "Walk me through your maintenance program. Do you do pre- and post-trip DVIRs on all drivers? Are your trucks on a preventive maintenance schedule? Who handles defect repairs when a driver writes one up?"

You don't need to verify any of it. You can't. But you need to ask, and you need to write down what they told you.

That conversation does two things. First, it actually helps you assess the carrier — a carrier whose maintenance manager can't explain their DVIR process, or who gets defensive when you ask, is telling you something. Second, it creates a record. If something goes wrong, your file shows you identified the elevated BASIC, you made a specific inquiry, and you got satisfactory answers. That's not a perfect defense, but it's a defensible one. It shows you weren't just moving loads blind.

A carrier that has a good maintenance operation will tell you how it works in about three sentences, and they won't mind the question. That's been my experience. The ones who bristle at it are usually the ones who don't have an answer.

The § 396.17 Annual Inspection Piece

There's one more angle brokers almost never think about: 49 CFR § 396.17 requires every commercial motor vehicle to pass a periodic inspection at least once every 12 months. The inspection has to cover all the systems listed in Appendix G to Subchapter B of Part 396 — brakes, tires, wheels, lighting, coupling devices, the whole list.

You can ask a carrier when their equipment was last through an annual inspection. You can ask whether they use a third-party shop or do it in-house. You can ask whether the inspection reports are available to shippers and brokers on request. Most carriers won't mind the question. Some will say something like "we do them annually at our yard" with no third-party documentation — and that's worth noting. Not a hard stop, but worth noting.

None of this is in the typical carrier packet. The carrier agreement doesn't mention it. The ACORD 25 certificate doesn't mention it. The SAFER snapshot doesn't tell you when the last § 396.17 inspection happened. You have to ask. And the asking is what distinguishes the broker who survives depositions from the broker who gets a verdict read against them.

How I Document This

When a carrier's Vehicle Maintenance BASIC is at or above the 65th percentile:

• Pull the current BASIC percentile and note it in the carrier file with the date.
• Note any alerts. A BASIC "alert" isn't a disqualification, but it should trigger an inquiry.
• Make a phone call. Ask specifically: "How does your shop handle defects that come in on DVIRs? Who's responsible for certifying repairs?" Write down what they say, with the date and who you spoke to.
• If you ask about the § 396.17 annual inspection and they can't tell you when the last one was, note that too.
• Put all of it in the carrier file. Not an email thread — a carrier file entry that dates the action and records the response.

If the BASIC is below 65, I still note the number in the file. It takes five seconds. If a crash happens eight months from now and the BASIC was clean at tender, that's a useful data point.

The DVIR is the carrier's document. The decision to tender is yours. Your file should make it clear that you connected those two things.

---

— Mason Lavallet

Founder, DOTScreener.com