The 14-Hour Pause Is a Pilot, Not a Policy: Planning Detention and HOS Before 2027

A planner is looking at a driver with four hours left on the 14 and a receiver running three hours behind. Under today's rules, every minute in that door is a minute gone from the driving window, so the call is simple: escalate, recover, or reschedule. Next year, for a small group of drivers in a federal study, that call changes. The real risk for the rest of the network is that appointment setters, shipper ops, and carrier dispatch start acting as if it changed for everyone.

That is the practical takeaway from two Federal Register notices FMCSA published this week. They do not change Part 395 for the industry. They do put a date on the most consequential HOS experiment since the 2020 rewrite, and they bring back the exact detention question that killed the idea six years ago.

What actually moved this week

On October 6, 2026, FMCSA published an information collection notice (Docket FMCSA-2026-2081) for the Split Duty Period pilot. Participating drivers would be able to pause the 14-hour driving window once a day with a single period of 30 minutes to 3 hours. Qualifying time includes off-duty time, sleeper berth time, or on-duty, not-driving time spent at a pickup or delivery location. About 256 drivers would take part for 16 weeks.

On October 7, 2026, a companion notice (Docket FMCSA-2026-2080) covered the Flexible Sleeper Berth pilot. It cuts the minimum sleeper period in a split from 7 consecutive hours to 5, which opens 5/5 and 6/4 splits for enrolled drivers. It is also sized at about 256 drivers.

Comments on both notices are due December 7, 2026. Both still need OMB clearance. FMCSA's August 27, 2026 update said pre-tests ran in spring and summer 2026 (nine drivers from three carriers per pilot, six weeks each) and that the full programs launch in 2027, with 512 participants in total, four months of participation, and up to $1,600 per driver for completing study tasks.

Put plainly: in 2027, a few hundred drivers will run under exemptions. Everyone else stays on the 14-hour window, the 11-hour driving limit, the 30-minute break, and the 7/3 or 8/2 split.

Why the detention clause is the part to watch

This is not the first time FMCSA has tried a 14-hour pause. The August 2019 HOS proposal included a single off-duty pause of 30 minutes to 3 hours. The June 1, 2020 final rule dropped it, because commenters argued drivers would be pressured by carriers, shippers, or receivers to burn the pause on someone else's schedule. A September 2020 pilot proposal never launched, and it would not have let on-duty time count anyway.

The 2026 design goes further than either. It explicitly lets on-duty, not-driving time at the dock pause the clock, and FMCSA's own background text names unreasonably long detention as a reason drivers need the flexibility. The agency says it will monitor shippers during the pilot so the change does not lead to more detention.

The detention baseline explains why that monitoring matters:

• FMCSA's 2014 detention study found detention on about 1 in 10 stops, averaging 1.4 hours beyond the two-hour standard (3.4 hours at the stop). Medium-sized carriers saw detention roughly twice as often as large carriers.

• The DOT Office of Inspector General's 2018 report estimated detention cuts for-hire truckload driver earnings by more than $1 billion a year, and that a 15-minute increase in average dwell raises expected crash rates by 6.2 percent.

• An industry research report on 2023 data found 39.3 percent of stops involved detention, drivers lost between 117 and 209 hours a year depending on sector, and detention cost $3.6 billion in direct expenses plus $11.5 billion in lost productivity. Nearly all carriers (94.5 percent) bill detention, but fewer than half of those fees were paid.

FMCSA's newer, ELD-based detention study is still underway, so there is no fresh national number yet.

Here is the operational point. A pause protects the driver's day. It does not give back the truck's revenue hours, the next morning's load, or the fuel spent idling at the dock. If the market treats the pause as a pressure valve for slow docks, free time gets longer in practice, and detention collection, already under half, gets weaker. Ops leaders should make sure the pilot is measured against that baseline, not against a world where waiting at a dock is free.

Decision 1: Should your fleet volunteer?

Carrier eligibility in the October 6 notice is strict. You need interstate authority and minimum financial responsibility, and you cannot be a high or moderate risk carrier. You also need no Unsatisfactory rating, no FMCSA enforcement actions in the past three years, and driver and vehicle out-of-service rates at or below the national average. Unpaid civil penalties can exclude you. Drivers cannot appear in the Drug and Alcohol Clearinghouse (even after return-to-duty) or have a disqualifying suspension in the prior two years.

Participating carriers also agree to share each driver's records of duty status with the research team for the full study. Drivers wear actigraphy devices, take vigilance tests, and run a telematics unit. FMCSA estimates 16.68 hours of study tasks per driver over 16 weeks.

The fleets that get the most from volunteering are the ones whose drivers regularly hit the end of the 14 before they use the 11: regional and multi-stop retail, grocery and DC-heavy freight, reefer with long receiving windows. You get structured evidence about whether a pause changes your lane economics, which you can carry into rate and free-time conversations before anything becomes permanent.

The cost is internal. For four months your planners handle two rule sets, and a mistake in either direction is expensive. Applying the exemption to a non-enrolled driver is a violation. Ignoring it for an enrolled driver wastes the study.

Decision 2: Keep your network from planning around a rule it does not have

The more likely failure mode is not inside the pilot. It is outside it. An appointment scheduler hears that drivers can pause their clock now and books a tighter double. A broker rep promises a same-day reload because the driver can just pause. A dispatcher reads a headline about 5/5 splits and builds a relay that only works for enrolled drivers.

Brokers and 3PLs should treat this as a training and contract issue now, not in 2027. Appointment and ETA assumptions should keep using current HOS math unless a carrier confirms, in writing and per driver, that an exemption applies. Shippers that run their own appointment portals should not let pilot language change their free time or check-in rules.

Decision 3: Write detention terms that a pause cannot erase

If your rate confirmations and customer contracts tie detention to driver hours lost, a paused clock gives the other side an argument that no hours were lost. Close that gap before it shows up in a dispute.

• Start detention on documented arrival or check-in, not on duty status. Duty status is the driver's regulatory record. It is not a billing trigger.

• State that a driver's use of any HOS exemption does not change free time, detention, or layover terms.

• Back every claim with the same evidence set: ELD status changes, geofence arrival and departure, and facility check-in and check-out times.

• Score facilities on dwell regardless of who was waiting. If a receiver's dwell rises when pilot drivers show up, you want that data before FMCSA asks for it.

Decision 4: Comment, with data, by December 7

These are Paperwork Reduction Act notices, so comments go to whether the data collection is necessary, accurate, and as light on burden as possible. That is exactly where operators can help. A shop with clean ELD and geofence data can explain how to separate normal load and unload time from true detention, which FMCSA has called a critical gap in earlier research. It can also suggest how to record on-duty time at a facility so the pause measurement is not just noise. Comments that bring real dwell distributions by facility type carry more weight than opinions about whether the pause is a good idea.

Asset, broker, and hybrid: where the exposure sits

Asset carriers own the clock and the compliance risk. The pilot is a chance to recover driving hours on lanes that strand drivers at docks, but only if dispatch can plan for enrolled drivers separately and prove each pause was logged correctly.

Brokers own the promise. Their exposure is overcommitting appointments and reloads based on flexibility the assigned carrier probably does not have. They also lose detention leverage if customers start treating the pause as an excuse for longer dwell.

Hybrids get both problems at once. Their fleet side may enroll drivers while their brokerage side books the same customers. If the two desks use different assumptions about the clock, the customer hears two answers about the same facility.

What serious shops configure before the pilot opens

Every operation has a different mix of lanes, facilities, and driver schedules, which is why generic HOS planning breaks first at the edges. The shops that come through rule changes cleanly encode their own rules in the workflow instead of keeping them in planners' heads.

• A driver-level exemption attribute with start and end dates. Planning logic honors a pause or a 5/5 split only for drivers flagged as enrolled, and only during their exemption window.

• Separate remaining-14 and remaining-11 visibility. Load assignment and ETAs should show both, so planners can see when the window, not drive time, is the constraint.

• Facility statuses that separate waiting, loading, and off-duty at the facility. Billing, detention, and safety reviews each need a different slice of the same stop.

• Customer and facility free-time rules keyed to arrival. Detention triggers that fire on check-in, regardless of how the driver logged the time.

• Permissions on HOS assumptions. Only roles that can see a driver's enrollment should be able to plan against an exemption.

• Dwell reporting split by enrolled and non-enrolled drivers. If pause-eligible drivers wait longer at certain docks, you will see it in your own data first.

None of this requires waiting for 2027. Most of it pays off under today's rules, because the 14-hour window is already the binding limit at slow facilities.