Reduce Detention Time Instead of Learning to Live With It
Most fleets treat detention as weather: unpleasant, external, unavoidable. It is none of those. A truck standing inside a customer's fence is waiting for a reason that somebody controls, and KO Fleetz sets out to name that reason rather than absorb it. Billing for the wait is the consolation prize. The hours are the actual prize.
Fleet and logistics operators run KO Fleetz in production
An asset you own, parked, on somebody else's schedule
The detention charge is the least interesting part of this. A vehicle held for four hours has not lost you an hourly fee. It has lost you the second run that was never scheduled because the first one might overrun, and that run is where the margin was. Waiting consumes the two things that actually constrain a fleet: the driver's legal hours, which are finite and cannot be recovered, and the vehicle's availability, which you paid for in full whether or not it moved. KO Fleetz counts the wait against both, because those are the constraints the schedule actually runs on.
The reason it persists is a straightforward incentive failure. The wait costs the carrier and is free to the site causing it. A dock that turns trucks in ninety minutes and a dock that turns them in four hours face identical consequences, which is to say none. Nobody at that site has any reason to look at their gate process, because the cost of it lands entirely in somebody else's depreciation schedule.
There is a quieter cost in the schedule itself. Once planners know a consignee is unpredictable, they build slack around it, and slack is capacity held in reserve for a bad day, paid for on every day. The fleet shrinks to fit its worst customer. Put your own numbers through the detention cost calculator — the figure usually lands well above what the detention clause would ever have recovered, which is precisely the point.
Everybody knows which site is bad. Nobody can prove it.
Ask any transport office which consignee is the problem and you will get an answer in under two seconds. Ask what the average turnaround there was last month and the room goes quiet. That gap is the whole reason nothing changes. A commercial conversation about a site's performance cannot be opened with a strongly held belief, and everybody in it knows that, so the conversation never happens and the site stays bad.
What passes for measurement makes it worse. The driver reports his arrival time from memory at the end of a long shift, into a message typed in a lay-by. It is approximately right and completely unusable, because the first response will be the customer's own gate log showing something different, and against a documented record an approximation loses every time. Meanwhile the wait at your own yard — which is nobody's contractual claim and often longer — is not measured at all, because there is no invoice at the end of it to motivate anyone. KO Fleetz measures it regardless, since the cheapest hours to win back are the ones nobody bills for.
- Arrival times recorded by a tired driver from memory cannot survive contact with a customer's gate log, so the claim dies before it is raised.
- The clock nobody measures is the one before the bay: booked in at 06:40, called at 09:15, and only the ninety minutes of actual unloading appears in anyone's record.
- Free time differs by site and contract. A single global assumption misstates every claim and quietly discredits the ones that were correct.
- Your own depot's turnaround goes unmeasured because there is no invoice to raise at the end of it, which makes the cheapest available hours the ones nobody counts.
- Arriving ninety minutes early to be safe burns your own free time before the appointment starts, and no manual process ever catches this.
- Without a per-site history, the account manager has an anecdote. The consignee has a process document. That negotiation has one predictable outcome.
How KO Fleetz resolves this
The KO Fleetz modules that fix it
Reduce Detention Time is not one feature — it is a few KO Fleetz modules working off the same records. These are the ones that carry it.
The workflow
Locate the hours, then make them cost somebody something
Step 1: Time the wait from the vehicle
KO Fleetz draws a boundary around each site and turns entry and exit into events with a coordinate and a timestamp. The clock starts when the wheels stop inside the fence, which is what the contract meant and what nobody measures.
Step 2: Split the wait into its parts
Gate to bay, bay to release, release to gate. These have different owners and different fixes. A site that unloads fast but queues for three hours has a yard problem, not a dock problem, and the remedy is nothing alike.
Step 3: Rank the sites and show them the ranking
A per-consignee history of typical and worst-case turnaround is the one artefact that has ever changed how a customer runs a booking slot. It works because it is specific, dated and hard to dispute.
Step 4: Fix your own arrival behaviour first
Some of the wait is self-inflicted. Vehicles sent ninety minutes early against a booked slot spend their own free time in a queue. That one is fully within your control and is usually the fastest win available.
Step 5: Bill what remains, and plan around what will not move
Where a site will not improve, the wait becomes a claim with evidence and a cost priced into the lane. A consignee who genuinely cannot turn trucks faster is a commercial fact, not a mystery.
What you use
The capabilities that do the work
Drawn from across the platform — this problem is not solved by one module.
Gate-to-gate timing from position
KO Fleetz records entry and exit from where the vehicle is, so the wait is measured by the truck rather than reconstructed by a driver at the end of a fourteen-hour day.
Wait decomposed by phase
Queueing, working and releasing are timed separately, because a three-hour queue and a three-hour unload are different failures belonging to different people at that site.
Consignee turnaround league table
Sites ranked by typical and worst-case wait with dates attached, which is what an account manager needs before raising it with somebody who has a process document.
Live overdue escalation
A vehicle past its allowance raises an alert while it is still standing on the site, early enough for a person to pick up a telephone and change the outcome.
Early-arrival detection
Vehicles reaching a site well before their booked slot are flagged as a planning issue, since burning your own free time in a queue is a self-inflicted wound.
Own-yard turnaround
The same measurement runs across your depots, where a long wait is not a claim to raise but a scheduling cost with an obvious and usually uncomfortable owner.
Hours consumed by waiting
Time in a queue is counted against the driver's remaining legal hours, so the schedule reflects the wait instead of assuming it away and discovering it at 16:00.
Detention cost in lane margin
KO Fleetz prices waiting time into the corridor's profitability, which is how a customer who is pleasant to deal with and structurally unprofitable finally becomes visible.
In the product
What this looks like in KO Fleetz
What changes
The difference it makes
- The wait is measured, not recalled from memory
- Timed from the truck
- A site sees where it sits before the conversation
- Ranked and dated
- Self-inflicted waiting is counted, not just billed
- Own yard too
- Reclaimed time turns into a second run
- Hours, not invoices
How you will know it worked
Measure these
We publish no savings figure for your fleet, because we have not measured your fleet. These are the metrics that will move if this works.
| Metric | How to measure it |
|---|---|
| Median and 90th percentile turnaround per site | Gate-to-gate minutes per consignee, from vehicle position. Track both. The median is what your planner should schedule against; the 90th percentile is what actually wrecks the day, and averaging the two hides it completely. |
| Queue time as a share of site time | Minutes between arrival and reaching a bay, over total minutes on site. This is the number that separates a slow dock from a badly run yard, and it is the one that a site manager can act on directly. |
| Early arrivals against booked slots | The share of stops where the vehicle arrived materially before its appointment. This is your own contribution to the problem and the fastest thing on this page to fix, which is why it is worth measuring first. |
| Driver hours consumed while stationary at sites | Waiting time counted against legal availability, per depot and per week. This converts detention from an invoicing question into a capacity question, which is the framing that gets it funded. |
| Second runs achieved per vehicle per week | The real prize. Track whether shorter turnarounds actually convert into additional work, because if the reclaimed hours do not become runs, the wait was not the binding constraint and you have been fixing the wrong thing. |
| Own-depot turnaround | The same gate-to-gate measure at your own yards. Compare it honestly against the customer sites you complain about. This comparison is uncomfortable in a useful way roughly half the time. |
Put a number on it before you talk to anyone
The detention cost calculator is free, shows its formula, and asks nothing of you. Work out your own figure, then bring it to a demo.
Customer evidence
Fleets using KO Fleetz to do this
Customer story pending. A short, attributed quote from a fleet that used KO Fleetz for reduce detention time belongs here — the result, in their words.
Frequently asked questions
The feature proves the wait and assembles the claim. This page is about ending the wait, which is a different objective and frequently in tension with the first. A fleet that gets very good at billing detention has monetised a problem rather than solved it, and the hours are still gone. Reduction needs the measurement plus three things the module does not supply: a commercial conversation with the site, a hard look at your own arrival discipline, and the willingness to price a lane that will never improve — which is why KO Fleetz frames detention as an operational problem rather than a billing one.
Sometimes, and rarely by asking nicely. What moves a site is a specific, dated record showing they sit at the wrong end of a ranking, presented by someone who is also in a position to reprice the lane. Some customers respond quickly, because the delay is caused by something they did not know about — a booking system issuing sixty-minute slots for a dock that has never turned a truck in under ninety. Others will not move at all. For those, the honest answer is not persistence, it is pricing.
Easier, yes. Better, usually not. Detention rates are negotiated to be tolerable to the payer, which means they rarely approach what the hours are worth to you, and a customer who pays the charge has bought the right to keep doing it. The charge is worth raising, and you should. Just be clear that it is compensation, not a fix, and that a fleet whose detention revenue is rising is a fleet whose vehicles are standing still more often.
More than most fleets expect, and we will not put a number on it because it varies enormously and inventing one would be worthless. The recurring culprits are consistent though: vehicles arriving well ahead of a booked slot and burning their free time in a queue, paperwork that is wrong on arrival and takes an hour to resolve, and your own loading yard releasing vehicles late so every appointment downstream is already compromised. The first thing this work usually produces is an unwelcome finding about your own depot.
By agreeing what arrival means before you argue about when it happened. Most of these disputes are definitional rather than factual. Their clock often starts at the gate office when the driver books in; the position-based clock KO Fleetz keeps starts when the vehicle crossed the site boundary, and on a yard with a long queue at the barrier those can be an hour apart. Both records are honest. Getting the measurement point written into the contract is worth more than winning any individual claim.
Possibly not as a programme, and it depends on whether waiting is what limits you. If your vehicles are idle for want of freight, reclaiming two hours a day achieves nothing except a longer idle period, and you should be looking at utilisation instead. If your fleet is fully committed and you are turning work away or contemplating another vehicle, then detention is capacity you already own and are giving to somebody else for free. The measure that answers this is second runs achieved, not hours saved.
Get the hours back, not just the invoice
Name the consignee your drivers complain about most. KO Fleetz will lay out a month of real turnarounds there, and what your own yard looks like beside it.