Detention is the most contested money in freight precisely because it's the least documented. The carrier's clock starts when the driver says it starts. The receiver's clock starts when the paperwork says the truck checked in — if anyone wrote it down. In between sit two hours of dwell, a $300 invoice, and a broker who has to either eat it, fight it, or pass it to a shipper who'll fight it harder. Multiply by every busy dock in your network and accessorials quietly become a meaningful tax on margin and on carrier relationships.
Why brokers lose these fights
- The evidence was never captured: arrival and departure exist as GPS pings nobody pulled, driver texts nobody saved, and check-in sheets at a dock you don't control.
- It's reconstructed weeks later: the dispute lands when the carrier invoices, long after anyone remembers load 4471's Tuesday morning. Reconstruction is expensive, so small claims just get paid.
- Each fight is handled solo: pay-or-fight gets decided per-invoice by whoever's annoyed that day, with no view of which docks, lanes, or carriers generate the pattern.
- Both relationships are at stake: stiff a carrier on legitimate detention and your coverage suffers; bill a shipper on weak evidence and your scorecard does.
Evidence as a side effect of watching the load
An agent that's already monitoring every load for service reasons is incidentally building the detention file. The same tracking review that catches a late truck records when it arrived at the dock; the dwell that becomes an exception becomes a timestamp; the driver follow-up and receiver communication land in the load history instead of a personal inbox. The audit trail you keep for accountability turns out to be the accessorial evidence you were missing.
- 1Dwell becomes an exception, liveTruck arrives, clock runs, threshold trips — an exception opens with the arrival timestamp while the driver is still at the dock, not three weeks later on an invoice.
- 2The file assembles itselfTracking events, geofence times, driver communications, and dock notes attach to the load record — the same way missing PODs get chased, the detention picture gets captured.
- 3The shipper hears about it earlyA drafted heads-up — 'your receiver is running 90 minutes behind, detention exposure starting' — goes through approval and out while there's still time to work the dock. Billing surprises are how detention sours accounts.
- 4Pay-or-fight becomes a data decisionWhen the invoice arrives, the record answers it. And across a quarter, the pattern report — which receivers, which lanes, which carriers — tells you what to fix or reprice instead of re-litigating one invoice at a time.
The Haulbase Agent builds this record alongside your current TMS as part of watching your freight; in Haulbase ATMS the dwell exceptions, communications, and per-load evidence live natively in the system of record. Either way, financial decisions — paying, billing, disputing — stay with your people through approval. The agent's job is making sure that when money gets argued about, you're the side holding the file.