HOS awareness & ELD integration
Stage 4 · Driver App, Communication & Service Standards
P3Initial MVP
Four-Lane View
Software Function
- ›Read-only ELD integrations (Motive/Samsara/Geotab APIs) for HOS-aware planning Loop legs validated against available hours before offer No proprietary ELD, no data hostage-taking — integration, not replacement
Service Provider / Admin
- ›Dispatch never plans an illegal week; violations prevented upstream
User — Driver / IOO
- ›Keeps their existing ELD; FreightShift plans around their clock HOS data shared by consent, scope shown plainly
Customer — Client / FF / NVOCC
- ›Legs planned within hours = fewer service failures from fake ETAs
Software Function
- ›Read-only ELD integrations (Motive/Samsara/Geotab APIs) for HOS-aware planning Loop legs validated against available hours before offer No proprietary ELD, no data hostage-taking — integration, not replacement
Competitors
Motive/Samsara own the ELD layer (3-yr contracts, their moat). Highway weaponized ELD access against carriers.
Differentiation
We don’t fight the ELD duopoly — we read from it with consent. HOS-aware loop planning is the use nobody built because nobody else plans weeks.
Make It Better
Zero HOS-infeasible dispatches. The loop respects the clock by construction, not by driver heroics.