Detention Charges: Stop Losing Time and Margin
Detention charges erode haulage margins when vehicles wait. Learn how to set terms, capture proof and invoice delay time accurately on every delayed job.
A vehicle arrives on time, checks in correctly and then sits for three hours waiting for a bay, paperwork or a container release. The transport job may look complete on the plan, but detention charges can decide whether it made money.
For haulage and container transport operators, waiting time is not a minor inconvenience. It ties up a vehicle, driver and planned capacity that could have been used on the next job. When that time is not recorded, agreed and billed, the operator absorbs a cost created elsewhere in the supply chain.
What are detention charges?
Detention charges are fees applied when a vehicle, driver or equipment is held beyond an agreed free waiting period at a collection or delivery point. In road freight, they are commonly charged by a carrier to a customer, shipper, consignee or site where excessive waiting occurred.
The commercial logic is straightforward. A quoted transport rate assumes that the vehicle can complete a job within a reasonable operating window. If a site delays that vehicle for reasons outside the carrier's control, the carrier loses productive time and may incur overtime, missed slots, driver hours issues and re-planning work.
The detail depends on the contract. A customer may allow 30 minutes, one hour or two hours of free time. Charges may then apply in 15-minute, 30-minute or hourly increments. Some operators use a fixed fee after the free period; others charge a rate that reflects the vehicle type, driver cost and lost utilisation.
For container haulage, terminology can become confusing. Carrier detention charges for a lorry waiting at a terminal or customer site are different from shipping line detention, which often relates to keeping a container or equipment beyond an agreed period. Demurrage usually concerns containers remaining at a port or terminal. These costs can overlap operationally, but they should be tracked separately in billing and job records.
Why waiting time damages more than one job
The obvious cost is the driver's paid time. The larger cost is the disruption that follows.
A delayed collection can make a driver late for a delivery appointment. A late delivery can trigger another wait, a failed delivery or an out-of-hours charge. Dispatchers then spend time calling sites, moving work between vehicles and updating customers. If the driver approaches their legal driving or working-time limit, the problem may require an overnight stop or a next-day recovery plan.
This is why detention should not be treated as an occasional admin charge. It is an operational exception that affects capacity, service and margin. A business that plans 10 jobs per vehicle per week but loses several hours to uncharged waits may need extra fleet capacity simply to deliver the same volume.
The challenge is that customers often dispute waiting charges when the evidence is weak. A handwritten note saying “held up at site” rarely answers the questions that matter: when did the vehicle arrive, when was it ready to load or unload, who caused the delay and when did it leave?
Set detention terms before the job moves
The best time to agree detention charges is during onboarding, quoting or contract renewal, not after a dispute. Terms should be clear enough for a transport planner, driver, accounts team and customer contact to interpret the same way.
Define the free waiting period, the point at which the clock starts and the charging increment. For example, does time begin at the booked slot, at gate check-in, or when the driver reports ready at the loading point? Does it stop when loading ends, when paperwork is signed, or when the vehicle exits the site?
These distinctions matter. A driver might check in at 09:55 for a 10:00 booking but wait at security until 10:30. If the agreement says detention begins at the booked slot, that delay is billable sooner than if it starts only when the driver reaches the bay.
Terms should also state the exceptions. Delays caused by the carrier, such as arriving late, missing required paperwork or presenting the wrong equipment, should not be charged to the customer. Equally, a site closure, unavailable stock, terminal congestion or a customer-requested hold should not be allowed to disappear into a standard transport rate.
For regular work, include detention rules in the customer rate card or service agreement. For ad hoc work, make them visible in the quote confirmation or job acceptance. Commercial teams should avoid vague phrases such as “waiting time may apply”. A specific rate and trigger create fewer arguments later.
Capture proof while the driver is on site
Detention billing succeeds or fails on the quality of the timeline. The driver should not be asked to recreate a three-hour delay from memory at the end of a shift.
A practical record needs arrival time, check-in time where relevant, bay or loading start time, completion time, departure time and a short delay reason. It should also identify the site and job reference. Where possible, capture supporting evidence such as gate tickets, site-issued timestamps, booking references, messages from the transport office or a signed note from the customer.
Proof of delivery processes are useful here, but a POD alone may not show when a vehicle first arrived. Operators need job events that record the full stop, not just the final delivery signature. Mobile updates from the driver, linked to the live job, reduce the risk of missing information and give dispatchers visibility before the delay becomes costly.
Driver adoption is essential. The process must be quick enough to use in a busy yard or at a congested terminal. Asking drivers to enter long narratives is unrealistic. A simple event flow - arrived, waiting, loading started, complete - combined with a selectable reason code is more likely to be completed accurately.
Turn delay data into an invoiceable job item
Too many detention claims are lost between transport and accounts. The planner knows that the vehicle waited, but the invoice is raised from a basic job record that contains only the agreed transport rate. By the time somebody notices, the detail has gone cold.
Build detention into the job workflow. When waiting exceeds the agreed free period, the system should flag the exception and calculate the charge using the customer's terms. The planner or supervisor can then review whether the delay is valid, add supporting notes and approve it before invoicing.
This is where connected transport management software earns its place. A jobs grid that brings together planned times, driver updates, PODs, delivery notes and chargeable extras gives operations and finance one version of the job. Logivo can help operators keep those job events and invoice-ready records connected, rather than relying on a planner's spreadsheet or a separate email trail.
Automation should support judgement, not remove it. A late departure does not automatically prove customer-caused detention. The transport team still needs to confirm the booked time, actual arrival and reason for delay. However, automatic alerts and rate rules prevent legitimate charges from being overlooked.
Make detention charges easier for customers to accept
A clear invoice line is less likely to be challenged than a bundled “sundries” amount. Show the job reference, site, agreed free time, actual waiting period, billable period, rate and total. Attach or retain the relevant proof so that accounts staff can answer a query without chasing the driver weeks later.
Consistency matters as much as firmness. If an operator bills one customer for 45 minutes but waives identical delays for another without a commercial reason, it becomes difficult to defend the policy. There will be strategic cases where a charge is waived - perhaps during a service recovery or for a high-value contract - but that decision should be visible and deliberate.
It also helps to share recurring delay data with customers. A monthly review showing average wait time by site, number of delayed jobs and cost can shift the conversation from individual invoice disputes to practical improvement. The customer may be able to improve booking discipline, staffing, paperwork readiness or yard access. The carrier gains more reliable vehicle turnarounds, even if the charge itself falls over time.
Use the data to protect future capacity
Detention reporting should influence planning and pricing. If a site regularly holds vehicles for two hours, a standard one-hour collection slot is not an accurate planning assumption. Planners may need to schedule wider buffers, avoid tight follow-on bookings or allocate a different vehicle window.
Commercially, persistent delays may justify a revised rate, a different free-time allowance or a requirement for booked slots. There is a trade-off: a tougher detention policy can protect margin but may create friction with a customer that sees waiting as part of the service. The right approach depends on job volume, relationship value, alternative capacity and whether the customer is willing to fix the source of the delay.
The key is to make the cost visible. When waiting time is recorded at job level, reviewed by operations and passed accurately into invoicing, detention stops being an accepted leak in the business. It becomes a fact-based conversation about who controls the delay and what it costs to keep a vehicle standing still.