The Daily Inspection Report Your Carrier Is Required to Keep — and That You've Never Asked About

Here's a number that changes how I look at Vehicle Maintenance BASIC scores: roughly 40% of out-of-service orders during CVSA roadside inspections are brake-related. Not brake violations in general. Out-of-service brake violations — the kind where the inspector decides the truck should not move under its own power.

Legally, those violations are evidence that the carrier knew or should have known about the defect. The driver should have caught it at pre-trip. The carrier should have caught it in their maintenance program. The form that documents whether either of those things happened is the Driver Vehicle Inspection Report. DVIR. 49 CFR § 396.11. And the honest answer is that most brokers have never asked a carrier whether they maintain it consistently, and couldn't tell you how long carriers are required to keep it.

That's a gap. After Montgomery v. Caribe Transport II, LLC — the Supreme Court's unanimous May 2026 decision that FAAAA preemption does not bar state-law negligent-selection suits against brokers — that gap is no longer theoretical.

What 49 CFR § 396.11 actually requires

§ 396.11 is the carrier-facing rule. It requires the driver to prepare a written report at the end of every day the vehicle is operated. The report must cover, at minimum:

• Service brakes, including trailer brake connections
• Parking brake
• Steering mechanism
• Lighting devices and reflectors
• Tires
• Horn
• Windshield wipers
• Rear vision mirrors
• Coupling devices
• Wheels and rims
• Emergency equipment

If the driver identifies a defect, it goes on the report. The carrier must then certify — in writing, on the same form — that the defect was repaired or that it isn't a safety issue and the vehicle can operate. The carrier must retain these reports for three months.

That retention window isn't about FMCSA audits. It's about what's available in discovery when a crash happens in month two.

How § 396.13 connects — and where brokers get confused

§ 396.13 is the driver's side of the same transaction. Before taking the wheel, the driver must review the previous trip's DVIR. If that report noted defects and the carrier certified they were repaired, the driver signs the form acknowledging the repair. If the previous DVIR was clean, no signature is required. The driver just drives.

This is where most brokers who've heard about "pre-trip attestations" misunderstand what they're asking for. The § 396.13 acknowledgment only generates a paper document when the previous DVIR had defects noted. A clean DVIR produces nothing the driver signs. So asking a carrier for "the pre-trip attestation" and getting nothing back is technically consistent with a clean prior inspection — or consistent with no inspection at all.

You can't tell the difference from outside the cab.

The DVIR itself (§ 396.11) is the document that exists regardless. That's the one most brokers have never thought to ask about.

What the Vehicle Maintenance BASIC tells you — and what it doesn't

The Vehicle Maintenance BASIC tracks violations found during roadside inspections. Brake violations. Tire violations. Lighting defects. It reflects what inspectors found when they stopped the truck.

What it doesn't track: whether the carrier's drivers are completing DVIRs daily. A carrier with a blank BASIC hasn't necessarily been inspected. Blank can mean genuinely low inspection frequency, genuinely clean compliance, or a carrier operating lanes and schedules that avoid weigh stations. All three look the same from the outside.

A carrier with a 74% Vehicle Maintenance BASIC has a documented history of inspectors finding violations. That tells you violations existed and were found. It doesn't tell you whether the carrier's internal DVIR process was catching the same problems before an inspector showed up.

That's the question that never gets asked.

The scenario that makes this concrete

MC-1247893 / DOT-3512047 has been operating 26 months. Vehicle Maintenance BASIC at 62% — below the 80% intervention threshold, nothing in alert. Clean authority, valid $750,000 BIPD and $100,000 cargo on file in L&I. You tender a load. Three hours into the haul, the truck has a rear brake failure on an interstate downgrade. Three vehicles involved. Serious injury crash.

The plaintiff's lawyer — in state court, because post-Montgomery the FAAAA preemption shield is gone — sends a discovery request that includes:

"All documents relating to the condition of the vehicle at the time of dispatch, including driver vehicle inspection reports, pre-trip inspection records, maintenance logs, and brake inspection records."

Your carrier file has: a SAFER snapshot from the tender date, an L&I insurance verification, a broker-carrier agreement, and a BASIC printout.

The plaintiff's argument: "The broker performed no diligence into the carrier's vehicle inspection practices. The carrier's Vehicle Maintenance BASIC showed a history of roadside violations. The broker never asked whether the carrier maintained daily DVIRs, never asked whether the assigned vehicle completed a pre-trip inspection, never asked the carrier to confirm compliance with 49 CFR § 396.11."

Whether that argument wins depends on the judge, the jury, and the specific crash facts. But the argument is available because the file has no record that you asked the question.

What you should actually be asking

This doesn't require demanding a carrier's DVIRs on every load. It requires one question, in writing, per dispatch:

"Please confirm that a pre-trip inspection under 49 CFR § 396.11 was completed on the assigned vehicle prior to dispatch, and that your driver reviewed the previous DVIR per § 396.13."

Carrier responds in text, email, or dispatch note. That response goes in the load file.

What this does legally: it's a carrier representation that they complied with their independent regulatory duty. If they lied — if they skipped the DVIR and something broke — their false representation to you is now a separate fact in the case. You relied on it. You documented that you asked. The carrier's FMCSR violation is front and center, and your position as a diligent broker is documented.

If the carrier doesn't respond, or says something like "we don't really do it that way" — that's information you needed before the load moved.

Some carriers will push back on this question as unnecessary overhead. A carrier who argues that confirming basic regulatory compliance is burdensome is telling you something about their compliance culture. I move on.

For carriers with high Vehicle Maintenance BASICs

If a carrier's Vehicle Maintenance BASIC is at 75% or above, one question isn't enough. At that level, inspectors have repeatedly found violations. The question shifts from "did you do a DVIR today" to "what does your maintenance program actually look like."

For those carriers I want written responses covering:

• Preventive maintenance interval — how often does each vehicle get a full inspection?
• Whether they use a third-party maintenance shop or in-house, and the shop name
• Whether DVIRs are electronic (traceable) or paper
• The last brake service date on the specific tractor assigned to this load

That's more homework than most loads warrant. But if you're tendering to a carrier with Vehicle Maintenance in alert, you need documentation that you went beyond the standard check. The additional documentation doesn't protect you if the carrier is fundamentally unsafe. It demonstrates that you took the BASIC seriously and dug further.

How I document this

Every load file gets:

1. T-call confirmation. Text or email to the carrier with the § 396.11/396.13 compliance question and their written response. Time-stamped. Filed against the load number. "Carrier confirmed per-trip DVIR compliance in writing at 10:47 AM [date] via text — [message body]" is the full record.

2. Vehicle Maintenance BASIC at dispatch date. Not from onboarding. The score at the time of this specific tender. If it changed significantly between onboarding and today, I note it.

3. Assigned equipment note. If the carrier identifies the specific tractor and trailer, that goes in the file. If they don't, I ask. "We have a truck for it" is not a carrier file entry.

For carriers at 75%+ Vehicle Maintenance: add the maintenance program summary items above, or don't tender.

This takes about ninety seconds. The documentation it produces is the difference between "we checked their scores" and "we exercised reasonable diligence on the specific mechanical risk this carrier presented based on their BASIC history." The first answer doesn't hold post-Montgomery. The second one might.

The DVIR sits in the carrier's cab and their maintenance files. But the question of whether it exists — that's something you can document asking.

— Mason Lavallet

Founder, DOTScreener.com