ELD Data as Detention Proof When Times Conflict

When ELD data and a driver-entered arrival time disagree on a detention claim, the answer is not to pick the record you like. ELD data as detention proof is strong on one thing (where the truck was and when it moved) and weak on another (what the driver was doing while it sat). The driver-entered time is the reverse. The reconciliation that holds up in settlement uses the ELD to establish the outer bounds of the dwell, then uses the driver’s entry, the facility record and the appointment to explain what happened inside those bounds.

If you settle brokered freight, this is the most common evidentiary conflict you will handle. A carrier submits a detention claim citing an 09:12 arrival. The ELD shows the truck stationary at that location from 09:31. Nineteen minutes on a two-hour free time clock is nothing, until the billing crosses an hour boundary, and then it is a full hour of detention. Here is how to work it without becoming the referee who guesses.

Why the two records disagree in the first place

Neither system is lying. They measure different events.

An ELD’s job is hours-of-service compliance. It records duty status changes with time and location, and it flags the vehicle as stopped or moving. Location is captured at a granularity meant to place a truck in a place, not to fix it at a specific gate. It knows when the wheels stopped turning. It does not know whether that stop was the guard shack, the fuel island across the street, or the shoulder half a mile out waiting for a door assignment.

A driver-entered arrival time is a human recording an event that has meaning to the driver: reaching the facility. Drivers commonly enter the moment they reach the property line or the gate queue, because from their point of view that is when their time stopped being theirs.

So the gap is predictable: the driver’s arrival is usually earlier, because it marks approach and queue, and the ELD’s stop is later, because it marks the wheels settling. The gap is two definitions of arrival, not evidence of fraud.

The gap is a definitional problem, not a data problem

Before you compare records, read the agreement. Detention on domestic truckload is contractual, not regulatory: no federal rule sets free time or a detention rate. What the rate confirmation says starts the clock is what starts the clock.

The common triggers produce different results on the exact same load:

• Arrival at the facility. Ambiguous by design. Property line, gate queue, or guard shack.
• Check-in with the facility. Later, and documented by someone other than the driver.
• Appointment time, or arrival, whichever is later. Protects the facility against early arrivals.
• Geofence entry in the carrier’s or broker’s app. Machine-generated, and the geofence radius quietly decides the answer.
• Signature or door assignment. Latest of all, and the hardest for a carrier to accept.

We break each of these down, including how they behave when a driver shows up two hours early, in when detention free time actually starts. The point for reconciliation is this: if the rate con says “arrival,” then a driver’s gate-queue entry is a defensible reading of the contract and the ELD stop time is not automatically superior. If the rate con says “check-in,” the facility’s log outranks both.

Most conflicts you are asked to settle are not conflicts about facts. They are conflicts about which event the contract named. Resolve that first and half the disputes evaporate.

What ELD data can and cannot prove

Be honest about both sides of this, because carriers know their own systems and a broker who overclaims loses the thread.

What ELD data supports well:

• That the vehicle was stationary in a given area over a continuous interval.
• The moment it began moving again, the strongest departure evidence available on most loads.
• A pattern across many loads at one facility, which is how you learn a receiver averages three hours of dwell regardless of appointment.
• Corroboration. An ELD stop that brackets the driver’s entered times makes the claim much harder to argue with.

What ELD data does not settle:

• Whether the truck was in the receiver’s yard or in the lot next door. Location precision is compliance-grade, not survey-grade.
• Whether the driver was working, waiting, or taking a break. Duty status is an annotation, and drivers move it for their own reasons.
• Whether the delay was the facility’s fault. A truck sitting for three hours because the driver arrived without an appointment is dwell, not necessarily billable detention.
• The moment of check-in, which is a facility event the ELD has no view of.

The practical consequence: ELD data is excellent at establishing a window and poor at establishing a trigger. Use it as the outer envelope, and use the facility-side records to place the trigger inside it.

The reconciliation procedure

Work in this order. It takes about five minutes per claim once the habit is set, and it produces a defensible number instead of a split-the-difference number.

1. Read the clock trigger off the rate confirmation. Write it down verbatim in the claim file. Everything downstream depends on it.
2. Establish the ELD envelope. First stationary timestamp at or near the facility, first movement timestamp on departure. Real dwell cannot exceed this window plus whatever approach time is credibly claimed.
3. Place the driver-entered times against the envelope. Inside it, they are consistent. Earlier than the envelope start, they are an approach or queue claim, and the contract’s trigger decides whether that counts.
4. Pull the facility-side record. Gate log, guard sign-in, receiving door log, dock scheduler entry, or the receiver’s WMS check-in. This is the record that resolves the trigger, and on brokered freight nobody thinks to request it until week three.
5. Check the appointment. An arrival ninety minutes early usually does not accrue billable free time under a “later of arrival or appointment” clause, and the carrier is not wrong to have arrived early.
6. Compute detention from the trigger, not from the earliest available timestamp. Then check how the carrier converted elapsed time to money, because rounding decides more of these bills than anyone expects. The math is worked through in detention billed in 15-minute versus hourly increments.
7. Write the reconciliation into the file. One paragraph: which trigger, which records, what the elapsed time was, and what you paid. The next person to touch this load, and the auditor six months later, both need it.

A worked example

Illustrative numbers, one load, to show what the procedure produces. Free time is two hours, detention is $75 per hour after, and the rate confirmation says the clock starts on arrival at the facility.

The carrier claims 3 hours 53 minutes, less two hours free, so 1 hour 53 minutes, billed as two hours: $150.

Run the procedure. The trigger is arrival at the facility. The guard log at 09:26 is a facility-side record of the truck being at the property, five minutes before the ELD shows it settled, which is exactly what you would expect from a truck in a gate queue. The driver’s 09:12 is 14 minutes earlier still and has no corroboration, so it is an approach claim.

Take 09:26 as arrival, because it is the earliest corroborated facility-side record and the contract says arrival. Take 13:02 as departure, because the ELD’s first movement is the better departure record. That is 3 hours 36 minutes, less two hours free, so 1 hour 36 minutes.

The remaining question is rounding, which the contract has to answer. Nothing here is a bad-faith claim by the carrier, and nothing here is a broker refusing to pay. It is a 17-minute correction with a documented reason, which is the kind of settlement that does not come back.

When the driver-entered time should win

Do not default to the machine record. There are situations where the driver’s entry is the better evidence, and refusing to acknowledge them is how brokers acquire a reputation carriers warn each other about.

• The facility staged the truck off-site. Some receivers park trucks in an overflow lot or a nearby street and call them in by radio. The ELD shows a stop that is not at the consignee, and the driver’s entry is the only record of the real sequence.
• The trigger is arrival and the queue is on public road. A half-mile gate line at a grocery DC is arrival by any reasonable reading, and the ELD stop reflects the truck reaching the front of it.
• The ELD record is thin. Lost connectivity or a truck shuffled between doors produces a fragmented trace. A single continuous driver entry is cleaner than five ELD fragments.
• The driver’s entry is corroborated and the ELD is not. A gate ticket, a lumper receipt, or a timestamped photo at 09:12 outranks an absence of ELD detail at 09:12.

The rule is not “machine beats human.” It is “corroborated beats uncorroborated.” When both are corroborated and they still disagree, the contract’s trigger decides.

What to ask the carrier for, and how

Ask specifically. A request for “your ELD data” gets you a decline, sometimes for a legitimate reason, because ELD records contain driver hours-of-service and personal data that carriers are careful with.

Ask instead for the narrow slice:

• The stop and first-movement timestamps for this unit at this stop, as a report or screenshot.
• The driver’s entered arrival and departure times as submitted.
• Any facility check-in confirmation the driver received.
• The carrier’s detention worksheet showing hours claimed, rate applied, and how the elapsed time was rounded.

That last request has a rule behind it. Under 49 CFR 373.103, a freight or expense bill must show the exact rates assessed and the total charges due with the nature and amount of each charge. A detention line that shows only a dollar figure does not describe its own nature or amount, and asking for the hours and rate behind it is a reasonable request, not a challenge to the claim.

Practitioners who work these disputes converge on the same short list of what you need before contesting a carrier invoice: the rate confirmation with the free-time and clock-trigger language, the BOL or POD with facility timestamps, and the carrier’s own detention documentation. The ELD trace is a fourth record that corroborates or contradicts the second.

Frame it as reconciliation rather than challenge. Most carriers produce this in a day when the request is specific and the reason is stated. The full evidence set, including what to do when one of these documents simply does not exist, is in the documents that win a detention dispute, and the reconstruction path for a load where the POD came back blank is in disputing a detention charge with no POD times.

The pass-through problem, which is really the whole job

For a broker, the reconciliation is only half the work. The other half is whether the shipper funds it.

You are exposed in the gap between two agreements. The carrier’s rate confirmation may say detention starts on arrival with two hours free. Your customer’s agreement may say detention is payable only with documented in and out times signed by the receiver, or may be silent, which is worse. When the two do not line up, the difference comes out of your margin. That misalignment, and how to catch it at the point of tender rather than at settlement, is the same class of problem as a rate confirmation that does not match the carrier’s invoice.

Two things reduce this structurally:

• Mirror the trigger language. Whatever the customer agreement says starts the clock, put the same words on the carrier rate confirmation. Different triggers on the two sides of the same load guarantee an unfunded gap.
• Require the evidence at claim submission, not at dispute. Carriers that know detention claims need arrival evidence attached tend to arrive with it attached.

Do not overstate the evidence, and do not understate the cost

Two failure modes, opposite directions.

Overstating: telling a carrier that ELD data proves the driver arrived late, when the ELD proves only where the truck settled. Carriers know their systems better than you do and that argument ends badly.

Understating: treating detention as a nuisance line to be negotiated down. The cost on the carrier side is documented. The DOT Office of Inspector General’s 2018 driver detention report estimated that detention reduces for-hire truckload driver annual earnings by $1.1 to $1.3 billion and truckload carrier net income by $250.6 to $302.9 million annually, and that a 15-minute increase in average dwell raises the average expected crash rate by 6.2 percent. A carrier claiming detention on a load where a receiver held the truck four hours is not working an angle.

Timing is not unlimited on either side either. Under 49 U.S.C. 13710, a carrier billing charges additional to those originally billed must do so within 180 days of the shipper’s receipt of the original bill to preserve collection rights, and the shipper must contest within 180 days of receipt. A detention invoice that shows up seven months after delivery has a timing problem before you look at any timestamps.

The checklist

1. Read the clock trigger off the rate confirmation and write it in the file.
2. Build the ELD envelope: first stationary timestamp, first movement timestamp.
3. Place the driver-entered times against that envelope and mark them corroborated or not.
4. Request the facility-side record: gate log, guard sign-in, receiving log, or dock scheduler entry.
5. Compare against the appointment time and the contract’s early-arrival language.
6. Compute from the trigger, then check the rounding convention separately.
7. Document the reconciliation in one paragraph on the load.
8. If the customer agreement and the carrier agreement use different triggers, fix the template, not this load.

The habit that pays is step four. Facility-side timestamps are the record that resolves most of these conflicts, they are cheap to capture at the time, and they are nearly impossible to reconstruct a month later. Electronic BOL and delivery systems that stamp arrival and departure automatically remove the conflict at the source, which is why timestamped delivery records prevent detention disputes rather than just settling them.

Sources

• DOT OIG Report ST2018019, Driver detention economics and crash-rate effect (U.S. DOT Office of Inspector General)
• 49 U.S.C. 13710, Billing and contesting windows (Cornell LII)
• 49 CFR 373.103, What a freight or expense bill must show (Cornell LII)
• Documents needed before contesting a detention charge (Laneproof)
• Detention fee calculation and the role of timestamped delivery records (Vector)