The loaded movement is the part of a freight service most readily connected to revenue. A customer has goods to move, a route is proposed and a price is discussed. The equipment's position after delivery can receive less attention, particularly when the commercial and planning accounts are separated. Yet the unit does not disappear when the customer's immediate need has been met. It has a location, a condition and a possible next use. The cost of bringing those elements together belongs in the business model from the beginning.
I became interested in this while planning corridors with uneven demand between directions. A strong outward flow could create confidence about a service that depended on expensive repositioning afterwards. Local teams understood the difficulty, but the tender discussion sometimes treated it as an operating detail to be solved later. That separation made the price look simpler than the service. It also left planners responsible for absorbing a consequence that the commercial account had not fully recognised when the commitment was made.
The return problem begins before delivery
Equipment balance is not just a question of finding something to fill the return leg. The timing, type of unit and next customer's location matter. A theoretical demand opportunity may not fit the equipment available at the time it is needed. A local depot may hold units for a forthcoming commitment while another corridor arranges empty movement from farther away. Each decision can be sensible within its own remit, but their combination may be expensive for the network. The management question is how much coordination the enterprise can support without making every local decision slow.
I ask commercial colleagues to involve equipment planners before treating a corridor's outward volume as sufficient evidence of its attractiveness. This is not a request for a perfect forecast. Demand will change, and opportunities will appear that nobody could identify at tender stage. It is a request to make the principal assumptions visible: where units are expected to finish, what demand may follow and which costs arise if the expected balance does not materialise. A price can then be discussed with a more complete account of the movement it is intended to support.
The customer may reasonably ask why a return problem affects its outward price. The answer should be specific to the service, not an invitation to pay for every inefficiency in the supplier's network. We need to understand which equipment obligations arise from the proposed movement and which reflect choices we can improve. That distinction makes the commercial conversation more credible. It also prevents management from using imbalance as a permanent explanation for weak performance without examining whether the organisation's own boundaries are making the problem harder than it needs to be.
A larger pool can carry fewer empty kilometres
At Ordelune, we reviewed corridors that had been operating separate equipment pools. A unit available near one return movement was not always accessible to the team planning another. We proposed a shared pool with common availability and a process for competing requirements. The plan included eighty additional leased units at an annual cost of €240,000. Finance colleagues challenged the apparent contradiction: why did an efficiency proposal ask the company to hold more equipment? The challenge was useful because it forced us to explain the complete cycle rather than rely on the attractive word pooling.
Across comparable twenty-four-week observations, empty road distance fell from 1.28 million to 0.96 million kilometres. The reduction was substantial enough to justify attention, but it did not erase the additional lease cost or the work of coordination. Some depots spent longer resolving priorities, and the allocation rules needed adjustment when demand shifted. We had exchanged part of one problem for a different operating requirement. The decision remained worthwhile only if the wider account, including those new requirements, supported it over time.
Local managers were concerned about losing equipment they expected to need. It would have been easy to describe that concern as resistance to collaboration. In practice, they were responsible for customer commitments and had learnt that a distant assurance of availability did not always produce a usable unit. The shared pool needed a credible escalation process and evidence that local requirements would be understood. Without that, the organisation could announce a common resource while teams quietly rebuilt their own protective arrangements. Trust in the allocation process was an operating condition, not a cultural slogan.
Do not turn an operating measure into a broader claim
A reduction in empty kilometres is not the same as an equal reduction in cash expenditure. Some costs are fixed over the relevant period, vehicle schedules change and the additional equipment has its own price. I therefore keep the distance measure separate from a net financial result unless the complete calculation has been established. The board should be able to recognise an operational improvement without being asked to accept an unsupported earnings claim as part of the same sentence. Precision helps the next investment decision because it shows which benefit has actually been observed.
I apply the same restraint to environmental language. Fewer empty kilometres may be relevant to a wider assessment, but the distance figure alone does not establish a verified emissions outcome. Equipment type, energy use, the boundaries of the comparison and other factors matter. Our case describes the operating observation and leaves a broader claim to work that can substantiate it. This is not an argument against discussing environmental performance. It is an argument for giving that subject an account as careful as the one we would expect for revenue or cost.
The pool also needs continuing review. A pattern that worked across the observed periods may become less useful when customers change their shipping locations or demand moves unevenly. We should not keep a larger equipment commitment merely because it once supported a good result. Equally, one unusual period should not automatically dismantle a system that serves the network well. I want the review to examine the actual equipment cycle, the local service consequences and the cost of available alternatives, rather than defend or reject pooling as a general philosophy.
The practical lesson is that equipment deserves a place in the revenue conversation before the outward movement is sold. The commercial offer, the unit's next use and the organisation's ability to coordinate them are parts of the same proposition. When they are examined together, a larger pool may be a sensible choice. When they are separated, even a busy corridor can leave a costly trail of empty journeys that appears only after the sales success has already been celebrated.