Detention and Demurrage Tracking Log

This template covers the core events needed to calculate or challenge detention and demurrage charges: driver arrival, check-in, load or unload start, release time, free-time allowance, and any charge outcome. It is designed to create a clear timeline, not to replace your carrier invoice or TMS. Use it as the operational record that ties a shipment stop to a specific dwell period. If you need to prove whether a delay was blocking or non-blocking, this log gives you the evidence trail.

Use it any time a shipment can incur time-based accessorial charges at a warehouse, yard, port, or customer dock. It is especially useful when free-time windows are tight, handoffs are frequent, or disputes happen after the invoice arrives. If your operation rarely sees dwell beyond the allowance, a lighter exception log may be enough. If charges are common or contested, this template should be part of the standard receiving or dispatch workflow.

The DRI is usually a dock supervisor, transportation coordinator, or warehouse lead who can verify timestamps and collect supporting notes. The person entering the log should be close to the event, because delayed entry is one of the main reasons dispute records fail. Finance or logistics can review the log later for charge validation, but they should not be the only owners of the source data. If multiple sites use it, assign one owner per location to keep the timestamps consistent.

Update it per stop or per load, as soon as the key milestone happens. At minimum, capture check-in, start of service, end of service, and departure in the same shift so the dwell calculation is not reconstructed from memory. If your operation runs around the clock, make the recurrence continuous rather than daily batch entry. A delayed log is still useful for trend review, but it is much weaker for a charge dispute.

The biggest mistake is recording only the final charge without the underlying timestamps and free-time allowance. Another common issue is mixing up blocking delays caused by the facility with non-blocking delays caused by the carrier or appointment miss. Teams also forget to note proof, such as gate stamps, signed receipts, or detention notices, which makes disputes harder to win. Finally, avoid vague notes like 'waited a long time' and use exact times and a clear verification step instead.

Yes, and it should be. Some sites need appointment number, trailer number, seal status, or yard location, while others need port terminal, container number, or carrier reference. You can also add fields for grace period, rate basis, dispute status, and DRI. Keep the checklist items atomic so each field answers one question and can be verified independently.

Email threads and ad hoc spreadsheets usually lose the timeline, the owner, or the proof needed to validate a charge. This template standardizes the record so every stop is captured the same way, which makes review and escalation much faster. It also helps separate normal operational delays from chargeable delays. If you already use a TMS or ERP, this log can sit alongside those systems as the operational source of truth for exceptions.

Yes. It pairs well with a TMS, WMS, appointment scheduling system, document storage, or a finance workflow for dispute review. You can attach photos, signed paperwork, gate logs, or carrier notices as verification evidence. Many teams also link it to a Kanban board so unresolved disputes stay visible until closed. The key is to keep the log as the structured record and use integrations for supporting documents and follow-up.