All articles
Broker Guides August 17, 2026 7 min read

The Pre-Trip Your Carrier Skipped Left a Trail. Most Brokers Never Look for It.

The Vehicle Maintenance BASIC isn't just an equipment score — it's a window into whether a carrier's drivers are actually doing pre-trip inspections before they roll. Most brokers never read it that way. Post-Montgomery, that's a mistake with a dollar amount attached.

The driver who put his rig into the back of a stopped semitruck on I-65 near Lafayette signed a pre-trip inspection form that morning. His terminal manager confirmed it. The form said the unit — a 2019 Peterbilt with 612,000 miles on it — was in satisfactory condition.

Post-crash inspection told a different story. Brake lining worn past the service limit. A cracked brake chamber on the right steer axle. The kind of degradation that doesn't happen in twelve hours; the inspecting officer estimated it had been building for days. Which means the pre-trip that morning was either done badly, or it wasn't done at all.

The carrier was MC-1247893, DOT-3871045. Their FMCSA Vehicle Maintenance BASIC was sitting at the 76th percentile — flagged — and had been there since the previous quarter. The load had been a refrigerated produce run, $54,000 of chicken going to a distribution center outside Indianapolis. The broker who'd tendered that load eight months prior had a carrier file with a COI, a SAFER screenshot, and an MC Authority Active check. The VM BASIC wasn't in it. Nobody had checked it at load tender. The deposition established that nobody had ever checked it.

After Montgomery v. Caribe Transport II, "I didn't know about that" is the start of a negligent-selection analysis, not the end of one.

What 49 CFR § 396.13 Actually Requires

Before a driver moves a commercial motor vehicle, the law requires them to be satisfied that the vehicle is in safe operating condition. That's § 396.13. Specifically, the driver has to review the last Driver Vehicle Inspection Report — the DVIR — submitted for that unit before taking it out.

§ 396.11 is the companion rule: at the end of each driving day, drivers must prepare a written report noting any defects or deficiencies observed. If defects are noted, the carrier has to certify that repairs were made — or that the defects noted don't affect safe operation — before the next driver signs off.

At load-tender time, that chain matters because it's your carrier's internal safety filter. Driver finds defect → reports it → carrier repairs or certifies it as non-safety-affecting → next driver acknowledges the report before rolling out. That process is supposed to catch bad equipment before it rolls onto a federal highway. When it breaks down, inspectors catch it instead — and it goes into the FMCSA record.

The Vehicle Maintenance BASIC Is a Pre-Trip Failure Signal

Here's the connection most brokers never make. The FMCSA's Vehicle Maintenance BASIC counts inspection violations involving equipment defects found during roadside inspections over a 24-month window. Brakes. Tires. Lights. Steering. Suspension. These aren't exotic categories — they're exactly the items a driver is supposed to check during a pre-trip inspection.

If inspectors are repeatedly finding brake violations on a carrier's units during roadside stops, those violations represent defects that the driver either didn't catch or didn't report. Either the pre-trip is being done carelessly, or the form is getting signed by someone who didn't actually walk around the truck.

A carrier at the 75th percentile on Vehicle Maintenance isn't just a carrier with older equipment. It's a carrier whose inspection chain is breaking down. The roadside record is the evidence.

That matters for your vetting in two ways. Equipment defects are in the causation chain in a significant portion of serious injury crashes — not always the root cause, but often a contributing factor. And in a post-Montgomery environment, "contributing factor" is enough to survive a motion for summary judgment and go to a jury.

Second: when a carrier's VM BASIC is elevated, a plaintiff's expert can reconstruct a pattern from the inspection record. They don't need to prove this specific defect caused this specific crash. They need to show the carrier had a known, documented pattern of equipment problems, and you tendered them anyway without noting it.

What This Looks Like in Discovery

Your carrier had a 71st-percentile VM BASIC at the time of tender. You didn't note it. A year later, a crash, and post-crash inspection finds a brake defect.

Plaintiff's counsel pulls the carrier's roadside inspection history. Seven violations involving brake deficiencies across four units in the 18 months before your load. They ask: "Did your vetting of this carrier include any review of their FMCSA Vehicle Maintenance BASIC?"

If you say no, the next question is why not. If you say yes but can't document it, you might as well have said no.

Then they show the jury the inspection history. They don't ask you whether this carrier was safe. That question was already answered in the breach.

Before Montgomery, a broker in the 7th or 11th Circuit could argue federal preemption — FAAAA as a liability shield. That argument is dead. The Supreme Court was unanimous. Brokers are now fully exposed to state-law negligent-selection claims, which means the deposition that used to stop at "we checked the MC authority" now goes a lot further.

The Vehicle Maintenance BASIC is sitting in SAFER. It's free. It was there when you tendered. That's the part that's hard to explain from the witness stand.

When to Treat It as a Hard Stop

I'll share where I draw lines, not because you have to draw them in the same place, but because having documented thresholds is better than reviewing the same facts and reaching different conclusions on different days.

Above 65th percentile on VM BASIC, I want to understand the violation mix before I proceed. Predominantly light and marker violations? Different conversation than predominantly brake and tire violations. The specific defect categories matter — a carrier at 68th percentile because of three burned-out marker lights is different from a carrier at 68th because of two OOS brake violations and a tire separation.

Above 80th percentile, I need a specific documented reason to proceed. A review of the underlying violations, a conversation with the carrier about current equipment status, something on paper.

Above 80th percentile combined with authority under 18 months? That's a combination I'm walking away from unless I have a very specific written reason to stay. Young authority at high VM percentile isn't a carrier still figuring things out — it's a carrier that was already having equipment compliance problems in their first year of operation. That's a different risk profile.

The Vehicle Out-of-Service rate compounds this. A carrier with a high VM BASIC and a Vehicle OOS rate above 25% isn't just scoring poorly on an index — they're having units pulled out of service during active inspections. That means equipment that wasn't road-worthy when it rolled out. That's not a data problem; that's an operations problem.

Pre-Trip in the Carrier File

Here's what I want documented at onboarding when VM BASIC is a flag worth noting.

I ask the carrier to describe their pre-trip inspection process. Who does the inspection? What form are they using? How do they handle a reported defect before the next driver takes the unit? I'm not auditing their terminal. I'm creating a record that I asked. The deposition question isn't "did they have a good process?" — it's "did you inquire?"

DOTScreener pulls the Vehicle Maintenance BASIC as part of every carrier screen. When a screen comes back with an elevated VM BASIC, that score is part of the Carrier Selection Record — date-stamped, specific percentile, attached to the carrier's MC. If I screen the same carrier in six months and the BASIC has moved, the new record shows the new score. The old record stays.

That matters because "I screened this carrier on March 15 and their VM BASIC was at the 43rd percentile" is a provable, documented claim. "I checked and everything looked fine" is not.

How I Document This

For every carrier screen, Vehicle Maintenance BASIC gets noted. Not just the percentile — the interpretation. What's the violation mix? Is this brakes and tires, or is this markers and reflectors?

Above the 60th percentile: document the score and my read on it. Is this a trend or a recent spike? Does the carrier's operating profile (age of authority, fleet size, type of freight) fit the violation history?

Above the 75th percentile: I document a specific decision. If I'm proceeding, I write down why. If I'm not proceeding, same. The file needs to show that I saw the number and made a considered call, not that I never looked.

At onboarding for any carrier with elevated VM BASIC: I note that I asked about their pre-trip and DVIR process, and what they told me. That response doesn't bind them to anything legally. But it shows up in my carrier file as evidence that I treated vehicle maintenance compliance as part of my selection criteria.

The carrier file needs to be able to answer one question: "Did you know this carrier had equipment maintenance compliance issues, and what did you do about it?" If the VM BASIC was elevated and I tendered anyway, the file shows what I knew, when I knew it, and why I made the call I made. That's not a red flag. That's documented judgment.

Documented judgment survives a deposition. A blank file doesn't.

— Mason Lavallet

Founder, DOTScreener.com

DOTScreener

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