The clock is the real cost
Hours of Service is unforgiving about waiting. The 14-hour window runs continuously from the moment a driver comes on duty and it does not pause for a dock.
So a four-hour wait doesn't cost four hours of pay. It costs four hours of the day's driving capacity. A driver who could have covered a long run in the afternoon now can't legally start it. That is a load that doesn't move, or moves tomorrow, or goes to someone else.
Detention pay compensates the driver. Nothing compensates the fourteen-hour clock.
What it costs, itemized
Build the number once, for your own operation, and detention stops being an annoyance and becomes a business case.
- Lost revenue capacity: hours of the driving window burned, valued at your revenue per hour of driving.
- Driver pay for non-productive time, whether through detention pay or hourly guarantees.
- Idle fuel and engine hours accumulated while waiting.
- Schedule disruption downstream. A late departure cascades into the next two days of appointments.
- Turnover cost, weighted by how often detention shows up in exit interviews. It shows up a lot.
Measure it automatically or don't bother
Detention measured by driver self-report is disputed by definition, and any customer conversation built on it goes nowhere. The receiver's records say one thing, your driver says another, and the accessorial gets denied.
Geofenced arrival and departure timestamps end the argument. The truck entered the facility at 09:12 and left at 14:40. That is a record rather than a claim, and it converts detention from a billing fight into a documented fact.
- Geofence every regular customer facility, sized to the property rather than a generic radius.
- Record arrival, dock-in where available, and departure automatically.
- Attach the timestamps to the invoice as supporting documentation rather than as an afterthought.
- Track free-time thresholds per contract so the billable line is calculated rather than argued.
An accessorial backed by geofence timestamps gets paid far more often than one backed by a driver's message.
Turn the data into a customer conversation
Once you have facility-level dwell data, you have something most shippers have never seen: their own performance measured from the outside. Presented well, this is a constructive conversation rather than a complaint.
Rank your customers by average and 90th-percentile dwell. Take the numbers to the worst offenders with a specific ask, such as appointment windows that reflect reality, a drop-trailer program, or an earlier gate time. Many facilities will engage, because they're being told about a problem they can fix. For those that won't, you now have the data to price the lane properly or to stop serving it.
- Average dwell and 90th-percentile dwell by facility. The tail matters more than the mean.
- Dwell by day of week and time of day. The fix is often just a different appointment slot.
- Percentage of stops exceeding contracted free time.
- Trend over time, so improvement is visible and can be acknowledged.
What you can fix on your own side
Not all of it is the customer's fault, and the parts you own are the fastest to fix.
- Drop-and-hook wherever volume justifies the trailer pool. It converts a dwell problem into an equipment cost, which is usually the better trade.
- Plan appointments against the driver's actual remaining hours rather than an idealized schedule.
- Build known dwell times into the plan for facilities you can't change. A predictable four-hour wait is a schedulable one.
- Give drivers a way to log arrival and status without a phone call, so dispatch knows about a stall while there is still time to react.
