The first detention claim is the moment when the discipline built into a dock workflow either pays off or doesn't. A driver showed up at a receiver, got held past free time, and now the carrier is trying to collect the additional pay the rate confirmation promised. The amount probably isn't huge — a couple of hundred dollars at most. But the process that goes into collecting it sets the pattern for every detention claim the operation will handle from that point forward. Get it right once and the rest become routine. Get it wrong once and a habit forms of leaving accessorial revenue on the table.
What should already be in place from the dock
The strength of a detention claim is almost entirely a function of what was documented at the dock:
- Check-in time stamped on BOL or guard slip. The moment the truck arrived.
- Loaded-out time stamped on BOL. The moment the truck was released.
- Driver-signed acknowledgment of those times.
- Real-time notification to the broker that detention was accruing — sent while the driver was still at the dock, not after.
- Rate confirmation in hand with the specific detention terms (free time, hourly rate, cap).
If all five are present, the claim is straightforward. If any are missing, the claim is harder but often still recoverable.
What goes into the submission
The submission format varies by broker, but the standard pieces:
- Load identifier, pickup and delivery dates and locations
- Free time per the rate confirmation
- Total time at the dock (with arrival and release timestamps)
- Hours of detention claimed
- Rate per hour per the rate confirmation
- Total detention claimed
- Supporting documentation: BOL with stamps, broker notification timestamps, any photos
The submission goes through the broker's specified channel — accessorial portal, email to AP, or whatever they've designated — within their claim window. Most brokers allow 7-14 days; some 30. The rate confirmation will say.
This is the kind of repetitive paperwork that disappears into the back office of a dispatch operation. For carriers running with dispatch, submission is usually handled on their behalf as part of the post-delivery workflow, leaving the driver responsible only for the dock documentation.
How brokers actually process
The broker's claims desk is checking:
- Does the BOL show the stamps being claimed?
- Was the broker notified contemporaneously?
- Do the stamps match what the shipper or receiver reported on their end?
- Is the claim within the broker's window?
- Does the math match what's in the rate confirmation?
If everything checks out, payment flows through with the next regular payment cycle — sometimes faster on the accessorial than on the linehaul.
If something doesn't check out, the broker comes back with a question. Common ones: "Receiver shows departure time as X — your claim shows Y, can you reconcile?" or "BOL not stamped at check-in, do you have alternate documentation?" or "Detention hours exceeded the cap per rate confirmation — we can pay the cap amount only." These are negotiable conversations, not denials.
When a claim is denied
A denial isn't necessarily the end. The reasons to push back:
- The denial reason doesn't match what the documentation shows.
- The receiver's reported times look wrong compared to the carrier's contemporaneous notification.
- The rate confirmation language is being misinterpreted by the claims desk.
The escalation path is straightforward: start with the broker rep who handled the load, escalate to operations if needed, and document the rate confirmation language carefully. Most legitimate detention claims get paid by the first or second touch. Persistent disputes where the documentation clearly supports the claim and the broker still refuses are rare and usually a signal that the broker isn't worth continuing to work with.
What patterns emerge after several claims
After 5-10 detention claims with the same broker, the pattern becomes clear. Some brokers pay smoothly; for those, detention claims become a routine task, paid reliably. Others dispute every claim; for those, each claim becomes a multi-touch interaction.
That distinction matters for broker selection over time. A broker who pays the linehaul promptly but fights every accessorial is producing lower realized rates than the posted rate suggests. Tracking accessorial collection rate by broker becomes one of the inputs to which brokers the operation prefers to work with. The ones who pay accessorials clean are worth more than the ones who don't, even if the posted rates look similar.
When something was missed at the dock
For cases where the BOL didn't get stamped or the broker wasn't notified contemporaneously, the claim is weaker but not necessarily impossible. Driver-attested times sometimes substitute, ELD GPS data can supplement, and an honest conversation with the broker sometimes results in pay even on weaker claims — especially with brokers the operation has a positive relationship with.
The first response to a thin claim is "let's see what we have and how we can support it" rather than "this is hopeless." Even weak documentation is better than no submission.
Building the habit forward
After the first claim — successful or not — the right move is to calibrate for next time:
- Was BOL stamping reliable, or did the driver have to ask multiple times?
- Was broker notification clean, or were there gaps?
- Did the documentation hold up under broker review?
- What single thing would have made the next claim easier?
Each detention event is an opportunity to refine the workflow. By the tenth claim, the process should be muscle memory.
The receiver matters too
Sometimes detention happens because the receiver is consistently slow. They hold every carrier, not just yours. The detention pay covers the time at the prevailing rate, but the operational disruption — later delivery on the next load, missed reload — isn't always covered.
For consistently slow receivers, the long-term answer is sometimes to avoid loads going there if alternatives exist. Some receivers are bad enough that even with full detention paid, the loads aren't worth running. That kind of receiver-level intelligence is exactly what a dispatch desk accumulates across many carriers and many loads, and applies on behalf of the carriers it supports.
Honest caveat: detention pay rarely makes you whole on a really bad dock
Spending six hours at a receiver waiting to unload generates detention pay at the prevailing rate, but the pay doesn't cover the cascade effects — missing the next load, sitting an extra night in the area, fatigue affecting the next day's run. Even fully-collected detention pay is usually less than the actual opportunity cost of a bad dock experience. The realistic view is that detention is partial compensation, not full restoration. The carriers who handle this best file every legitimate detention claim diligently (because the pay is real and adds up across the year) while also operationally avoiding the docks that consistently produce detention events. Both moves work together; neither alone solves the problem.
The detention claim process is one of the routine operational mechanisms that distinguishes a tight carrier operation from a loose one. The first claim teaches the process; the next several refine it; by the second year, it's running on autopilot.
Talk to dispatch
If detention paperwork, broker follow-up, and accessorial chasing are eating evening hours after long driving days, those are exactly the back-office tasks a dispatch desk absorbs. Talk to dispatch about handling the post-delivery workflow so the driver isn't also the accounts receivable department.