A truck reaches a customer’s gate at 09:40 and leaves at 12:05. Everyone involved knows it waited — the driver, the dispatcher, the loading crew. Two and a half hours of a working truck, and none of it reaches the invoice.
This is almost never a tracking problem. Most carriers already have GPS on every truck, and the position history is sitting in a telematics portal right now. The problem is what that history can and cannot tell you.
Speed zero is not an answer
A truck queueing at a customer’s gate, a truck refuelling and a truck stuck behind an accident look identical in the data. All three are speed zero for a while, then they move again. Only one of them is somebody else’s fault.
So the wait gets handled the way everything else gets handled: somebody remembers it, or somebody does not.
By hand
- The truck enters the customer’s yard
- The driver mentions the wait in the group chat
- The dispatcher notes it down, or does not
- At month end somebody opens the telematics portal
- Nobody can say which hours were the customer’s
- The line is dropped from the invoice
With a system
- Entering the zone starts the clock
- Free time runs out and the dispatcher is warned
- The excess is priced and attached to the trip
The dashed steps are the ones that depend on somebody remembering.
The money is not lost at the gate. It is lost three weeks later, when the invoice is being put together and nobody can defend the line.
Four questions about every stop
A stop becomes billable only after it survives four questions. None of them is clever on its own; the value is in asking all four, every time, without anyone having to think about it.
-
Is the truck inside a customer’s zone? A geofence is drawn around each loading and unloading site. Outside every zone, a stop is the carrier’s own business: fuel, rest, traffic, a tyre.
-
Is that customer on this trip? A truck can stand in a yard it is not working for today. Same gate, same zone, nothing to charge. The trip is what makes the zone mean something.
-
Did the load change? A weight reading that rises means loading, one that falls means unloading. No change at all usually means the truck was waiting for something other than cargo.
-
What does the contract allow? Every customer contract sets its own free time, often a different allowance for loading and for unloading. Only the excess over that is billable.
The contract decides, not the clock
This is the part most carriers get wrong when they try to solve it in a spreadsheet. There is no such thing as a long wait in the abstract. There is only a wait measured against what a particular customer agreed to.
Two hours at one customer is free. The same two hours at another is an hour and a half of billable time. Nothing in the GPS data knows the difference.
| The stop | What the GPS shows | What can be invoiced |
|---|---|---|
| Queue at the customer’s gate | Speed 0 · 2 h 25 min | The 25 minutes beyond free time |
| Refuelling | Speed 0 · 20 min | Nothing |
| A yard the truck is not working for | Speed 0 · 15 min | Nothing |
| Driver rest | Speed 0 · 30 min | Nothing |
| Unloading inside free time | Speed 0 · 1 h 45 min | Nothing |
Sample figures. Five stops, one of them billable — and the portal shows all five the same way.
A charge has to survive the conversation
The customer’s answer to a waiting charge is nearly always the same sentence: “We did not keep you that long.”
At that point the carrier needs more than a number. It needs the arrival time, the departure time, the zone the truck was standing in and the moment the weight changed. All of it recorded while it happened, not reconstructed afterwards from a chat thread.
A charge stored together with its evidence is a conversation that ends in a minute. A charge stored on its own is a conversation that ends with the line being removed.
When this is not worth building
We build these systems, and there are three situations where doing so is the wrong order of work:
- When the contracts say nothing about free time. No software can bill what was never agreed. Put the clause into the contracts first. That costs nothing and it is most of the value.
- When the sites are not fixed. A geofence needs a place that repeats. A carrier delivering to a different address every day has nothing to draw a zone around, and the four questions collapse to one.
- When waiting is genuinely rare. If trucks seldom pass their free time, the recovered amount will not pay for anything. Measure it by hand for a month before deciding.
Where to start
Start with the measurement, not with the invoice. Take one month of telematics history and the free-time clauses from your five largest customers, and work out by hand how many hours fell outside the allowance.
That number is the whole business case. If it is small, you have learned something cheaply. If it is not, you now know what the first process to automate is, and you can start with waiting time alone rather than with a system for everything.
Which of those two it is for your operation is something we can usually tell after one conversation. If the answer is that your contracts need the work rather than your software, we say that too.
Projects behind this article
-
Sahil Transport
Logistics · Fleet data platform
-
ATLAS BIP Logistics ERP
Logistics · TMS and ERP product
What we build in this area
-
Logistics software & TMS
Transport management, fleet telematics, logistics ERP and driver apps — with CMR, e-qaimə and AYNA documents built in.
-
Data, BI & forecasting
Power BI dashboards, data integration and warehouses, telematics data platforms, forecasting and machine learning.