What a driver should send from the dock
Three updates settle most questions later: arrival at the gate, check-in and release, with times nobody typed afterwards.
LoadHunt team · Oct 2, 2026
huntDRIVE · PlannedBy turning the clock into a record instead of a memory. A detention dispute is rarely about the hours; it is about whose note of the arrival time survives. Carriers who win them capture arrival, check‑in and release as each happens, from the driver, with times nobody typed in afterwards.
By LoadHunt team · Reviewed by LoadHunt ops · Published Sep 24, 2026 · Updated Sep 24, 2026 · 6 min read
Use the checklistWritten by the LoadHunt team and reviewed on 24 September 2026. This page makes no claim about what any regulation requires: detention between a carrier and a broker is contractual, and the rate confirmation is the primary source for every term in it.
In short: capture arrival and release when they happen, not on Friday from a text thread.
A detention claim is settled by evidence of when the truck arrived and when it was released, so the work is capturing both at the moment they happen rather than reconstructing them afterwards.
This applies where detention terms live in the rate confirmation rather than in a contract. Two things have to be true before any of it works: the confirmation names a free time and a detention rate, and the driver can send something from the dock.
Step 01
Step 02
Step 03
Step 04
Arrival is the driver’s step and release is marked the same way; the free time is dispatch’s, read off the rate confirmation. Check-in is recorded with whatever the facility will give you, and the gate matters because the dock is later.
Where it breaks down: a facility that will sign nothing, a driver who marks arrival from the truck stop down the road, and a confirmation that never named a free time at all.
Sources and assumptions
The driver side of this is huntDRIVE, and huntDRIVE is Planned, so today the capture is whatever your driver already sends you. What the extension does sit on is earlier: the rate and the broker are on the row before you call, which is where the free time gets agreed in the first place.
Two things: the rate confirmation names a free time and a detention rate, and the driver can send something from the dock.
Then the gate time and the driver’s own release message are the record. A facility that signs nothing is one of the three places this method stops working, and no software changes that.
Not yet. The driver side of this is huntDRIVE, and huntDRIVE is Planned, so today the capture is whatever your driver already sends you.
This page was written from operating practice rather than from regulation, and last reviewed on 24 September 2026. Where a claim would be regulatory it says so and points at the rate confirmation instead, because that is the document the terms actually live in.
The rate confirmation, which is the primary source for any detention term between a carrier and a broker. Nothing on this page cites a statute, because nothing on it is a statutory claim.
Picked from the same cluster: the dock, the rate confirmation and the handoff that carries both to the office.
Three updates settle most questions later: arrival at the gate, check-in and release, with times nobody typed afterwards.
LoadHunt team · Oct 2, 2026
huntDRIVE · PlannedFree time, detention rate, TONU and lumper terms: the lines that decide whether an accessorial gets paid.
LoadHunt team · Oct 1, 2026
huntTMSKeep one record each person writes into, instead of three copies passed between dispatch, the driver and the office.
LoadHunt team · Sep 24, 2026
huntTMS