Freight Broker Liability After Montgomery: What Changed?
Quick Answer
Short answer: Yes. After Montgomery v. Caribe Transport II, LLC, a freight broker can face a state-law negligent-hiring claim tied to the selection of a motor carrier. The Supreme Court held in May 2026 that the Federal Aviation Administration Authorization Act does not categorically preempt that type of claim when it falls within the statute’s motor-vehicle safety exception. That does not mean a broker is automatically liable after a crash. A plaintiff still must prove the elements of the applicable state-law claim, including duty, breach, causation, and damages where those elements apply.
In this article
Freight broker liability after Montgomery changed the preemption analysis for certain negligent-selection claims and increased the importance of documented carrier-selection practices.
Freight Broker Liability After Montgomery: Practical Implications
Last reviewed: October 2026. This article is educational information, not legal advice. Freight brokers, shippers, carriers, insurers, and counsel should review the facts and law that apply to a specific shipment or claim.
What did the Supreme Court decide in Montgomery?
In Montgomery v. Caribe Transport II, LLC, the Supreme Court considered whether the FAAAA’s preemption provision blocked a state negligent-hiring claim against a freight broker that selected a motor carrier. The Court held that the claim fell within the FAAAA safety exception for state authority “with respect to motor vehicles.” The Court therefore reversed the Seventh Circuit and sent the case back for further proceedings.
The practical point is narrower than some headlines suggest. The Supreme Court decided a preemption question. It did not decide that the broker was negligent. It did not create a nationwide checklist that automatically defines reasonable broker conduct. It did not rule that every crash involving a broker-selected carrier makes the broker responsible. Instead, the decision means certain state-law safety claims can proceed rather than being dismissed solely because of FAAAA preemption.
Why does Montgomery matter to freight brokers?
Before Montgomery, federal appellate courts were divided over whether negligent-selection claims against brokers were preempted. The Supreme Court resolved that specific split by concluding that the FAAAA safety exception can reach a claim that a broker negligently selected an unsafe motor carrier. That changes the litigation environment because a broker can no longer assume that federal preemption will end this category of claim before a court examines the underlying state law.
For brokers, the operational consequence is that carrier-selection practices may receive more attention after a serious collision. A plaintiff may ask what information was available when the carrier was selected, what the broker reviewed, whether the broker ignored a known disqualifying fact, and whether the broker followed its own written procedures. A broker’s records can become evidence of what the company actually did rather than what a policy manual says it usually does.
Does Montgomery create automatic broker liability?
No. A lawsuit being allowed to proceed is different from a plaintiff winning the lawsuit. State negligence law varies. Courts can disagree about the existence or scope of a duty, what conduct was reasonable, whether the alleged breach caused the injury, and whether other defenses apply. Facts that matter in one jurisdiction or case may carry less weight in another.
Brokers should also distinguish between a motor carrier being legally authorized to operate and a separate question about a broker’s own risk controls. FMCSA’s Compliance, Safety, Accountability system expressly cautions users not to treat SMS data as a federal safety rating. Unless a carrier has an unsatisfactory safety rating or has been ordered out of service, the carrier may remain authorized to operate. That warning matters because a broker should not convert a single public data point into a homemade federal safety rating that FMCSA itself says the data does not provide.
What carrier information should a broker document?
A defensible process starts with verified facts. Brokers commonly confirm the motor carrier’s identity, operating authority, insurance status where applicable, and basic safety information available through federal systems. FMCSA currently directs users to SAFER for safety rating and out-of-service information and to its registration systems for authority and insurance information. The goal should be a repeatable process that records what was checked, when it was checked, and how exceptions were handled.
- Legal business name and USDOT information
- Operating authority appropriate for the shipment
- Insurance filings and policy information required for the operation
- Federal safety rating and out-of-service orders
- Recent identity changes or unexplained contact mismatches
- Driver and equipment information when the workflow calls for driver-level verification
- Internal exception approvals and the reason for any override
The purpose of a checklist is not to guarantee that an accident will never happen. No vetting process can do that. A checklist is useful because it helps a brokerage apply its standards consistently and preserve a record of the facts considered at the time of selection.
What does “reasonable care” mean after Montgomery?
The Supreme Court did not define one federal “reasonable care” standard for brokers. That question is generally tied to state tort law and the facts of the case. A practical compliance program should therefore avoid claims such as “FMCSA authorization means the carrier is automatically safe” or “one SMS number proves the carrier is unsafe.” Both shortcuts can misstate what federal systems actually say.
A stronger approach is to identify objective disqualifiers, objective review triggers, and an exception process. For example, a broker may have a hard stop for an inactive authority or an out-of-service order. A different issue, such as a changed phone number, may require manual verification rather than immediate rejection. Written standards should match what the brokerage can actually perform on every load.
Should brokers verify the individual driver too?
Carrier-level due diligence and driver-level shipment verification answer different questions. Carrier authority tells you about the registered motor carrier. Driver-level verification helps confirm that the person and equipment arriving for a specific shipment match the information the broker and shipper expected. This distinction is especially important in fraud-prone workflows where a legitimate carrier’s identity can be impersonated.
CargoGuard’s driver verification workflow is designed to bring driver license information, selfie review, registration information, truck photos, and shipment tracking events into the load record. Those tools can support an operational review, but they do not determine legal negligence and do not replace carrier-selection due diligence, insurance review, or legal advice.
Why do identity checks matter separately from crash risk?
A brokerage can select a legitimate carrier and still face a shipment-security problem if a fraudster impersonates that carrier. FMCSA’s broker and carrier fraud guidance recommends independently confirming phone numbers through SAFER, carefully examining documents, and checking that the truck and trailer that arrive match the contracted carrier. These controls address identity and cargo security rather than the separate question of negligence after a crash.
How should a brokerage handle exceptions?
Exceptions are where a written policy becomes operational. A brokerage should decide in advance which findings require rejection, which require additional review, who can approve an exception, and what must be documented. An exception should not disappear into a phone call or chat message that cannot later be reconstructed.
For example, if a carrier presents a replacement tractor shortly before pickup, that may have an ordinary explanation. The safer workflow is to verify the change using a known contact, update the shipment record, and communicate the approved equipment information to the pickup facility. The same principle applies when a carrier changes a dispatcher, driver, email domain, payment instruction, or other material detail.
What records could matter after a serious accident?
Litigation often turns on what can be proved. A brokerage should preserve the carrier-selection record, timestamps, source information, internal notes, exceptions, and the version of its policy that applied at the time. If the shipment used driver verification or tracking tools, preserve those records according to the company’s retention policy and legal-hold obligations.
- Carrier qualification snapshot or verification record
- Authority and insurance verification date
- Safety rating information reviewed
- Communications about substitutions or exceptions
- Driver and equipment verification records when collected
- Tracking and shipment-event logs
- Pickup and delivery photos or documents
- Names of employees who made approval decisions
Should a broker change its carrier-selection policy now?
Montgomery is a good reason to review a carrier-selection policy with transportation counsel and insurance professionals, especially if the policy was written around the assumption that negligent-selection claims would always be preempted. The review should focus on whether the company’s written standards are clear, consistently followed, and supported by reliable records.
Overly complicated policies can create their own problems if employees routinely bypass them. A short, enforced standard can be more useful than a long checklist nobody follows. The process should also separate federal authorization from the brokerage’s additional business rules, because the two are not the same thing.
What should shippers ask their freight brokers?
Shippers can ask how the broker verifies carrier identity and authority, how it handles safety information, what triggers manual review, how substitutions are approved, and whether shipment-level driver and equipment information is available. These questions help the shipper understand the broker’s process without pretending that any single database or technology guarantees safety.
Frequently asked questions
Can a freight broker be sued for negligent carrier selection in 2026?
Yes. Montgomery held that the FAAAA does not categorically preempt this type of state-law safety claim. Whether the plaintiff ultimately succeeds depends on the applicable law and facts.
Did the Supreme Court create a federal broker vetting checklist?
No. The Court answered a preemption question. It did not define a universal carrier-selection standard.
Is a carrier’s FMCSA authority proof that it is safe?
Authorization is important, but it is not a guarantee of future safety. FMCSA also cautions against treating SMS data as a federal safety rating.
Should brokers keep screenshots of carrier checks?
A brokerage should use a documented retention method that shows what information was reviewed and when. The exact method should fit the company’s procedures and legal advice.
Can CargoGuard prevent negligent-hiring liability?
No software can guarantee that result. CargoGuard can support driver verification, equipment records, tracking, alerts, and shipment documentation. Legal responsibility is determined by the applicable law and facts.
A practical 2026 review checklist
- Confirm the carrier identity using authoritative contact information.
- Verify active authority appropriate to the load.
- Review required insurance information.
- Check federal safety rating and out-of-service status.
- Define objective rejection rules and manual-review triggers.
- Document who approved exceptions.
- Verify driver and equipment details when the shipment risk calls for it.
- Keep the record with the shipment.
- Train staff on what public FMCSA data does and does not mean.
- Review the policy with transportation counsel after major legal changes.
Bottom line
Montgomery v. Caribe Transport changed an important threshold issue for freight brokers: a broker negligent-hiring claim tied to motor-vehicle safety is not automatically blocked by FAAAA preemption. The decision makes documented, consistent carrier-selection procedures more important, but it does not impose automatic liability and does not create one national vetting checklist. Brokers should use reliable federal information, avoid overstating what that data proves, document exceptions, and work with counsel and insurers to align their process with the law that applies to their operations.
How a broker-liability claim can develop after a crash
When a serious crash occurs, the first questions usually concern the driver and motor carrier. If a broker arranged the transportation, plaintiffs may also examine how the carrier was selected. The investigation can reach beyond the final rate confirmation to qualification records, emails, safety information, exceptions, and the broker’s written policies. That does not mean every document creates liability. It means the carrier-selection record can become relevant to whether the broker acted reasonably under the law that applies to the case.
The most useful records are contemporaneous records: the information available when the carrier was approved, not a reconstruction prepared months later. A brokerage that stores the date and source of its checks can explain what it knew at the time. That is different from showing a current carrier profile after the underlying data have changed.
Broker, carrier, and shipper duties are not interchangeable
A motor carrier operates the vehicle and has direct regulatory responsibilities for drivers, equipment, maintenance, hours of service, and other safety requirements. A freight broker arranges transportation. A shipper tenders the freight and may impose contractual pickup or security requirements. Those roles can overlap operationally, but the legal duties attached to them are not identical. One reason careful contract drafting matters is that an agreement can describe the parties’ intended roles and responsibilities before a dispute arises.
Brokers should be cautious about accidentally representing themselves as controlling the carrier’s day-to-day driving operations if that is not the business relationship they intend. At the same time, calling a carrier an independent contractor does not answer every negligent-selection question. The actual claim, state law, contract language, and facts all matter.
What might a plaintiff ask about carrier selection?
- What carrier information did the broker review before tendering the load?
- Was the carrier’s authority active for the service involved?
- Was there an out-of-service order or official safety rating?
- Were there known facts that triggered the broker’s own escalation policy?
- Did an employee override a policy, and if so, why?
- Was a carrier approved even though the broker’s system identified a mismatch?
- Did the broker follow the same process it followed for similar carriers?
- Was the load reassigned or was the carrier identity impersonated?
These are examples of factual questions that can arise, not a statement that every broker must collect every data point on every load. The point is to make the company’s process deliberate enough that employees can explain it.
Scenario: active authority, but an identity mismatch
Suppose a broker verifies that a carrier’s authority is active, then receives a dispatch message from a phone number that does not match the company’s known contact information. That is primarily an identity question. A sensible response is to call a verified company number, confirm the dispatcher and driver, and document the result. Treating active authority as the end of the review would leave the identity mismatch unresolved.
This scenario also shows why fraud controls and crash-safety controls should not be collapsed into one score. A legitimate, authorized carrier can be impersonated. Conversely, an unusual email address does not make a legitimate carrier unsafe. The process should identify which question each check is trying to answer.
Scenario: an exception to the broker’s normal policy
Assume a brokerage has a written internal rule that a particular finding requires manager review. A carrier presents that finding, but an employee tenders the load without escalation because the customer needs an urgent pickup. If a later dispute occurs, the written rule and the unexplained deviation may receive attention. That does not determine liability by itself, but it illustrates why policies should be realistic and why exceptions should be documented.
A better process makes urgency part of the exception procedure rather than a reason to ignore it. The manager can record what was reviewed, why the exception was approved, and whether additional controls were added for the shipment.
How insurance fits into the post-Montgomery review
Brokers should talk with insurance professionals about how their policies respond to allegations involving carrier selection. Coverage labels can be confusing, and policy terms control. A brokerage should know which policies may respond to bodily-injury allegations, professional or broker errors, contingent exposures, cyber events, and cargo claims. It should also know the notice requirements that apply after a serious event.
Insurance review is not the same as carrier vetting. It is a separate part of risk management. The carrier’s insurance protects against certain carrier risks, while the broker’s own insurance may address allegations against the brokerage itself, subject to policy terms.
How contracts fit into the review
Broker-carrier and shipper-broker contracts should match actual operations. If the contract requires the brokerage to perform checks the company never performs, the mismatch creates avoidable problems. If the contract is silent about substitutions, communication, or carrier payment responsibilities, operational teams may create informal practices that differ by employee.
Transportation counsel can help align indemnity, insurance, carrier qualifications, independent-contractor language, records, and incident-notification provisions with the business. The goal is not to write a contract that promises perfect safety. It is to make responsibilities clear and consistent with what the company does.
Build a carrier-selection audit, not just a carrier checklist
A periodic audit tests whether the policy is actually being followed. Select a sample of completed shipments and ask whether the required carrier checks were completed, whether exceptions were approved, whether the driver and equipment matched where those checks were required, and whether records are retrievable. An audit can uncover inconsistent practices before a claim does.
Keep the audit proportionate. The goal is to improve the process, not to manufacture unsupported “safety scores.” FMCSA’s own warning about SMS data should guide how public safety information is described internally and externally.
Training points for brokers and carrier-sales teams
- Know the difference between active authority and a federal safety rating.
- Know which findings are hard stops and which require manual review.
- Verify changed contact information through an independent source.
- Do not call a carrier fraudulent based on one weak indicator.
- Do not bypass an exception process solely because the load is urgent.
- Record who approved material substitutions.
- Escalate serious crashes and claims promptly under the company’s incident plan.
- Preserve the carrier-selection record when litigation is reasonably anticipated.
What readers should remember
Montgomery changed the preemption defense, not the elements of negligence. The Supreme Court held that the FAAAA safety exception can allow a state negligent-hiring claim against a broker to proceed when it concerns motor-vehicle safety. It did not hold that every broker owes the same duty in every state, did not create a federal carrier-vetting checklist, and did not rule that C.H. Robinson was negligent. Brokers should therefore focus on accurate carrier information, consistent internal standards, documented exceptions, and advice from transportation counsel.
One final point: document what the broker knew at the time
Carrier information changes. A later screenshot may not show what was visible when the load was tendered. A useful qualification record therefore preserves the date, source, and result of the review. That lets the brokerage explain the actual decision rather than reconstructing it from memory after a crash. The same principle applies to exceptions, substitutions, and identity checks.
Primary sources: U.S. Supreme Court, Montgomery v. Caribe Transport II, LLC; FMCSA Compliance, Safety, Accountability; FMCSA Broker and Carrier Fraud and Identity Theft guidance.