Travel programme management

A programme is an operating function

Travel is frequently owned by procurement, negotiated annually, and then left to run. That works while nothing goes wrong. It works poorly for organisations whose travel is operationally load-bearing, because the value is not captured at the negotiation — it is captured or lost in thousands of servicing decisions afterwards.

We run programmes as an operating function: supplier arrangements as the starting position, and then active management of how journeys are actually booked, disrupted and recovered.

What the desk is for

The measurable difference between programmes is usually the quality of servicing at the moment something fails. A desk that understands the operational consequence of a delayed crew change makes a different decision from one optimising rebooking cost, and the difference compounds across a year.

That requires the desk to see the operational context — the roster, the manning requirement, the certification position — not just the itinerary. It is the argument for keeping travel on the same record as the operation, which is how the group runs its own.

Data that supports a decision

• Like-for-like benchmarking. Comparison against fares genuinely available under the same conditions.
• Total cost of a journey. Including the operational cost of arriving late, not just the ticket.
• Disruption analysis. Which routes fail, how often, and what recovery actually costs.
• Exception reporting. Read as a diagnostic of the policy rather than of the travellers.

Built inside an operator

This platform exists because the group needed it. Moving our own crews for the oil and gas platform produced the routing engine, the supplier relationships and the servicing model that are now offered outside the group. It is the same pattern as SubseaCore: an internal obligation first, a product second.