The 6 Documents That Win a Detention Dispute

Six documents decide almost every detention dispute: the rate confirmation clause defining free time, the bill of lading, the timestamped proof of delivery, independent arrival and departure evidence, the appointment record, and the carrier’s invoice with its detention worksheet. In that order, they answer every question the other side can raise. Missing one, and the dispute becomes two people remembering a Tuesday differently.

That is why detention claims get denied. Not because the driver was not there, but because nobody can prove when the driver arrived, when the clock was supposed to start, or what rate the hours bill at. The facts are rarely in dispute. The file is.

This post is the file. Its companion, how to dispute a detention charge when the POD has no in and out times, covers the argument. Both directions need the same package: a shipper refusing four hours of detention and a broker substantiating it are doing identical work from opposite sides of the table. Whoever has the better file wins, and it is not always the party who is right.

Why the burden lands where it does

Detention is not a regulated rate. It is a contractual charge, so the party asserting it has to point to the term that creates it and the facts that trigger it.

The invoice itself is regulated, though. Under 49 CFR 373.103, a freight or expense bill must state the exact rates assessed and the nature and amount of each charge. “DETENTION 4.0 HR” with a dollar figure, no rate and no clock is not a complete bill, and naming that defect politely usually produces the backup faster than asking for it does.

So do the clocks. Under 49 U.S.C. 13710, a shipper has 180 days from receipt to contest a bill and a carrier has 180 days to add charges. If you already paid, 49 CFR 378.4 says inadequate documentation alone cannot disqualify an overcharge claim. The rest are in our freight billing deadline reference.

Document 1: The rate confirmation or contract clause that defines free time

Proves the entitlement: how much free time the load carries, what event starts the clock, the rate, any cap, and whether detention requires prior notification. Without it, nobody can say what the right answer is.

Weak version: “detention as per carrier tariff” and nothing more. Two hours free with no named trigger, leaving arrival, check-in and gate-in all arguable. A rate with no cap on a load that sat 19 hours.

Get it from the signed carrier agreement and its accessorial schedule, then the load-level rate con. If a rules tariff is incorporated by reference, request the version in effect on the ship date.

Attacked by version substitution: the other side quotes a tariff revision that took effect after your shipment, so ask for its effective date. And by the notification clause, since many accessorial schedules require the carrier to notify before free time expires. A carrier that skipped that has a weak claim no matter how long the truck sat, which is why that clause decides more disputes than timestamps do.

Document 2: The bill of lading

Proves that the shipment existed as described and moved between the parties named. It ties every other document to one load. Under 49 CFR 373.101, the carrier’s receipt or bill of lading must show consignor and consignee, origin and destination, piece count, description, and weight where weight is relevant to rating.

Weak version: unsigned, or carrying no PRO or load number, so it cannot be matched to the invoice.

Get it from origin, destination, or the carrier. Ask for all three copies when there is disagreement about what was signed. The differences between them are often the most useful thing you find.

Attacked by being sidelined rather than challenged: it says nothing about time, so the argument moves to the POD. That is fine. The BOL is the spine of the file, not the proof of dwell.

Document 3: The signed proof of delivery with timestamps

Proves arrival and departure, signed by someone at the facility. The most load-bearing document in a detention file, and the one most often missing the exact data you need.

Weak version: a signature and a date with no times. Times in the driver’s hand with no countersignature. One time that could be either event. Times rounded to the hour on a claim billed in 15-minute increments.

Get it from the carrier’s settlement file. Shippers should also ask the receiving facility for its own signed copy, sometimes more complete than the one that rode back with the driver. Where facilities capture electronic BOLs, timestamps are recorded at signature, which is why vendors selling them pitch them as detention prevention.

Attacked by three moves: self-reported times, called unverified; the wrong event, where the POD shows when paperwork was signed rather than when the truck cleared the gate, a gap that runs an hour at a busy DC; and silence, the scenario the no-POD-times dispute walkthrough exists to solve.

Document 4: Independent arrival and departure evidence

Proves the same two moments as the POD, from a source with no stake in the outcome: gate logs, guard records, sign-in sheets, dock scheduling exports, camera timestamps, yard management events, ELD or telematics data. A POD proves the parties met. An independent record proves when.

Weak version: a geofence wide enough to include the truck stop across the road. An ELD duty-status change, which shows when the driver went on-duty-not-driving, not when the truck reached the gate. A gate log screenshotted with no facility header or system name.

Get it early. Brokers should request the raw telematics event list with timestamps and coordinates, not a summary. Carriers should pull the export the same day, since retention on some platforms is shorter than the dispute window. Request facility records in writing: security logs at third-party sites are often overwritten on a fixed cycle.

Attacked by precision and provenance: geofence radius, time zone (a UTC export against a local-time POD manufactures phantom hours), clock drift, and the argument that an ELD shows a stationary truck rather than a waiting one. The counter is convergence. When the geofence entry, the guard log and the POD agree within minutes, the argument about any single one stops mattering.

Document 5: The appointment record

Proves scheduled versus actual, which assigns fault. It is the document most often left out of the file entirely.

A truck arriving 90 minutes early and billing detention from arrival is making a claim most contracts do not support. A truck arriving on time and sitting three hours past a confirmed window has a claim that is hard to deny. Same dwell, opposite outcomes.

Weak version: a verbal appointment nobody wrote down. A window loose enough (“Tuesday AM”) that early arrival looks compliant. A rescheduling thread with no confirmed final time.

Get it from the dock scheduling platform, the confirmation email, or the dispatch note and driver check-in log.

Attacked by the early-arrival defense, which works more often than carriers expect, and by an undisclosed reschedule. If the appointment moved twice and the file shows only the original booking, the whole timeline looks suspect. Include the reschedules yourself.

Document 6: The carrier’s invoice and detention worksheet

Proves what is being claimed and how: hours, rate, increment, the start and stop times used, and whether free time was deducted at all.

Assemble it last, scrutinize it first. Most detention disputes are resolved not by disproving the dwell but by finding a billing convention error: free time never subtracted, hours rounded up to the full hour on a 15-minute-increment contract, a rate that does not match the rate con, or detention billed at both stops when only one qualified.

Weak version: a line with a total and no hours, or hours with no start and stop times. No facility named on a multi-stop load. A charge arriving weeks after the linehaul invoice, worth checking against the 180-day window in 49 U.S.C. 13710.

Get it by requesting the worksheet in writing. Most carriers have one, since settlement staff computed the figure somehow. If none exists, that answer belongs in your file.

Attacked by you. Recompute it against the free time and increment in document 1 and the timestamps in documents 3 and 4. “We compute 2.25 billable hours, not 4.0, and here is the arithmetic” settles far faster than “the charge is unsupported.”

The six documents at a glance

Document	What it establishes	Who holds it	Common failure
Rate con or accessorial clause	Free time, clock trigger, rate, cap, notification duty	Shipper, broker, carrier	Refers to a rules tariff nobody has produced
Bill of lading	The load exists as described; ties the file together	All three parties	No PRO or load number to match the invoice
Signed POD with timestamps	Arrival and departure, witnessed at the facility	Carrier and consignee	No in and out times, or times written only by the driver
Independent arrival and departure evidence	The same two moments, from a disinterested source	Facility (gate, guard, scheduler); carrier (ELD)	Geofence too wide, time zone mismatch, records purged
Appointment record	Scheduled versus actual, which assigns fault	Shipper or broker	Vague window; reschedules missing
Invoice and detention worksheet	What is claimed and how it was computed	Carrier	Free time not deducted, or the wrong increment

Why these six

Detention is an entitlement, a timeline, and an arithmetic. Documents 1 and 5 establish the entitlement and whether its conditions were met. Documents 3 and 4 establish the timeline, one witnessed and one independent. Document 6 exposes the arithmetic. Document 2 joins them into a single load.

The closest published treatment names three documents as the prerequisite to contesting a carrier invoice: the rate confirmation, the BOL or POD with facility timestamps, and the carrier’s own detention documentation. A fair minimum, mapping to documents 1, 3 and 6. The three we add decide the hard cases: independent evidence is the fallback when the POD is silent, the appointment record separates a facility’s delay from a carrier’s early arrival, and the BOL stops anyone answering about a different load.

It generalizes. Every accessorial dispute is entitlement plus event plus arithmetic, which is why the liftgate charge on a dock-to-dock delivery reduces to what the rate con authorized and what the BOL says happened at the door, and why fuel surcharge reduces to the DOE index week and the per-mile formula.

If you are the shipper

Your leverage is the entitlement and the arithmetic, not the timeline. You do not hold the ELD data and rarely hold a better POD than the carrier does. You do hold the rate con, the appointment record, and your own dock scheduling export.

Work document 1, then 5, then 6, and keep the rest in reserve. If free time was never deducted or the rate is wrong, you never have to argue about hours. Contest in writing inside the 180-day window, and state the amount you believe is owed rather than refusing the whole line. If you already paid, the carrier owes you a decision within 60 days under 49 CFR 378.8.

If you are the broker or the carrier

Your leverage is the timeline. You hold the ELD, the driver’s records and the POD, so submit the package unprompted with the invoice. A detention line supported by a timestamped POD, a geofence export that agrees with it, the appointment confirmation and a worksheet showing free time deducted is hard to short-pay in good faith. A line with a number and nothing else invites a dispute whether or not it is correct, and working that dispute usually costs more than the charge.

Brokers carry a specific risk: approving detention without the evidence to pass it through. If the carrier’s file will not survive your customer’s scrutiny, it will not survive yours, and the gap becomes margin.

When a document does not exist

Some will not exist for a given load. Small facilities have no gate. Older equipment has no telematics beyond the ELD. Appointments get made on the phone. None of that ends the claim.

Say so in writing before you are asked. A file that acknowledges a missing gate log reads as complete. One that omits it silently reads as evasive.

Substitute with contemporaneous, disinterested records. Ranked by how well they hold up: guard or gate logs, dock scheduling exports, ELD or telematics events, camera timestamps, driver app check-in messages, dispatch call logs with system timestamps, fuel or toll receipts that bracket the dwell, and last, the driver’s own notes. Two weak independent records that agree beat one strong record standing alone.

Fix it at the contract, not at the dock. If the rate con names arrival as the trigger but nothing at the facility records arrival, the clause is unenforceable in practice. Move the trigger to an event the facility captures.

Ocean demurrage and detention are better served, because invoice content is regulated: 46 CFR 541.6 requires the invoice to state the timeframes for requesting mitigation, refund or waiver, 46 CFR 541.7 requires it within 30 calendar days of the date the charge was last incurred, and 46 CFR 541.8 gives the billed party at least 30 days to request relief. Nothing equivalent governs truckload detention, which is why 49 CFR 373.103 is worth citing.

The assembly checklist

Pull the rate con and the accessorial schedule in effect on the ship date. Write down free time, trigger event, rate, increment, cap, and any notification requirement.
Pull the BOL and confirm the PRO or load number matches the invoice in dispute. If it does not, resolve that first.
Pull the POD. Note whether in and out times exist, who wrote them, and whether they were countersigned.
Request independent arrival and departure evidence the same week, before you know whether you need it. Gate logs and footage expire.
Pull the appointment record including every reschedule, and compare scheduled to actual.
Request the detention worksheet, then recompute the charge from steps 1, 3 and 4.
State your number. Send the recomputation, attach the file in this order, and cite the clause and timestamps you relied on.
Diary the deadline: 180 days to contest an unpaid bill, or 60 days for a decision on a written overcharge claim if you already paid.

Where the documents exist this takes about twenty minutes, the same twenty minutes whether you are refusing the charge or defending it. The operations that recover detention consistently are the ones that assemble the file before the argument starts, not the ones that argue best.