Detention charges are one of the few line items in freight where the money is genuinely recoverable, and most operators never try. The invoice arrives, it looks routine, someone approves it. Industry audits repeatedly find that roughly one in five detention invoices contains a billing error — which means a meaningful share of what gets paid every month did not need to be paid at all.

The reason those errors survive is not that carriers are dishonest. It is that the two sides are measuring different things, and only one side brought a stopwatch.

Where the clock actually starts

Most detention disputes come down to a single question: when did the truck arrive? Carriers commonly start the detention clock from the driver's check-in call. That call might happen in the queue outside the gate, in the receiving office ten minutes after parking, or not until the driver has already been waiting an hour and decides it is worth reporting.

None of those moments is the arrival time. They are all approximations of it, generated by a person with other things to do.

A geofence crossing is different. It is a timestamp produced by the vehicle entering a defined boundary, recorded without anyone deciding to record it. When the invoice says free time started at 08:20 and the geofence says the truck did not cross the boundary until 10:25, that gap is not a matter of opinion.

The four records that settle an argument

A detention dispute is won on documentation, not on tone. These are the records worth having before you send the first email:

Facility gate logs are worth requesting too, where the site keeps them. They rarely arrive quickly, but a second independent source turns a disagreement into an arithmetic problem.

Why timestamps changed the balance

Under the Federal Maritime Commission's billing rule, invoices on US trades must state when free time started and ended, within defined timelines. An invoice that fails to meet the requirement can be challenged on that basis alone, before anyone argues about the underlying facts.

This matters more than it sounds. It means a dispute backed by clean timestamped data is not a complaint — it is a documented discrepancy against a stated regulatory standard. Carriers settle those differently than they settle angry emails.

The dispute window is not open indefinitely, though. Miss the mitigation-request period and that avenue generally closes regardless of how good your evidence is. Which is the practical argument for capturing this data automatically rather than assembling it after an invoice raises eyebrows: by the time a charge looks wrong, reconstruction is already harder and the clock is already running.

Detention is a symptom worth reading

Recovering incorrect charges is the immediate return. The longer-term value is in what the pattern shows you.

Dwell data aggregated across facilities tells you which receivers consistently hold your equipment, which shifts are slower than others, and which lanes carry a hidden cost that never appears in the rate. That is the information you need going into a rate negotiation, and it is far more persuasive than a general impression that a particular customer is difficult.

Some operators now share that data openly with shippers in the form of carrier scorecards — dwell times, on-time performance, detention frequency, visible to both sides. It sounds adversarial and usually turns out to be the opposite. Most facilities do not know they are slow. Shown the numbers, a fair proportion fix it.

Getting started without a project

You do not need a systems overhaul to begin. You need arrival and departure timestamps that nobody typed in, and delivery confirmation captured at the dock rather than at the end of the week.

NGL FreightMate® records both as a by-product of normal work. The driver runs the load as usual; the timeline assembles itself. When an invoice looks wrong three weeks later, the evidence already exists and is already timestamped.

If your operation spans several vehicle types, the same principle applies across all of them — see running a mixed fleet without running three dispatch systems.

That is the whole trick. Not arguing better — just arriving at the argument with a record that was written down at the time.

Talk to us about what this looks like on your lanes.