Glossary
34-Hour Restart
How a 34-hour restart resets weekly on-duty hours and why its location and timing affect the next load plan.
Definition
A 34-hour restart is a period of at least 34 consecutive hours off duty that resets a commercial driver's cumulative weekly on-duty hours (the 60-hour/7-day or 70-hour/8-day limit). After the qualifying off-duty period, the weekly on-duty clock starts fresh.
The 34-hour restart is a planning tool as well as a compliance requirement. A driver who proactively plans a restart before reaching the weekly limit — at a well-positioned location — is in a much better operational position than one who reaches the limit in the middle of a load.
In a trip planning sentence
A driver at 58 hours on a 70-hour/8-day cycle on a Thursday has fewer than 12 hours of on-duty time available before reaching the weekly limit. If the next load requires more hours than that, the dispatcher should plan a 34-hour restart before dispatching the load — not after the driver is already committed and running short.
What the restart location should provide
| Location type | Services available | Next-load positioning | Planning note |
|---|---|---|---|
| Major truck stop near the next pickup region | Fuel, food, showers, rest | High — minimizes repositioning deadhead | Best outcome: HOS resets and driver is already in position |
| Truck stop in off-network location | Adequate but not ideal | Low — adds deadhead before next load | HOS resets, but the restart location creates its own cost |
| Public rest area | Parking only — no fuel, limited services | Variable | Acceptable for short restarts, but driver needs a plan for fuel and food separately |
| Shipper or receiver lot (if permitted) | Minimal or none | High if next load originates here | Confirm that overnight parking is allowed; not all facilities permit extended stays |
Why location matters as much as the hours
A restart is also a parking, services, food, security, and next-load positioning decision. The location where the 34 hours are spent affects the cost of the next dispatch. A restart at a well-positioned stop is a business advantage; an unplanned restart at a random exit adds repositioning deadhead, service gaps, and a worse starting point for the next load.
What to check before relying on this
Confirm the location explicitly allows a 34+ hour stay, has required services, and positions the driver for the next load. Verify the current FMCSA rule requirements and ELD calculation before building a dispatch plan around a restart.
Related terms
- hos
- sleeper berth
- off duty time
- 60/70 hour limit
Does the 34-hour restart need to start or end at a specific time of day?
Under the current FMCSA rule, the restart requires only 34 consecutive off-duty hours — no mandatory time-of-day window. An earlier version of the rule included a 1–5 AM requirement, which was suspended. That said, where the restart happens matters as much as when. A restart in a location with no services, poor security, or no reasonable next-load position wastes 34 hours of availability in exchange for a clean weekly slate at a difficult starting point.
Does a 34-hour restart also reset the daily driving and duty limits?
No — the restart resets only the cumulative 60/70-hour weekly on-duty total. The 11-hour driving limit and 14-hour duty window reset on their own after each qualifying 10-hour off-duty period, independently of the weekly bank. A driver who completes a restart starts the new cycle with both a clean weekly total and a fresh daily clock — but those two resets happen to coincide, not because the restart causes both.
When does a mid-week restart make more sense than pushing to the weekend?
When the remaining hours can't cover the next load and an unplanned stop mid-run would be worse than a deliberate one now. A driver approaching the 70-hour limit on Wednesday with a load requiring 15 more on-duty hours has to stop somewhere — the question is whether it happens on their terms at a well-positioned truck stop or at a random exit when the hours run out. Carriers who plan restarts around load position rather than treating them as a passive event recover better from heavy weeks.