A driver can restart the 60/70-hour weekly cycle limit by taking at least 34 consecutive hours completely off duty. After those 34 hours are complete, the weekly on-duty hour counter resets to zero and the driver can begin a fresh cycle. The restart is optional. It does not reset daily limits. A driver still needs the required off-duty time before starting a new driving shift. Verify current requirements against 49 CFR 395.3 and FMCSA guidance.
Most drivers and dispatchers understand the daily limits. The weekly cycle is where planning breaks down. A driver burns through their 70 hours by Thursday and dispatch does not know what to do next. The restart exists for exactly that situation, but it gets misunderstood constantly. Here is how it actually works.
- Drivers approaching or at the 60/70-hour weekly limit.
- Dispatchers planning multi-day schedules and weekly resets.
- Carriers choosing between a restart and waiting for recap hours.
- Owner operators managing their own weekly cycle.
What the weekly cycle limit is
Under HOS rules, a driver operating under the 7-day schedule cannot drive after accumulating 60 hours of on-duty time in 7 consecutive days. A driver operating under the 8-day schedule cannot drive after 70 hours in 8 consecutive days. Carriers choose which schedule applies to their operation. Once a driver hits that limit, they cannot drive again until hours have either recapped or been reset through a restart.
How the 34-hour restart works
The restart provision is in 49 CFR 395.3. A driver can restart their weekly cycle by taking at least 34 consecutive hours completely off duty. That means zero on-duty and zero driving time during the 34-hour window. If on-duty time appears at any point during the 34 hours, the restart does not count and must begin again from the interruption point.
Once the full 34 consecutive hours are complete, the weekly on-duty counter resets to zero. The driver can start a fresh 60 or 70-hour cycle. Under the current rule, there is no specific time-of-day requirement for when the 34 hours begin or end. Verify this against current FMCSA guidance before planning around restart timing.
Restart vs recap hours: the key difference
These are two separate tools that accomplish a similar goal, and dispatch often confuses them.
| Tool | How it works | When it applies | What it resets |
|---|---|---|---|
| 34-hour restart | Driver takes 34+ consecutive hours completely off duty | Any time a driver chooses to use it | Resets the entire 60/70-hour weekly counter to zero |
| Recap hours | Hours from 7 or 8 days ago naturally drop off the rolling window | Automatically, each day that passes | Adds back only the hours that aged out, not the full counter |
A driver on the 8-day/70-hour schedule who worked 10 hours 8 days ago will gain those 10 hours back today without taking any additional off time. Recap is often the better tool when a driver only needs a few hours back and cannot afford to sit for 34 hours. The restart makes more sense when the driver is at or near the limit and needs a full reset to continue running efficiently.
What the restart does NOT do
- It does not reset the daily 11-hour driving limit or the 14-hour on-duty window.
- It does not replace the required off-duty time before a new driving shift.
- It does not fix a log that shows a violation before the restart.
- It does not allow a driver to skip the 30-minute break requirement.
- It does not change the driver's underlying ELD records.
A driver who takes a restart still needs to complete the required daily off-duty time before driving again. The restart resets the cycle counter. It does not give the driver a clean slate on everything else.
Is a restart required every week?
No. The restart is optional. Drivers can continue running on the rolling 7 or 8-day window and let recap hours naturally restore available time. Many local and regional drivers never need a formal restart because their weekly hours recap before they hit the limit. Dispatch should understand both options and plan around which one actually fits the driver's schedule and workload, rather than defaulting to a restart out of habit.
When a restart makes sense vs when recap is better
| Situation | Restart makes sense? | Recap makes sense? | Why |
|---|---|---|---|
| Driver is at or near the 60/70-hour limit and needs a full week of hours | Yes | No | Recap will only restore what aged out, which may not be enough |
| Driver only needs 8-10 hours back to complete upcoming loads | Probably not | Yes | Waiting one or two days for recap is faster than 34 off-duty hours |
| Driver is headed home and will naturally be off for the weekend | May work out naturally | Yes | If the off time exceeds 34 hours, the restart applies automatically |
| Dispatch is planning a heavy week after a slow week | Worth checking | Worth checking | Run the actual hour count before assuming which tool is needed |
Common dispatch mistakes with the restart
- Assuming a restart happened because the driver was home over the weekend, without confirming 34 consecutive off-duty hours actually appear in the log.
- Planning dispatch based on a restart that was interrupted by a brief on-duty event.
- Forcing drivers to take unnecessary restarts instead of managing the weekly cycle through scheduling.
- Confusing recap hours with a formal restart and telling drivers they have more hours than they actually do.
- Not checking the ELD data to confirm the restart completed before assigning new loads.
What carriers should document
The ELD will reflect the off-duty period automatically. What dispatch needs to do is confirm the period is at least 34 consecutive hours with no on-duty or driving interruptions before planning loads around it. If a driver's ELD shows an on-duty event during an expected restart window, that restart is not valid. Treat it as a restart that still needs to happen, not one that already did.
If your team reviews logs internally, the free Daily Logbook Audit Checklist covers how to check duty status entries, including how to spot whether a restart window was actually clean.
Here is what I see all the time: dispatch tells a driver they have a fresh restart, the driver goes back out, and then an inspection finds that the 34 hours had an on-duty event in the middle. Now you have a driver who drove over the weekly limit on what dispatch thought was a reset. Check the ELD first. Do not assume the restart was clean because the driver was home.
Not Sure How Your Drivers Are Managing the Cycle?
Book a free compliance review. We will pull a sample of your ELD data, check weekly cycle management, and show you where the planning gaps are.
Book a Free Compliance Review →HOS & Log Auditing
We audit weekly cycle management, catch incomplete restarts, resolve unassigned driving, and work with dispatch on scheduling that keeps drivers legal.
Get HOS Support →Frequently Asked Questions
A driver can restart the 60/70-hour weekly cycle limit by taking at least 34 consecutive hours completely off duty. After those 34 hours are complete, the weekly on-duty hour counter resets to zero. The restart does not reset daily limits. A driver still needs the required off-duty time before starting a new driving shift. Verify current requirements against 49 CFR 395.3 and FMCSA guidance.
No. The restart is optional. Drivers do not have to take a 34-hour restart each week. Many let weekly hours recycle naturally as older hours drop off the 7 or 8-day window. Dispatch should understand both options and plan accordingly.
A restart resets the entire weekly cycle counter to zero after 34 consecutive off-duty hours. Recap hours are hours that naturally drop off the rolling window as older days age out. Under the 8-day/70-hour schedule, hours from 8 days ago drop off each day, giving the driver those hours back without a formal restart. Both create available weekly hours, but through different mechanisms.
No. The restart resets the weekly cycle counter only. A driver still needs the required off-duty time before starting a new driving shift and is still subject to the daily driving and on-duty limits.
Under the current HOS rules, there is no specific time-of-day requirement for the 34-hour restart. The earlier requirement for two periods from 1 to 5 AM was addressed by rule changes. Verify current requirements against 49 CFR 395.3 and FMCSA guidance before planning dispatch around restart timing.
The ELD or log will reflect the off-duty time. Dispatch should note when the restart began and ended and confirm the full 34 consecutive hours were off duty before resuming driving. If the restart was interrupted by any on-duty or driving time, it does not count and must restart from the interruption point.