Detention request
A carrier request for detention pay supported by written load terms, arrival and departure records, facility delay details, and billing documents.
Written and reviewed by LaneMath Editorial Team, with carrier workflow review from Dale Morrow where practical dispatch, paperwork, or lane-planning context is involved. Updated 2026-06-04. LaneMath pages use public references, example-only math, and conservative editorial review.
Carrier note
Use this term in context with the rate confirmation, broker communication, facility instructions, and billing paperwork. A short definition is useful, but the written load terms control the actual freight decision.
Carrier example
A carrier sees detention request mentioned during dispatch and checks whether the rate confirmation says how approval, documentation, and billing should work.
Common mistake
Assuming detention request is approved because it was discussed by phone.
Paperwork note
For detention request, keep written approval, timestamps, receipts when relevant, BOL, POD, revised confirmation, and invoice notes.
Building a detention request that holds up
A detention request is stronger when it connects timestamped evidence to the written terms in the confirmation. The carrier should show when the truck arrived, what the free time was, when the clock started, and when the truck was released — all tied to the specific written language in the load terms.
Sending the request while still on site gives the broker a chance to acknowledge the delay before the truck leaves. A broker who sees the delay notification while the truck is waiting can often confirm or adjust the terms with the facility directly. Waiting until the invoice cycle to ask about detention converts a dispatch question into a billing dispute.
Request timing and strength
A detention request made during the delay is stronger than one made after the fact. When a broker receives a message saying the truck has been waiting for two hours and the free time expires in 30 minutes, they can verify the facility situation, contact the receiver, and acknowledge the delay while it is still happening.
A request submitted two weeks after delivery — as a line item on an invoice — gives the broker no opportunity to verify the event and little incentive to approve a charge they have no record of seeing during the load. The documentation matters, but the timing of the communication changes how the request is received.
Questions to ask in context
- Has the delay been documented with timestamps and sent to the broker while still on site?
- Do the timestamps and free-time language in the confirmation support the request?
- Has the broker acknowledged the delay in writing during the load or before delivery?
References and methodology
- Accessorial documentation editorial methodology - LaneMath Editorial Desk. Used here for: Detention, lumper, layover, TONU, revised confirmation, and post-delivery document workflow examples.Used for documentation workflows and example scenarios, not for legal claims about collectability. Last checked 2026-06-29.
- Industry terminology and editorial explanation - LaneMath Editorial Desk. Used here for: Plain-English definitions, checklists, and example-only calculations.Editorial explanations are not official guidance, legal advice, or market data. Last checked 2026-06-29.