Broker risk
What Montgomery v. Caribe Actually Changed for Brokers (and What It Didn't)
· 6 min read
Montgomery v. Caribe did not create a new federal checklist, but it changed the broker liability fight by weakening preemption for safety-based negligent-hiring claims.
By LongMile
The short version: **Montgomery v. Caribe did not create a new federal carrier-vetting checklist for brokers. It did remove a major preemption defense for safety-related negligent-hiring claims.**
That difference matters. A broker can still argue it acted reasonably. But after the Supreme Court's May 14, 2026 decision, many brokers will have to make that argument on the facts instead of ending the case early with Federal Aviation Administration Authorization Act preemption.
This article is practical risk guidance, not legal advice. Use it to tighten your carrier-selection file, then review your actual standard with counsel.
Quick Answer: What Changed?
The Supreme Court held that a state-law negligent-hiring claim against a freight broker can fall within the FAAAA safety exception when the claim concerns motor-vehicle safety. The official opinion in Montgomery v. Caribe Transport II, LLC, No. 24-1238 is short, but the operational impact is not.
Before Montgomery, brokers often argued that negligent-selection claims were preempted because they related to broker services. After Montgomery, that argument is weaker for safety-based claims involving the motor carrier selected for a load.
| Broker question | Practical answer |
|---|---|
| Can brokers still use preemption? | Sometimes, especially for non-safety claims. |
| Did the Court create a checklist? | No. It left reasonableness to ordinary negligence analysis. |
| Does documentation matter more now? | Yes. Your file may become the proof of what you knew. |
| Is every bad crash broker liability? | No. Plaintiffs still need facts, duty, breach, causation, and damages. |
What the Court Actually Held
The case involved allegations that C.H. Robinson negligently selected Caribe Transport for a shipment even though the carrier had safety problems. Lower courts dismissed the broker claim on FAAAA preemption grounds. The Supreme Court reversed.
The Court reasoned that negligent-hiring duties are part of state safety authority and that selecting the carrier whose trucks will move the goods concerns motor vehicles. That put the claim inside the FAAAA safety exception.
The key operational point is simple: if the claim is about unsafe carrier selection, a broker should expect the plaintiff to focus on what public information was available before dispatch.
What Montgomery Did Not Do
Montgomery is easy to overstate. It did not say brokers are automatically liable when a carrier crashes. It did not impose a federal due-diligence standard. It did not say every state-law claim against a broker survives preemption.
Several legal alerts make the same distinction. Crowell notes that non-safety claims tied to prices, routes, or services remain different. Faegre Drinker frames the holding around negligent hiring and the safety exception. Adams and Reese points to underwriting and commercial-process effects for brokers.
So the right takeaway is not panic. The right takeaway is proof.
The New Broker Risk Framework
After Montgomery, carrier vetting needs to answer three questions:
- **What did we check before dispatch?**
- **What did those checks show at that time?**
- **Why was the booking decision reasonable despite any red flags?**
If you cannot answer those from a saved record, you may be left reconstructing the decision months or years later. That is a weak position because public data changes. Insurance status changes. Authority status changes. Safety ratings and inspection history can change.
What to Check Before Booking
A defensible process does not have to be complicated. It does have to be consistent.
| Check | Why it matters | Save proof |
|---|---|---|
| Operating authority | Confirms the carrier can operate for the move. | FMCSA/SAFER snapshot |
| Safety rating | Shows known federal safety posture. | Rating and date checked |
| Insurance status | Confirms required coverage signals. | Policy/source notes |
| OOS and crash indicators | Shows available safety history. | Public data snapshot |
| Authority age | Flags very new or reincarnated entities. | MC/DOT dates |
| Identity match | Helps catch fraud and chameleons. | Phone, address, packet match |
FMCSA describes brokers as intermediaries who arrange transportation rather than transport the freight themselves in its broker and freight-forwarder definitions. That intermediary role is exactly why the carrier-selection record matters: the broker's decision is the disputed act.
Manual Process vs. Documented Process
A manual process can work if it creates a record. A browser-only process is harder to defend.
A workable manual flow looks like this:
- Assign a dispatcher or compliance owner to run the same checks every time.
- Save the public-source snapshot or report with the load file.
- Note exceptions in plain English: what was found, who approved it, and why.
- Re-check when the load is delayed, re-powered, or materially changes.
- Keep the record in a place that cannot be casually edited later.
A documented process creates a time capsule. It does not prove the decision was perfect. It proves what the broker actually saw and how the broker responded.
Common Mistakes Brokers Make
The first mistake is treating Montgomery as only a legal department issue. It is an operations issue because dispatchers and carrier reps create the facts.
The second mistake is saving only the carrier packet. A polished packet is not the same thing as a public-source verification file.
The third mistake is applying standards inconsistently. If your policy says conditional ratings require manager approval, then the approval needs to be visible in the file.
The fourth mistake is relying on memory. A dispatcher may remember checking SAFER. A plaintiff attorney will ask for the timestamped proof.
Where LongMile Fits
LongMile helps brokers turn carrier checks into saved, timestamped verification records. That does not replace legal judgment or a written carrier-selection policy, but it does make the operational proof easier to keep with the load.
What to Do Monday Morning
Start with a one-page carrier-selection SOP. List the checks, the disqualifiers, the exception process, and the storage location. Then audit five recent loads. For each one, ask: if this load became a claim, could we prove what we knew before dispatch?
If the answer is no, Montgomery changed something very practical for your brokerage: it made undocumented vetting too expensive to ignore.
FAQ
Did Montgomery make brokers liable for every carrier crash?
No. The decision allows certain safety-related negligent-hiring claims to avoid FAAAA preemption. Plaintiffs still have to prove the elements of their claim.
Does the case require brokers to use a specific software tool?
No. The case does not mandate software. It makes consistent, provable carrier-selection records more important.
Should brokers stop using carriers with any red flag?
Not automatically. Some red flags are disqualifiers; others require documented review. The danger is ignoring red flags or failing to explain the decision.
What is the biggest operational change after Montgomery?
Treat carrier vetting as a recordkeeping workflow, not a quick lookup. The file should show what was checked, when it was checked, and who approved the decision.
Tags: Montgomery v. Caribe, freight broker liability, carrier selection, negligent hiring, FAAAA preemption