Northeast Freight Time one clock, four readings

The Two-Hour Convention

Two hours of free time before detention accrues is the most widely assumed number in road freight. Drivers cite it, receivers cite it, rate confirmations reproduce it, and a substantial share of people on both sides believe it comes from somewhere official. For a software-oriented reference on recording work time, this material.

It does not. For broader transportation and measurement context, see Reuters.

What it actually is

A convention. FMCSA records that there is no standard definition of detention time and that industry has typically treated dwell exceeding two hours as the point at which detention occurs.

That is a description of practice, not a rule. It is not in regulation, no agency has endorsed it as an allowance, and nothing in the federal research derives it.

And it is not a finding about loading. Nobody measured how long loading takes and concluded that two hours covers it. Average dwell across fleets runs around 1 hour 54 minutes, with refrigerated at 3 hours 16 minutes — which means the convention sits just above the general average and well below the reefer one. A single figure cannot be right for both.

Why it stuck anyway

It is round. Negotiable numbers gravitate to round ones, and two is rounder than ninety minutes.

It is defensible from both directions. Long enough that a receiver can call it generous; short enough that a carrier can call it minimal. Neither side wins the argument, which is exactly what makes a default survive.

It fits on a rate confirmation. "Detention after 2 hours" is four words, and the alternative — defining start event, stop event, tolerance and authoritative record — is four sentences nobody wanted to write.

And it predates the measurement. The convention was established before anyone could measure dwell precisely, and once established it did not need to justify itself.

What treating it as a rule costs

Carriers under-recover on slow commodities. A reefer load with temperature verification and a seal check routinely exceeds two hours as normal operation, not as detention. Free time set at the general average penalises the operation that takes longest for legitimate reasons.

Receivers over-concede on fast ones. A drop-and-hook that takes twenty minutes does not need a two-hour allowance, and giving one away costs nothing until the day it is used as a benchmark for something else.

And both sides stop negotiating. A number believed to be a rule is not discussed. Two parties who each think the other has no discretion will reproduce the default indefinitely.

What to do instead

Set free time to the operation. Thirty minutes for drop-and-hook, an hour for a straightforward dry van, three for a live-load reefer with a seal and temperature check. Free time should approximate the honest work, not a market-wide average.

Then set the rate to the cost of exceeding it. These are separate levers and they are usually conflated. A generous allowance with a firm rate is a different arrangement from a tight allowance with a soft one, and they suit different lanes.

And say when the clock starts, because free time without a start event is not a term at all.

What to say when someone cites it as a rule

Neither aggressively nor as a gotcha. Simply:

Two hours is the common default rather than a regulation — there is no standard definition of detention, and FMCSA says so. Given the work involved here, does two hours actually match what this load takes?

That converts an assertion into a question about the operation, which is where it belongs, and it is usually the first time either party has considered it.

The one advantage of the gap

Because the convention has no authority, everything about it is available to negotiate: the allowance, the rate, the start event, the notification requirement, and what happens when a record is missing.

A party that knows this and drafts the terms has a substantial advantage over one that assumes the number is fixed. Most people on both sides assume exactly that, and the mechanism that produced it is operating on other terms right now.

The short version