Warehouse Carrier Detention Audit

It covers the full detention event chain: shipment identification, gate arrival, dock-in, loading, departure, free-time calculation, and reason validation. The template is designed to compare carrier claims or invoices against warehouse records such as gate logs, yard check-in, dispatch records, and appointment schedules. It also captures whether any waiver or exception was approved. Use it when you need a documented basis to accept, dispute, or adjust detention charges.

Run it after a detention charge is received, during monthly freight audit review, or whenever a carrier disputes a detention invoice. It is also useful for internal root-cause review after recurring delays at a dock or facility. If your warehouse uses appointment windows or free-time rules, this audit should be part of the charge validation workflow. It is not a live dock operations checklist.

A transportation analyst, logistics coordinator, warehouse supervisor, or freight audit specialist usually completes it. The reviewer should have access to appointment records, gate logs, dock schedules, and any exception approvals. If the detention reason involves warehouse operations, a dock lead or operations manager should validate the narrative and supporting evidence. The key is that the reviewer can verify the records, not just read the invoice.

It creates a clear chain of evidence from arrival to departure so you can see whether the billed detention time is actually eligible. That makes it easier to identify mismatched timestamps, missing approvals, or unsupported reason codes. When a carrier disputes a charge, the audit record shows what was measured, what policy applied, and what documentation supported the decision. That reduces back-and-forth and helps standardize outcomes.

Attach or reference the gate log, yard check-in record, appointment schedule, dock door assignment, loading timestamps, dispatch or gate-out record, and any waiver or exception approval. If the detention reason cites a warehouse delay, include the operational record that supports it, such as labor shortage notes, equipment downtime, or dock congestion logs. The goal is to make the audit traceable without requiring someone to hunt for source documents later. If a record is missing, that gap should be noted as a deficiency.

Common mistakes include using the carrier's invoice as the only source, failing to reconcile arrival time with gate logs, and calculating free-time incorrectly. Another frequent issue is accepting a reason code without a narrative that explains the actual delay. Teams also miss approved exceptions because the waiver is stored outside the audit file. This template helps prevent those gaps by forcing each timing and approval point to be checked.

Yes. You can adjust the free-time rules, billing thresholds, reason codes, and required evidence fields to match your carrier contracts or internal policy. Some warehouses will want separate logic for live loads, drop trailers, or refrigerated freight. You can also add approval fields for finance, transportation, or operations depending on who owns the dispute decision. The structure stays the same even when the policy details change.

Ad hoc review usually leaves gaps because each person checks different records and uses different timing assumptions. This template standardizes the sequence, the evidence required, and the decision points, so the audit is repeatable. It also makes it easier to trend recurring causes such as late dock assignment or delayed unloading. That consistency is especially useful when multiple sites or reviewers handle detention claims.