How to confirm accessorials in writing
A paperwork-first guide to turning a phone approval into a clear written record for detention, lumper, layover, TONU, or stop-off charges, including the written terms and records that matter before dispatch and after delivery.
Written and reviewed by LaneMath Editorial Team. Updated 2026-06-08. LaneMath pages are maintained as practical carrier education using public references, example-only math, and internal editorial review.
Key takeaways
- State the load number, event, amount if known, and approval request plainly.
- Ask whether a revised confirmation will be issued before billing.
- Keep the reply with the POD, BOL, invoice, and receipts.
The document controls the memory
This topic is strongest when the carrier reads the paperwork before the truck is exposed. The working focus is turning a phone approval into a clear written record for detention, lumper, layover, TONU, or stop-off charges. 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
State the load number, event, amount if known, and approval request plainly. 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.
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.
What to check before booking
- State the load number, event, amount if known, and approval request plainly.
- 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.
Common questions
What should a written accessorial confirmation include?
At minimum: the load number, the event (delay, lumper cost, changed appointment), the dollar amount if known, and a direct request asking whether the charge is approved. Attaching the supporting record — receipt, timestamp, gate note — with the message makes it easier to process.
Is a phone approval sufficient for accessorial charges?
A phone approval is better than nothing but is harder to use at billing time. A brief written follow-up that restates the approval with the load number and event details gives both parties a matching record and reduces the chance of a dispute when the invoice is submitted.
References and methodology
- Accessorial documentation editorial methodology - LaneMath Editorial Desk. Used for documentation workflows and example scenarios, not for legal claims about collectability.