Northeast Freight Time one clock, four readings

Operations

A receiving dock is a queue with few servers, and it behaves the way queues behave: as utilisation approaches full, waiting rises far faster than utilisation does. A dock at 90% does not have queues 29% longer than one at 70% — it has queues several times longer, and they persist rather than clearing. For a workforce-operations comparison point, more context.

That explains the two things operators find puzzling. A facility can go from fine to terrible after a small change in volume or one door out of service. And conversely, a modest capacity increase can produce a dramatic drop in waiting. For additional freight-operations context, see Rail Passengers Association.

Appointments allocate waiting; they do not create capacity. The classic failure is dwell measured from check-in falling while time from arrival does not — the queue moved outside the gate, every internal report improved, and nothing about the driver's day changed. Compare gate-in with check-in timestamps: a widening gap is displacement rather than improvement.

The decision that actually removes the coupling is live load versus drop-and-hook. Live load ties the driver's time to the dock's schedule; a trailer swap decouples them. Every detention charge exists because of that coupling, and where volume supports a trailer pool no scheduling improvement substitutes for it.

And the cost that matters is not the hourly rate. Waiting consumes the driver's 14-hour federal window, which does not stop for anything — so a long wait costs the delivery, the next load, or the reset.

Most of the damage, though, is not the waiting at all. It is the delay in telling anyone about it: a wait reported at hour two leaves options, and the same wait reported at hour four is a failure somebody else has to absorb. Measuring the time from delay onset to first notification separates an information problem from a facility one, and very few operations know that number.