Detention proof and documentation

The document controls the memory

This topic is strongest when the carrier reads the paperwork before the truck is exposed. The working focus is building a factual record for detention requests using arrival time, free time, release time, written terms, and POD support. A broker call can explain the load, but the rate confirmation, revised confirmations, receipts, POD, BOL, and written approvals are what later support dispatch decisions and billing.

If one important detail is still verbal, treat that detail as unresolved. A short written reply or revised confirmation is easier to use than a remembered phone call.

Written terms to review

Record arrival, dock time when known, and departure or release time. Compare the broker call against the written confirmation line by line. Flag missing accessorial, appointment, or billing language before signing. Save revised confirmations, receipts, BOL, POD, and approval messages together. Also confirm commodity, weight, equipment, appointment type, facility rules, and whether any accessorial requires prior approval.

A good review leaves a short trail: what is confirmed, what is estimated, and what still needs a broker reply before dispatch.

The detention file should tell a timeline

A good detention request reads like a timeline: appointment, arrival, check-in, delay notice, dock or wait status, release, and broker follow-up. It does not need drama. It needs timestamps, written terms, and enough context for someone in billing to understand what happened without calling the driver again.

What to ask before signing

Read the confirmation against the call notes. If money, timing, equipment, commodity, accessorials, or paperwork requirements do not match, pause and ask for a corrected document.

The right question is not whether the broker meant it. The right question is where it is written.

Paperwork mistakes that create disputes

A frequent mistake is saving the first confirmation but losing the revised one. The final written version should travel with POD, BOL, receipts, and approvals.

A scattered load file makes a reasonable request harder to prove.

Records to keep together

The document file should connect the event to the charge or decision: appointment, arrival, delay, approval, release, delivery, and billing. Missing links make the story harder to follow.

Build the packet while the load is fresh.

Example scenario

Example scenario: the broker says detention is available after two hours, but the first confirmation does not say when the clock starts. The carrier asks for revised written language before pickup and keeps arrival, departure, BOL, POD, and message records in the same file. Replace any sample number or assumption with your actual rate, route, fuel, tolls, accessorial terms, equipment requirements, and payment setup.

References and methodology

• Accessorial documentation editorial methodology - LaneMath Editorial Desk. Used for documentation workflows and example scenarios, not for legal claims about collectability.
• Rate confirmation educational reference - LaneMath Editorial Desk. Used for document literacy. It is not legal advice and does not replace professional review.