How ELD Data Can Increase Carrier Revenue
ELD data is the most underused revenue asset in trucking. The GPS coordinates, timestamps, and HOS records your ELDs generate on every stop contain the evidence needed to collect detention pay, defend against broker disputes, document TONU events, and understand which lanes and facilities are costing you the most productivity. Most carriers use less than 20% of this data for anything beyond compliance.
What ELD Data Captures
Modern ELD systems (Motive, Samsara, Geotab, and others) capture on every trip:
| Data Type | What It Records |
|---|---|
| GPS location | Position every few minutes, accurate to meters |
| Timestamps | Hardware-generated, UTC-synced at every event |
| Geofence events | Entry/exit at configured facility boundaries |
| Engine activity | On/off, idle time, driving time |
| HOS status | Drive, on-duty, off-duty, sleeper transitions |
| Speed | Continuous record throughout the trip |
| Driver identification | Which driver is assigned to which unit |
For every stop your trucks make, ELD data can tell you exactly when the truck arrived, when it was idle (indicating loading/unloading), and when it departed — all with hardware-generated timestamps that can’t be plausibly disputed.
Revenue Use Case 1: Detention Pay Documentation
This is the highest-value ELD revenue use case for most carriers.
ATRI’s 2024 Detention Study found that 39.3% of all truck stops result in detention, but fewer than 50% of detention invoices are paid. The gap between what’s owed and what’s collected — approximately $15 billion annually — is almost entirely caused by documentation quality.
ELD GPS data is the evidence standard that wins detention disputes. A GPS export from your ELD showing:
- Truck arrived at facility geofence: 10:05 AM
- Truck departed facility geofence: 3:20 PM
- Free time (2 hours from appointment): ended at 12:00 PM
- Billable detention: 3 hours 20 minutes
…is essentially undisputable. Two hardware-timestamped data sources pointing to the same facts close the broker’s dispute window.
Revenue impact for a 100-truck fleet moving from 45% to 80% detention collection rate: approximately $20,000–$25,000/month in additional collected revenue.
Revenue Use Case 2: TONU Documentation
When a broker cancels a load after dispatch, ELD data shows exactly when the truck departed your facility and its location at the time of cancellation. This GPS record is your proof that the truck was dispatched — the triggering condition for TONU compensation.
Without ELD data: broker can claim the truck wasn’t actually dispatched. With ELD data: GPS shows the truck’s position en route at the time of cancellation. Dispute closed.
Revenue Use Case 3: Accessorial Charge Support
Beyond detention and TONU, ELD data supports other accessorial claims:
Layover: ELD HOS records show the driver went off-duty at the facility due to hours exhaustion — the evidence that the layover was HOS-driven rather than driver choice.
Stop-off timing: Multi-stop loads need documented arrival/departure at each stop to support stop-off charges. ELD geofence records provide this automatically.
Out-of-route miles: If a carrier was directed to take a non-standard route, ELD GPS data shows the actual route versus the standard routing, supporting mileage-based accessorial claims.
Revenue Use Case 4: Facility and Lane Analytics
Aggregated ELD stop-time data reveals patterns invisible from individual load records:
High-detention facilities: Which facilities consistently generate 3+ hour dwell times? This data gives you leverage to negotiate higher rates or detention terms for loads to those facilities.
High-detention brokers: Which brokers route loads to high-detention facilities without adequate RC coverage? This data informs your broker scorecard and load acceptance criteria.
Driver utilization: What percentage of your drivers’ available HOS is being consumed at facilities (loading/unloading/waiting) versus productive driving? For fleets where detention is consuming 1–2 hours per load, this is a meaningful reduction in total load capacity.
Lane-level profitability: Combining ELD dwell time data with rate data gives you actual cost per loaded mile per lane — including the detention and waiting time cost that standard rate-per-mile calculations miss.
Revenue Use Case 5: Dispute Defense
When a shipper or broker claims your truck was late, your cargo was damaged in transit, or your driver falsified logs, ELD data provides an objective record that’s hard to refute:
- GPS track showing the truck’s actual location at every point in the trip
- Speed records showing whether the driver was moving at the time of a claimed incident
- HOS logs showing compliance with driving time requirements
- Idle time records showing extended stops (useful for both detention claims and “driver caused the delay” defenses)
The Implementation Gap
The data is there. The gap is building the workflow to use it.
Most carriers with ELDs use the data reactively — pulling a record when a specific dispute arises, rather than systematically using it to document every potential detention event and prevent disputes.
The systematic workflow that captures full ELD revenue value:
- Configure geofences for regular facilities
- Monitor every stop for dwell time exceeding free time
- Automatically pull and attach GPS records to detention invoices
- Track payment and follow up systematically
Building this manually requires significant operational discipline. Automated tools like Dwell connect to your Motive account and handle this workflow automatically — turning data that’s already being generated into collected revenue.
Related Articles
- Motive Telematics ROI: Beyond ELD Compliance
- Geofencing for Trucking: How It Works and What It’s Good For
- How to Automate Detention Billing
- What Evidence Do You Need to Win a Detention Dispute?
Dwell connects to your Motive account, detects detention automatically, and builds the evidence package before a dispute happens. No new hardware. We make money only when you do.