A transport organisation can explain a late delivery through a sequence of locally reasonable decisions. The collection team worked to the booking received. The terminal followed its handling window. The rail operator ran the movement available to it. The onward planner acted on the status message in the system. Each explanation may be accurate, yet the customer still has goods arriving after the moment they were needed. I have learnt to be cautious when a service review becomes a search for the internal account under which nobody appears to have failed.
The customer did not purchase a collection of departmental explanations. It purchased a movement with an understood arrival commitment. That does not mean a forwarder controls every condition or can eliminate every disruption. It does mean that the service should be designed around the whole journey, including the transfers between organisations and the actions required when the intended connection is lost. Those transfers are part of the product even when they are less visible than the rail timetable or the road collection charge.
A satisfactory leg can still leave an unsatisfactory journey
My early claims work made this distinction difficult to ignore. A file often began with a simple description of lateness and became more complex as we reconstructed the sequence. One team's completion was another team's starting condition, but the two teams had not always attached the same meaning to it. An arrival notification might not establish that a unit could be collected. A collection completed late in one window might leave no practical route into the next. The problem was sometimes less an isolated failure than a promise built without enough attention to the interfaces.
This is why I want commercial and operating colleagues involved together before a service is sold. The conversation needs the customer's receiving requirement, the booking pattern, collection conditions, terminal handling and onward arrangements. If the offer depends on all of those elements working at their most favourable limit, it may be more fragile than its timetable suggests. We should examine that fragility while there is still a choice about the product, rather than discover it through repeated exceptions that frontline colleagues are expected to resolve.
On one Ordelune corridor, we moved the standard booking cut-off eight hours earlier. The original offer had left little room between a late booking and the terminal sequence needed for departure. Sales colleagues were right that the change reduced flexibility. Some late-booking volume moved away. We also added collection coordination at an annual cost of €96,000. The decision was therefore not a clever way to obtain reliability without giving anything up. It changed what the customer was buying and what we had to resource in order to provide it.
Put the conditions into the offer
Arrival within the agreed receiving window rose from 88% to 95% in successive twelve-week observations. I regard that as useful evidence, with limits. The shipment and customer mix changed, and several operating actions accompanied the cut-off revision. We could not honestly assign the entire improvement to one decision. Late-booking volume on the standard product fell by 11%. Keeping that consequence beside the service measure helped us discuss whether the revised offer was a better fit, rather than present the result as an unqualified improvement for everyone.
Customers have different reasons for booking late. Some face production variation they cannot readily remove. Others have internal approval habits that may be more flexible than they initially believe. The executive should not assume that every customer can adapt to the same earlier deadline, but neither should the business conceal the deadline it actually needs. A useful commercial conversation identifies the constraint and considers a different product where necessary. It is better to explain a narrower standard commitment than sell an apparently generous one whose real conditions emerge only after a problem.
The same reasoning applies to receiving windows. A late arrival can have a modest effect for one customer and disrupt a tightly planned operation for another. A single network punctuality figure cannot fully describe those differences. I want the service review to consider whether the commitment matched the customer's stated need, and whether exceptions were communicated early enough for the customer to act. That does not require publishing every customer's private operating detail. It requires using the relevant context internally when deciding which service the company should offer and how it should be supported.
Make the exception visible without making it the product
There will always be movements that need attention beyond the standard sequence. The question is whether the organisation has a workable way to handle them or relies on repeated informal intervention by experienced individuals. An exception process should identify who can decide, which alternatives are available and what the customer needs to know. It should also leave a record that helps the business see when an exception has become frequent enough to challenge the standard product. Otherwise, heroic recovery work can hide a service design that requires too much heroism.
I am wary of the opposite response, in which every unusual movement becomes evidence that the offer must be redesigned immediately. A freight network operates amid variation, and not every departure from plan reveals a structural flaw. We need to distinguish a rare event from a recurring mismatch between the sold promise and the operating conditions. That judgement benefits from both data and the experience of people handling the movements. A dashboard can show repetition; a planner can explain why the repetition occurs and which apparent solution would create another problem downstream.
The forwarder's responsibility also has boundaries. Purchasing rail capacity does not transfer the operator's technical and safety authority to the commercial team. A customer escalation is not permission to improvise an operating instruction outside that authority. I want our organisation to be clear about the decisions it can make and the professionals whose judgement it must respect. Clear boundaries help us coordinate the service more credibly because they prevent an executive promise from depending on control the company does not actually possess.
For me, a good freight product includes the handover conditions in its design, price and explanation. It gives the customer a realistic basis for planning and gives colleagues a commitment they can work towards without relying on an unwritten exception at every stage. The test is not whether each department can describe its own performance favourably. It is whether the complete movement makes sense at the customer's door, and whether the organisation can explain the remaining uncertainty without changing the meaning of the promise after the event.