Every driver who runs hard eventually hits the wall on their weekly hours. The 34-hour restart is how you get back on the road with a clean slate, but only if you take it right and log it right. Get either part wrong and you’ve got a restart that doesn’t count, a log that doesn’t match reality, and an inspection that goes sideways.
Here’s the 34 hour restart rule explained plainly: what the regulation actually says, when it makes sense to use it, how to map it out on a timeline, and the logging mistakes that turn a weekend off into a write-up.
The Weekly Limits the Restart Resets
You can’t understand the restart without understanding the clock it resets. Under 49 CFR 395.3(b), property-carrying drivers work under one of two weekly limits:
- 60 hours in any 7 consecutive days (395.3(b)(1)). This applies when your carrier does not operate CMVs every day of the week.
- 70 hours in any 8 consecutive days (395.3(b)(2)). This applies when your carrier operates CMVs every day of the week.
Once you’ve been on duty 60 hours in 7 days (or 70 in 8), you can’t drive. Note that the limit counts on-duty time, not just driving. Loading, inspections, fueling, and waiting at the dock all burn the weekly clock.
These weekly limits sit on top of your daily limits, which the restart does not change:
- 10 consecutive hours off duty before driving (395.3(a)(1))
- No driving after 14 consecutive hours from coming on duty following that 10-hour break (395.3(a)(2))
- A maximum of 11 hours of driving within that 14-hour window (395.3(a)(3)(i))
- A 30-minute interruption required once more than 8 hours of driving time have passed (395.3(a)(3)(ii))
How the 34-Hour Restart Works
The rule lives in 49 CFR 395.3(c). Under (c)(1), any 7-consecutive-day period may end when you begin an off-duty period of 34 or more consecutive hours. Under (c)(2), the same applies to any 8-consecutive-day period on the 70-hour schedule.
In practice, that means a properly taken restart closes out your old 7- or 8-day period. The on-duty hours you racked up before it no longer count against your weekly limit, and you start a fresh period when you come back on duty.
Three things to burn into memory:
It Has to Be Consecutive
34 hours means 34 consecutive hours off duty. Not 34 hours spread across a weekend. If you go on duty for any reason partway through, the consecutive count is broken, and the clock starts over when you go back off duty.
It’s Optional
The regulation says the period may end with a 34-hour break. Nobody is forcing you to take one. If your hours are fine, you can keep running and let your older days fall off the back of your 7- or 8-day window.
There’s No Nighttime or Weekly Limit Anymore
Plenty of drivers still believe the restart has to include overnight hours or can only be used once a week. That was true for a while, and it isn’t now. More on that below.
Timeline Examples
Example One: The Standard Weekend Reset (70-Hour/8-Day)
You’re running for a carrier that operates every day of the week, so you’re on the 70/8 schedule. By Friday you’re close to 70 on-duty hours. You park, go off duty at the end of your shift Friday evening, and stay completely off.
34 hours is one full day plus 10 hours. So if you shut down Friday evening, your restart is complete Sunday morning. Come back on duty after that point and your previous 8-day period is closed out. You’re running on a fresh clock.
Example Two: The Broken Restart
Same driver, same Friday evening shutdown. Saturday afternoon, they head to the yard to do a pre-trip, wash the truck, and top off fuel so they’re ready to roll Sunday. That’s inspecting, servicing, and conditioning a CMV, which 49 CFR 395.2 defines as on-duty time. The consecutive off-duty period ended the moment they went to work on the truck.
When they finish and go back off duty Saturday, the 34 hours start over from zero. Sunday morning comes and they’re nowhere near done. If they roll anyway on a log showing Saturday as off duty, the log is false.
Example Three: The 60-Hour/7-Day Driver
A regional driver whose carrier doesn’t run every day is on the 60/7 schedule. They hit 60 hours on Thursday night. They can either wait for older hours to roll off their 7-day window, or take 34 consecutive hours off starting Thursday night and be back to a fresh period by Saturday morning. If the next week is heavy, the restart is usually the cleaner play.
When the Restart Actually Helps
The restart is a tool, not a ritual. It pays off when:
- You’ve burned most of your weekly hours. If you’re near 60 or 70, waiting for days to roll off can trickle back only a few hours at a time. A restart gets you all of it.
- You’re stuck anyway. Waiting on a load over the weekend, sitting at a receiver that’s closed, or home on time off: if you’re going to be off duty that long regardless, log it cleanly and get the reset.
- The next week is front-loaded. Dispatchers, take note: a driver who restarts before a heavy run has the full weekly limit available instead of scraping by on whatever rolls back.
It’s less useful when your weekly hours are light. Taking 34 hours off when you’re nowhere near your limit just costs you time and revenue.
New dispatchers should also know that “7 consecutive days” and “8 consecutive days” start at the time the motor carrier designates for a 24-hour period (49 CFR 395.2). Know your carrier’s designated start time before you plan anyone’s week.
The 1 a.m. to 5 a.m. Rule Is Dead
The December 27, 2011 HOS final rule required restarts to include two periods between 1 a.m. and 5 a.m., which the rule called “the window of circadian low.” It also limited use of the restart to once every 168 hours. Compliance for most of those changes was due July 1, 2013.
Then Congress suspended both provisions through a series of appropriations acts. FMCSA’s 2019 restart final rule, effective September 12, 2019, removed both from the regulations to align them with the 34-hour restart option already in effect.
Bottom line: today’s restart has no overnight requirement and no once-every-168-hours limit. If a trainer or an old company handbook tells you otherwise, they’re working from outdated rules.
Common Logging Mistakes That Cause Write-Ups
The restart itself is simple. The violations come from what drivers log as “off duty” when it legally isn’t. Under 49 CFR 395.2, on-duty time runs from when you begin work or are required to be ready to work until you’re relieved of all work and all responsibility for work. Here’s where drivers trip.
Doing Truck Work on Your “Day Off”
Pre-trips, fueling, chaining up, swapping a light: 395.2 counts “all time inspecting, servicing, or conditioning any commercial motor vehicle at any time.” Logging it as off duty during a restart misstates your on-duty time and breaks the consecutive period.
Helping at the Dock
Loading or unloading, and supervising or assisting with it, is on duty under 395.2. Standing at the dock “just keeping an eye on things” during your restart is not off duty.
Babysitting a Broken-Down Truck
Repairing, getting help for, or staying with a disabled CMV is on duty. If your truck breaks down and you’re waiting on the wrecker, that time doesn’t count toward a restart.
Working a Side Job
This one catches a lot of people. On-duty time includes other work for a motor carrier and “any compensated work for a person who is not a motor carrier.” Picking up a shift somewhere else during your restart counts as on duty.
Coming Back a Little Early
34 means 34. Going on duty even a few minutes short means you didn’t take a restart, and the hours from your previous period are still on the books.
Ignoring Unassigned Driving Prompts
If someone moves your truck while you’re off, it can show up as unassigned driving. Under 49 CFR 395.32, you must review unassigned driving time when the ELD prompts you, and either claim it or indicate it isn’t yours. Don’t claim miles you didn’t drive. That would wreck a valid restart on paper.
ELD Tips to Keep Your Restart Clean
ELDs have been required for most motor carriers since December 18, 2017 (49 CFR 395.8). Use yours to protect yourself:
- Certify honestly. You certify your records by selecting “Agree” (395.30(b)(2)). Look at the restart period before you do. Under 395.8(e), no driver or carrier may make a false report in connection with duty status.
- Annotate every edit. Every change or addition to an ELD record must be annotated (395.30(c)(2)). If you correct a status, say why.
- Know your rights with dispatch. A motor carrier may not coerce you to falsely certify your records (395.30(e)), and may not alter or erase the original ELD information (395.30(f)).
- Handle malfunctions fast. If your ELD malfunctions, give your carrier written notice within 24 hours and reconstruct your record of duty status for the current 24-hour period and the previous 7 consecutive days (395.34(a)). A restart that disappears in a malfunction still has to show up on your reconstructed record.
- Remember what the officer sees. You must keep records of duty status for the previous 7 consecutive days (395.8). At inspection, that’s where the officer looks at your hours before and after the restart. Your carrier has to keep records and supporting documents for at least 6 months (395.8(k)), so a sloppy restart log doesn’t go away after the weekend.
The 34-hour restart is one of the most useful tools in the hours-of-service rules, and one of the easiest to botch. Take 34 truly consecutive hours off duty, keep your hands off the truck and away from side work, clear unassigned driving prompts honestly, and certify a log that matches what actually happened. Do that every time and the restart works exactly the way it’s supposed to: a full weekly clock, a clean record, and nothing for an officer to write up.
0 Comments