The Supreme Court's broker-liability ruling answered one big question and quietly opened another. Montgomery v. Caribe Transport II, LLC (May 14, 2026) made clear that brokers can be sued for negligently selecting a carrier. But carriers don't freeze in time after onboarding. A carrier that was Satisfactory when you approved it last year can pick up a Conditional rating, let its insurance lapse, or run its CSA scores into the red — and you may book it again next week without noticing. The unsettled question that will drive the next wave of litigation: does a broker's duty end at selection, or does it follow the carrier? Here's why "monitor, don't just onboard" is becoming the safer answer.

What the ruling did and didn't decide

Montgomery was, on its face, a selection case: the broker chose a carrier with a Conditional FMCSA rating, and the court let the negligent-selection claim proceed. It did not announce a freestanding "duty to monitor." But it framed the broker's obligation around the safety information available at the time of booking — and that framing has a logical tail. If the relevant question is what you knew or should have known when you tendered the load, then for a carrier you've used for two years, "what you should have known" includes whether its safety picture has deteriorated since onboarding. For the core holding and its operational fallout, see our Montgomery ruling breakdown.

Why onboarding-only vetting has a blind spot

Most brokerages vet hard at onboarding and rarely again. That made sense when preemption capped exposure, but it leaves a gap the new liability standard will probe. Consider what changes after you approve a carrier:

• Safety ratings shift. A compliance review can drop a carrier from Satisfactory to Conditional months after you onboarded it.
• Insurance lapses. A certificate that was active at onboarding can be cancelled or non-renewed without anyone telling you.
• CSA scores drift. Unsafe Driving, HOS, and Maintenance percentiles move as new inspections and crashes post.
• Authority changes. Operating authority can be revoked or go inactive.

If you re-book a carrier whose record quietly went bad, the plaintiff's argument writes itself: the warning signs were public, you'd worked with them for months, and you never looked again. That's the onboarding blind spot.

Does the broker have a duty to monitor carriers after onboarding?

Honestly, the law isn't settled — and that's exactly why it's risky. No court has yet imposed a crisp, universal duty of continuous monitoring on brokers, and reasonable lawyers disagree about how far Montgomery's logic reaches. But "the duty is unsettled" is cold comfort when a catastrophic-crash plaintiff is arguing to a sympathetic jury that any careful broker would have re-checked a carrier it used every week. Waiting for an appellate court to draw the line is a strategy that gets tested with your own case.

The defensible posture is to get ahead of it: treat carrier safety as a status you keep current, not a gate you pass once. That's both better risk management and better operations — you'd rather not be the broker still booking a carrier whose insurance lapsed last month, regardless of who's liable.

What continuous monitoring actually looks like

Continuous monitoring doesn't mean re-running a full onboarding packet every week. It means watching the signals that change and re-checking before reuse:

• Re-pull safety ratings and CSA scores on a cadence for active carriers, and before re-tendering after a gap.
• Track insurance status so a lapse or cancellation flags before the next load, not after a loss.
• Watch authority for revocations or inactivity.
• Log each re-check, so your record shows the carrier was still current when you booked — the same "document or defend" logic that governs selection. See Document or Defend and the Carrier Vetting Checklist 2.0 for the underlying checks.

Onboarding-only vs. continuous

• Before: Vet once at onboarding; assume the carrier stays as approved. Preemption limited the downside of being wrong.
• After: Treat safety as a live status; re-check before reuse and log it. The downside of a stale approval is now a jury question.
• Before: "We vetted them when we signed them up."
• After: "We confirmed they were still safe on the day we booked this load."

Why this is an automation problem, not a willpower problem

Continuous monitoring is where manual processes fall apart completely. Re-pulling ratings, watching insurance, and logging re-checks across an active carrier base of hundreds is not something a sales team will sustain on top of moving freight — and the moment it slips, the blind spot reopens. This is precisely the kind of always-on, every-load discipline software is built for.

Debales deploys AI agents that handle carrier communications and load tendering and capture safety checks and approvals automatically as a timestamped trail — so re-verification can run as part of the booking flow rather than as a separate chore someone has to remember. Whether or not courts ultimately impose a formal monitoring duty, the broker whose system already keeps carrier safety current is the broker who never has to explain the gap. The diligence you can prove is the diligence that protects you.

The takeaway

Montgomery made selection a liability. The next case may make re-selection one too. You don't have to wait for that ruling to know which way the wind is blowing — close the onboarding blind spot now by treating carrier safety as a status you keep current on every load. It's better risk posture and a better-run brokerage either way.

See how Debales keeps carrier safety checks current and logged across every booking. Learn more at debales.ai.