Your driver conversations are evidence now. Is there a record?

In 2026's biggest broker liability cases, the fight isn't only about which carrier a broker picked. It's about what was said to the driver, what the driver said back, and who checked who actually showed up at the dock. Brokers need driver communication that is scoped by SOP to authenticate who's at pickup, logged automatically on every load, and kept out of dispatch, because ad hoc calls look like control and leave no record.

That puts brokers in a squeeze. Too much contact with drivers reads as control. Too little reads as no gatekeeping at all.

Below: three 2026 cases, where the line between gatekeeping and control sits, and what a defensible record contains. This is an operator's read of public filings and reporting, not legal advice.

Three cases turn on the same question: who said what, and who checked

Lipe v. Lupus Superior. A Dallas County jury returned a $604 million advisory verdict against C.H. Robinson, its carrier and the driver, and found the driver was the broker's "borrowed employee" (8-K; Saxton & Stump). Plaintiffs said the driver communicated he was too sick to keep driving (SupplyChain247); C.H. Robinson says he "did not communicate with C.H. Robinson" (statement). With no shared record, a jury chose between two accounts.

Coleman (allegations only). A complaint alleges the truck that picked up a Unilever load brokered by C.H. Robinson belonged to a different carrier than the one booked, one whose authority had been inactive for nearly a year (FreightWaves). The question it raises: who checked who showed up?

Montgomery v. Caribe Transport II. On May 14, 2026, the Supreme Court unanimously held that state negligent-hiring claims against brokers aren't preempted (opinion). More broker conduct now goes to juries, and a reasonableness defense rests on what a broker can show it did.

In each case, the argument turns on what was said to the driver and who checked who arrived at the dock. A broker without a record of either is left arguing from recollection.

Brokers are caught between gatekeeping and control

Ordinary brokerage tools can read as control

In Lipe, plaintiffs pointed to pickup and delivery windows, scheduling and rescheduling, late-delivery fines and contract termination. As Saxton & Stump put it, "the ordinary tools of freight brokerage were read by a jury as evidence of an employer-employee relationship."

Brandon Wiseman of Trucksafe Consulting told CCJ that monitoring hours of service, getting access to ELD records, "communicating directly with the drivers, calling them on their cell phones" are the kinds of involvement that invite a control argument. He also cautioned against dictating routing, handling driver-level dispatch decisions, and bypassing carrier dispatch to call drivers' personal phones for location checks.

Gatekeeping answers a narrower question

Gatekeeping asks one thing: is this the driver and truck we were told to expect? Confirming the assigned driver and equipment at pickup, holding the pickup number until that's settled, and documenting how the carrier was selected all sit on that side of the line.

The line is scope, not volume. One check that confirms identity at pickup is a different act from a string of calls about where the truck is and when it will arrive.

An unlogged phone call is the worst of both

A broker rep calling a driver's cell phone is direct contact, which feeds the control argument. It also leaves no record, so it does nothing for the gatekeeping argument. If the call is ever disputed, it's one person's memory against another's.

The habits around those calls make it worse. Notes live in someone's head or on a personal phone. CDL photos arrive by text or email and sit in inboxes with no retention policy and no link to the load.

That's a record-discipline problem. The fix isn't collecting more about drivers. It's making the contact you already need narrower, consistent and written down.

A defensible driver communication record has five properties

Use this as a checklist against your current driver-contact SOP.

1. It's scoped by SOP

In scope: identity, credentials, the truck and its DOT/MC match to the booked carrier, and pickup release. Out of scope: routing, hours of service, location pings and dispatch decisions. Write the scope down so every rep works from the same one.

2. It runs automatically on every load

The same trigger fires on every load. A record that only exists on loads where someone felt uneasy looks selective, and a selective record is easy to attack.

3. It's timestamped, with the decision and who made it

Each record shows the go/no-go, the evidence behind it and the person who made the call. The broker keeps the final say, and the record shows that it did.

4. Exceptions and overrides are logged with a reason

Overrides happen. When someone releases a load despite a flag, the override, the reason and the person who approved it stay visible in the load history.

5. It's shared with the shipper where it matters

Shippers and warehouses release freight at the dock. Sending them the expected driver and truck before arrival gives the dock something to check against, which is the gap the Coleman allegations describe.

One note on the regulatory floor. FMCSA's broker recordkeeping rule, 49 CFR 371.3, requires brokers to keep transaction records (consignor, carrier, bill of lading, compensation, freight charges) for three years. It says nothing about driver contact. The gap between that floor and what gets argued at trial is where brokers carry risk.

Shippers should ask their brokers what record exists

In In re Home Depot U.S.A., Inc. (May 15, 2026), the Supreme Court of Texas held that Texas law "does not impose a duty of care on a passive shipper under the facts alleged" when it hires a federally regulated carrier to haul ordinary cargo. That ruling applies in Texas only.

Coleman shows the other side. Shippers and warehouses can still be named when the release at the dock is in question, even at the allegation stage.

The practical step for a shipper is a direct question to each broker: for a given load, what record shows who picked it up, when, and who approved the release?

E3 driver authentication turns the authentication step into the record

E3 driver authentication runs the authentication step of a broker's SOP. Ahead of pickup, it texts the assigned driver a link to a short web form, with no app to download. The form takes over the phone's camera, so the driver captures live photos of their CDL, the cab card and the side of the truck, plus a quick face scan. Old or edited images can't be uploaded. Once the driver submits, E3 checks 50+ fraud signals and returns a result in under 60 seconds.

On a pass, E3 can release the pickup number automatically on the broker's behalf, and the go/no-go lands in Slack, Teams or Google Chat, where the broker keeps the final say. Authorized bypasses require a reason, and every decision stays timestamped in the load history. Shippers can receive the expected driver's selfie and truck photo before arrival.

It works for the real driver too: one short, consistent check instead of calls to a personal phone, and a record showing their identity wasn't the one being borrowed. E3 helps design the SOP around driver communication, then implements it alongside the TMS your team already uses. Across 700K+ loads authenticated through E3 driver authentication, zero have been stolen. For how E3 compares with other tools, see Eight questions that separate driver vetting tools.

Frequently asked questions

Can a freight broker be liable for a carrier's driver?

Yes, in some circumstances. Montgomery v. Caribe Transport II (May 14, 2026) held that state negligent-hiring claims against brokers aren't preempted by the FAAAA. Separately, the jury in Lipe v. Lupus Superior found a driver was the broker's "borrowed employee," a finding C.H. Robinson disputes and the verdict is not yet final.

Does calling a driver directly make a broker liable?

Not automatically. Liability turns on the facts, including how much control the broker exercised. Compliance consultants have flagged calls to drivers' cell phones, ELD access and driver-level dispatch as conduct that invites a control argument. Contact scoped to confirming identity at pickup, and logged, is easier to explain. Ask your counsel about your specific process.

Does FMCSA require brokers to keep driver communication records?

No. 49 CFR 371.3 requires brokers to keep transaction records, such as the consignor, carrier, bill of lading number and compensation, for three years. It doesn't address contact with drivers. Brokers who want a record of that contact need to build it into their own SOPs.

Can shippers be sued over a carrier's crash?

It depends on the state and the shipper's role. The Supreme Court of Texas held in In re Home Depot (May 15, 2026) that a passive shipper of ordinary cargo owes no duty under Texas law on the facts alleged. In the California Coleman case, plaintiffs have named the shipper and warehouse; those claims are allegations.

Start with your last disputed load

Pull the last load that was disputed or flagged. Ask what record you could hand your lawyer today: who confirmed the driver and truck, when, against what, and who made the call. If the answer is a phone log and someone's memory, start with the SOP.

Bring us your driver-contact SOP and your last disputed load. We'll show you what the record should look like. Talk to E3.

Aqil Naeem is Co-Founder and CEO of E3 Group.