The 70-Hour Rule, the Recap, and the 34-Hour Restart: How the HOS Clock Actually Works

Most hours-of-service trouble in a small fleet isn't the 11-hour or 14-hour rule. Drivers feel those every day and the ELD counts them down on the screen. The violations that show up at a new-entrant audit come from the weekly clock — the 60-hour/7-day or 70-hour/8-day limit in 49 CFR §395.3(b) — because it's a rolling total nobody feels until an auditor adds up eight days of logs and finds a Tuesday where the driver was already out of hours before the truck moved.

This post explains how that clock is actually counted: what "on duty" includes, why the limit is rolling rather than weekly, how the daily recap hands hours back, when the 34-hour restart is worth taking (and when it isn't), and how to audit your own eight days before someone else does. Every limit below is quoted from the current text of Part 395; nothing here changed in the 2020 final rule's wake, and the pilot programs FMCSA is running in 2026 are tests, not rules — more on that at the end.

If you're deciding whether you need an ELD at all, or what records the ELD doesn't replace, that's a different post: ELD records and HOS supporting documents. This one is about the arithmetic.

The daily limits, in one paragraph

So the weekly rule has context — §395.3(a), property-carrying drivers:

• 10 consecutive hours off duty before a shift starts (§395.3(a)(1)).
• A 14-consecutive-hour window from the moment you come on duty; no driving after the 14th hour (§395.3(a)(2)). Off-duty time inside the window does not stretch it — the window is wall-clock time.
• 11 hours of driving inside that window (§395.3(a)(3)(i)).
• A 30-consecutive-minute break once you've accumulated 8 hours of driving without one (§395.3(a)(3)(ii)). Any non-driving status counts — off duty, sleeper, or on-duty-not-driving. Drivers running under either short-haul exception in §395.1(e) are exempt from the break requirement.

Those four rules reset every day. The weekly clock does not.

The 60/70-hour rule: what it actually says

§395.3(b) is two sentences, and both words that matter are in them:

No motor carrier shall permit or require a driver … to drive … for any period after — (1) Having been on duty 60 hours in any period of 7 consecutive days if the employing motor carrier does not operate commercial motor vehicles every day of the week; or (2) Having been on duty 70 hours in any period of 8 consecutive days if the employing motor carrier operates commercial motor vehicles every day of the week.

Four things to get straight before you count anything:

1. It's a limit on driving after too many on-duty hours. The clock counts all on-duty time, not just driving. Under the §395.2 definition, on-duty time runs from when a driver begins work (or must be ready to work) until relieved of all responsibility, and it expressly includes waiting to be dispatched, inspecting and servicing the truck, loading and unloading or attending the load, time at a shipper's dock, repairing or attending a disabled vehicle, and time spent giving a drug or alcohol test specimen. A driver who drove 6 hours but sat 5 hours at a receiver burned 11 hours of the weekly clock. Once the driver has hit the cap, they may still work — they may not drive.

2. 60/7 vs. 70/8 is the carrier's schedule, not the driver's choice. If your operation runs trucks every day of the week, you are a 70-hour/8-day carrier. If there is a day of the week you don't operate CMVs, you're on 60/7. The driver's ELD should be configured to match — a driver set to 70/8 in a fleet that parks on Sundays is showing hours they don't legally have.

3. "Any period of 7 (or 8) consecutive days" means the window rolls. It's not Monday-to-Sunday. Every day, you look back at today plus the previous 6 (or 7) days and total the on-duty hours. When that total reaches 60 or 70, driving stops. §395.2 also says the 7- or 8-day period "begin[s] on any day at the time designated by the motor carrier for a 24-hour period" — you, the carrier, set the start time of the log day (midnight is typical), and every rolling window is measured in those days.

4. Nothing else in Part 395 extends it. The 2-hour adverse-driving-conditions allowance in §395.1(b)(1) extends the 11-hour and 14-hour limits of §395.3(a) — it does not add hours to the 60/70. Neither does the 16-hour short-haul exception in §395.1(o), which relieves the 14-hour window once a week for drivers who return to their home terminal every day. The weekly clock only ever gets hours back two ways: the recap, or a restart.

The recap: how hours come back every day

Because the window rolls, every new day the oldest day falls out of it. That's the recap. On a 70/8 clock, the hours you get back tomorrow are exactly the hours you worked eight days ago. Here's a driver on 70/8 who started fresh on day 1:

Read across day 8: the driver has zero hours available — 70 on-duty hours in the trailing 8 days — and cannot drive, even though they've had a normal 10-hour break and the ELD's daily clocks look fine. On day 9, day 1 (12 hours) drops off the back, so 12 hours are available. On day 10, day 2's 11 come back. That is the whole recap: tomorrow's hours = 70 − (on-duty hours in the 7 days ending today), which is the same as saying "you get back what you worked eight days ago."

Three consequences small fleets miss:

• A heavy week has an eight-day tail. Nothing you do today changes what comes back tomorrow — that number was fixed a week ago. If day 3 was 13 hours, day 11 will hand back 13 hours; if day 3 was 4 hours, day 11 hands back 4.
• On-duty-not-driving is where the week goes. A dock that holds a driver 4 hours costs 4 weekly hours the driver never spent driving. Two of those in a week and a "60-hour driver" is a 52-hour driver.
• The ELD's weekly clock is only right if the log day and rule set are right. Wrong 60/70 setting, wrong start-of-day designation, or on-duty time miscoded as off duty all produce a confident wrong number.

The 34-hour restart: when it's worth taking

§395.3(c): any period of 7 or 8 consecutive days "may end with the beginning of an off-duty period of 34 or more consecutive hours." Take 34 straight hours off and the rolling window is over — you start the next day with a full 60 or 70. The current rule text attaches nothing else to it: no once-a-week limit, no required overnight periods, no minimum time between restarts. (If you remember those conditions, they were suspended in late 2014 and are not in today's §395.3.)

The restart is optional. Whether it's useful is arithmetic:

• Take it when the recap is thin. If the trailing days were all 12–13 hours, the recap will hand back one heavy day at a time and the driver will be running on 10–12 available hours all week. Thirty-four hours off resets that to 70 at once. A driver who runs out of hours Friday afternoon, goes off duty at 3 p.m., and stays off until 1 a.m. Sunday has a full week again.
• Skip it when the recap is fat. If the driver worked light days last week (say 6–8 hours), those light days come back one at a time anyway, and the driver keeps a comfortable balance without losing a day and a half.
• A restart does not reset the daily clocks. The 11/14/30-minute rules run on their own 10-hour break; a 34 covers that trivially, but a driver who takes 34 off and then works 15 straight hours has still broken §395.3(a)(2).
• Off duty means off duty. Time in the sleeper counts; personal conveyance counts as off duty and can sit inside a 34-hour restart (see personal conveyance and yard moves for the honest boundaries). Answering dispatch calls and doing paperwork does not.

If your drivers use the sleeper-berth split under §395.1(g) — 7 consecutive hours in the berth plus at least 2 more hours off or in the berth, totaling 10, with neither period counting against the 14-hour window — that changes the daily math, not the weekly. Split or not, every on-duty hour still lands in the 60/70 total.

What this looks like at an audit and at the roadside

Two things happen with weekly-clock violations, and they're worse than the daily ones because they're rarely one-offs.

Roadside. A driver found to have driven after exceeding "the maximum periods permitted by this part" is placed out of service on the spot under §395.13(b)(1) — that language covers the 60/70 exactly as much as the 11 and the 14. Separately, a driver who can't produce a current record of duty status for today and the prior seven days is out of service under §395.13(b)(2). Both go on the carrier's record; see §395.3 — driving beyond the limit and §395.13 — driving after OOS for how the codes are cited.

Audit. The auditor doesn't spot-check; they pull the RODS the carrier is required to keep for 6 months under §395.8(k)(1) and add up the trailing days for each driver. That is exactly why the weekly clock is the one that bites: a driver who "just went a little over" on Wednesday because the ELD said 3 hours and it should have said 0 has a violation for every day the arithmetic was wrong. Systematic hours-of-service falsification — editing on-duty time to off duty to make the week fit — is a §395.8(e) false-record finding, and the ELD's own edit history is the evidence. And if a majority of the RODS you should have simply don't exist, that's §395.8(a) at the 51%-of-records threshold — one of the sixteen violations that fails a new-entrant audit outright under §385.321(b). The rest of the failure list is in what happens if you fail the audit.

Audit your own eight days (do this monthly, per driver)

You don't need software to check the weekly clock — you need eight days of logs and ten minutes. Software just does it every day instead of when you remember.

1. Confirm the rule set. Do you operate CMVs seven days a week? Then 70/8. Otherwise 60/7. Check that every driver's ELD profile matches, and that the log-day start time is the one you designated.
2. Pull the last 8 log days for the driver (7 on a 60/7 clock) — the ELD's daily summary is enough; you want total on-duty per day, which is driving plus on-duty-not-driving.
3. Add them up. If any trailing 8-day sum exceeds 70 (or 7-day sum exceeds 60), find the day the total crossed the line and check whether the driver drove after that point that day or on any later day before enough hours came back. That's a §395.3(b) violation per day.
4. Look at the recap the driver was working with. Compare "hours available at start of day" on the ELD to your own subtraction. A mismatch usually means miscoded status — on-duty time logged as off duty, or a yard move or personal conveyance that wasn't one.
5. Look for the 34. If the driver "restarted," find 34 consecutive off-duty hours on the log. Thirty-three hours and fifty minutes is not a restart; the week continues rolling.
6. Check the edit trail. Every edit to on-duty time should carry an annotation (§395.30 covers the mechanics). Edits that always move on-duty time to off duty, right before a driver would have run out, are what an auditor reads as falsification.
7. Cross-check one day against supporting documents — a fuel receipt or bill of lading time-stamped while the log says "off duty" is the classic §395.8(e) finding. The document rules are in the supporting-documents guide and the §395.11 page.

Do that for each driver once a month and the weekly clock stops being a surprise.

Two pointers, so you don't over-apply this post

• Short-haul drivers. A CDL driver working within a 150 air-mile radius of the normal work reporting location and released within 14 hours (§395.1(e)(1)) doesn't keep RODS or an ELD — but §395.3 still applies to them in full, including the 60/70. The carrier keeps time records (start, end, total hours per day) for 6 months, and those records are what you audit instead of logs. Non-CDL short-haul drivers under §395.1(e)(2) get relief from the 14-hour rule on a 14/16-hour pattern, but the weekly clock still counts. Details in the ELD and supporting-documents post.
• The 2026 pilots aren't rules. FMCSA is testing two flexibility concepts in 2026 — a "Flexible Sleeper Berth" pilot (adding 6/4 and 5/5 splits) and a "Split Duty Period" pilot (pausing the 14-hour window with up to a 3-hour break) — with a handful of enrolled drivers. Unless your driver is in a pilot, §395.3 as quoted above is the rule.

Keeping the weekly clock honest without doing the math yourself

The 60/70-hour rule is a rolling sum across every driver, every day, with a wrong-setting failure mode that looks fine on the ELD screen. Roadworthy HQ keeps each driver's daily duty-status totals — on-duty, driving, off-duty, sleeper — and the supporting documents behind them in the 6-month window §395.8(k) requires, with the retention enforced in the database rather than by memory, and flags the recordkeeping gaps that turn into §395.8(a) and §395.8(e) findings at audit. If you're staying audit-ready on a whiteboard today, start a 14-day free trial — no credit card required.

Related violation codes

The requirements covered above are cited as these violation codes in audits and roadside inspections:

• §395.3 — Driving beyond the 11-hour or 14-hour limit
• §395.8(a) — No record of duty status
• §395.8(e) — False record of duty status
• §395.11 — HOS supporting documents missing
• §395.13 — Driving after being declared out of service
• §395.30 — ELD record submissions, edits, and annotations