Compliance & Safety

Hours of service, explained for the dispatch desk

Route illustration

Hours of service is usually explained as a compliance topic. On the dispatch desk it is a planning constraint, and the difference matters: a dispatcher who understands the clocks builds schedules that work, while one who treats them as a legal footnote builds schedules that fail at the shipper gate.

There are three clocks running on every driver. Knowing which one binds first is most of the job.

The three clocks

  • 11-hour driving limit — total driving time after ten consecutive hours off.
  • 14-hour window — the shift clock. It starts when the driver goes on duty and does not stop for lunch, fuel, or a four-hour detention. This is the one that ruins plans.
  • 60/70-hour cycle — rolling seven or eight days, restarted by 34 hours off.

The 14-hour window is where dispatch decisions land. Driving time is protected; the window is not. Every hour a driver spends waiting at a dock is an hour of earning capacity burned, and no amount of pushing later in the day gets it back.

Plan the appointment, not the miles

A 600-mile run is comfortably legal and routinely impossible, because the delivery appointment sits an hour past the end of the window. Work backward from the appointment: subtract loading, driving, the 30-minute break, and a realistic detention allowance. If the answer does not fit inside 14 hours, the schedule is wrong — reset the appointment or split the run.

Drivers do not run out of miles. They run out of window.

Use the split and the exceptions honestly

The sleeper-berth split lets a driver pause the window with a qualifying rest period, which is genuinely useful for early-morning appointments after a long wait. The short-haul and adverse-conditions exceptions exist too, and both get abused into findings. Use them when they apply and document why.

Detention is an HOS problem

Four hours at a dock is not just an accessorial you may or may not bill. It is four hours of window, and it usually converts a one-day run into two. Recording arrival and departure times does two things at once: it supports the detention invoice and it tells you which customers are quietly costing you a truck-day per week.

What dispatch should see on the screen

Before a load is assigned: hours remaining on all three clocks, the time the window closes, and the driver's next required break. When that information sits next to the load instead of in a separate app, the planning question answers itself and the violation conversation never has to happen.

See it work in TMS Forge.

Book a 15-minute demo and we'll show you on your own numbers.