HOS Trip Planning

HOS planning works best when it is treated as a trip constraint, not a paperwork problem. A load that looks possible by mileage can still be poor planning if the final parking option sits at the edge of the 14-hour window, the weekly hours are nearly exhausted, or the receiver has no overnight plan.

This section covers daily limits (11-hour driving, 14-hour window), weekly limits (60/70-hour), break and restart planning, split sleeper strategy, and less-discussed topics like the short-haul exemption and personal conveyance.

The common thread across all HOS planning is the same: the constraint is real before the trip starts, not after the driver is already committed and running short. Planning that treats hours as a ceiling rather than a budget protects both the driver and the dispatch relationship.

A conservative HOS plan asks

• What is the realistic average speed after traffic, grades, fuel, and stops?
• Where will the 30-minute break happen without wasting parking options?
• What is the last safe parking decision point before the clock is too tight?
• Does the appointment plan leave room for check-in, staging, detention, and a post-delivery parking move?
• How many cumulative weekly hours remain, and when will the 60 or 70-hour limit become the binding constraint?
• What is the plan if detention at the shipper or receiver consumes two or more hours of the available window?

The 14-hour window is the binding constraint on most days

Most planning conversations focus on the 11-hour driving limit, but the 14-hour duty window is usually what decides the day. The window starts the moment a driver goes on duty and runs continuously — through loading, waiting, fueling, breaks, and traffic. A driver who goes on duty at 7 AM and spends two hours at a shipper, one hour in traffic, and 30 minutes fueling has already used nearly a third of the 14-hour window before covering meaningful miles.

This is where planning decisions made at dispatch have downstream consequences the driver cannot recover. A plan that builds in no buffer for known on-duty activities is a plan that assumes everything goes right.

HOS daily and weekly limits at a glance

HOS guides in this section

Start with the 14-hour clock article if your recurring problem is runs that look fine on the map but end with a tight parking search. Use the dispatcher HOS guide if your loads are frequently built around theoretical maximum hours rather than realistic available time. The 60/70-hour article is the right entry point if weekly limits are creating mid-week surprises on multi-day loads.

Guides in this section