Detention Time Tracking Software That Proves the Wait

From the vehicle. A boundary around the site produces an entry event the moment the truck crosses it and an exit event when it leaves, each with a timestamp and a coordinate. The driver can add context — a bay number, a reason, a photograph of the gate ticket — and that context is welcome, but the clock does not depend on it. This matters because the times a driver is least likely to record accurately are exactly the long, frustrating waits you most want to charge for.

It holds up better than anything else you have, and it is not a verdict. What the record proves is that a specific vehicle was inside a specific boundary between two specific times, continuously, with position reports throughout. What it cannot prove is what happened in there or who was at fault. Whether it converts into a paid invoice depends on your contract's wording, not on the software. Fleets that win these conversations send the evidence early and consistently rather than once a quarter in anger.

Almost never, and treating it that way is how claims get rejected. Most contracts grant free time for the loading or unloading itself, and detention is only the time beyond that allowance. KO Fleetz splits the visit accordingly: total on site, free allowance, the working window, and the chargeable overage. It also keeps the parts you cannot bill for, because unbillable waiting is what wrecks your schedule and it deserves to be measured even when no money attaches to it.

Yes, and it is usually the first place to look. The same fences and the same clock run on your own yards, producing gate-to-gate turnaround per vehicle, per bay and per shift. Nothing is billable here, which is the point: the wait is entirely yours and entirely fixable. Fleets that start by measuring customers and never turn the lens around tend to discover their worst site is one they own, which is an awkward finding and a much cheaper one to act on.

They could, and the design assumes somebody eventually tries. The fence is drawn to the site boundary, so a vehicle standing on the approach road sits outside it and no detention accrues. Reports show arrival relative to the booked slot, which makes turning up early visible rather than rewarded. Beyond that this is a policy matter, not a software one. Any time-based measure can be nudged, and the honest position is that the record makes nudging visible rather than impossible.

They overlap and answer different questions. Proof of delivery establishes that goods were handed over, in what condition and to whom, with a signature or a photograph as evidence. This module measures time, and time on site is mostly spent before and after the handover — queuing, waiting for a bay, waiting for paperwork. A delivery can be perfectly evidenced and still have cost you half a shift. Run both: the delivery event is a useful marker inside the visit, not a substitute for timing it.