The Pre-Trip Inspection Most Brokers Never Ask About — And Why Montgomery Changed That

The pre-trip inspection is one of those parts of the FMCSRs that everyone in trucking knows exists and almost no broker thinks about. It's in the carrier's lane. The driver does it before the trip. It's their job, not the broker's. Why would a broker ask about it?

That used to be the right answer. Yesterday's answer. Pre-*Montgomery*, brokers had FAAAA preemption to lean on — most state-law negligent-selection claims got dismissed early, so the analysis of what counted as "reasonable diligence" was thinner than it needed to be. After *Montgomery v. Caribe Transport II* dropped the preemption shield, that thin analysis is being rebuilt in real time. The pre-trip inspection question turns out to be one of the cleanest places for a broker to *shift* the legal posture, because it's the carrier's job and the carrier can be asked, in writing, to confirm they did it.

That confirmation is doing actual legal work. Most brokers haven't started using it yet. Here's why they should.

What the regulation actually says

49 CFR § 396.13 is the pre-trip inspection rule. It says — and I'm paraphrasing the practical effect — that before driving a motor vehicle, the driver shall:

1. Be satisfied that the motor vehicle is in safe operating condition.

2. Review the last driver vehicle inspection report (DVIR).

3. Sign the report, if the vehicle has one with defects noted, to acknowledge that any defects requiring repair have been certified as repaired.

This is the driver's independent duty. Not the carrier's, not the broker's — the driver's. If a driver pulls out without doing this, they've violated § 396.13. If the vehicle then has a wreck because of a defect a pre-trip would have caught, the driver and carrier are independently in violation.

The brilliant — and underused — thing about § 396.13 from the broker's standpoint is that it creates a fact the carrier alone can know. Did the driver inspect the vehicle this morning? The broker doesn't know. The shipper doesn't know. Only the carrier knows. So if the broker asks the carrier to *attest* that the pre-trip happened, the broker is asking the carrier to make a representation about something only the carrier can speak to.

That representation, in writing, is gold.

Why this matters legally — the mechanics

When a plaintiff sues a broker for negligent selection after a crash, the broker's defense rests on showing reasonable diligence in selecting the carrier. The diligence file is everything the broker did to know who they were tendering to.

In the carrier file, an attestation that the pre-trip was completed (with a signature, a timestamp, and a name) does a few things at once:

It's evidence the carrier represented compliance with § 396.13. If the carrier later turns out to have skipped the pre-trip — say, the brakes were obviously broken and any inspection would have caught it — the carrier's signed attestation is now a *false representation* in the broker's file. That false representation is simultaneously (a) an independent FMCSR violation by the carrier and (b) a contract breach by the carrier with the broker.

It supports an indemnification claim. Most broker-carrier agreements have an indemnification clause that runs against the carrier for breach. A false safety attestation is a breach. The indemnification kicks in.

It documents the broker's reliance. The broker's negligent-selection defense isn't "I knew the carrier was safe." It's "I exercised reasonable care to know what I could know, including by requiring the carrier to confirm in writing the things only the carrier could confirm." The reliance language matters because the legal posture is materially better when the broker is documented as relying on the carrier's representations rather than relying on their own (potentially wrong) judgment about safety.

This is the architecture that *Montgomery* changed. Pre-Montgomery, none of this analysis mattered much because the suit got tossed on preemption. Post-Montgomery, the diligence file is the case. Pre-trip attestations are one of the highest-leverage line items in it because they're cheap to obtain, easy to document, and the legal weight is real.

A concrete scenario

You tender a load to MC-1289304 / DOT-3019847. The carrier signs an electronic safety attestation confirming, among other things, that "a pre-trip inspection has been completed on the assigned vehicle in accordance with 49 CFR § 396.13."

Three days later, the truck has a wreck. The post-crash inspection shows the brakes were in critical out-of-service condition — they would have failed any honest pre-trip.

Now look at the file. The carrier signed an attestation saying the pre-trip was done. The post-crash evidence shows the pre-trip wasn't done — or was done dishonestly. The carrier's attestation is now a false representation in the broker's diligence file.

Plaintiff's argument: the broker was negligent in selecting this carrier. Broker's argument: we exercised reasonable diligence, including obtaining a written representation from the carrier that the vehicle was inspected and in safe operating condition. The carrier breached that representation. The breach is the carrier's fault, not the broker's.

This is the liability-shift mechanic. It's not magic — a determined plaintiff's lawyer will argue that the broker should have done more, and depending on the facts they may be right. But the file has gone from "broker tendered to a carrier who turned out to be unsafe" to "carrier represented they had inspected the vehicle, broker relied on that representation, representation was false." The legal weight on the broker's shoulders is different.

Why this only works if you actually do it

The attestation has to be specific, the carrier has to have signed it before the trip began, and the broker has to have a tamper-evident record of it. A vague "we agree to comply with all federal regulations" boilerplate doesn't do this work. The attestation needs to cite the specific representations the carrier is making, by name. Pre-trip done. Driver qualified. Insurance in force. Cargo securement complete. Each one ties to a specific FMCSR provision.

The attestation also has to be paired with reliance language. Something like: "I acknowledge the broker is relying on these representations in selecting our company for this specific load." Without that language, you have a representation but not necessarily an established reliance relationship. With it, you have both.

Most carriers don't object to signing this kind of attestation because each item is, in fact, their existing legal duty. Asking them to confirm in writing that they did something they're already required to do is not asking them for anything new. It's asking them to make their existing compliance visible.

The brokers I see resisting this process are usually the ones who haven't sat through a deposition yet.

A second concrete scenario

Same carrier, same load. Different ending. The driver actually did the pre-trip honestly. They found nothing wrong with the brakes (because there was nothing wrong with the brakes). They drove out. Three days later, the truck is rear-ended at a stoplight by an inattentive four-wheeler.

The carrier's pre-trip attestation in your file did nothing to prevent the wreck. But it also wasn't false — and the post-crash evidence supports that. The diligence file is what you wanted it to be: a record of reasonable steps taken before dispatch. The wreck wasn't the carrier's fault and isn't the broker's responsibility. The case probably doesn't get filed against you. If it does, your file is what it should be.

Either way — false attestation or honest one — the broker is in a defensibly better position than the broker who didn't ask the question at all.

The regulation, in plain English

49 CFR § 396.13 is the pre-trip inspection rule. § 396.11 is the related driver vehicle inspection report (DVIR) requirement — what the driver writes up after the trip if defects are found. § 396.7 is the general rule that no carrier shall operate a motor vehicle in such a condition as to likely cause an accident. These three sit together in Part 396 (Inspection, Repair, and Maintenance) and form the carrier-and-driver responsibility chain.

What this means at load-tender time: the broker can require, by contract, that the carrier represent and warrant compliance with these provisions for the specific load. That representation creates the documented reliance the broker needs in the post-*Montgomery* world. The carrier's compliance is their problem; the broker's evidence that they relied on the carrier's stated compliance is the broker's protection.

How I document this

For every load tendered, the carrier file contains:

1. **A specific, itemized safety attestation** signed by the carrier or its driver-of-record before dispatch. The pre-trip item must be present and cited by CFR section.

2. **Reliance language** acknowledging the broker is relying on the representations for the selection decision.

3. **Signer identity** — name, title (driver of record / safety director / dispatcher with authority), timestamp, IP, and ideally device fingerprint.

4. **Continuing duty to notify** — language requiring the carrier to update the broker if any representation becomes untrue between attestation and delivery.

The whole thing fits on one screen, takes the carrier two minutes to sign, and adds the strongest single line item to the broker's diligence file. After *Montgomery*, this is no longer a nice-to-have. It's the architecture of the defense.

— Mason Lavallet

Founder, DOTScreener.com

---

Sources

• [49 CFR § 396.13 — Driver inspection](https://www.ecfr.gov/current/title-49/subtitle-B/chapter-III/subchapter-B/part-396/section-396.13)
• [49 CFR § 396.11 — Driver vehicle inspection report(s)](https://www.ecfr.gov/current/title-49/subtitle-B/chapter-III/subchapter-B/part-396/section-396.11)
• [49 CFR Part 396 — Inspection, Repair, and Maintenance (overview)](https://www.ecfr.gov/current/title-49/subtitle-B/chapter-III/subchapter-B/part-396)
• [Hanson Bridgett — Supreme Court Unanimously Holds Negligent-Hiring Claims Against Freight Brokers Survive FAAAA Preemption](https://www.hansonbridgett.com/publication/260514_8509_supreme-court-faaaa)
• [Bricker Graydon Wyatt — SCOTUS: FAAAA Does Not Preempt Negligent-Selection Claims Against Freight Brokers](https://www.bricker.com/insights/publications/scotus-faaaa-does-not-preempt-negligent-selection-claims-against-freight-brokers-what-brokers-carriers-and-shippers-should-do-now)