A truck 300 miles from the receiver looks five hours away on every map in the industry. If the driver has ninety minutes left on the clock, it isn't — it's a 10-hour break plus tomorrow morning away, and every system that computed five hours just promised a delivery window the load cannot legally make. Hours of service are the single largest input a distance-based ETA ignores, and the gap isn't minutes; it's often half a day.
The federal HOS rules that matter for ETA math are few but hard: a driver may drive at most 11 hours within a 14-hour on-duty window, must take a 30-minute break after 8 cumulative hours of driving, and needs 10 consecutive hours off duty before the next shift — all inside 60/70-hour weekly limits. None of these bend for an appointment. An ETA that doesn't model them is a physics answer to a compliance question.
The failure pattern is predictable: the load is fine all afternoon, then 'goes late' in the evening when the clock runs out — a surprise to the customer, but never to the math. The clock was knowable at dispatch. An HOS-aware ETA folds the driver's remaining drive time, the required breaks, and the 10-hour reset into the arrival projection, so a load that can't make its window shows at-risk hours or days early, while there's still time to repower, reschedule, or re-plan the stop sequence.
The data to do this already exists in every fleet, because the ELD mandate put it there. Since December 2017, drive time and duty status have been recorded electronically, and every major ELD platform exposes them through an API. What's usually missing is the connection: hours in the ELD, appointments in the TMS, position in telematics, and an ETA calculation that reads only the last of the three. Making an ETA HOS-aware is an integration exercise, not new hardware.
HOS-awareness also changes planning upstream of the ETA. Scoring a tender against the assigned driver's realistic clock — not the truck's distance — catches the impossible appointment before acceptance instead of after failure. The same logic ranks recovery options when a load does slip: which nearby driver actually has the hours to take it, not just the proximity.
The test for any ETA tool is a one-question demo: give it a load whose driver will run out of hours mid-route, and see whether the ETA lands after the mandatory break or sails through it. Position plus traffic answers where the truck is; position plus traffic plus the driver's legal clock answers when the freight arrives. Only one of those is an ETA a dispatcher — or a customer — can act on.
See it in practice: Tranztec Predictive ETA Tracking — HOS-aware ETAs →