Northeast Freight Time one clock, four readings

Safety and Billing Are One Argument

Inside most companies, detention is two unrelated topics. For a related perspective on workplace measurement, read more.

Finance sees a billing dispute. Charges arriving, some paid, some contested, a line in accessorial spend. For broader industry reporting and context, see Descartes.

Safety sees fatigue and hours-of-service exposure. Drivers running out of window, late-day driving, near misses.

They are the same interval. Nobody in either department usually knows that the other is looking at it.

The connection, stated once

Waiting consumes the 14-hour window, which does not stop for anything. A driver held three hours has three fewer hours to reach a delivery, and the pressure to arrive lands on the driving that remains — later in the day, in worse conditions, with a deadline.

That is the plausible mechanism behind the federal audit's finding that a 15-minute increase in average dwell is associated with a 6.2% higher expected crash rate. The association is measured; the mechanism is reasonable and separately unproven.

So the invoice and the incident report describe the same hours. One arrives at accounts payable and the other at the safety committee, and they are never joined.

Why joining them changes the conversation

Safety has standing that billing does not.

A carrier disputing an invoice is a vendor arguing about money. A carrier presenting a federal audit associating dwell with crash risk is raising a safety matter, and in most organisations those go to different people with different authority.

It also changes the receiver's internal politics. A receiving manager can decline a detention charge indefinitely. A receiving manager whose facility appears in a safety discussion has a harder position, because the party who controls the dwell is not usually the party who receives the invoice.

This is not a rhetorical trick. It is a more accurate description of what detention is, and the billing frame is the narrower one.

The honest limits

Being precise, because overstating this discredits it.

The audit finding is an association across fleet-level data, not a demonstrated chain for an individual driver on an individual day. Your dock caused that crash is not supported and invites a rebuttal that discredits everything else.

Not all detention creates safety exposure. A wait at hour two of a driver's day, with a local delivery afterwards, costs money and no margin. The exposure is specific to waits that push the window.

And drivers make choices too. Logging off duty during a wait protects the clock and undermines the detention claim, and the fact that this trade exists at all is the clearest evidence that the two systems have never been reconciled.

What to do inside your own company

Show the same data to both departments. Dwell by facility, with the proportion of visits that pushed a driver's window. One report, two audiences.

Have safety in the room at contract renewal. Free time and appointment terms are safety terms, and they are currently negotiated by people who do not know that.

And put the hours consumed on the invoice. Not as a charge — as a line of context. 3h 12m detained; driver's remaining window at departure: 2h 40m. It costs nothing, it is true, and it makes the interval legible to someone who does not think in dollars.

What to do as a facility

Ask what your dwell does to a driver's day, once, of a carrier who will tell you honestly.

Most receiving operations have never been told that waiting consumes a federal clock. It is not indifference — the information has never reached them, because it arrives as an invoice and invoices go to a different department.

Explaining it once changes behaviour more reliably than billing does, and it costs a conversation.

The short version