34 Hour Restart
34 hour restart - Optimize your fleet in 2026 with our 34-hour restart guide. Learn HOS, ELD interactions, & practical strategies for hauliers & dispatchers
At some point every dispatcher gets the same unpleasant screen. One good driver is close to the weekly cap. A time-sensitive job is sitting unassigned. Sales wants it covered. The customer doesn't care about your Hours of Service clock. The driver wants to keep moving, but only if the plan makes sense.
That's where the 34 hour restart stops being a compliance term and becomes an operating decision.
If you treat it as a default habit, you'll park trucks when you didn't need to. If you ignore it, you'll burn through available hours and paint yourself into a corner. The essential task isn't memorizing the rule. The essential task is deciding when a restart protects the week and when rolling hours would keep the truck earning.
For general haulage and container work, that distinction matters. Port queues, late paperwork, depot cut-offs, driver handovers, and backhaul timing all turn the restart into a scheduling tool with real consequences for margin and service.
Table of Contents
The Dispatcher's Dilemma An Introduction
A planner's mistake rarely looks dramatic in the moment. It usually starts with a reasonable decision made under pressure.
You've got a driver deep into the week, close to the top of the available weekly hours. There's still work on the board. One customer wants a same-day collection. Another wants an early slot tomorrow. If you assign the wrong job now, the driver may run short at the worst possible point, halfway through a profitable sequence. If you stand the driver down too early, you lose productive time that you'll never bill back.
That's why experienced dispatchers don't ask only, “Is the driver legal?” They ask better questions.
- Can this driver finish today's work without damaging tomorrow's plan?
- Would rolling hours recover soon enough to avoid a full stop?
- Is a restart being chosen because it's smart, or because nobody has checked the board properly?
- Will the driver be parked in a place where the break can stay uninterrupted?
In container work, the decision gets sharper. Port environments punish vague planning. A driver may look like a good candidate for a reset until a quay instruction, terminal update, or yard move lands in the middle of the break. In general haulage, the issue is different. The restart might be the cleanest way to line the truck up for a stronger next cycle, especially if a backhaul or outbound run is already visible.
Practical rule: Don't treat the 34 hour restart as a weekly ritual. Treat it like any other scarce operational tool. Use it only when it improves the next sequence of jobs.
Good dispatch work sits between two failures. On one side, there's pure compliance thinking. On the other, there's over-aggressive scheduling that looks efficient right up to the point where the truck can't move.
The best planners learn to read the restart in commercial terms. What capacity does it free up, what revenue does it delay, what risk does it remove, and what flexibility does it buy back for the rest of the fleet.
What Is the 34 Hour Restart The Core Rules
A dispatcher usually meets the restart in the middle of a problem, not in a handbook. The driver still has enough daily hours to work, the load is there, and the truck is parked, but the weekly clock is nearly spent. That is where bad planning shows up fast.
The 34 hour restart is a voluntary provision in FMCSA Hours of Service rules. A property-carrying driver can reset the weekly 60-hour in 7-day or 70-hour in 8-day on-duty limit by taking 34 consecutive hours off-duty or in the sleeper berth. For dispatch, the practical point is simple. This option restores weekly capacity in one block instead of waiting for hours to roll off day by day.
What the restart does
The restart clears the accumulated weekly total for the rolling workweek clock. It does not extend the daily driving window, replace the break rules, or fix a bad dispatch plan. It gives the driver a fresh weekly clock once the full qualifying break is complete.
That distinction matters on a busy board. A driver can be legal on the daily limits and still be unusable because the weekly total is nearly gone. Dispatchers who miss that tend to promise work the truck cannot lawfully cover.
Used well, a restart buys certainty. Used badly, it parks revenue-producing equipment longer than necessary. If your team is trying to forecast that trade-off across several drivers, a good predictive scheduling approach for dispatch planning helps you spot where a clean reset creates more value than waiting for hours to return gradually.
What counts as a valid restart
The break must be 34 consecutive hours. Consecutive means unbroken. If the driver goes back on duty during that period, even for something that feels minor in the traffic office, the restart fails and the clock keeps its prior weekly total.
That is where new dispatchers get caught.
A practical briefing looks like this:
- Protect one continuous block: The full period has to run without interruption.
- Keep the driver off admin work: A status change for paperwork, yard moves, inspections, or other small tasks can destroy the restart.
- Check the log, not the plan: “He was supposed to be resting” does not matter if the ELD shows on-duty time.
- Match the status to how the break is taken: If the driver is using sleeper berth time, the record has to reflect it correctly.
Later guidance explains sleeper berth use in operational terms. Dispatch control is more straightforward than the legal wording makes it sound. Keep the break uninterrupted, keep the status clean, and do not let anyone chip away at it with small requests.
Here's a useful visual explanation before we go further.
Old myths that still confuse dispatch
A lot of restart mistakes come from old rule memory. Drivers, planners, and even some office staff still repeat earlier restrictions that no longer apply, especially the old 1 a.m. to 5 a.m. requirements.
For day-to-day planning, the lesson is not historical. It is operational. If someone on the board is building the week around an outdated version of the rule, you get unnecessary layovers, missed loading slots, and poor asset use for no compliance benefit.
Some dispatch problems come from old assumptions. The truck gets parked for a rule that is no longer in force, and the revenue loss is real even if nobody notices it on the first day.
The 34 hour restart is there to restore weekly capacity when the operation benefits from a clean reset. It is not a required weekly ritual. Good planners use it on purpose, with a clear view of what that parked truck costs and what the fresh clock is worth.
Restart vs Rolling Hours Strategic Choices for Planners
The expensive mistake is using a restart when rolling hours would have done the job. The dangerous mistake is gambling on rolling hours when the next sequence of jobs needs more certainty than the clock can offer.
Dispatch has to choose between those two.
Why dispatchers overuse restarts
The restart is simple to explain. Park the driver, protect the break, start again clean. Rolling hours are less tidy. They demand attention to what drops away from the cycle and when those hours become useful.
That's why many operations default to the restart even when it's optional. The restart feels safer from the traffic office chair. But optional means exactly that. Drivers can wait for hours to refresh through the rolling 7-day or 8-day cycle instead of taking a restart, as explained in this guide on the optional nature of the restart and the knowledge lag around old restrictions.
In practice, I'd be suspicious anytime a weekly restart appears on the board with no discussion. Habit is not a strategy.
A practical decision framework
When you're choosing between a restart and rolling hours, work through the next operating window rather than the current problem.
Ask these questions in order:
What work is committed next?
If tomorrow and the following day are soft, a restart may cost less than it looks. If the board is full and timing is tight, stopping the truck may create more damage than managing the clock carefully.
How predictable is the work?
General haulage with planned reloads suits a restart better than volatile ad hoc work. Container moves often swing on port timings, empty return windows, and customer release issues. In that setting, flexibility may be worth more than a clean reset.
Where is the driver now?
A restart in the wrong place can be operationally useless. If the truck will complete the break far from the next profitable move, the reset may solve a legal problem but create a commercial one.
What is the driver's remaining usefulness without a restart?
If rolling hours will restore enough usable capacity soon, you may be paying with idle time for a reset you didn't need.
How likely is interruption?
If the driver is in a port, shared yard, or customer site where “just one quick task” often happens, the restart is at risk from the start.
A short comparison helps frame it:
| Choice |
Best fit |
Main weakness |
| 34 hour restart |
Predictable sequence, strong demand after the break, easy place to park uninterrupted |
Non-revenue downtime and loss of immediate flexibility |
| Rolling hours |
Variable workflow, short jobs, close monitoring, frequent rescheduling |
Harder to manage and easier to misread |
Where software helps
This decision gets easier when dispatch can see future pressure, not just current legality. A board that shows job timing, driver allocation, and likely pinch points is far more useful than a bare compliance screen.
Teams trying to improve this usually benefit from pairing Hours of Service decisions with forward planning logic. A good example of that broader planning mindset appears in this piece on predictive scheduling for dispatch teams, where the focus is not just “can the truck move?” but “what does today's decision do to tomorrow's board?”
If the next two days are uncertain, preserve options. If the next two days are booked and clean, reset with purpose.
For container hauliers, that trade-off is sharper. A parked driver may avoid a weekly cap issue but miss the very appointment sequence that would have justified staying available. The right answer usually comes from timing quality, job visibility, and interruption risk, not from rule memorization.
Managing Restarts with ELDs and Your Jobs Grid
The ELD records the statuses. Dispatch owns the process around them.
That distinction matters because most restart failures aren't caused by the device. They're caused by poor coordination between the office and the driver. Someone assumes the driver is “basically on break.” Someone else asks for a small task. The driver complies. The clock starts again.
What the ELD shows and what dispatch should check
A dispatcher doesn't need to overcomplicate this. The ELD gives the factual trail. The office has to interpret it against the live plan.
Look for three things:
- Current status integrity: Is the driver indeed off-duty or in the appropriate sleeper status?
- Elapsed uninterrupted time: Has the break remained clean from the starting point?
- Future temptation points: Are there planned calls, gate instructions, swaps, paperwork requests, or site moves that could turn into on-duty activity?
The board view matters just as much as the ELD. A dispatcher who can see assignment pressure in one place is far less likely to sacrifice a restart to solve a minor short-term problem. That's why a visual planning layer such as a jobs grid for transport scheduling is so useful. It helps the office protect the restart instead of accidentally consuming it.
The micro-interruption problem
Such interruptions result in unnoticed financial losses. Any on-duty activity breaks the restart and forces a reset to zero, and a single fragmented task near hour 30 can turn a planned break into a much longer non-revenue stoppage, as described in this discussion of restart interruptions and their operational cost.
For container work, this is painfully familiar. The office sends a quick request to check a terminal detail, update a reference, reposition for access, or handle a brief paperwork step. It sounds harmless because the task is short. Operationally, it can destroy the entire reset.
A 15-minute job can be more expensive than a missed collection if it kills a nearly completed restart.
That's why dispatch should treat restarting drivers as protected assets, not spare capacity.
How to brief drivers so the restart survives
A workable briefing is simple and direct. Don't bury it in policy language.
Use something like this:
- State the purpose clearly: “You are on a planned restart, not stand-by.”
- Define the boundary: “Do not go on duty for checks, moves, paperwork, or terminal tasks unless dispatch confirms we are abandoning the restart.”
- Give one contact route: The driver should know exactly who to call if a customer, yard, or terminal asks for action.
- Mark the jobs board visibly: Everyone in the office should be able to see that the truck is protected.
If your office can't do that consistently, the restart becomes unreliable as a planning tool. Then dispatch starts distrusting restarts, and the business falls back on overly conservative scheduling or last-minute firefighting.
Worked Examples for Haulage and Container Operators
The rule makes more sense when you watch how the decision changes with the operation. The same legal option can be smart in one workflow and wasteful in another.
Example one general haulage
Driver A is running regular road freight with a planned reload already visible. The truck finishes a delivery, and the office can see the next worthwhile sequence, but only if the driver comes back with enough usable weekly capacity to handle it without stress.
Here the restart often makes sense for one reason. Predictability.
The planner looks at the board and sees:
- A clean stopping point: The current job ends in a place where the truck can be parked without likely interruption.
- A known next cycle: There's useful work waiting after the break, not vague hope.
- A stronger downstream plan: A reset creates room to complete the next chain of jobs without constant clock management.
In that situation, letting hours roll might keep the truck technically available, but only in fragments. Dispatch then spends the next period trying to fit freight around a shrinking and reappearing weekly balance. That can work, but it often creates awkward handoffs, slower decision-making, and more missed opportunities.
A general haulage planner usually wants one thing from a restart. A fresh, dependable operating block.
For work of that type, the restart is less about today's legal position and more about tomorrow's execution quality.
Example two container operations
Driver B is serving a port and inland delivery points. The workflow is unstable. Appointment times move. Containers aren't always released when expected. Queue time can change the shape of the whole day. Consequently, dispatch has to be more careful with automatic resets.
The office sees a driver near the weekly edge and considers a 34 hour restart. On paper, a reset would clean the week up. In reality, the decision is harder.
If the driver parks for the restart:
- the truck loses immediate availability
- a released unit may become someone else's problem
- a cut-off or return window may become harder to meet
- the office may still end up interrupting the break because port work often generates “small” tasks that don't stay small
If the office relies on rolling hours instead:
- the driver stays in play
- dispatch keeps flexibility
- the plan requires tighter tracking and better communication
That's why container teams should decide from the jobs board backward, not from the rulebook forward. If the likely work ahead is fragmented and timing-sensitive, rolling hours may preserve more useful optionality than a full restart.
One practical habit helps here. Match the HOS decision to the type of job pressure.
| Situation |
Better starting instinct |
| Stable backhaul, known delivery sequence, low interruption risk |
Lean toward a restart |
| Port uncertainty, changing releases, likely gate delays, small reactive jobs |
Lean toward rolling hours |
For teams dealing with quay work and intermodal coordination, this kind of decision-making sits inside the wider challenge of managing container jobs effectively. The restart only pays off when it supports the actual flow of container work rather than fighting it.
Compliance Tips and Final Strategic Takeaways
A dispatcher usually feels the pressure at the worst moment. Friday is filling up, one driver is short on weekly hours, another could restart, and the customer only cares that the box moves. These circumstances reveal weak planning. If you treat the 34 hour restart as a default reset button, you can protect compliance and still lose revenue, miss service windows, or strand equipment in the wrong place.
The practical rule is simple. Use the restart only when it improves the next block of work. If it does not improve truck availability, service reliability, or margin, rolling hours may be the better call even if the restart looks cleaner on the log.
The checklist that holds up in live operations
- Use the restart on purpose: Put it in the plan because the next 2 to 3 days support it, not because the driver is getting tight on hours.
- Protect the off-duty period: A quick favor, a yard move, or a call that turns into work can break the reset and force a complete replanning of the board.
- Check freight position before HOS position: A legal driver in the wrong port, depot, or delivery area can still be the wrong asset for the job.
- Give the driver a clear instruction: If the message sounds like “rest, but stay near the phone,” the office has not really committed to the restart.
- Strip out old rule talk: Dispatch errors still come from people repeating outdated restart requirements and planning around limits that no longer apply.
- Price the downtime properly: Parked time affects utilisation, trailer flow, parking risk, and exposure while the unit is sitting. For fleets reviewing that side of the decision, a resource on commercial truck insurance Florida can help frame the risk alongside scheduling.
A good planner asks two questions in order. Is the driver legal? Then, is this the best use of that driver and truck for the next operating window?
That second question is where stronger dispatch teams separate themselves. A restart can clean up the week, but it also removes a truck from circulation for a day and a half. In container work, that can mean losing flexibility around cut-offs, storage pressure, empty returns, or last-minute release changes. In steadier linehaul work, the same restart may create a cleaner handoff into a profitable run with less admin and less HOS babysitting.
The strategic takeaway is straightforward. The 34 hour restart is an option, not a weekly habit. Use it when it improves the plan. Let hours roll when keeping the truck available creates more value and the team can manage the tighter margin for error.
If your office gets that decision right consistently, compliance stops being a box-ticking exercise and starts supporting service, driver management, and fleet margin.
If your team wants tighter control over planning, driver briefings, POD capture, and invoicing in one workflow, take a look at Logivo. It's built for hauliers and container operators that need a clearer jobs board and less admin drag in day-to-day dispatch.