Four hours back on the motorway
A driver delivers a pallet to a distribution centre near Exeter at one in the afternoon. The job was well paid. Now they have a four-hour drive back to the Midlands with an empty van. The controller did look for a return load in the morning, but it was busy, and by the time they remembered, the driver was already on the way back.
Meanwhile, a customer in Bristol had phoned at eleven asking for a collection going to Birmingham tomorrow. Nobody connected the two.
Why return loads are missed
Finding a backload is a matching problem, and controllers are doing it in their heads under pressure. The information is spread across your own bookings for today and tomorrow, regular customers who might have work near the drop, and exchange postings. Timing is tight: the return load has to fit after the delivery and before the driver's day ends.
| Source of return work | Why it is not used |
|---|---|
| Your own bookings near the drop point | Not searched by location |
| Tomorrow's jobs that could be done today | Not visible to the controller in the moment |
| Regular customers in that area | Nobody thinks to ask them |
| Courier exchange postings | Checked only when someone has time |
| Jobs on the route home | Only the destination is considered, not the way back |
What empty miles cost
Fuel, driver time and vehicle wear on every empty return, which the outbound price has to carry. That makes your long-distance quotes higher than a competitor who does find return loads, so you lose work at the quoting stage too.
Owner drivers feel it directly. A driver paid for the outbound job only, driving home empty, earns less for the day than they expected, and the good ones find firms that keep them loaded.
There is an environmental cost as well, which some of your larger customers now ask about in tenders.
The return-leg matching we build
- When a long job is booked, the drop point, expected finish time and route home are calculated.
- Search of your own bookings for today and tomorrow with collections near the drop or along the route home, and deliveries back towards base.
- Suggestions of regular customers with a history of work from that area, so a controller can ask them.
- Exchange postings matching the location and time, where the exchange offers a way to search or be notified, shown alongside.
- A list of options for the controller with the extra miles, time and revenue for each, ready to book.
- A record of return legs loaded and empty, by route and area, so you can see where to look for regular return work.
Price for the outbound job can also reflect whether a return load is likely, which is your pricing decision.
What changes
Return-load options appear when the long job is booked, not when the van is already heading home. Controllers make a quick decision rather than a search. Drivers spend fewer hours empty. And you can see which routes regularly need return work, which is useful when talking to customers in those areas.
Signs you are driving home empty
- Long same-day runs routinely return empty.
- Return loads depend on a controller remembering to look.
- Exchange postings are checked only when there is time.
- You do not know how many empty miles you run each week.
- Owner drivers complain about empty returns.