Scheduling Around the Clocks
Detention is billed by the hour and the hourly charge is rarely the real cost. The real cost is that waiting consumes the driver's 14-hour window, and once that window closes the day ends regardless of how much driving time remains. For a workforce-operations comparison point, additional guidance.
Understanding which clock a wait damages is what makes scheduling around it possible. For additional freight-operations context, see Northeast Corridor Commission.
This is a summary of federal limits, not compliance advice. Verify against 49 CFR Part 395 and your own safety department.
Reviewed August 9, 2026.
The four limits
For property-carrying drivers in interstate commerce.
11-hour driving limit. Maximum driving after 10 consecutive hours off duty.
14-hour window. Driving is prohibited beyond the 14th consecutive hour after coming on duty. The window starts when the driver begins any work, not when they start driving, and off-duty breaks during it do not extend it.
30-minute break. Required after 8 cumulative hours of driving.
60/70-hour limit. Over 7 or 8 consecutive days, with a 34-hour restart to reset the cycle.
Which clock detention actually damages
The 14-hour window, almost always.
A three-hour wait consumes three hours of the window and no driving time. A driver who arrives with 11 hours of driving available and 14 hours of window loses the ability to use the driving time long before the driving time runs out.
This is why the 14-hour clock, not the 11-hour one, is the binding constraint on most days that include a dock. Pre-trip, loading, waiting, scale stops and fuelling all consume it, and none of them is driving.
So when planning around a facility known to run long, the question is not whether the driver has hours left. It is how much window remains after the wait, and whether the delivery is reachable within it.
The point where sources disagree
Worth flagging, because two widely-read guides contradict each other on this and it matters at a dock.
Can the 30-minute break be satisfied by on-duty not-driving time?
Since the September 2020 final rule, yes — the break may be satisfied by 30 consecutive minutes in any non-driving status, including on-duty not driving. Before that change only off-duty or sleeper berth counted.
Some guides still state the old position. Check 49 CFR 395 rather than a blog, including this one — the general lesson about sources applies to regulations too.
The practical consequence is direct: a driver at seven and a half hours of driving who is going to wait 30 minutes at a dock anyway can satisfy the break while waiting, which converts dead time into required rest instead of pure loss.
The 2026 pilots
FMCSA is running pilot programmes that bear directly on this, and they are pilots, not general rules.
Flexible Sleeper Berth, adding 6/4 and 5/5 split options to the existing 8/2 and 7/3, keeping the 10-hour total.
Split Duty Period, which lets an enrolled driver pause the 14-hour window with one break of between 30 minutes and 3 hours — explicitly so that detention does not consume driving hours already available.
That second one is the regulator testing a direct answer to the problem this site is about. It applies only to participants, it is not permanent, and it is worth watching rather than planning around.
Scheduling that survives a bad dock
Plan to the 75th percentile, not the average. Averages describe almost no actual visit, and a schedule built on the mean fails on half of loads.
Do not stack a tight delivery behind a known slow facility. The cascade costs more than the wait, and most of that cost is the delay in telling anyone.
Put the slow stop first in the day where possible. A wait at hour two leaves options; the same wait at hour ten does not.
Take the break at the dock when the arithmetic allows.
And plan parking before the window closes. A driver who runs out of window in the wrong place has a worse problem than a lost delivery, and it is the mechanism behind the association between dwell and crash risk.
What to tell a facility
Most receiving staff do not know that waiting consumes a legal clock. Explaining it once changes behaviour more than an invoice does.
Every hour here comes out of a 14-hour federal limit that does not stop for waiting. At three hours my driver cannot reach the next delivery, which is why we ask for the appointment to hold.
That is checkable, non-adversarial, and it reframes the request from money to feasibility — which is the framing that works.
The short version
- Four limits: 11 hours driving, a 14-hour window, a 30-minute break after 8 hours driving, and 60/70 hours weekly
- The 14-hour window starts with any work and is not extended by breaks — it is the clock detention consumes
- Since the 2020 final rule the 30-minute break can be satisfied by on-duty not-driving time; some guides still say otherwise
- FMCSA's 2026 Split Duty Period pilot lets participants pause the 14-hour window specifically so detention does not eat driving hours
- Plan to the 75th percentile, put slow stops early, and never stack a tight delivery behind a known slow dock
- Telling a facility that waiting consumes a federal clock changes behaviour more reliably than an invoice