Container Detention Prevention Guide for Hauliers
This container detention prevention guide helps hauliers control free time, appointments, PODs and billing with disciplined, visible transport workflows daily.
A container can be delivered on time and still become an unprofitable job. The problem is often not the road movement itself, but the period after collection: free time expires, the empty is not returned, and detention charges arrive after the operational window has closed. This container detention prevention guide sets out how hauliers can make that risk visible early and manage it through daily transport workflows.
Detention is rarely caused by one careless person or one missed email. It is usually the result of disconnected information: a planner cannot see the last free day, a driver has no confirmed empty return slot, a customer delays unloading, or the office receives delivery paperwork too late to challenge a charge. Prevention needs a process that connects each of those points.
Start with a clear view of the detention clock
Detention generally applies when a container remains outside the terminal beyond the carrier's agreed free time. The exact rules vary by shipping line, equipment type, port, customer agreement and movement. Demurrage, by comparison, normally relates to containers remaining within the terminal. The distinction matters because the responsible party, evidence required and available actions may differ.
For every import collection, the operations team should know four facts before the job is dispatched: the collection date, the last free day, the nominated empty return location, and the return appointment requirement. If any of these details are unknown, the job is not operationally ready, even if the collection appointment is confirmed.
Do not rely on a planner remembering dates from carrier portals or email threads. Record the critical dates against the transport job, where dispatch, customer service and accounts can see them. A jobs grid should make containers approaching their last free day easy to identify, rather than leaving the team to search for risks after a charge appears.
Free time is a planning constraint, not an accounts query
Many operators only investigate detention once an invoice lands. By then, the empty may have been sitting at a customer site for days and the evidence trail may be weak. Treat free time in the same way as a delivery appointment or a driver hours constraint: it affects the plan from the moment the container is collected.
This changes the conversation with customers. Instead of asking vaguely when the container may be available, the planner can confirm the latest practical date for unloading and collection. Where the customer needs the container longer, the commercial decision can be made upfront. They may accept the charge, arrange an alternative solution, or agree a timed unload. The key is that responsibility is visible before costs accumulate.
Build detention controls into the job lifecycle
Effective prevention does not require a separate detention team. It requires a consistent workflow from booking to empty return. Each handover needs a named owner and a visible status.
At planning stage, validate the container number, release status, free-time expiry, delivery address, delivery booking and intended empty return depot. It is also worth checking whether the nominated depot is accepting returns and whether the container type has restrictions. An empty return plan that exists only in principle is not a plan.
At collection, capture the interchange condition and any equipment damage or seal issues. These can delay the next step and may affect who carries responsibility. At delivery, obtain a time-stamped POD that records arrival, completion and any detention at the customer premises. This is valuable operational data, not simply paperwork for invoicing.
Once the container is empty, the job should move into a distinct return-to-depot stage. Too often, a delivery is marked complete while the container remains on the road operation's liability clock. Keeping the return leg visible prevents the empty from disappearing into a vague follow-up list.
A practical status sequence might include planned, collected, at customer, empty ready, return booked, returned and interchange received. The labels can vary, but the workflow should show exactly which containers need intervention today.
Make exceptions visible before they become charges
No schedule survives every port delay, failed delivery, closed depot or customer request. The objective is not to eliminate exceptions. It is to identify them while choices remain.
Set exception rules around the last free day. For example, flag containers that have not been delivered within a defined period after collection, empties still at the customer one day before expiry, and returns without a confirmed appointment. The appropriate lead time depends on local congestion and depot availability. In busy periods, waiting until the last free day is too late.
Daily exception review works best when it is short and operational. A planner should be able to answer: which containers expire next, what is blocking each return, who owns the next action, and when will it be checked again? A long weekly report is less useful than a focused morning view of genuine risk.
The common blockers are familiar:
- the consignee has not unloaded or cannot release the container;
- the return depot has no suitable appointment or is refusing equipment;
- the driver has completed delivery but the empty collection has not been planned;
- documentation or release information is incomplete; and
- responsibility for charges has not been agreed with the customer.
Each blocker needs a different response. A depot availability issue may require checking an alternative nominated location with the shipping line. A customer delay may need a documented escalation and an agreed charge position. An operational planning gap needs reassignment, not another email reminder.
Use POD and timestamps to protect the recovery process
Prevention will reduce charges, but it will not remove every legitimate dispute. Ports, depots, shipping lines and customers can all introduce delays outside the haulier's control. When that happens, accurate evidence determines whether a charge can be challenged or passed on correctly.
Capture delivery and collection timestamps through the same system used to manage the job. Include signed PODs, delivery notes, customer communications, return booking confirmations and empty interchange receipts. Store them against the container movement rather than across individual inboxes and paper files.
This has two benefits. First, dispatch can see whether a container is genuinely ready for collection. Second, back-office teams can validate detention invoices quickly. If a customer held the container beyond the agreed period, the supporting record is already attached to the job. If a return depot refused the empty or a booking was unavailable, the timeline can support a dispute with the relevant party.
There is a trade-off here. Asking drivers to enter excessive information will slow them down and reduce compliance. Focus mobile capture on the proof that matters: arrival and completion times, POD, equipment condition where relevant, and return interchange. The office can add carrier correspondence and booking data without turning every driver task into an admin exercise.
Align commercial terms with operational reality
A strong detention process can still fail if customer terms are vague. Quotes and service agreements should make clear what is included, what free time is assumed, and how charges caused by delayed unloading or non-availability will be handled. This is especially important where the haulier is arranging transport but does not control the customer site.
Avoid treating all containers as identical. Free time may differ by line and trade lane, while delivery locations may have very different unloading capabilities. A regular consignee with a reliable unloading slot presents a different risk from a site that only accepts containers on limited days. Planning and pricing should reflect that difference.
When a customer requests extended use of a container, record the agreement against the job. The team should not have to reconstruct a verbal instruction when accounts asks why detention has been incurred. Clear terms protect the customer relationship as well as the margin.
Connect planning, operations and billing in one record
Fragmented systems create detention risk because each team sees only part of the movement. Planning knows the delivery booking. The driver holds the POD. Customer service receives the request to delay collection. Accounts sees the carrier invoice weeks later. No one has the full timeline when it matters.
A container haulage TMS should connect the job plan, status updates, delivery documentation and invoicing evidence in one operational record. That means a dispatcher can act on an approaching expiry date, while the back office can use the same job data to validate a charge or invoice the customer without rekeying information.
Logivo supports this type of connected workflow through transport planning, job management, digital POD and invoicing. The value is not simply having more data. It is giving the right team the relevant operational detail before a preventable charge becomes a margin problem.
Detention prevention becomes reliable when the empty return is treated as part of the original transport job, not an afterthought once delivery is complete. Give every container a visible clock, an owner, a return plan and a documented trail. That discipline gives planners more control, accounts cleaner evidence and customers clearer expectations when the pressure is on.