The ELD Question You Never Ask on the T-Call

The dispatcher said it so casually I almost missed it. "Yeah, we run paper logs — we're a short-haul operation."

It was a 680-mile run from Indianapolis to Memphis. That's not short-haul by any definition in the regulations. Not even close.

I didn't say anything. This was years ago, before DOTScreener, before I'd internalized what I was actually supposed to be listening for on these calls. I tendered the load. Nothing happened. The freight delivered, the carrier invoiced, everyone moved on. But I've thought about that call a lot. I was a bad set of facts away from a scenario that, post-Montgomery, would be a genuinely bad day for me.

What the ELD Mandate Actually Requires

Since the final compliance deadline in December 2019, most motor carriers hauling freight in interstate commerce are required to use an electronic logging device from FMCSA's registered provider list. Not a tablet with a spreadsheet on it. Not a device from a vendor who went out of business in 2021 and never removed themselves from customer agreements. A device registered with FMCSA at the time of use — the agency maintains that list publicly and updates it as providers are added or removed.

49 CFR § 395.22 is the specific rule. Motor carriers must ensure that the ELD their drivers use is certified and registered. The device has to meet the technical specifications in § 395.24. If a carrier's logging device isn't on FMCSA's registered ELD list, the carrier is out of compliance with § 395.22 regardless of what the logs themselves show. The list has several hundred registered providers. Sounds like a lot until you realize how many carriers are using discontinued products, rebranded devices, or white-label hardware that was never independently registered.

There are real exemptions and they matter. 49 CFR § 395.1(e) covers short-haul drivers — commercial drivers who operate within a 150 air-mile radius of their normal work-reporting location, return to that location within 14 hours on every shift, and don't exceed 11 hours of driving time. Those drivers can use timecards instead of a log. Drive-away-tow-away operations have a separate exemption — drivers moving a vehicle that is itself the cargo. Vehicles manufactured before January 1, 2000 are exempt because the engine architecture often can't support ELD integration. And a driver who uses paper logs eight or fewer days in a 30-day period doesn't need an ELD for those specific days.

Those exemptions are legitimate. "We're a small operation" isn't one of them.

The BASIC Score Doesn't Show What Happened Last Week

The HOS Compliance BASIC in FMCSA's CSA system is built from roadside inspection data. When a driver gets pulled at a scale and an officer finds HOS violations — falsified logs, hours exceeded, exemption claimed incorrectly — those violations get recorded and eventually flow into the BASIC. The critical word is eventually. The data lag between a roadside inspection and its appearance in a BASIC score runs roughly 60 days, sometimes longer depending on state reporting.

A carrier who started ignoring ELD requirements six weeks ago looks identical in your BASIC pull to a carrier who's been fully compliant for four years. A score of 42nd percentile doesn't tell you what happened at a weigh station in Kentucky last Tuesday. It tells you what happened before the data cutoff, processed, cleaned, and posted.

This is why the T-call is not a formality. It's the one point in the vetting process where you have a shot at real-time information — and most brokers spend it confirming equipment availability and rate.

What a Gap Looks Like in Practice

Take a carrier I'll call Riverline Freight LLC — MC-1247893, DOT-3567102. Two power units, just under five years of authority, HOS Compliance BASIC at 41st percentile. Nothing in SAFER that jumps out. You pull their certificate of insurance, the coverage checks out, and you go to the T-call.

The dispatcher tells you they "switched back to paper logs" because the ELD vendor raised subscription prices and the owner didn't want to deal with it. The driver is qualified, experienced, and the carrier has a solid delivery history with you.

Here's what happened: the carrier made a business decision to drop ELD compliance. Maybe the price increase was real. Maybe they had a bad experience with the vendor. Doesn't matter — "cost reasons" isn't an exemption under § 395.22. That's a live compliance gap. It won't appear in any score for another eight weeks minimum, and only then if someone gets inspected and the violations get properly recorded and attributed.

That information exists in exactly one place: the phone call you're on right now.

You have two options. You document it, decline to tender, and note in the file that the carrier disclosed non-compliance with § 395.22. Or you ignore it, tender the load, and hope nothing goes wrong.

What the Plaintiff's Lawyer Is Actually Looking For

The Supreme Court's Montgomery v. Caribe Transport II decision, handed down May 14, 2026, held unanimously that the FAAAA does not preempt state-law negligent-selection claims against freight brokers. Justice Barrett's opinion means plaintiffs can bring these cases in state court. The legal theory is simple: brokers have a duty to exercise reasonable care in selecting carriers, and the federal statute doesn't take that duty away.

Plaintiff attorneys in truck crash cases have been building the "broker liability" playbook for years, and they're good at it. They don't just pull SAFER and call it a day. They subpoena your T-call notes, your carrier file, your internal emails, and your documented vetting process. They're looking for the gap between what you could have known and what you actually found out.

Fatigue is a significant factor in serious truck crashes. FMCSA's own research has found driver fatigue or recognition failure in a substantial share of fatal commercial vehicle crashes, though underreporting is a real problem — fatigued drivers and their employers have every incentive to attribute crashes to other causes. But plaintiff lawyers know the pattern, and they know HOS violations are the documented proxy.

Here's the narrative when a fatigued driver causes a crash and you never asked about ELD compliance: The broker selected this carrier. The carrier had stopped using ELDs. The broker never asked about it. The broker had no real-time knowledge of whether the driver was legal. Carrier pocketed the freight revenue, broker pocketed 18%, and nobody asked the question that might have caught the problem.

Here's the alternative: The broker asked on the T-call which ELD system the carrier uses. The broker noted it down and checked it against FMCSA's registered ELD list. The driver was legal. The broker has a timestamped note showing that question was asked and answered. The plaintiff's expert now has to address why a carrier who passed that check should have been disqualified.

Those two scenarios involve the same carrier and the same crash. The broker's exposure in them is not the same.

Three Questions Worth Adding to the T-Call

These are specific. They're short. They take about three minutes total.

"Which ELD system does the driver use?" Write down whatever they say. If they hesitate, that tells you something. If they name a device you've never heard of, check it against FMCSA's registered ELD list before the call is over or as soon as you hang up. If the device isn't on the list, that's a § 395.22 violation — note it in the file.

"Is the driver claiming any exemption from the ELD requirement?" If yes, which one? Short-haul under § 395.1(e)? Walk through whether it actually applies to this load. A 500-mile run is not short-haul regardless of what the dispatcher tells you. A driver who claims an exemption that doesn't apply is driving illegally. Document what they said.

"How many hours does the driver have on their 70-hour cycle?" Under 49 CFR § 395.3, a driver who's used 70 hours on duty in 8 consecutive days needs a 34-hour restart before driving again. This isn't about micromanaging the carrier's dispatch. It's about knowing whether a driver who's already at 65 hours can legally accept a load with a 10-hour drive time. If they're at the limit and it doesn't work, either you wait for the restart or you find a different carrier.

You're not the carrier's compliance department. But you are the entity that selected the carrier. That distinction matters when someone's looking at your file two years from now.

How I Document This

ELD compliance goes in the per-load vetting note, not just the carrier profile. A carrier who was fully ELD-compliant when you onboarded them 18 months ago might not be today. The profile gets updated when information changes; the per-load note captures what you knew at the time of tender.

My per-load T-call note for ELD includes:

• ELD system named by dispatcher: [device name or "paper logs claimed"]
• On FMCSA registered list: Y / N / Not checked / N/A (exemption claimed)
• Exemption claimed: Y/N — if yes, which one and whether it applies to this load
• Driver hours on current 70-hour cycle: [hours stated]
• HOS feasibility confirmed for this load: Y/N
• Any discrepancies noted: [verbatim or close paraphrase of anything that sounded off]

If something's off — carrier claims exemption that doesn't apply, device name that's not on the list, driver who's been on duty longer than they should be — that gets flagged before I tender. Either the load doesn't move until it's resolved, or I document the decision to proceed and why.

The documentation isn't just self-protective. It creates discipline. When you know you're going to write down the ELD question answer, you ask the question. When you know you're going to check the device name, you write down the device name. The habit is the protection.

---

The ELD mandate has been final since December 2019. This is not new law or an emerging trend. It's a compliance requirement that's been in place for years, and most freight brokers never work it into their T-call protocol because nobody told them it was their problem.

After Montgomery, it is.

— Mason Lavallet

Founder, DOTScreener.com