Detention is a contractual right. Filing it is operationally legitimate. Both of those things are true. They also have nothing to do with whether the broker’s calling pattern stays the same in the weeks afterward, which is its own variable, and one operators usually only notice when it’s already shifted.
The truck arrives at the receiver inside the appointment window. Six hours later it’s still in the dock yard waiting to unload. The operator logs the detention time, files the claim with the broker after the receiver releases the truck, and submits the supporting documents the contract requires. The broker reviews, agrees, and pays the detention rate. The transaction closes cleanly on paper.
Two weeks later the operator notices that broker’s freight has gone quieter. Not absent, the loads are still there. But the lanes that used to come up first now come up third, the freight that fit the truck used to be offered before it hit the public board and now isn’t, and a couple of the better customers the broker handles seem to be running with different carriers. The operator can’t prove the detention claim caused any of this. The operator also can’t rule it out.
The operator’s side of the claim
The detention math is real. Six hours of unpaid time on a truck that costs the operator something north of $90 an hour to keep in position, fuel idle, the driver’s clock burning, the next reload window slipping, adds up to a meaningful piece of the week’s revenue. Operators who don’t collect detention when it’s owed are absorbing a cost they didn’t agree to. The contractual right exists for a reason, and operators who exercise it are running their business correctly.
The other piece operators sometimes underweight is the knock-on timing. Six hours late off the receiver pushes the next pickup, which pushes Thursday’s reload, which compresses the operator’s remaining hours going into Friday. The detention payment doesn’t undo any of those operational consequences. It only prices them. Operators who collect detention are recovering the dollar; the time has already been spent.
The broker’s side of the same claim
Brokers aren’t typically thinking about detention claims as moral events. They’re thinking about them as costs. The detention rate the broker pays the carrier may or may not be passable to the customer, sometimes the customer agrees to pay detention up front, sometimes the broker has to absorb it against their margin, and sometimes the customer disputes it and the broker is left holding the difference. From the broker’s seat, every detention claim is a cost decision, and the relationship with the carrier is one input into how that cost decision lands.
What can shift after a claim isn’t usually a conscious decision. Brokers don’t keep a list of carriers who file detention. The shift is quieter. The next time the broker’s dispatcher is routing freight on that lane, the carrier who recently filed a $400 detention claim is one of several variables in the dispatcher’s head. If the freight has tight margins or a customer the broker is trying to keep happy, the dispatcher may instinctively reach for a carrier with a smoother recent history. The detention claim wasn’t wrong, the dispatcher just made a different call than they would have made if the recent history had no claim in it.
The customer behind the broker
The piece operators don’t see is the conversation the broker had with the customer about the detention. That conversation can go several ways. The customer may pay without question, in which case the claim has no downstream effect at all. The customer may pay reluctantly and ask the broker to “use a different carrier next time” without saying so directly, instead phrasing it as “let’s find someone faster on this lane.” The customer may refuse to pay, in which case the broker absorbed the claim and is now running a slightly different mental ledger on the carrier.
None of those customer reactions are the operator’s fault. None of them are the broker’s fault either. They’re the structure of three-party freight: the carrier moves the load, the broker arranges it, the customer pays for it, and the cost of an unscheduled event has to land somewhere. Where it lands isn’t always the place the contract says it should.
If filing a detention claim seems to cool a broker off afterward, it’s worth knowing whether that pattern is real before your next one. A dispatcher who handles detention claims across a lot of carriers will have seen it either way.
The version where collection and access both hold
Some brokers absorb detention claims without changing their calling pattern at all. The customer paid, the math closed, the carrier did the right thing by collecting, and the relationship continues exactly as it was. Operators who run with these brokers report that filing detention feels structurally normal, there’s no aftertaste, no quiet week that follows, no slot shift that becomes visible months later. The contractual right and the operating relationship coexist cleanly.
Those brokers exist. They’re often larger brokerages with more diversified customer books, or smaller brokerages whose entire business model is built on carrier loyalty. The carrier knows fairly quickly which kind of broker they’re dealing with, because the second or third detention claim closes as smoothly as the first.
The version where they don’t
Other brokers can’t absorb detention claims without it surfacing in their working order with the carrier. Sometimes that’s because the customer is making it surface, a specific customer who pushed back on the claim is now associated with the carrier in the broker’s mind. Sometimes it’s because the brokerage’s margin is thin enough that any claim against an account changes the math on routing future loads to that carrier. Sometimes it’s something the broker isn’t conscious of, just a small reluctance that shows up as which carrier they call first.
Operators who run with these brokers have to decide whether collecting on a $400 detention claim is worth what comes after. The answer isn’t obvious. $400 is real money. So is the lane access that may or may not stay available. The operator who collects and the operator who absorbs are both making operating decisions; the difference is which cost they’re choosing to carry forward.
What operators settle into
Most operators eventually develop two postures depending on the broker. With brokers whose detention claims have closed cleanly in the past, claims get filed automatically, there’s no friction, the right exists, the math works. With brokers whose past claims have coincided with quieter weeks, operators sometimes hold the claim under a threshold the broker is more likely to absorb, or absorb the claim themselves on smaller events and only file when the detention is significant enough that the math compels it.
Neither posture is wrong. Filing every detention claim is contractually correct and operationally consistent. Holding some claims for relationship preservation is operationally pragmatic and contractually conservative. Operators who run pure on either rule end up with different broker books and different revenue patterns, and the decision usually emerges from one detention event at a time rather than from a stated principle.
What dispatch can carry into the decision
The information that helps an operator decide isn’t legal, they already know the contractual right. It’s relational. Which brokers in the operator’s mix have absorbed claims cleanly, which have not, and which haven’t been tested yet. That history gets read across multiple operators and multiple lanes, and the pattern is more visible from outside one truck than from inside it.
| Stage at the dock | Operator’s leverage | Broker’s likely response |
|---|---|---|
| Hours 0-2 | Verbal note to broker | “We will see what they say” |
| Hours 2-4 | Time-stamped log in app | Reluctant acknowledgment |
| Hours 4+ | Formal claim filing | Contract-language reply |
| Repeated shipper | Pattern documented | Broker pressure on shipper |
That visibility doesn’t change the contractual question. The detention claim is still owed. The decision to file or absorb is still the operator’s. What it changes is the operator’s ability to predict what comes after, whether the claim closes cleanly, whether the load board thins, whether the next month feels normal or quietly different. The dispatch coverage isn’t a substitute for the operator’s judgment on the claim. It’s just additional context for the call.
