Supreme Court Freight Liability Shift: Preserve the Evidence Behind Every Shipper Handoff

Freight claims rarely begin with a missing document. They begin with a missing connection: a carrier qualification completed days before tender, a seal number written on paper but not attached to the shipment record, or a temperature file that cannot be matched to the trailer that arrived.
That gap matters more after the U.S. Supreme Court's 2026 freight-broker ruling. The Court unanimously rejected the broad preemption defense that brokers had used against certain state-law negligent-selection claims. Now a newer dispute is renewing questions about when liability can reach shippers and receivers as well.
The practical response is not indiscriminate recordkeeping. It is a defensible chain of evidence that shows who made each decision, what they knew at the time, and what happened at every physical handoff.
Liability is moving toward the decision record
The Supreme Court ruled 9-0 in Montgomery, sending the case back to the Seventh Circuit and allowing negligent-selection litigation against a freight broker to proceed. Reuters explains that brokers are now more likely to face lawsuits over carrier-selection decisions after catastrophic crashes.
The ruling did not automatically make every participant liable for every loss. It did, however, weaken the assumption that one party's federal preemption defense protects the entire transportation transaction. As FreightWaves reports in its analysis of renewed shipper and receiver liability, the next legal boundary is still developing.
Operations teams should therefore avoid trying to predict one universal legal outcome. Their job is to preserve contemporaneous facts. A court, insurer, customer, or regulator may later ask whether a party selected the carrier, controlled the work, created an unsafe condition, accepted damaged goods, or failed to act on a known exception. A timestamped shipment record answers those questions better than reconstructed email threads.
Map both the contractual and physical handoffs
Consider a refrigerated produce load. The grower or packing house may sell to a distributor. A broker may arrange transport. The receiver may impose appointment, temperature, trailer, and food-safety requirements. A motor carrier may accept the tender but assign the trip to a specific driver and tractor shortly before pickup.
That creates two overlapping chains.
The contractual chain records who hired whom, which terms applied, who selected or approved the carrier, and who could issue instructions. The physical chain records custody of the product: loading, sealing, pickup, in-transit control, arrival, unloading, inspection, and acceptance or rejection.
Claims become difficult when those chains are stored separately. A rate confirmation might identify the carrier but not the tractor that arrived. A bill of lading might show a seal but not who applied it. A receiver's temperature reading might not correspond to the sensor used in transit. Every load needs one shipment identity connecting both chains.
Preserve evidence at six critical events
1. Tender and acceptance
Retain the original tender, every material revision, acceptance time, rate confirmation, equipment requirements, pickup and delivery appointments, and special instructions. Preserve the identity of the user or system that issued and accepted each version. If the shipper or receiver required a particular carrier, route, or operating method, record that instruction explicitly.
2. Carrier qualification
Capture the carrier's legal name, USDOT and motor-carrier numbers, operating-authority status, insurance certificate, coverage dates, safety information reviewed, qualification rules applied, reviewer, and decision timestamp. A current snapshot matters: a lookup performed after an incident does not prove what was visible when the carrier was selected.
Also record exceptions. If an approved carrier substituted another entity, changed equipment, or arrived under a different operating identity, the system should require review rather than silently treating the shipment as unchanged.
3. Loading and condition
Link the purchase order, product and lot identifiers, count, weight, pallet configuration, packaging condition, trailer number, tractor number, driver identity, sanitation check, and loading times. For produce, retain pulp or product temperatures where required, trailer pre-cool evidence, set point, loading pattern, and photographs of cargo condition.
The record should distinguish observation from instruction. “Trailer at 34°F” is an observation; “maintain continuous 34°F” is an operating requirement. Both belong in the file.
4. Seal and departure
Record the seal number, who applied it, time applied, and a photograph showing the seal on the correct trailer. Capture the departure timestamp and signed shipping document. If a seal is replaced, preserve both numbers, the reason, location, authorizing party, and supporting photograph. Overwriting the original seal destroys part of the custody story.
5. In-transit temperature and exceptions
Retain raw sensor data, device identifier, calibration information, reporting interval, trailer set point, reefer operating mode, location history, and all alerts. Keep acknowledgment and response times when an excursion occurs. A temperature chart without a device-to-load association is weak evidence; a chart tied to the trailer, shipment, and custody period is useful.
6. Delivery and disposition
Capture arrival, gate-in, dock assignment, seal inspection, seal-break authorization, unloading times, receiver temperature readings, visible condition, shortages, photographs, signed proof of delivery, and exception codes. If the receiver rejects, salvages, segregates, or conditionally accepts freight, retain the decision maker, reason, supporting inspection, and disposition instructions.
Build a claim-ready file, not a document pile
A claim-ready workflow should answer five questions without manual archaeology:
- Which party made or controlled the relevant decision?
- What information and qualification criteria were available then?
- Which person, carrier, driver, vehicle, trailer, seal, and sensor handled the load?
- What changed, who was alerted, and how quickly did they respond?
- What condition was documented when custody transferred?
Use immutable timestamps, version history, and role-based access. Set retention rules with counsel and insurers according to cargo, contract, jurisdiction, and claim type. Legal requirements vary, so this operational framework is not a substitute for legal advice.
Make evidence part of execution in CXTMS
CXTMS can connect qualification data, tender versions, shipment milestones, equipment identifiers, documents, photographs, temperature events, alerts, and proof of delivery under one load record. Required-field rules can prevent departure without a seal record or block an unapproved carrier substitution. Exception workflows can preserve who knew what and when instead of relying on memory after a loss.
The liability landscape may continue to change. The strongest operational position remains stable: make every handoff visible, attach evidence to the exact event, and preserve the decision record before a claim begins.
Request a CXTMS demo to see how event-level freight records can strengthen chain of custody and claim readiness.


