Detention and waiting time: charging for the hours you already lost

Two hours at a loading dock feels like nothing until it is counted across a month. A driver waiting because the warehouse is running behind, because the paperwork is not ready, or because someone else’s truck is unloading first is a truck not earning anywhere else that day. Most small carriers know this cost exists and swallow it anyway — not because it is small, but because charging for it usually means an argument they would rather not have, backed by evidence they do not actually hold.

The free time nobody wrote down

Ask most dispatchers where the line sits between “the driver is waiting” and “the driver is late” and the honest answer is a feeling, not a number. Detention time only becomes billable if a free-time allowance and a rate were agreed before the truck arrived — raised after the fact, it looks like an invented charge rather than a contracted one, and the customer treats it that way. The agreement does not have to be elaborate: a stated number of minutes free per stop, a rate per hour or part-hour beyond it, and somewhere it lives — a rate card, a framework agreement, a line on the booking confirmation. What matters is that it exists before the wait does, because a term introduced retroactively is not a term, it is a negotiating position, and negotiating positions lose to whichever side has less patience.

Evidence that outlasts the argument

Even with a contracted rate, detention dies at the point where it becomes “the driver says” against “the warehouse says.” A driver’s own note of arrival time, written from memory at the end of a long day, does not survive a customer who disputes it — and a customer who has never been charged detention before will often dispute the first invoice on principle, whether or not the hours are real. The fix is not asking drivers to be more careful; it is not asking them to remember anything at all. An arrival timestamp and a departure timestamp, captured as a by-product of the stop being worked rather than as a separate thing to log, are credible precisely because nobody had to decide in the moment to record them. A one-tap status update a driver is already making — to say a stop has been reached, and later that it has been left — produces the same two timestamps a detention claim needs, for a reason that has nothing to do with billing, on every stop, not just the ones that turn into a dispute.

That matters because most stops never will. Building a separate detention-logging habit for the rare stop that runs two hours over trains drivers to skip it on the one day it would have mattered, because on every other day it felt like paperwork for nothing. Evidence that rides on top of the status update every stop already generates exists whether or not anyone predicted the need for it in advance.

Invoicing it without becoming the carrier who nickel-and-dimes

The account-souring version of detention billing is the one dispatchers actually fear, and the fear is not unfounded: a surprise line item on an invoice, unexplained and unagreed, reads as opportunism even when the hours are genuine. The version that holds is contracted, itemised, and consistent — the same rate applied the same way every time it is triggered, appearing as its own line next to the freight charge rather than folded invisibly into a bigger total, with the timestamps that justify it available if asked rather than volunteered as an unrequested wall of proof. A customer who sees one clearly-labelled detention charge, at the rate they agreed to, referencing hours they can check against their own gate log, has very little to argue with. A customer who sees an unexplained higher total has every reason to push back — and every reason to remember the carrier as difficult the next time a quote is compared against someone else’s.

Consistency matters as much as itemisation. A carrier that charges detention on the customer who complains and quietly eats it for the customer who does not is not enforcing a policy, it is picking fights selectively — and sooner or later the charged customer notices they are the only one paying it. Applying the same free-time allowance and rate to every account, backed by the same evidence trail behind every charge, is what turns detention from a confrontation into an unremarkable line item customers stop querying, because they have seen it often enough to know it is not personal.

Where navichain stands

Charging for detention starts with the two things a claim actually needs: a rate agreed before the wait, and timestamps nobody had to remember to write down. navichain prices services and price sheets by weight, distance, time or geographic zone, so a detention or waiting-time rate sits alongside the freight rate rather than as an improvised add-on. The driver app’s one-tap status updates for today’s stops already produce the arrival and departure record a detention line depends on, and signatures, photos and failed-delivery reasons captured on the spot sit on the same stop. Invoicing bills a booking, merges several, or covers a whole period in one pass, with a field-level audit trail on the records that matter behind every figure — so the detention line on an invoice is backed by the same timestamps the customer could check themselves, not by a driver’s memory of a bad afternoon.