Detention and Demurrage Tracking Log
Track driver check-in, dwell time, free-time windows, and charge disputes in one detention and demurrage log. Use it to prove where delays happened and whether accessorial charges are valid.
Trusted by frontline teams 15 years of frontline software
Built for: Freight And Logistics · Warehousing · Port Operations · Third Party Logistics · Manufacturing
Overview
This detention and demurrage tracking log is a task template for recording the timing details that determine whether accessorial charges are valid. It captures driver check-in, dock arrival, loading or unloading start, release, check-out, free-time allowance, and the point where detention or demurrage begins. Use it when a shipment may incur wait-time charges, when a customer facility is known for long dwell times, or when your team needs evidence before approving an invoice.
The template is especially useful for operations, dispatch, billing, and claims teams that need a consistent record across many stops and facilities. It helps you separate blocking delays, such as no dock availability or paperwork holds, from non-blocking notes like routine status updates. It also supports ASAP review when a charge needs immediate attention and SLA-based review when disputes are handled on a set cadence.
Do not use this log as a generic delivery checklist or as a substitute for contract terms. If your operation does not bill detention or demurrage, or if the shipment has no free-time rules, a simpler delivery record may be enough. The value of this template is in the verifiable timing trail, the DRI assignment, and the evidence needed to approve, reject, or dispute charges without re-creating the event later.
Standards & compliance context
- This template supports ITIL-style incident and exception tracking by preserving a clear record of what happened, when it happened, and who verified it.
- For OSHA-aligned site operations, use the log to document wait-time conditions and any safety-related access restrictions that affected loading or unloading.
- For FDA-regulated freight or cold-chain moves, add temperature or hold-release notes when dwell time may affect product integrity or chain-of-custody evidence.
- If your contracts define detention or demurrage differently by carrier, terminal, or customer, keep the applicable rule in the record so the charge basis is clear.
- Do not use the log to store unnecessary personal data; keep only the operational details needed to validate the accessorial charge.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
How to use this template
- Create one log per shipment, container, or facility visit and enter the site name, appointment reference, and free-time allowance before the driver arrives.
- Assign a DRI for the record, then capture each independently verifiable timing point such as check-in, dock-in, loading start, release, and check-out.
- Record the reason for any delay, mark whether it is blocking or non-blocking, and attach supporting evidence such as gate stamps, photos, or facility notes.
- Compare the total dwell time against the free-time rule and mark the charge as expected, questionable, or disputed based on the documented timeline.
- Review unresolved entries on a daily or weekly cadence, then route approved disputes or billing corrections to the next owner with the relevant evidence attached.
Best practices
- Record timestamps as close to the event as possible so the log reflects the actual dwell timeline, not a reconstructed memory.
- Use one checklist item per timing milestone and keep each item independently verifiable with a yes, no, or N/A answer.
- Capture the free-time rule in the same record as the shipment so reviewers do not have to search for contract terms later.
- Separate facility-caused delays from carrier-caused delays so the dispute record shows who controlled the blocking step.
- Attach photos, gate receipts, lumper receipts, or appointment confirmations at the time of the event rather than after the invoice arrives.
- Keep priority normal for routine charge review and reserve critical only for time-sensitive disputes or compliance-sensitive exceptions.
- Review recurring delays by facility so you can spot repeat offenders and escalate with a consistent evidence package.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What does this detention and demurrage tracking log cover?
This template tracks the time a driver arrives, checks in, waits, loads or unloads, and checks out at a shipper or receiver facility. It also captures the free-time allowance, the point where charges begin, and any notes needed to support a dispute. Use it to document accessorial charges with a clear audit trail.
When should I use this log instead of a general delivery record?
Use it whenever detention or demurrage charges may apply, especially at busy docks, warehouses, ports, or customer sites with appointment windows. A general delivery record usually misses the timing detail needed to validate charges. This log is designed for dwell-time proof, not just proof of delivery.
Who should run this template?
Dispatch, operations, billing, or the DRI responsible for freight exceptions can run it, depending on your workflow. The person entering the record should be able to verify timestamps, facility names, and any detention trigger point. If the site provides gate or dock timestamps, those should be attached or referenced by the same DRI.
How often should the log be used?
Use it for every load where detention or demurrage may be billed, disputed, or monitored. Many teams run it per shipment or per facility visit, then review it daily or weekly for unresolved charges. If your operation has recurring accessorial issues, make the recurrence explicit in your workflow rather than relying on memory.
What are the most common mistakes with detention and demurrage logs?
The biggest mistake is recording only arrival and departure without the check-in, dock-in, and release milestones that prove dwell time. Another common issue is failing to note the free-time allowance or the exact rule used to calculate the charge. Teams also lose disputes when they do not attach supporting documents or identify who verified the timestamps.
Can this template help with disputes against carriers, shippers, or receivers?
Yes. The log is built to capture the facts needed to challenge a charge, including who caused the delay, when the delay started, and what evidence supports the claim. It does not replace contract language, but it gives you a consistent record to compare against the accessorial invoice or detention notice.
How should I customize it for my operation?
Add the fields your contracts require, such as appointment number, container number, trailer number, or dock door. You can also add a task type for checklist items like document verification or photo capture if your team needs a repeatable intake process. Keep the core timing fields intact so the log still supports charge validation.
Does this integrate with TMS, billing, or proof-of-delivery workflows?
It can sit alongside transportation management, billing, and proof-of-delivery records as the exception log for accessorials. Many teams link it to shipment records, invoice review tasks, or a claims workflow so the DRI can move from capture to dispute without rekeying data. The key is to keep one source of truth for the timing evidence.
How is this better than tracking detention in email or spreadsheets?
A structured log makes each timing point, free-time rule, and dispute note independently verifiable. Email threads bury the evidence, and spreadsheets often miss the DRI, recurrence, or verification step needed for clean follow-up. This template gives you a repeatable record that is easier to review, audit, and act on.
Related templates
Go deeper on the topic
-
A daily huddle is a brief (10–15 minute) standing meeting held at the start of a shift or workday to align the team on priorities, surface issues, and...
-
A deskless worker is any employee whose job happens without a desk, a company laptop, or a fixed workstation. They're roughly 80% of the global workforce —...
-
A frontline employee app is a phone-first application that gives hourly, field, and deskless workers access to their schedule, pay, announcements, training,...
-
A frontline worker is any employee whose job happens away from a desk — on a production floor, in a patient room, behind a store counter, in a customer's...
-
Fix recruiting pipeline handoffs with a unified candidate portal, branded career pages, and faster offers that keep top talent engaged.
-
MangoApps AI agents now take action across 21 apps—approving leave, advancing candidates, managing schedules—not just surfacing recommendations.
-
MangoApps is now Workday Design Approved, surfacing benefits, pay, learning, and time-off data directly inside the MangoApps platform for frontline workers.
-
Artificial Intelligence helps Human Resources improve hiring, reduce bias, and boost workforce efficiency with smarter, data-driven decisions.
Ready to use this template?
Get started with MangoApps and use Detention and Demurrage Tracking Log with your team — pricing built for small business.