Flexible Sleeper-Berth Pilot: A Dispatch Readiness Playbook

Why this topic matters to a trucking operation

Hours of Service is not an isolated office task. It affects the driver’s available time, the truck’s utilization, customer service, document quality, safety exposure, and the final margin on the load. A weak decision at the beginning of the trip often creates several smaller problems later in the workflow.

The subject of “Flexible Sleeper-Berth Pilot: A Dispatch Readiness Playbook” should therefore be handled as a repeatable operating process. The dispatcher needs reliable information, a clear owner for the next action, a deadline, and an escalation path when the plan changes.

Small fleets benefit from this discipline as much as large carriers. A documented process reduces dependence on one experienced employee and gives managers a consistent way to train new dispatchers, review exceptions, and improve performance.

Build the operating picture

FMCSA’s flexible sleeper-berth study could let approved volunteer drivers divide the required 10 hours off duty into 5/5, 6/4, or intermediate combinations during the exemption phase. That possibility can improve a driver’s ability to rest around congestion, appointments, and circadian lows, but it does not give dispatchers a new scheduling shortcut today. The current 7/3 and 8/2 framework remains the operating baseline for drivers who are not formally enrolled and authorized. A carrier considering participation needs a controlled plan for eligibility, ELD and telematics data, driver consent, customer appointments, fatigue escalation, privacy, and the return to normal rules when the study period ends. The practical goal is to make the next action obvious to the dispatcher, driver, and manager without searching across separate calls, messages, and spreadsheets.

A connected transportation management system gives the team one timeline for the load. That timeline should contain the current status, responsible person, supporting documents, and the next decision point.

Use this field playbook

Apply the process consistently to every applicable load, then make exceptions visible instead of keeping them in someone’s memory.

• Create a written scope for the pilot before assigning any qualifying load. Identify the approved carrier and driver, effective participation dates, exemption documentation, tractor and sleeper berth, ELD account, study contacts, allowed split combinations, data devices, and the compliance manager authorized to release or stop an operation.
• Keep ordinary dispatch planning separate from pilot planning. The load record and driver profile should make authorization unmistakable so no dispatcher applies a 5/5 or 6/4 split to a driver who is outside the study, waiting for approval, on a different unit, or past the exemption period.
• Build each trip from the driver’s actual rest opportunity, not only the extra scheduling flexibility. Review when and where each qualifying period can occur, parking and facility conditions, expected noise and interruption, appointment risk, traffic, weather, securement checks, and whether the driver can obtain restorative sleep.
• Protect driver discretion and fatigue reporting. Participation should never become a reason for a shipper, receiver, broker, or carrier to consume the shorter rest period as free detention or pressure a driver to continue when tired. Give the driver a direct stop-work and escalation path without retaliation.
• Test ELD, actigraphy, telematics, survey, and record-retention workflows before the first pilot load. Confirm time zones, status changes, annotations, device pairing, data transmission, technical support, privacy notices, access controls, and the process for correcting a missing or inaccurate record without concealing the original event.
• Create an exit and exception plan for device failure, driver withdrawal, disqualification, crash, illness, excessive sleepiness, out-of-service order, missed appointment, study suspension, or the end of the 16-week participation window. The plan should restore the applicable standard HOS calculation and protect every active load.

Measure the result

Measure sleep opportunity, subjective fatigue, safety-critical events, hard braking, lane or speed alerts, HOS exceptions, detention, on-time service, parking availability, driver feedback, ELD corrections, data failures, and loads rescheduled for safety. Review results with the driver, safety, dispatch, and study contacts. The purpose is to learn whether added flexibility supports alertness and quality of life—not to extract more work from the same duty cycle. Track a small number of outcomes such as on-time performance, empty miles, document cycle time, accessorial recovery, calls per load, and contribution per truck-day.

Review exceptions weekly. The purpose of measurement is not to create more reporting; it is to find the recurring handoff or missing field that causes preventable work.

How to put the information into daily practice

Start by identifying where hours of service appears in the current dispatch workflow. Review what information is collected, who confirms it, where it is stored, and what event triggers the next action. If the answer depends on a private text message or someone’s memory, the process is difficult to audit and difficult to scale.

Use one load timeline to connect the booking decision, driver assignment, route and appointment plan, status updates, exceptions, supporting documents, accessorial approvals, and invoice readiness. Each update should answer three questions: what changed, who owns the response, and when the next update is due.

Introduce the improvement on a small group of active loads before applying it to the whole fleet. Review the exceptions at the end of each shift, correct unclear fields or instructions, and then make the successful version the standard operating procedure.

• Create a written scope for the pilot before assigning any qualifying load. Identify the approved carrier and driver, effective participation dates, exemption documentation, tractor and sleeper berth, ELD account, study contacts, allowed split combinations, data devices, and the compliance manager authorized to release or stop an operation.
• Keep ordinary dispatch planning separate from pilot planning. The load record and driver profile should make authorization unmistakable so no dispatcher applies a 5/5 or 6/4 split to a driver who is outside the study, waiting for approval, on a different unit, or past the exemption period.
• Build each trip from the driver’s actual rest opportunity, not only the extra scheduling flexibility. Review when and where each qualifying period can occur, parking and facility conditions, expected noise and interruption, appointment risk, traffic, weather, securement checks, and whether the driver can obtain restorative sleep.
• Protect driver discretion and fatigue reporting. Participation should never become a reason for a shipper, receiver, broker, or carrier to consume the shorter rest period as free detention or pressure a driver to continue when tired. Give the driver a direct stop-work and escalation path without retaliation.
• Test ELD, actigraphy, telematics, survey, and record-retention workflows before the first pilot load. Confirm time zones, status changes, annotations, device pairing, data transmission, technical support, privacy notices, access controls, and the process for correcting a missing or inaccurate record without concealing the original event.
• Create an exit and exception plan for device failure, driver withdrawal, disqualification, crash, illness, excessive sleepiness, out-of-service order, missed appointment, study suspension, or the end of the 16-week participation window. The plan should restore the applicable standard HOS calculation and protect every active load.
• Assign a named owner and a due time for every unresolved exception.
• Keep customer and driver communication attached to the load record.
• Review the result after delivery and carry the lesson into the next similar load.

Common mistakes and practical risk controls

The most common mistake is acting with incomplete information because the load feels urgent. Speed is useful only when the basic facts are verified. Before committing the truck, confirm the parties, rate or cost exposure, equipment, timing, route constraints, required documents, and the person authorized to approve changes.

Another mistake is allowing an exception to remain inside a phone call. If detention, a missed appointment, an equipment problem, a route change, a rejected shipment, or a compliance concern is not recorded, the next person cannot make a fully informed decision. Written timestamps and supporting documents protect both service and payment.

Finally, avoid measuring activity instead of outcomes. More calls, messages, or status entries do not necessarily mean better control. The useful question is whether the process produced a safer trip, an on-time delivery, a complete document set, a satisfied customer, and an acceptable contribution margin.

• Do not promise an appointment before checking realistic transit and driver hours.
• Do not rely on an unverified email, changed phone number, or altered payment instruction.
• Do not close the load while documents, accessorials, or customer exceptions remain unresolved.
• Do not change a compliance process based only on a headline; confirm the official requirement first.

What managers should measure

A useful scorecard for hours of service should be short enough to review every week. Combine service, cost, workflow, and safety measures so that one improvement does not hide damage somewhere else.

Compare performance by customer, lane, dispatcher, equipment type, and exception reason. Trends become actionable when the team can see where a delay or cost begins, not only the final monthly total.

• On-time pickup and delivery percentage, including the documented cause of every miss.
• Loaded and empty miles, revenue per total mile, and contribution per truck-day.
• Average check-in, loading, unloading, and detention time by facility.
• Time from delivery to verified POD and time from verified POD to invoice.
• Number of avoidable exceptions, repeated data corrections, and unresolved driver issues.
• Safety or compliance events that required a dispatch change or management review.

A simple implementation checklist

Use this checklist during a dispatch meeting or process review. Each item should be visible in the company’s transportation management workflow and understandable to the person covering the desk after hours.

• The load has a verified customer or broker, rate, commodity, equipment type, weight, and reference number.
• Every stop has an address, appointment, contact, instructions, service-time allowance, and required document.
• The assigned driver and equipment can complete the plan safely and legally.
• Fuel, toll, deadhead, parking, and likely delay exposure are reflected in the operating decision.
• The driver knows the next action, expected updates, and the exceptions requiring immediate escalation.
• Delivery paperwork and accessorial evidence will flow directly into review and invoicing.
• A manager can reconstruct the load history without searching personal messages or separate spreadsheets.

Frequently asked questions