How Do Freight Brokers Recover Detention Charges: The Evidence Chain Most Never Assemble

How do freight brokers recover detention charges. Most of the time, they do not, because the proof is scattered across three systems that never talk to each other. The appointment time lives in the TMS. The gate-in and gate-out timestamps live in the carrier's ELD. The actual door assignment and check-in live in the shipper's dock scheduler. Each system holds one slice of the dwell story, and the recovery claim never gets filed because nobody assembles the full evidence chain. The detention happened. The money was real. But the screen that would have proven it was never built, so the charge quietly became absorbed margin.

How do freight brokers recover detention charges when the proof lives in three systems?#

Freight brokers recover detention charges by assembling the appointment time, the gate timestamps, and the dock check-in record into one dwell timeline, then attaching that timeline to the invoice as evidence before the claim is filed. The recovery is not blocked by the contract. Most rate confirmations already specify free time, usually one or two hours at pickup and delivery, and a per-hour detention rate after that, typically in the range of 50 to 100 dollars an hour according to FreightWaves. The entitlement exists on paper. What goes missing is the proof.

The proof is fragmented by design. The broker's TMS knows the load was scheduled for an 0800 appointment at a grocery distribution center outside Atlanta. The carrier's electronic logging device, governed by the hours-of-service recordkeeping rules in 49 CFR 395, knows the truck rolled through the gate at 0742 and did not roll back out until 1218. The shipper's dock scheduler knows the appointment slipped, the door was not ready, and the driver checked in at a podium at 0755. Three systems, three timestamps, one truck that sat for four and a half hours against a two-hour free window. No single screen shows all three, so the dispatcher who could have filed two and a half hours of detention never saw the case clearly enough to act on it.

This is what we call a SEE-mode problem: show me what I am missing. The detention is not hidden because it is complicated. It is hidden because the evidence is spread across three logins and nobody assembles it under the pressure of forty active loads. A SEE-mode dwell timeline does the assembly automatically, binds the three records to one shipment, and keeps every source visible so the broker can put a defensible number in front of the shipper.

What causes detention at shippers, and why does it stay invisible?#

Detention at shippers is caused by appointment slippage, unready doors, labor shortages, and yard congestion, and it stays invisible because the only system most brokers watch (the TMS) records the intended appointment, not the time the wheels actually stopped turning. The TMS says 0800. It has no idea the truck sat until 1218. By the commercial record, the load looks clean.

The scale of the problem is not anecdotal. ATRI's 2024 detention research found that in 2023, drivers reported detention on 39.3 percent of all stops, rising to 56.2 percent for refrigerated trailers and 42.5 percent for spot-market fleets. That same research put the direct cost of detention to the industry at 3.6 billion dollars in 2023, with another 11.5 billion dollars in lost productivity. Detention is not a tail risk. It is a structural feature of how freight moves, and it lands hardest on exactly the produce and grocery lanes where margins are already thin.

Detention stays invisible to the broker for a specific structural reason: the broker sits between the shipper who caused the dwell and the carrier who absorbed it, and the broker's primary system of record was never designed to witness the event. The TMS records intent. The ELD records execution. The dock scheduler records what the facility actually did. The broker watches the first one and is blind to the other two. So the dwell that proves the claim is recorded faithfully by two systems the broker does not habitually open, and the one system the broker lives in says everything went fine.

The downstream consequence reaches past money. FMCSA research summarized in its work on detention and crash risk found that drivers experienced detention on roughly one in ten stops in an earlier study, averaging 1.4 hours beyond the two-hour standard, and a related Office of Inspector General analysis concluded that a fifteen-minute increase in average dwell time raises the expected crash rate by 6.2 percent. ATRI's 2023 data reinforced the safety link: detained trucks drove 14.6 percent faster on average than trucks that were not detained, because a driver who burns four hours at a dock tries to claw the time back on the road. Detention is a margin problem for the broker and a safety problem for everyone behind the truck.

What is the difference between detention and demurrage, and why does it matter for recovery?#

Detention is a per-hour charge for holding a truck or chassis beyond its free time at a facility, while demurrage is a per-day charge for leaving cargo in an ocean container or at a port terminal beyond its free time. They are different clocks, different counterparties, and different evidence, and conflating them is one reason claims get rejected.

Detention runs against the carrier's equipment and the driver's hours. The free window is short, usually one or two hours, and the meter runs hourly after that, commonly cited at around 75 dollars per hour by FreightWaves. The evidence that supports a detention claim is a tight timeline measured in minutes: gate-in, check-in, gate-out. Demurrage, by contrast, is an ocean and port concept governed by free days at the terminal, and the regulatory frame is different. The Federal Maritime Commission requires container carriers and marine terminal operators to issue detention and demurrage invoices within 30 calendar days of when charges were last incurred, with at least 30 days for the billed party to dispute, which is a fundamentally different recovery rhythm than a same-week trucking detention claim.

The distinction matters for recovery because the two charges demand different proof at different time granularities. A demurrage dispute turns on calendar days and terminal free-time clocks. A detention dispute turns on minute-level gate timestamps. A broker who files a detention claim with day-level appointment data instead of minute-level gate data has handed the shipper an easy rejection. The SEE-mode dwell timeline matters here precisely because it preserves the granularity the claim type requires: it carries the ELD gate timestamps to the minute, not the rounded appointment window the TMS happened to store.

Why does the recovery claim never get filed?#

The recovery claim never gets filed because filing it requires assembling evidence from three systems under time pressure, and the person who could file it only ever sees one of the three. ATRI's research makes the cost of this gap explicit: even among fleets that bill for detention, the invoices are honored less than half the time. ATRI's 2024 study reported that 94.5 percent of fleets charge detention fees, but they are paid on fewer than 50 percent of those invoices. The charge is rarely disputed on principle. It is disputed because the bill arrives without receipts.

Walk the failure forward. A driver for a carrier like Schneider sits four hours at a shipper. The carrier, if it is organized, sends the broker a detention invoice citing the dwell. The broker now has to decide whether to pass that charge to the shipper. To do that defensibly, the broker needs to reconcile the carrier's claimed dwell against the appointment in the TMS and, ideally, against the dock scheduler's own check-in record. That reconciliation is three logins and a phone call per load. At forty loads a month out of one shipper, multiplied across a book of business, nobody does it. The broker either eats the carrier's detention to keep the carrier relationship, or pushes back without evidence and loses the carrier's trust. Both outcomes leak money.

The deeper failure is that the absence of evidence compounds. Because the broker cannot prove the dwell, the broker cannot show the shipper a pattern. Because there is no pattern, the shipper has no incentive to fix the unready doors. Because the doors stay broken, the detention recurs next week, and the cycle repeats with the same invisibility. The single missing artifact, an assembled dwell timeline with its sources attached, is the thing that would break the loop. This is the same fragmentation problem we examined in unifying TMS, ELD, and dock data without replacing your TMS: the value is not in any one system, it is in the join that no one maintains.

How does a SEE-mode dwell timeline attach receipts to a detention claim?#

A SEE-mode dwell timeline attaches receipts to a claim by binding the TMS appointment, the ELD gate timestamps, and the dock-scheduler check-in to one shipment record, then keeping each source row visible and linked next to the value it produced. Instead of a dispatcher reconstructing the dwell from memory and a phone call, the timeline is already built when the carrier's invoice arrives.

Concretely, the unified shipment carries a dwell timeline that reads in order: appointment 0800 (source: TMS load 48213), gate-in 0742 (source: ELD trip for tractor 5567), dock check-in 0755 (source: dock scheduler, door 14), gate-out 1218 (source: ELD trip for tractor 5567). The contracted free time is two hours. The measured dwell from check-in to gate-out is four hours and twenty-three minutes. Billable detention is two hours and twenty-three minutes at the rate on the rate confirmation. Every number in that sentence links back to the system row that produced it. When the broker forwards the claim to the shipper, the shipper is not being asked to trust the broker's recollection. The shipper is looking at its own dock scheduler's check-in time sitting next to the carrier's own ELD gate timestamps. There is nothing left to dispute.

This is the inspectability principle the Mithrilis platform is built on: sources are visible and every cited number links back to its source row. A unified detention number that you cannot trace is just another number the shipper will reject. A unified detention number with its three sources attached is the artifact that turns a 50-percent payment rate into a defensible claim. Mithrilis is not a TMS replacement and it is not workflow automation that auto-fires invoices. It is the intelligence layer that assembles the evidence the broker was always entitled to bill but could never prove, drawn from the connected systems the broker already runs.

What does a worked detention recovery look like on a real lane?#

A worked detention recovery looks like a single dwell timeline turning a quietly absorbed cost into a filed, paid claim and a renegotiated lane. Take a broker moving 40 loads a month out of a produce shipper in California's Central Valley, running the Bakersfield to Dallas reefer lane with a carrier like J.B. Hunt on the back of it.

By the TMS, this lane is healthy. The rate is good, the carrier is paid fairly, and the accessorial column is mostly empty. Nobody flags it. Now bring in the other two systems. The ELD data shows trucks arriving at that shipper sit an average of three hours and forty minutes before they are loaded, well past the two free hours the rate confirmation allows, and deep into the driver's 14-hour on-duty window under the hours-of-service rules. The dock scheduler confirms the cause: appointments slip, doors are not ready at the booked time, and the gate timestamps tell the same story week after week. Across 40 loads, that is roughly 66 hours of billable detention a month that never became an invoice, because the TMS, the only screen anyone opened, said the loads were fine.

Once the three systems resolve to a shared shipment, the SEE-mode dwell timeline flags this shipper as a repeat offender. The pattern is no longer a feeling the night dispatcher has. It is a number with its sources attached: average dwell, count of loads over the free window, total billable detention hours, each backed by the gate timestamps and the appointment record. The broker can now do two things that were previously impossible. First, file the accumulated detention with receipts, recovering the per-hour charge the rate confirmation already permitted. Second, take the dwell pattern to the shipper at renewal and either fix the dock problem or reprice the lane to reflect its true cost. The broker did not work harder. The broker could finally see what was already true in the data, sitting in plain sight across three systems that never spoke to each other.

How does the same dwell timeline work for an asset carrier?#

The same dwell timeline works for an asset carrier by exposing the true cost of a facility against the carrier's own equipment and driver hours, rather than defending a margin claim against a shipper. A broker absorbs detention as eroded margin on a load it brokered. An asset carrier absorbs it as eroded utilization on a truck and a driver it owns, which makes the carrier even more sensitive to dwell than the broker is.

For an asset carrier, the three systems are slightly different but the structure is identical. The dispatch system holds the planned appointment. The ELD, which the carrier owns outright, holds the gate-in and gate-out to the minute. The facility's dock scheduler, or the carrier's own arrival app, holds the check-in. When those three resolve to one shipment, the carrier can see which facilities consistently burn its drivers' hours-of-service clock, which lanes deadhead the longest after a late release, and which customers are quietly the most expensive to serve even when the line-haul rate looks attractive. A driver detained four hours has lost four hours of the 14-hour window in which the carrier can legally earn revenue from that truck. That is not just a billing question. It is a utilization and a safety question, the same one FMCSA's detention research raises about fatigue and crash risk.

The intelligence mode is the same for both audiences: SEE, show me what I am missing. For freight brokers, the missing thing is a defensible detention claim with receipts. For asset carriers, the missing thing is the true cost of a facility measured against owned equipment and finite driver hours. The structural problem and its solution are identical. Connect the systems you already run, resolve them to a shared shipment, and keep every source visible so the dwell timeline can be trusted in a dispute. This is the conviction we wrote into our manifesto: you should be able to verify every result, because intelligence you cannot inspect is intelligence you will not act on.

Detention recovery is a data problem, not a billing problem#

Brokers treat unrecovered detention as a billing discipline problem: file faster, chase harder, train the team. It is not. It is a data problem wearing a billing costume. The reason the claim never gets filed is that the proof does not sit in one place long enough to assemble.

Mithrilis fixes the data problem underneath. It connects your TMS, the carrier ELD, and the shipper dock scheduler and resolves them into one dwell timeline, so the appointment, the gate-in, the gate-out, and the contracted free time line up on a single screen with every timestamp traceable to its source. The evidence chain stops being something a person reconstructs and becomes something the record already holds.

From there the discipline takes care of itself. Atlas can answer which shippers cost you the most dwell this quarter, and an agent can file and follow the claims your team never has the hours for. Fix the data, and the recovery follows. See it on your lanes.

Related Mithrilis capabilities

• The Mithrilis platform

  How connected data becomes verifiable intelligence with sources on every field.

• For freight brokers

  Detention claims that ship with receipts attached from a unified dwell timeline.

• For asset carriers

  True facility cost measured against owned equipment and finite driver hours.

• Unify TMS, ELD, and dock data

  The connect-and-resolve foundation the dwell timeline is built on.

Frequently asked questions

How do freight brokers recover detention charges?

Brokers recover detention by assembling a complete dwell timeline from the TMS appointment, the carrier's ELD gate-in and gate-out timestamps, and the shipper's dock-scheduler check-in, then filing the claim with those source records attached as evidence. The recovery usually fails not because the detention did not happen but because the proof is scattered across three systems nobody reconciles, so the invoice arrives without receipts and gets rejected.

What causes detention at shippers?

Detention at shippers is caused by appointment slippage, doors that are not ready at the booked time, dock labor shortages, and yard congestion. It stays invisible to the broker because the TMS records the intended appointment, not the time the truck actually waited. ATRI found drivers were detained on 39.3 percent of all stops in 2023, rising to 56.2 percent for refrigerated trailers.

What is the difference between detention and demurrage?

Detention is a per-hour charge for holding a truck or chassis beyond its free time at a facility, billed against the carrier's equipment and the driver's hours. Demurrage is a per-day charge for leaving cargo in an ocean container or at a port terminal beyond its free days. They run on different clocks, involve different counterparties, and require different evidence, so a detention claim filed with day-level data instead of minute-level gate timestamps will usually be rejected.

What are detention recovery best practices for brokers?

The core best practice is to attach receipts before you file: assemble the appointment, the gate timestamps, and the dock check-in into one timeline so every number traces back to its source. Track dwell by facility to surface repeat offenders, preserve minute-level ELD granularity for the claim, and bring the documented pattern to renegotiation. ATRI found that even when fleets bill detention, fewer than 50 percent of those invoices are paid, almost always because the bill arrives without evidence.

How much does detention cost the trucking industry?

ATRI's 2024 research estimated that driver detention cost the industry 3.6 billion dollars in direct expenses in 2023, plus an additional 11.5 billion dollars in lost productivity. For-hire trucking alone exceeded 135 million total hours lost to detention. A typical detention rate runs 50 to 100 dollars per hour after a free window of one or two hours.

Is detention a safety problem as well as a cost problem?

Yes. FMCSA-linked research found that a fifteen-minute increase in average dwell time raises the expected crash rate by 6.2 percent, and ATRI's 2023 data showed detained trucks drove 14.6 percent faster on average than trucks that were not detained, as drivers try to recover lost hours on the road. Detention consumes the driver's 14-hour hours-of-service window under 49 CFR 395, which is why it is a fatigue and safety issue, not just a billing one.

Do I need to replace my TMS to recover detention?

No. A dwell timeline reads from the systems you already run, the TMS, the carrier's ELD or telematics feed, and the dock scheduler, and resolves their records to one shipment without migrating anything. The point is not a new system of record. It is the intelligence layer that assembles the evidence chain you were always entitled to bill but could never prove in one place.