HOS Trip Planning
60/70-Hour Driving Limit Planning
Plan around the 60/70-hour weekly on-duty limit before recaps, delays, detention, and dispatch timing create a mid-week problem.
By Dale Connors, Founding Editor · Content reviewed quarterly against FMCSA guidance and official state resources. The 60 or 70-hour limit is a rolling cumulative constraint, not a daily one. A driver who runs heavy for three or four consecutive days can reach the weekly limit on day five or six — and unlike the 14-hour clock, this is not a surprise that only appears at the end of the day.
Dispatchers and drivers who track the weekly limit proactively can choose restart timing, manage load density, and protect the driver's ability to finish a week without a forced mid-load stop.
Where the weekly limit catches drivers off guard
It usually starts on a Wednesday or Thursday. The driver has been running solid — Monday was a 10.5-hour day, Tuesday was close to 11, Wednesday included a 2-hour wait at a shipper that ate into the day without adding miles. Each individual day looked fine on the ELD. But 34 on-duty hours used in three days means the 60-hour limit is now a Thursday-afternoon problem, not a Sunday-night abstraction.
The dispatcher books a load Thursday morning because Friday delivery windows are hard to fill and the driver 'has hours.' The driver is 6 hours into the shift when the ELD shows 58.5 cumulative hours in the 7-day window. The Friday delivery is 10 driving hours away. At that point, the choices are a repower, a missed appointment, or creative math that the ELD will not accept.
This is not a compliance gap that catches new drivers — it catches experienced drivers who manage daily hours well but do not track the rolling window as a mid-week planning variable. By the time the ELD shows the warning, the load is already accepted, the customer expects a Friday delivery, and the options are all bad.
Planning moves that help
- Track cumulative on-duty hours through the rolling window, not just today's ELD display.
- Identify the day or load when the 60/70-hour limit will become the binding constraint.
- Plan a 34-hour restart when the cumulative limit would otherwise force a mid-load stop.
- Confirm the applicable cycle (7-day or 8-day) with FMCSA guidance, the ELD, and carrier policy.
Common planning mistake
The common mistake is treating the 60 or 70-hour limit as a week-end accounting problem rather than a mid-week planning variable. By the time it appears as a warning on the ELD, the options for managing it are usually already gone.
The second mistake is confusing 'hours available today' with 'hours available for the week.' A driver can have 8 hours left in the driving day and less than 2 hours left in the rolling window at the same time. Both are binding constraints. Dispatch plans that only check daily availability against a new load miss the weekly constraint entirely — until it shows up as a forced stop mid-haul on day five.
The 60/70-hour limit as a weekly planning problem
The 60/70-hour limit is a weekly planning problem more than a daily compliance item. A driver who reviews rolling hours only when the ELD shows a warning is consistently solving the weekly limit problem on the day when options are most constrained. Dispatchers who don't include cumulative hours in the pre-acceptance conversation for multi-day loads late in the week are building schedules that work on Monday and fail by Thursday.
For owner-operators, the difference between a planned restart and a forced one is the difference between a business decision and an operational failure. The planned version is scheduled around a well-positioned location with services and a clear next-load position; the forced version is wherever the truck runs out of hours — with no certainty about services, next-day departure time, or whether the restart location produces a good next-load opportunity.
What to check before relying on this
- Current ELD cumulative on-duty hours for the rolling 7-day or 8-day window.
- Whether the applicable cycle is 60 hours/7 days or 70 hours/8 days based on operation type.
- Carrier policy on restart usage, load acceptance near the limit, and driver substitution.
- FMCSA guidance for any exception or exemption that may apply to the specific operation.
Identifying when the weekly limit becomes the binding constraint
Identify the point in the week where the 60/70-hour limit will become the binding constraint. That is the planning trigger for a restart conversation — before the trip starts, not after the driver is already running short.
Map the week before accepting the next load
A strong weekly-hours plan starts before the next dispatch, not after the driver is already committed. The driver and dispatcher should look at the hours used in the rolling window, the hours expected to fall off, and the on-duty time required for the next load.
This matters most late in the week. A load may fit tomorrow's 11-hour driving limit and today's 14-hour window while still failing the weekly-hours plan two days later. That is the point where a restart, repower, different appointment, or different load choice should be discussed.
Weekly-hours checkpoint
| Checkpoint | Question | Planning use |
|---|---|---|
| Before accepting a multi-day load | How many on-duty hours remain in the rolling window? | Prevents booking freight that cannot be finished legally. |
| At the start of each dispatch day | Which older hours will drop off tonight or tomorrow? | Shows whether the driver is gaining useful hours or running into the limit. |
| Before a restart decision | Will the restart improve the next two loads or only patch the current one? | Treats restart timing as a business choice, not only a compliance reset. |
| Before final delivery | Will unloading time leave enough weekly hours for the next move? | Avoids finishing one load and immediately stranding the next plan. |
Dispatch conversation that prevents surprises
The driver should not have to explain the weekly limit only after the ELD warning appears. A better conversation sounds like this: 'I can make the pickup and delivery, but I will be down to a small number of weekly hours after unload. If the reload is tight, we need a restart plan or a different appointment.'
That kind of message gives dispatch something useful to do: adjust the load plan, warn the customer, schedule a restart, or avoid stacking another time-sensitive load behind a driver who is already near the limit.
What is the 60-hour and 70-hour rule for truck drivers?
Under FMCSA property-carrier HOS rules, a commercial truck driver cannot drive after accumulating 60 hours of on-duty time in a 7-day period (if the carrier does not operate every day of the week) or 70 hours in an 8-day period (if the carrier operates every day). The clock is a rolling window — it resets by dropping the oldest day's hours and adding the newest. When the cumulative total reaches the limit, the driver cannot drive until enough hours drop off the rolling window or a qualifying 34-hour restart is completed.
When should a driver and dispatcher start planning around the 60/70-hour limit?
When cumulative on-duty hours for the rolling window reach approximately 45–50 hours, the 60/70-hour limit should become an active planning factor in dispatch conversations. Waiting until the ELD warns at 55–58 hours leaves very little room to adjust load acceptance, plan a restart, or modify delivery commitments. Proactive tracking — reviewing cumulative hours at the start of each dispatch day — is what makes managing the weekly limit feel routine rather than urgent.
Can a driver continue past the 60/70-hour limit if they have not finished a delivery?
No. When the on-duty limit is reached, the driver must stop driving and go off duty, regardless of whether a delivery is complete. The same adverse driving conditions exception rules that apply to daily limits may apply in limited circumstances — but this is not a routine scheduling tool. When the weekly limit is approaching and a delivery is at risk, the correct response is to communicate with dispatch and the customer in advance, not to attempt to continue past the limit.