Detention, Layover, TONU: How We Get You Paid Faster (and What Most Drivers Leave on the Table)
- American Trust Logistics Team

- Dec 24, 2025
- 4 min read
A clear guide for dry van drivers on detention, layover, TONU, and lumper reimbursement, what qualifies, what paperwork is required, and a simple process to get paid consistently.
The uncomfortable truth
A lot of drivers lose money on accessorials because:
they don’t document it correctly
they don’t ask early enough
the rate con language doesn’t support the claim
they don’t know what “counts”
they wait until after delivery to bring it up
This is exactly where a strong dispatch partner pays for itself.
Part 1: Simple definitions (no industry fluff)
Detention
Detention is pay for time spent waiting at shipper/receiver beyond the free time allowed.
Usually it requires:
proof of arrival/check-in time
proof of release/departure time
sometimes a signed form or timestamped document
Layover
Layover is pay when a load causes you to lose a day (or significant hours) because you couldn’t move due to shipper/receiver delay.
This typically happens when:
you arrive and can’t load/unload that day
they tell you to come back later (next day)
you lose the ability to run a productive schedule
TONU (Truck Ordered Not Used)
TONU is pay when:
you were dispatched to a load,
you accepted,
you showed up (or were en route),
and the shipper cancels or can’t load you.
TONU usually requires:
proof you were on the load
proof of dispatch/confirmation
proof of arrival or attempt to arrive (depends on broker terms)
Lumper Reimbursement
A lumper fee is when the receiver requires paid labor to unload.
Reimbursement usually requires:
lumper receipt
proof you paid (if you paid)
broker approval process (EFS/comchek or reimbursement)

Part 2: The #1 reason drivers don’t get paid for these
The #1 reason is documentation timing.
Many drivers wait until after delivery to mention it.By then:
the broker doesn’t care
the paperwork isn’t clean
the rate con language gets used against you
The win is to handle accessorials in real time.
Part 3: The real-world process that works (industry standard in practice)
Here’s the process we use to maximize paid accessorials:
Step A: Confirm detention rules before you roll
Before pickup, we confirm:
free time allowed (e.g., first 2 hours free)
detention rate (e.g., $50/hr) and increments (hourly vs half-hour)
when detention starts (from appointment time or from check-in?)
required proof (BOL timestamp? guard shack check-in? signed form?)
If a broker won’t confirm this, that’s a red flag.
Step B: Driver sends “arrived + checked in” message immediately
This is the moment most drivers miss.
Driver message should include:
“Arrived at pickup/delivery, checked in.”
Time of arrival
Who they checked in with (if known)
Any notes (line is long, told to wait, etc.)
Photo proof if possible (guard shack sign, check-in screen, location stamp)
Step C: Dispatcher starts the clock and flags the threshold
When free time is about to expire, we notify the broker early:
“Driver checked in at ___, we’re approaching detention. Please confirm detention approval.”
This protects you because it creates a written record before the bill is large.
Step D: Driver sends “loaded/unloaded” with time stamps
When released:
send exact release time
send BOL/POD photos
send any signed time slips
Step E: Detention request is sent same day
Not next week. Not “when we get around to it.”
Same day:
check-in time + release time
appointment time (if applicable)
BOL/POD proof
detention amount requested per agreed terms
Part 4: How to avoid getting denied
Here are the common denial reasons—and how to prevent them.
Denial reason 1: “No proof of check-in”
Fix: always send a timestamped check-in message + photo proof if possible.
Denial reason 2: “Detention starts from appointment time, not arrival”
Fix: confirm the rule in writing before booking.
Denial reason 3: “You didn’t notify us in time”
Fix: dispatch notifies broker when free time is about to expire.
Denial reason 4: “Rate con doesn’t include detention”
Fix: we negotiate and confirm detention policy before acceptance.
Denial reason 5: “Receiver was closed / you arrived late”
Fix: protect appointment integrity and track delays in writing.
Part 5: When layover applies (and when it doesn’t)
Layover typically applies when the delay causes:
a full day of lost productivity
It usually does not apply when:
you arrived late
you missed the appointment
the issue was preventable by the carrier
Key move: if you’re told to come back tomorrow, we immediately request layover approval in writing, same day.
Part 6: TONU: how to actually get paid
TONU gets denied when:
broker claims the load was never “confirmed”
driver can’t prove they were dispatched
cancellation was vague or undocumented
To get paid:
Save the dispatch confirmation / rate con
Capture the cancellation message/email
If you arrive, document arrival (photo + timestamp)
Submit TONU request immediately with proof
Part 7: Why this matters to weekly revenue (not just “extra money”)
Accessorials aren’t “bonus.” They’re revenue recovery.
If detention steals 6 hours:
you lose miles
you lose reload options
you risk missing appointments
your week becomes unstable
Getting paid for detention won’t replace the time, but it:
compensates the loss
reinforces professionalism
trains brokers to take you seriously
Part 8: The American Trust Logistics promise in plain terms
If you hire a dispatch service, you should get:
clean paperwork
real-time communication
someone tracking your time
someone pushing back professionally
someone making sure you’re not leaving money on the table
That’s what we do.
If you’re a dry van owner-operator who’s tired of waiting for free, American Trust Logistics runs your load planning, broker communication, paperwork, and accessorial recovery, so you keep moving and stop donating your time to shippers and receivers.
🇺🇸📌 If you’re ready for a dispatch partnership built on discipline, strategy, and profitability, American Trust Logistics is built for you.
Apply today to work with a team that brings Navy discipline to trucking.


Comments