Ask most transport operators where their money leaks, and they will say fuel, tyres or breakdowns. Fewer will say the gate. Yet a truck that arrives at 06:00 and only leaves the customer's premises at 14:00 has lost most of a working day, and in many cases nobody has recorded it, charged for it or even noticed it.
Waiting time at collection and delivery points is one of the quietest costs in road freight. It does not show up as a line on a maintenance report. It shows up as a truck that did one trip instead of two, a driver who ran out of hours, and a customer at the next stop who is now asking where you are.
Why waiting time goes unrecorded
The usual reasons are simple and very human:
- Nobody wrote down the times. The driver knows he waited five hours, but the only record is a phone call or a remark at the end of the week.
- The times exist, but in the wrong places. Arrival time is on a gate slip, departure time is on a signed POD, and the dispatcher's version is in a WhatsApp chat.
- The rate agreement is vague. The quote says "waiting time as per agreement", but the agreement has no free hours, no hourly rate and no process for claiming.
- Nobody wants to upset a good customer. So the cost is absorbed, load after load, until it is just accepted as normal.
The result is that the transporter carries a cost the customer controls. The customer decides how quickly trucks are loaded or offloaded, but the transporter pays for the delay.
Start by defining what you are measuring
Before you can charge for waiting time or manage it, you need consistent definitions. A workable set of timestamps for every stop looks like this:
- Arrived at site (at the gate or in the queue).
- Started loading or offloading (when the truck was actually called in or docked).
- Finished loading or offloading.
- Departed site.
With these four, you can separate the delay before the truck was called in (the customer's queue) from the time it took to load (which may involve your driver, the product or the equipment). That distinction matters when a customer disputes a claim, and it matters when you are trying to work out whether the problem is the site or your own process.
Put the rules in the agreement, not in the invoice
Detention charges are far easier to recover when they are agreed in advance. Cover these points in your rate agreements or quotes:
- The number of free hours allowed at each end of the trip.
- The hourly or part-hourly rate after that, and whether it differs for different vehicle types.
- How waiting time is evidenced: gate times, driver timestamps, signed documents.
- The window within which a claim must be raised, so old disputes do not pile up.
- What happens if the truck arrives outside the booked slot. Fair terms protect both sides, and a customer is far less likely to resist a clause that also covers your late arrivals.
A customer who has agreed to the terms beforehand will usually accept a claim backed by clear times. A customer who sees the charge for the first time on an invoice will usually dispute it.
Capture the times as the work happens
Reconstructing waiting time a week later from memory is where claims fall apart. The better approach is to have the driver or dispatcher record each status as it happens, so the timestamps are created by the operation rather than by the person in accounts.
This is one of the practical benefits of running trips through a TMS with a driver app, such as TitanFleet: status updates carry a time, they sit against the load, and the same record is available to operations, billing and management. You are not chasing the driver for his version of the day. Whatever tool you use, the principle is the same: one record, created at the time, attached to the load.
Turn the data into site intelligence
Once you have a few weeks of timestamps, you can ask more useful questions than "how late were we?"
- Which sites are consistently slow? Compare average time on site across your regular collection and delivery points.
- Is it a particular time of day? Many sites are fine at 07:00 and gridlocked at 11:00. If so, you can book earlier slots or avoid the peak.
- Is the delay before or after the truck is called in? A long queue points to the customer's capacity. A long loading time may point to product readiness, paperwork or equipment.
- Is the rate still worth it? A load that looks profitable on distance may be a poor one once five hours of standing time are included.
This last question is the most valuable. A route can look healthy on paper while the real revenue per truck-day tells a different story. Waiting time belongs in your costing, whether or not you manage to bill for it.
Use the numbers in the conversation with the customer
Most site delays are not malicious. They come from understaffed docks, unplanned arrivals or unclear booking systems. When you can show a customer that their site averaged a particular waiting time across the last month, with dates and times, the conversation changes from complaint to problem-solving. Sometimes the outcome is a detention charge. Sometimes it is a booking slot, a dedicated bay or a different collection window, which helps both of you.
A simple place to start
You do not need to overhaul everything. This week, pick your five busiest customer sites and do three things:
- Make sure arrival, start, finish and departure times are recorded for every trip to them.
- Check whether your agreements actually state free hours and a waiting rate.
- At the end of the month, rank the sites by average time on site.
You will probably find one or two sites quietly costing you more than any fuel price movement. Once you can see them, you can charge for them, schedule around them or decide whether the work is worth taking at all.