The rule says two periods. Your week says six. Here is how a chain actually resolves.
395.1(g)(1)(ii) allows the equivalent of 10 consecutive hours off duty from not more than two periods. So "8/2/8" is never one calculation — it is two pairings sharing a break:
The shared 2-hour break works in both pairings — the regulation does not "consume" a period. What matters at every junction: the two periods are consecutive rest periods separated only by on-duty/driving time, one of them contains ≥7 consecutive berth hours, neither is under 2 hours, and together they total ≥10.
| Time | Status | What it does |
|---|---|---|
| Day 1, 06:00–14:00 | Drive + on duty | 8 h work |
| Day 1, 14:00–22:00 | Sleeper berth | Berth period A (8 h) |
| Day 1, 22:00–Day 2, 00:00 | Drive | Window recalculated from 22:00 (end of A) |
| Day 2, 00:00–06:00 | Sleeper berth | Berth period B (6 h) |
| Day 2, 06:00–08:00 | Drive | — |
| Day 2, 08:00–10:00 | Off duty | Short period C (2 h) — pairs with B (6+2 = 8… fails 10) or A? A is long past |
Watch the totals: B (6 h berth) + C (2 h) = 8 h — that pairing fails the 10-hour total. B needs a 4-hour partner. This is exactly how over-stacked chains break: every junction must independently clear ≥10 total with a ≥7-hour consecutive berth stretch on one side.
Log every berth stretch as sleeper berth status. The engine pairs automatically when the floors are met; short periods logged off duty are usable as the shorter period. If your device pairs differently than you intended, check which two periods it chose — the anchor (and your deadline) moves with the pairing. More in ELD false violations.
All guides · The rule explained · Break order · 14-hour recalculation · Contact
Rule basis: 49 CFR 395.1(g)(1)(ii)–(iii) via eCFR.