34
Consecutive off-duty hours required
60/70
The only clock it resets
0
Limits on how often you may use it
What the Restart Is — and Is Not
The 34-hour restart is one of the most misunderstood provisions in the entire hours-of-service rulebook, mostly because the rule changed twice in the last decade and outdated versions still circulate. The current law is short and simple. Under 49 CFR 395.3(c), any period of 7 consecutive days (for the 60-hour rule) or 8 consecutive days (for the 70-hour rule) may end with the beginning of an off-duty period of 34 or more consecutive hours. That is the entire requirement: 34 consecutive hours off duty.
When a driver completes a 34-hour restart, the 60/70-hour on-duty total resets to zero. The prior week’s accumulated on-duty hours no longer count against the limit. The driver starts the next duty cycle with a full 60 or 70 hours available. Critically, that is all the restart does. It does not touch any other HOS clock.
The One Clock It Resets
The 34-hour restart applies only to the 60-hour/7-day and 70-hour/8-day on-duty limits in 49 CFR 395.3(b). It is the only mechanism — other than letting the rolling window drop off old hours one day at a time — that zeroes the cumulative weekly clock.
Because 34 hours is longer than the 10 consecutive hours required to reset the daily clocks, finishing a restart also satisfies the 11-hour and 14-hour reset by default. But the restart is not about those clocks. The 11-hour driving limit, the 14-hour window, and the 30-minute break all reset with any 10 consecutive hours off duty, restart or no restart. The unique, distinguishing function of the 34-hour restart is the weekly on-duty total.
The clean mental model
10 consecutive hours off duty resets your daily clocks (11 and 14). 34 consecutive hours off duty resets your weekly clock (60/70). The restart is the weekly tool.
Common Misconceptions (and the Truth)
The 34-hour restart was modified by a 2013 final rule that added two conditions, then those conditions were suspended by Congress in December 2014 and never reinstated. As a result, a lot of training material, dispatch lore, and even some software still reflects rules that are no longer in force. Here is what is true under the current 49 CFR 395.3(c).
Myth: The restart must include two periods from 1 a.m. to 5 a.m.
False under current law. The two-overnight requirement was part of the 2013 rule and was suspended in 2014. Today the only requirement is 34 consecutive off-duty hours, taken at any time of day.
Myth: You can only use the restart once every 168 hours (once a week).
False under current law. The once-per-168-hours limit was also part of the suspended 2013 rule. There is now no cap on how frequently a driver may take a restart.
Myth: The restart resets my 11-hour and 14-hour clocks specifically.
Misleading. Those reset with any 10 consecutive hours off. The restart's defining purpose is the 60/70-hour weekly total. Completing 34 hours off does reset the daily clocks too, but only because 34 is more than 10.
Myth: A short on-duty task in the middle of my time off is fine.
False. The 34 hours must be consecutive and entirely off duty (or sleeper). Any on-duty entry breaks the period and the 34-hour count starts over from the next off-duty moment.
A Worked Example
Suppose a driver works for a carrier that operates every day of the week, so the 70-hour/8-day limit applies. By the end of Friday, the driver has logged 68 of the available 70 on-duty hours across the rolling 8-day window — only 2 hours remain, not enough to run a full day Saturday. The driver has two options.
Option A — ride the rolling clock: wait for older on-duty hours to drop off the back of the 8-day window. Each day, the hours logged 8 days earlier fall away and become available again. This works, but the recovery is gradual.
Option B — take a 34-hour restart: go off duty Friday evening and stay off duty for 34 consecutive hours. When the restart completes (say, early Sunday), the 70-hour total resets to zero. The driver starts the new week with all 70 hours available. This is the faster recovery, which is why long-haul operations frequently build a weekend restart into the schedule.
The documentation that proves it
A restart is only valid if the records show 34 consecutive off-duty hours with no on-duty interruptions. In an audit, FMCSA reconstructs the duty status from the ELD and supporting documents. A fuel receipt or a dispatch record timestamped inside the claimed restart window can invalidate it — which is why the supporting records matter as much as the log itself.
Where FileFlo Fits
FileFlo is the records and proof layer, not an ELD. Your ELD records duty status and computes the 60/70-hour clock and your restarts. FileFlo holds the supporting documents (49 CFR 395.11) — bills of lading, fuel and toll receipts, dispatch records — that an auditor uses to confirm a claimed 34-hour restart was genuinely a clean, uninterrupted off-duty period.
FileFlo does not record duty status. It organizes the documents around the logs so that, when FMCSA reconstructs your week, the restart holds up.
Key Takeaways
- The current rule is 34 consecutive off-duty hours — full stop. 49 CFR 395.3(c) has no other conditions.
- It resets only the 60/70-hour weekly clock. The daily 11 and 14 clocks reset with any 10 hours off.
- The two-overnight and once-per-week rules are gone. They were suspended in 2014; do not apply them.
- The 34 hours must be uninterrupted. One on-duty entry breaks the block and restarts the count.
- The restart is optional. The rolling 7/8-day window also recovers hours, just more gradually.
The 34-Hour Restart: FAQ
Answers to common questions about the 34-hour restart under 49 CFR 395.3(c).
The 34-hour restart is an optional provision in 49 CFR 395.3(c) that lets a property-carrying driver reset the 60-hour/7-day or 70-hour/8-day on-duty clock to zero. The regulation states that any period of 7 or 8 consecutive days may end with the beginning of an off-duty period of 34 or more consecutive hours. After taking 34 consecutive hours off duty, the driver's cumulative weekly on-duty total starts fresh — the prior week's hours no longer count against the 60- or 70-hour limit. The restart is optional; a driver can instead let the rolling 7- or 8-day window drop off old hours naturally.
It resets only the 60-hour/7-day or 70-hour/8-day on-duty clock under 49 CFR 395.3(b). It does NOT affect the 11-hour driving limit, the 14-hour window, or the 30-minute break — those reset with 10 consecutive hours off duty regardless. Because 34 hours is more than 10, completing a restart also necessarily satisfies the daily off-duty requirement, so the driver begins the next shift with full 11-hour and 14-hour clocks too. But the unique function of the 34-hour restart is the weekly clock: it is the only way, other than waiting out the rolling window, to zero out the 60/70-hour total.
No. The two-overnight-period requirement and the once-per-168-hours limit were part of a 2013 version of the rule, but those restrictions were suspended by Congress in late 2014 and ultimately removed. Under the current 49 CFR 395.3(c), the only requirement is 34 or more consecutive hours off duty. There is no requirement that the restart include two periods from 1 a.m. to 5 a.m., and there is no limit on how often a restart may be used. Any reference to those older conditions reflects a rule version that is no longer in effect.
As often as you want. Under the current 49 CFR 395.3(c), there is no limit on how frequently a driver may use a 34-hour restart. The once-per-168-hours (once-per-week) cap that existed in the 2013 rule was removed. A driver could, in principle, take a 34-hour restart multiple times within a single week. The practical limit is simply that the restart requires 34 consecutive off-duty hours, which is a meaningful chunk of time. The restart is a tool, not a mandate — drivers and carriers choose when it makes operational sense.
Yes. The 34-hour period must be 34 or more consecutive hours in off-duty status (or sleeper berth, which counts as off duty for this purpose). Any on-duty time — even a short dispatch call logged as on-duty, a pre-trip inspection, or loading — breaks the consecutive period and restarts the 34-hour count from the next off-duty moment. This is the most common way drivers accidentally invalidate a restart: a single on-duty entry in the middle of what should have been a clean 34-hour block. The off-duty time must be continuous.
The restart is entirely optional. The 60/70-hour limit in 49 CFR 395.3(b) is a rolling total: each day you add the newest day's on-duty hours and drop the hours that fall outside the 7- or 8-day window. A driver who manages on-duty time carefully can operate indefinitely on the rolling clock without ever taking a restart. The 34-hour restart simply offers a faster way to recover available hours — instead of waiting for old hours to roll off one day at a time, the driver zeroes the weekly total in a single 34-hour off-duty block.
Make Your Restarts Hold Up in an Audit
Your ELD computes the 60/70-hour clock. FileFlo holds the supporting documents and audit trail that prove a claimed 34-hour restart was a clean, uninterrupted off-duty period — and lets you produce the whole package the moment FMCSA asks. FileFlo is the compliance records layer, not an ELD.
Plans from $89/month — No credit card required — 5-day free trial