The Supreme Court’s decision in Montgomery v. Caribe Transport II, LLC raises scrutiny on one of the most important parts of a broker’s workflow: carrier selection.
In a unanimous 9-0 ruling, the Court determined that freight brokers are not shielded from state-level negligent-hiring lawsuits under the Federal Aviation Administration Authorization Act (FAAAA). The decision allows personal injury claims against brokers to proceed when questions arise around the safety of the carrier selected to haul a load.
For brokers, the ruling changes how carrier selection decisions may be evaluated after an incident occurs.
Federal operating authority alone is no longer enough to point to when defending carrier selection decisions. Courts may now look more closely at whether brokers ignored warning signs tied to a carrier’s safety history, inspection performance, or operational record.
The case centered on allegations that a broker hired a carrier with a conditional safety rating and a history of driver qualification deficiencies.
The Supreme Court’s opinion clarified an important distinction inside FAAAA. While the law limits state regulation tied to prices, routes, and services, it does not eliminate a state’s authority to regulate motor vehicle safety.
The ruling makes carrier selection practices more central to how broker liability may be evaluated in court, adding more pressure for broker due diligence than ever before.
For years, brokers have worked in an environment where FMCSA authority often served as a baseline indicator that a carrier was approved to operate.
The ruling increases attention on how carriers are evaluated and documented.
Questions that may carry more weight moving forward include:
The decision does not mean brokers are automatically liable when accidents occur.
It does mean carrier selection workflows may become a more central focus in litigation, underwriting, and insurance review.
The ruling comes at a time when brokers are already managing tighter margins, growing documentation demands, and rising compliance expectations.
Now, the ability to demonstrate consistent carrier vetting may become even more important across several areas of the business:
Plaintiff attorneys may place greater focus on the broker’s decision-making process and whether safety concerns were overlooked during carrier selection.
Insurance providers may begin placing more emphasis on documented carrier risk management practices, auditability, and ongoing monitoring.
Brokerages may need stronger consistency around how carriers are reviewed, approved, monitored, and retained inside their networks.
The challenge for many organizations is scale.
Reviewing carrier history manually across thousands of carriers creates operational friction and increases the likelihood that important details are missed.
The ruling increases pressure on brokers to show how carrier decisions are made and monitored over time. That creates a stronger need for systems that support consistent carrier evaluation, centralized safety visibility, ongoing monitoring, and documented review processes.
CAB by Fusable has been helping the transportation industry evaluate and understand risk for decades. Through its Motor Carrier Brokerage solution, CAB helps freight brokers build more consistent and defensible carrier vetting workflows using centralized safety, inspection, operational, and monitoring data.
Many of the nation’s top freight brokers and leading shippers use MC Brokerage to strengthen their risk management strategies and improve visibility into the motor carriers moving their freight.
Instead of relying on fragmented research or static snapshots, brokers can evaluate carriers through a more complete operational view.
That includes visibility into:
The platform also supports ongoing carrier monitoring, helping brokers identify potential safety exposures earlier and maintain stronger consistency around carrier review processes over time.
As carrier selection decisions face greater scrutiny, brokers need workflows that make vetting more visible, repeatable, and easier to document.
