Most dispatchers know the HOS rules. The 11-hour driving limit. The 14-hour duty window. The 30-minute break requirement. The 70-hour/8-day cycle. What most dispatchers do not have is a planning system that treats those rules as hard constraints during route generation rather than as a post-planning check. The result is routes that look valid at 5 AM and require live re-assignment by 2 PM when a driver's available hours do not stretch to the final three stops.
The FMCSA HOS Framework: What the Rules Actually Say
The FMCSA Hours of Service regulations under 49 CFR Part 395 govern property-carrying drivers operating commercial motor vehicles in interstate commerce. The core rules for understanding route planning constraints are:
The 11-Hour Driving Limit
A driver may drive a maximum of 11 hours after having taken 10 consecutive hours off duty. This is the driving-time limit — time behind the wheel, not time on duty. A driver who spent 2 hours in pre-trip inspection, dock waiting, and administrative tasks before the first mile turned is still at 11 available driving hours for that shift. The 11-hour limit resets only after a 10-consecutive-hour off-duty period.
In route planning, the 11-hour driving limit is the constraint that catches long-haul assignments. A 740-mile direct lane from Chicago to Detroit — nominally 11 hours at average speed — hits the limit exactly and has no buffer for traffic, weather, weigh station stops, or extended dwell time at the shipper. Routes planned to this edge will fail regularly in execution.
The 14-Hour Duty Window
The 14-hour rule is often more constraining than the 11-hour driving limit in practice. A driver cannot drive after 14 hours have elapsed since they came on duty, regardless of how much driving time they have used. A driver who came on duty at 06:00 must stop driving by 20:00 — full stop. If they used 3 of those 14 hours in loading dock wait time, they have 11 hours of driving time available but only 11 hours of calendar time in which to use it.
This interaction — driving time remaining versus duty window remaining — is the calculation that manual dispatch routinely gets wrong. A dispatcher planning routes at 5 AM is estimating driver on-duty times, dwell times at each stop, and traffic conditions across a 12-stop route. Any one of those estimates being 20 minutes wrong can push the last two stops outside the 14-hour window.
The 30-Minute Break Requirement
Drivers must take a 30-minute break if they have been driving for 8 cumulative hours without a 30-minute interruption. The break can be on-duty not driving (e.g., at a customer's dock waiting to unload) — it does not need to be off-duty. This is a commonly misunderstood provision: dwell time at a stop counts as the break if the driver is off the road and not driving for 30 consecutive minutes.
For route planning, the 30-minute break requirement means that routes with 8 or more hours of driving time need a scheduled stop — either a rest area or a customer location with sufficient dwell time — in the middle segment of the route. A solver that does not account for this will produce routes where the driver technically violates HOS by driving 9 continuous hours without a break, even if total driving time is within the 11-hour limit.
The 70-Hour / 8-Day Cycle
A driver may not drive after having been on duty for 70 hours in any 8 consecutive days. This is the cumulative cycle limit that governs week-over-week dispatch planning. A driver who worked 65 hours over the past 7 days has only 5 hours of on-duty time available on day 8, regardless of how much rest they took the previous night. The 70-hour clock resets only after the driver takes 34 consecutive hours off duty (the 34-hour restart provision).
For a fleet dispatcher planning the following week's routes on a Friday, the 70-hour cycle status of every driver is the binding constraint on available capacity. A driver coming into Monday morning with 58 hours accumulated over the past 7 days will be cycle-limited — not driving-limit limited — on Tuesday afternoon. Planning that ignores cycle-hour status will short-staff Tuesday routes mid-day when three drivers hit their 70-hour caps simultaneously.
Personal Conveyance: The Edge Case That Breaks Simple HOS Models
FMCSA permits drivers to use their CMV for personal conveyance (PC) — moving the vehicle for their own purposes while off-duty — under specific conditions. PC miles do not count against HOS driving limits. The practical use case is a driver repositioning the truck from a truck stop to a closer drop point after coming off duty, or moving a drop-trailer to a nearby customer facility during off-duty time.
We are not saying personal conveyance is a planning tool — it is a driver option for genuine personal use, and ELD systems must log it as PC accurately to withstand a DOT audit. The reason it matters for route planning is that some dispatchers informally rely on PC repositioning to close geographic gaps, and if the HOS planning model does not know when PC miles were logged, it will miscalculate available driving hours for the subsequent on-duty period. The cleanest approach is to plan routes without any PC dependency and treat PC mileage as incidental.
ELD Mandate and the AOBRD Transition
The FMCSA ELD mandate, phased in between 2017 and 2019, required most property-carrying CMV drivers to use Electronic Logging Devices rather than paper logs or Automatic On-Board Recording Devices (AOBRDs). The AOBRD grandfather period ended in December 2019. As of 2020, nearly all commercial operations subject to HOS regulations must use ELD-compliant devices.
For route planning integration, the ELD mandate is a data availability enabler: every compliant driver now has machine-readable HOS data that a route optimizer can query. ELD APIs from providers like Samsara, Motive (formerly KeepTruckin), and Geotab expose current driver HOS status — hours remaining on the driving limit, hours remaining in the duty window, cycle hours used — as queryable data. A planning system that pulls this data before each optimization run is working with real remaining hours, not assumed start-of-day hours. The planning accuracy improvement from using live ELD data versus assumed-fresh HOS is significant on Thursday and Friday when weekly cycle accumulation starts to constrain capacity.
How HOS Constraints Change Route Generation
When a route optimizer treats HOS rules as hard constraints — not post-planning checks — the output looks structurally different from manual dispatch in several ways:
Shorter route assignments for high-cycle drivers. Drivers approaching their 70-hour cycle cap receive shorter routes with earlier cutoffs, even if their current-day driving hours are fresh. This prevents the mid-day capacity failure where a driver must park at stop 7 of 11 because their weekly cycle is exhausted.
Break-stop insertion. For routes with more than 8 hours of driving time, the solver inserts a break stop — either at a planned stop with expected dwell time over 30 minutes, or at a designated rest point — to satisfy the 30-minute break requirement without requiring the driver to make an unplanned stop.
Duty window buffering. Rather than planning routes to the edge of the 14-hour window, a properly configured solver includes a buffer — typically 45–60 minutes — to absorb expected variability in dwell time and traffic. Routes planned to the 13-hour mark rather than the 14-hour mark complete within compliance bounds even when individual stops run long.
Driver-route matching by available cycle hours. The optimizer assigns routes to drivers by remaining cycle hours, not just current-day availability. A 350-mile route that takes 12 hours of duty time should go to a driver with at least 15 hours of cycle availability remaining, not to the driver with the freshest daily hours who is 8 hours from their weekly cycle cap.
What HOS-Aware Planning Cannot Fix
HOS compliance in route planning does not substitute for carrier safety management. A dispatcher who produces HOS-compliant routes on paper has met the planning obligation — but if drivers are logging breaks incorrectly, using PC status inaccurately, or logging off-duty time that was actually spent performing carrier duties, no planning system detects that from the dispatch side. DOT compliance is a driver management and safety culture question, not a routing question.
HOS-aware planning also does not help with the 150 air-mile short-haul exemption, which allows drivers operating within a 150 air-mile radius of their normal work reporting location to use the short-haul exception to HOS requirements (12-hour driving time, 14-hour duty window, no ELD requirement in some cases). For dispatchers using this exemption, the planning system needs to know which drivers qualify — based on their depot location and the geographic distribution of that day's stops — to apply the correct rule set per driver, not a blanket 11-hour limit.
The operators who use HOS-aware route planning most effectively are running fleets where driver time is the binding constraint, not vehicle count. When your fleet has enough trucks but your drivers are regularly hitting HOS limits before completing their manifests, the planning side of the problem is where the constraint lives. Solving it there — before the driver leaves the yard, not at 2 PM when the violation is already forming — is where the operational value is.