Unpaid Detention: How to Escalate and Actually Collect

You have the ELD timestamps, the gate receipt, the text message sent the moment free time expired, and the invoice submitted the same day — and the broker still came back with "detention not approved." This is the part carriers don't expect: even well-documented detention claims get denied on the first pass more often than not, because brokers know most carriers stop pushing after one rejection. The invoice being correct isn't the same as the invoice being paid. Getting paid requires knowing exactly how to escalate once the first "no" shows up.

Why Do Brokers Deny Detention Claims So Often?

Denying the first submission is, for some brokers, a default response rather than a genuine dispute. It costs the broker nothing to say no, and a meaningful share of carriers accept the denial and move on rather than escalate. Common denial reasons include "not on the rate con," "notification wasn't received in time," or "the shipper disputes the wait time." Some of these are legitimate. Many are a first-line filter designed to reduce how much detention actually gets paid out. Your job on escalation is to figure out which one you're dealing with and respond accordingly.

It also helps to understand the broker's incentive on the other side of the transaction. The broker doesn't pay detention out of their own margin in isolation — in many contracts, they try to pass some or all of it back to the shipper. If the shipper resists reimbursing the broker for detention, the broker has a financial reason to deny or delay your claim rather than absorb the cost themselves. Understanding this dynamic changes how you frame your escalation: you're not just asking the broker to pay you, you're giving them documentation strong enough that they can, in turn, collect from the shipper without a fight.

What Documentation Do You Need Before You Escalate?

• ELD arrival and departure timestamps — the single hardest piece of evidence to dispute.
• A written notification to the broker sent at the moment free time expired, not after delivery.
• A gate check-in receipt or photo showing arrival time at the facility.
• The rate con's free-time and detention-rate terms, or proof detention was agreed to verbally if it wasn't written down.
• A BOL notation of actual departure time, ideally with a shipper or dock supervisor signature.

If any of these are missing, gather what you can before escalating — a partial record still strengthens your position, but a complete one is what actually forces payment. Also pull the economics into your escalation: a driver sitting three hours past free time at $2.50/mile and 55 mph represents roughly $412 in lost revenue opportunity, against a detention recovery of maybe $150–$225 at $50–$75/hour. Referencing that gap in your escalation — that you're not even asking to be made whole, only partially compensated — is a reasonable point to raise with a broker who's treating the claim as negotiable.

What Is the First Escalation Step After a Denied Claim?

Don't argue with the same rep who denied it — go over their head, in writing, to a manager or the accounts payable department. State the load number, the documented wait time, the rate agreed, and attach every piece of evidence in one email. Ask directly: "What specific term of the rate con or company policy justifies this denial?" Forcing the broker to cite a specific reason, rather than accepting a generic no, frequently exposes that there isn't a real basis for the denial at all.

Keep this first escalation email short and factual — a wall of text reads as an argument, while a tight summary with attachments reads as a case that's already built. Give a reasonable but firm reply window, three to five business days, before moving to the next step. Escalating too slowly is as costly as not escalating at all; the longer a denied claim sits, the easier it is for the broker to treat it as closed.

How Do You Write a Detention Demand That Gets Paid?

If the manager-level appeal doesn't resolve it, send a formal written demand. This should read differently from a routine invoice follow-up — it should make clear you understand your escalation options and intend to use them.

• Restate the documented facts: arrival time, free time expiry, departure time, and the applicable detention rate.
• Attach every piece of supporting evidence again, even if sent before — make it a self-contained document.
• Set a specific payment deadline, typically 10 business days.
• State plainly that non-payment will result in a claim against the broker's surety bond and, if unresolved, small claims court.

When Should You File Against the Broker's Bond for Detention?

Once the demand deadline passes without payment, a bond claim is a legitimate next step — detention is a valid accessorial charge under the rate con, not a discretionary add-on, and unpaid accessorials are recoverable against a broker's bond the same way an unpaid linehaul rate is. Our guide to how the broker surety bond works and how to file a claim walks through the process in detail, including how to find the surety company on file for a given MC number.

For a single detention claim of a few hundred dollars, a bond claim can feel like overkill, and in isolation it sometimes is. But detention denials are rarely isolated — a broker who denies your $225 claim this month is likely denying similar claims from other carriers on the same lane. Filing the bond claim isn't just about this one invoice; it's about putting a documented mark against a broker whose denial pattern will eventually cost other carriers too, and it strengthens your position if a larger dispute with the same broker ever follows.

Can You Deduct Detention From What You Owe the Broker?

No — resist the temptation to unilaterally deduct unpaid detention from a factoring balance, a future load payment, or anything else you might owe that broker. Self-help deductions almost always backfire: they give the broker a legitimate counter-claim, they can trigger a breach-of-contract argument against you, and they muddy what should be a clean, documented claim. Pursue detention as its own claim through the proper escalation channel, not as an offset.

Should You Blacklist Chronic Detention Offenders?

Yes, and this matters more than any single collection. Track every broker and every shipper facility where detention becomes a repeated pattern. A broker who disputes detention on nearly every load from a particular shipper is telling you something about that shipper's dock operations — and about how hard you'll have to fight for every future invoice from that lane. Some carriers keep hauling for chronic offenders because the linehaul rate looks attractive; factor the collection friction into the real cost of that lane before accepting the next load.

A simple spreadsheet works fine for this: broker name, shipper facility, load date, hours of detention, whether it was paid, and how many escalation steps it took. After a handful of loads, the pattern becomes obvious — some facilities are reliably fast, and some cost you two or three hours of unpaid waiting on a majority of visits. That data is also useful leverage in itself: showing a broker a documented history of repeated delays at a specific dock is often more persuasive than arguing about a single load in isolation.

How Do You Build Detention Terms Into Every Rate Con Going Forward?

• Never accept a rate con silent on detention — add the terms in writing before dispatch, not after.
• Set a clear notification requirement in writing: text or email the moment free time expires, every time.
• Submit detention as a separate, clearly labeled invoice line the same day the load delivers — not bundled in, not delayed.
• Review what actually gets carriers paid on time for the broader payment-terms discipline that makes accessorial disputes far less common in the first place.

A dispatcher who fights detention claims through every escalation step — not just the first denial — recovers money that most carriers write off. Get dispatched with TRUCC and stop absorbing the cost of every dock that runs three hours behind schedule.