Why Monitoring Tools Aren't Enough Post-Montgomery

For years, the carrier-vetting conversation had a comfortable answer. "We use a monitoring service." It signaled diligence. It checked the box. If anyone asked how you managed carrier risk, you named your tool and moved on, and that was usually the end of it.

Montgomery v. Caribe Transport ended that. Not because monitoring tools got worse — they're as good as they ever were — but because the question changed, and monitoring was never built to answer the new one. This is the most important thing the industry hasn't fully absorbed yet: the most popular tools in carrier vetting are excellent at a job that is no longer the job that gets you sued.

Let me be fair before I'm critical. Carrier411, SaferWatch, DAT CarrierWatch and their peers do real work. They watch authority, insurance, and CSA scores across your roster, alert you when something changes, and — in some cases — share bad-actor reports so a carrier who burns one broker gets flagged for the next. For fraud prevention and ongoing monitoring, that's valuable, and I'm not telling anyone to cancel their subscription. I'm telling you it isn't a legal defense, and after Montgomery, that distinction is the entire ballgame.

What Montgomery actually changed

The short version: for a long time, brokers leaned on FAAAA preemption as a shield against negligent-selection claims — the argument that federal transportation law preempted state tort suits over how a broker chose a carrier. *Montgomery v. Caribe* knocked that shield down. Negligent-selection theory now maps cleanly onto brokers, and — because they never had the preemption defense to begin with — onto shippers who pick their own carriers, too.

Here's why that's a monitoring problem specifically. Before Montgomery, the dominant risk in carrier selection was fraud — double-brokering, chameleon carriers, freight theft. Monitoring is exactly the right tool for fraud: it's continuous, it watches for changes, it networks bad-actor reports. The tool and the risk were perfectly matched.

After Montgomery, the dominant risk became a negligent-selection lawsuit. And that risk has a completely different shape. The plaintiff's attorney doesn't ask whether you were defrauded. They ask:

That is an evidentiary question about a single moment in the past. Monitoring is a surveillance capability oriented toward the present and the future. The mismatch isn't a flaw in the tool. It's a category difference.

The four things litigation needs that monitoring doesn't produce

When you actually sit down with what a negligent-selection defense requires, the gap stops being abstract. A defensible record needs four specific properties, and monitoring is structurally oriented away from all four.

1. A tender-date snapshot — not a live status. The legal question is what the carrier's safety profile looked like on the day you selected them. Monitoring tools are designed to tell you the status now and to alert you when it changes. That's the opposite orientation. "We monitor this carrier" says nothing about what their BASICs were on March 14th or what you did about it that day.

2. A per-decision record — not account-level coverage. The case is about this load, this carrier, this tender. Monitoring is roster-level and continuous — "we watch all our carriers." A jury doesn't ask whether you have a subscription. It asks what you did before you put this carrier on the road, on this day.

3. An immutable timestamp — not an editable dashboard. The defense lives or dies on proving when the record was created. Monitoring dashboards show live, changing data and aren't built to freeze a tamper-evident artifact of a specific moment. A dashboard screenshot is the textbook "screenshots and notes" evidence plaintiff's attorneys attack as undated, cherry-picked, or created after the crash.

4. The carrier's own attestation — not just external data. A strong record pairs the public FMCSA data with the carrier's signed representations about its insurance and safety practices, so that if the carrier lied, your reliance was demonstrably reasonable. Monitoring watches external data; it doesn't capture the carrier attesting, under its own name, on the date of tender.

So a brokerage can have a flawless monitoring setup and still have nothing to hand the plaintiff that says: "Here's what we checked, on this carrier, on this day, against this standard — and here's the carrier confirming it." The monitoring kept the fraudsters out and watched the scores. It did not build the evidentiary trail.

"But our tool keeps a history"

This is the most reasonable objection, so let me take it seriously. Several monitoring tools log alerts and keep a change history. Isn't that a record?

It's a record — of changes the tool observed, on the tool's schedule, in the tool's format. It is not a record of your decision. It doesn't capture the policy you applied, the pass/fail standard you held the carrier to, the human who approved a borderline carrier and why, or the carrier's attestation. And critically, it's still oriented around "what changed and when did we notice" — surveillance — rather than "what did we decide, and on what basis, before we tendered" — diligence.

A change log proves the tool was running. A defense needs proof that you exercised reasonable care. Those are not the same artifact, and a jury is being asked about the second one.

What "enough" looks like now

The bar moved. The informal standard at a lot of shops used to be: glance at SAFER, maybe save a screenshot, jot a note in the TMS, move on. In a fraud-dominated risk world, that was roughly adequate. In a negligent-selection world with eight-figure verdicts, it isn't.

The standard a careful broker or shipper should now hold itself to is a consistent, per-load, timestamped, policy-scored, attestation-backed record — applied the same way on every tender, by every operator, and frozen into something you can produce in discovery three years later. An evidentiary trail, not a folder of screenshots and a monitoring login.

That's the category DOTScreener was built for, and it's deliberately not a monitoring tool. It runs the carrier's live FMCSA picture at the moment of decision, scores it against your written, versioned policy, captures the carrier's signed attestation, and freezes the whole thing into a tamper-evident, timestamped record — a Carrier Selection Defense Packet built backwards from the deposition. You can screen a carrier and watch the record get built in real time.

To be clear, this is and, not or. Keep monitoring to catch fraud and roster drift. Add documented diligence to build the record that defends you when the question is no longer "were you defrauded" but "were you careful, and can you prove it." The two tools cover two different risks, and after Montgomery, you're exposed on both.

A monitoring subscription tells you a carrier is risky today. It does not tell a jury you were careful then. That second sentence is the one that wins or loses a negligent-selection case — and it's the one monitoring was never built to say.

— Mason Lavallet

Founder, DOTScreener.com

Frequently Asked Questions

Are carrier monitoring tools still worth using after Montgomery?

Yes — for the job they're built for. Monitoring tools are strong at fraud prevention and watching your roster for authority, insurance, and CSA changes over time. Montgomery didn't make them less useful for that. It just exposed a second risk — negligent-selection liability — that monitoring was never designed to address. Most mature programs keep monitoring and add documented diligence on top.

Why isn't continuous monitoring a legal defense?

Because a negligent-selection claim turns on what you knew and did on the day you selected a specific carrier, and monitoring is oriented toward the present and future — current status and change alerts. It generally doesn't capture a tender-date snapshot, a per-decision record tied to one load, an immutable timestamp, the written policy you applied, or the carrier's signed attestation. Those are the elements a defense actually needs.

What does a defensible carrier-selection record include?

A snapshot of the carrier's FMCSA safety profile as of the tender date; a record tied to that specific load and carrier; the written, versioned policy and pass/fail standard you applied; a verifiable, tamper-evident timestamp; a documented approval trail for any borderline (WARN/FAIL) decisions; and the carrier's own signed attestation so your reliance was demonstrably reasonable.

Does adding documented diligence mean dropping my monitoring tool?

No. They solve different problems. Run monitoring to keep bad actors out and catch changes; run documented screening to manufacture the evidentiary record that defends a negligent-selection claim. After Montgomery, you have exposure on both fronts, so the strongest programs run both.

Sources

• What Montgomery v. Caribe Means for Brokers and Shippers
• DOTScreener vs. Carrier411 for Legal Defense — the head-to-head breakdown
• Carrier Vetting Software Compared
• Carrier411 Isn't Legal Protection — Here's the Difference
• Restatement (Second) of Torts § 411 — Negligent Selection of an Independent Contractor
• FMCSA SAFER Company Snapshot — the underlying public safety data
• FMCSA Safety Measurement System (CSA BASICs) — the scores monitoring tools track