Container Detention Guide for Haulage Operators
A container detention guide for haulage operators: reduce free-time risk, control returns, capture exceptions and protect invoice margins daily.
A missed empty return can turn an otherwise profitable move into a costly exception. This container detention guide is for haulage operators who need to control free time, act before charges build and retain the evidence needed to recover costs from the right party.
Detention is not simply a port or shipping-line issue. It is an operational workflow issue. The charge is usually created by a gap between collection, unloading, empty return and the information shared between planners, drivers, customers and the back office. When those events sit in separate inboxes, spreadsheets or paper PODs, the deadline is easy to miss.
What container detention means in practice
Container detention is a charge raised when a shipping line’s container is kept beyond the agreed free-time period outside the terminal. For a road transport operator, the clock commonly starts once the laden container is collected or made available for collection, depending on the line’s terms. It stops when the empty is returned to the nominated depot and the return is recorded.
The detail matters. Free time can differ by shipping line, customer agreement, container type, trade lane, depot and booking. A planner cannot safely rely on a standard rule such as seven days for every job. The agreed date and time, the nominated return location and the return acceptance conditions need to be attached to the specific container move.
Detention is often confused with demurrage. Demurrage generally applies while the container remains inside the terminal after free time expires. Detention generally applies once it has left. The terms can be combined in a carrier invoice or used differently across contracts, so operators should read the tariff and customer instruction rather than assume the label determines liability.
Why detention charges escalate so quickly
Shipping-line tariffs are designed to encourage equipment circulation. Charges may rise by band after the free period expires, meaning a delay of one day can become a much larger cost if it extends over a weekend, a rejected return or a depot closure.
The operational causes are familiar: an import delivery is not booked promptly, the consignee cannot unload, a driver arrives at a depot with no acceptance slot, a return reference is missing, or the customer changes the delivery plan without considering free time. None of these is unusual. The problem is failing to identify the risk early enough to choose a lower-cost response.
For example, if an empty must be returned on Friday but unloading is arranged for late Thursday, there is little recovery time if the site delays the vehicle or the depot rejects the container. A planner may decide to move the delivery forward, arrange a pre-booked return slot, request an extension or warn the customer that waiting time and detention exposure are now likely. The right choice depends on the commercial agreement and the cost of each option.
The container detention guide: control the job from collection to return
The most reliable approach is to treat detention as a milestone-led workflow, not a diary reminder.
1. Capture free time at job creation
Create the transport job with the container number, shipping line, collection point, delivery address, nominated empty depot, free-time expiry, reference numbers and agreed customer responsibility. If the expiry is still unconfirmed, flag it as an exception rather than leaving the field blank.
A date alone is not always enough. Record the relevant cut-off time and source of the information. A free-time date copied from an email without the tariff reference or line confirmation can become difficult to defend later, particularly when a customer disputes a recharged cost.
2. Plan delivery backwards from the empty return
Plan the move around the latest safe return, not only the earliest delivery appointment. Build in practical allowance for unloading, traffic, driver hours, depot opening times, booking availability and the possibility of a failed return.
This is where transport planning needs judgement. A low-rate delivery that leaves no room to return the empty may not be commercially sensible. Equally, sending a vehicle too early can create avoidable waiting time. Good planning makes the trade-off visible before the container is on the road.
3. Give the driver a clear return instruction
Drivers need the right information at the point of execution: the depot location, return booking or acceptance reference, equipment requirements and what to do if the depot refuses the box. “Return empty” is not a usable instruction when the depot has multiple lanes, restricted hours or a booking rule.
The driver should also know what evidence to capture. A clean empty return receipt is the strongest proof that detention has stopped. If the return fails, capture the rejection reason, time, location and any supporting photograph or message. That record supports both escalation and recovery.
4. Monitor jobs before they become urgent
Use status-based alerts rather than relying on someone to inspect every container manually. A practical workflow highlights containers approaching expiry, containers delivered but not yet returned, and returns that have been attempted but not completed.
The most useful alert is not always “free time expires today”. By then, options may be limited. A warning two or three working days before expiry allows the planner to secure a depot slot, chase unloading, reallocate work or notify the customer of the exposure.
5. Close the job with evidence and a financial decision
Once the empty is returned, attach the receipt and record the actual return time. If charges have been incurred, do not leave the job commercially unresolved. Decide whether the cost is absorbed, disputed with the shipping line or recharged to the customer under the agreed terms.
That decision should flow directly into invoicing. A detention recharge that is identified weeks after the main transport invoice creates unnecessary credit-control work and invites dispute. Where liability is clear, the charge, evidence and explanation should be available to the accounts team while the job is still current.
Set clear ownership across the operation
Detention control breaks down when everyone can see the issue but nobody owns the next action. The planner may believe the customer is arranging unloading. The driver may assume the office has booked the return. The back office may only discover the charge when the shipping-line invoice arrives.
Assign operational ownership at each stage. Planning owns free-time capture and pre-expiry review. The driver owns timely status updates and return evidence. Customer service or the account manager owns escalation where the consignee causes delay. Finance owns correct recharge and dispute records. In a smaller operator, one person may perform several roles, but the ownership points should remain explicit.
A useful exception record should contain at least four elements:
- the container number, shipping line and confirmed free-time expiry;
- the current job status and the action required;
- the party responsible for removing the blockage; and
- time-stamped evidence of calls, emails, depot rejection or customer instruction.
This creates a defensible audit trail without adding a separate administrative process.
How to recharge detention without damaging customer relationships
Not every detention cost should be passed on automatically. The commercial answer depends on the transport terms, who controlled the delay and whether the operator warned the customer in time. If a customer held a container for three extra days after being notified of the deadline, a documented recharge is reasonable. If the haulage operator missed a booked depot slot, the case is weaker.
Clarity before the move matters more than forceful wording after it. Customer rate agreements should state whether detention, demurrage, storage, aborted journeys, waiting time and re-delivery are excluded from the base rate. They should also explain the notification process and the evidence provided with a recharge.
When a charge is disputed, present the timeline rather than a vague explanation. Show the collection date, free-time expiry, delivery appointment, communications, attempted return and final return receipt. A factual timeline is easier for both the customer and the shipping line to assess.
Use a connected TMS to prevent blind spots
A container haulage TMS should connect the planning view, jobs grid, driver updates, POD or delivery notes, return documents and invoicing record. The goal is not to create more alerts. It is to make the next operational action obvious and ensure the commercial record follows the job.
For example, a planner can see a delivered container with no empty-return confirmation and act before the deadline. Once the driver uploads a receipt, the job status updates and the evidence is available to the back office. If an exception leads to a customer recharge, the invoice can be raised with the supporting record already attached to the job.
AI-assisted workflow can help prioritise the jobs that need attention, particularly when planners are handling a high volume of containers with different free-time rules. It should support operational decisions, not replace verification of carrier terms, depot requirements or customer instructions. Logivo is built around this connected execution model, bringing planning, proof of delivery, documentation and invoicing into one transport workflow.
Detention will never disappear entirely. Ports become congested, depots reject equipment and customers change plans. But when free time, job status, return evidence and invoicing sit in one controlled process, a detention charge becomes an exception to manage rather than an unpleasant surprise discovered after margin has gone.