Carrier Detention Tracking Log

This template records the timing milestones that matter in a detention or demurrage review: arrival, check-in, dock assignment, service start, service end, and departure. It also captures the reason for any delay and whether a charge dispute is being requested. Use it when you need a consistent record to compare against appointment windows or carrier billing.

Complete it as close to the event as possible, ideally during the receiving or shipping shift while the details are still fresh. The arrival, dock assignment, and departure fields are time-sensitive, so delaying entry increases the risk of missing or conflicting timestamps. If your operation uses paper sign-in sheets or yard notes, transfer the data into this log the same day.

The person who actually observes the handoff should complete it, such as a dock supervisor, gate clerk, warehouse lead, or transportation coordinator. If one person records arrival and another records departure, the form should still show who submitted the entry and how they can be reached. That makes follow-up easier when a carrier asks for clarification.

Yes. The template is built to preserve the facts that usually decide a dispute: when the carrier arrived, when a dock was assigned, when service started, and when the trailer left. The exception and supporting-documents fields help you attach notes, photos, appointment records, or gate logs so the charge review has context. It does not replace your contract terms, but it gives you a cleaner evidence trail.

The biggest mistakes are leaving times blank, using vague wait reasons, and recording only one timestamp instead of the full sequence. Another common issue is marking every field required, which slows down entry and leads to inaccurate data. Use conditional logic for exception details and other reasons so people only see the fields that apply.

Yes. You can rename appointment fields, add carrier-specific references, or change the wait-reason list to match your yard and dock workflow. If your site uses check-in kiosks, ELD data, or a TMS, map those fields to the same timing milestones so the log stays consistent across systems. Keep the form focused on the minimum necessary data.

Attach only the documents needed to explain the exception or support the dispute, such as gate logs, appointment confirmations, photos, or email threads. Avoid collecting unrelated PII or broad document uploads when a single timestamp or note will do. If your process allows it, make the upload field optional and explain what happens after submission.

A structured log is easier to search, compare, and audit than scattered emails or ad hoc spreadsheets. It also standardizes the fields needed to calculate detention minutes and document why a delay occurred. That reduces back-and-forth when operations, billing, and carrier relations need the same record.