The 34-hour restart, and when it helps

← All guides

Every driver who works a full week meets the same wall. The daily clocks come back with rest — sleep tonight, drive tomorrow. But the weekly clock, the 60 hours in 7 days or 70 hours in 8 days, does not come back all at once just because you slept. Hours return slowly, a day at a time, as old days fall off the back of the count. For a driver with a long run ahead, that slow return can mean short days, split loads, and plans that never quite work.

The 34-hour restart is the other way back. It clears the whole weekly count in one stretch of time off. This guide explains the rule as it stands today, works a real example both ways — restart and recap — and helps you judge when a restart is worth taking and when it is wasted time.

What the 34 hours must be

The 34 hours must be consecutive. That is the whole shape of the rule. One unbroken stretch of at least 34 hours in which you are not on duty. Off duty time counts. Sleeper berth time counts. A mix of the two counts — a driver who spends part of the stretch in the berth and part at home, off duty, has still been off duty the whole way through.

What breaks it is going on duty in the middle. A shift in the middle restarts the count. If you take 20 hours off, come on duty for a short job, and then take 20 more hours off, you have not taken a 34-hour restart. You have taken two shorter rests, and the 34-hour clock starts again from the end of that shift. Forty hours off with work in the middle is not more than 34 hours off without it — for this rule, the unbroken stretch is all that matters.

Thirty-four is a minimum, not a target you must hit exactly. More than 34 consecutive hours off also ends the old count and starts a new one. A full weekend at home, Friday night to Monday morning, is well past 34 hours, and it does the same job. The rule does not ask you to watch the clock and jump up at hour 34; it asks whether, when you came back on duty, you had been off for at least 34 consecutive hours.

What the restart clears — and what it does not

The restart clears the weekly clock only. It is aimed at one thing: the 60/70-hour count in 395.3(b). After a valid restart, that count is zero, no matter how heavy the days before it were.

The daily clocks — the 11-hour driving limit and the 14-hour window — still need their own rest. They always did. But here the arithmetic is kind: before driving again, a driver needs 10 consecutive hours off duty, and a 34-hour stretch off contains that 10 many times over. So a driver who completes a restart does start fully fresh: weekly count at zero, and the 10 hours off before the next shift already taken inside the 34. There is no extra rest owed on top of the restart before the next day can begin.

What the restart does not do is reach backward. It does not fix a week that already went over the limit, and it does not make hours driven while the weekly count was already full legal after the fact. The rule is about starting a new count, not rewriting the old one. If you are at the limit now, the restart is how you start clean from here — it is not a cure for hours already worked past the line.

The old extra conditions are gone

Older drivers may remember a harder version of this rule. In 2013, the restart carried extra conditions: it had to include two overnight periods, and a driver could use it only once a week. Drivers who learned the rule then sometimes still plan around those conditions now — leaving home later than they need to, or refusing a second restart in a week they think they are not allowed to take.

Say it plainly: those conditions are not in the current rule text of 395.3(c). They were suspended years ago and are gone. The current rule has no requirement for two overnight periods, and no once-a-week cap. There is no limit on how often a driver may take a restart. If the week calls for one on Sunday and the next week calls for one on Saturday, both are allowed. Plan by the rule as it is written today: 34 or more consecutive hours off, and the count starts again from zero.

Restart or recap? The two ways back

A restart is optional. Nobody must take one. The alternative is recap: keep working on the hours that fall off the back of the 7- or 8-day count each day. Under recap, there is no single moment when your hours come back. Instead, each morning, the hours you worked on the day that just left the count become available again — a few hours at a time, never a full clock all at once.

Recap suits a driver whose hours come back as fast as he uses them. If you worked light days a week ago, good hours fall off the back each morning, and you can run steadily without ever stopping for a restart. Restart suits a driver whose recent days were all heavy: nothing light is about to fall off the count, the hours coming back are thin, and a long run is waiting. Rather than nurse small hours for days, he takes the 34 hours off and starts again with everything.

The choice is really about the days behind you. Look at the day that falls off tomorrow. If it was a 12-hour day, recap hands you 12 hours and running makes sense. If it was a 4-hour day, recap hands you 4, and the day after that may hand you little more. A driver staring at a string of thin returns is exactly the driver the restart was made for.

Put the two paths side by side and the trade is clear. The restart costs him Saturday — a full day and a night off — and pays him back with the entire 70 on Sunday morning. Recap costs him nothing in days off, and pays him in small pieces that may not add up to a workable day for most of the week. Neither path is always right. The right one depends on what work is waiting and what hours are coming back.

When a restart helps

• A weekend home. If you are home from Friday night to Sunday morning anyway, you have likely taken the restart without planning it. Come back Monday — or Sunday — with the count at zero instead of spending the week nursing recap hours.
• The end of a hard week. When heavy days are stacked behind you and only thin days are falling off the count, recap returns too little to run on. The restart ends the squeeze in one stretch.
• Before a long run. A long run planned against a nearly full week is a run planned to fail. Starting it with a fresh 70 means the week stops being the thing you are watching; the day clocks become your only concern.

When a restart does not help

• Midweek, with good recap hours coming. If a heavy day from last week falls off the count tomorrow morning, recap may hand you a full working day without any time off at all. Taking 34 hours off to get what tomorrow gives you for free is time spent for nothing.
• When the daily clocks were the real problem. A driver short on sleep but long on weekly hours gains nothing extra from the weekly count resetting. Ordinary rest answers a daily problem; the restart answers a weekly one.
• When the off time cannot stay unbroken. A stretch off that will be interrupted by a shift in the middle will not reach 34 consecutive hours. If the interruption is certain, do not plan the week as if the restart will happen.

A short drill for deciding

1. Read your count

   How many on-duty hours have you used in the current 7- or 8-day period, and how many are left? If plenty are left, there is nothing to decide.

2. Look at what falls off

   Check the next two or three days that will leave the count, and how many hours each hands back. Good hours coming back point to recap.

3. Look at the work waiting

   A long run or a heavy few days point to the restart. Light, local days can often run on recap alone.

4. If you restart, protect the stretch

   Pick the start, count 34 consecutive hours forward, and keep the whole stretch off duty. One shift in the middle starts the count over.

The restart is a simple rule that rewards a simple habit: when the week is nearly spent and the returns are thin, take the full stretch off, keep it unbroken, and start again at zero. When hours are already flowing back on their own, let them — and save your days off for when they buy you something.

Rules checked October 2026. Rule sources: 49 CFR 395.3(b)–(c).