Travel policy

Policy fails at the edges, not the centre

Almost every travel policy handles the ordinary case adequately: book in advance, choose a reasonable fare, submit the receipt. Policies fail at the edges — a cancelled leg at midnight, a crew change that has to happen regardless of cost, a traveller whose permit position changed while airborne.

Those edges are where the money is, and more importantly where the operational risk is. A policy that says only what to do in the ordinary case delegates the expensive decisions to whoever happens to be awake.

Designing for the exception

• Name the override. State explicitly when operational necessity outranks cost, and who may declare it.
• Pre-authorise. Decide the escalation before the disruption, so nobody is seeking approval at 02:00.
• Make the cheap path the easy path. Compliance follows convenience; if the compliant route is slower to book, it loses.
• Write for the reader. A policy consumed under stress must be scannable, not a document that assumes a careful reading.

Where cost policy and manning policy collide

For an operator moving crews, the two most common policies in the business are in direct tension. Cost control says take the cheaper routing tomorrow. Manning says the relief must be on the facility tonight. If the policy does not resolve that in advance, it will be resolved case by case, inconsistently, by people without the authority to make the trade.

We write the resolution in. That normally means a defined class of journey — a rotation-critical movement — where the operational constraint governs and the cost variance is expected rather than queried.

Measuring the right thing

Savings measured only against ticket price reward decisions that create operational cost elsewhere. We prefer measures that survive scrutiny: fares against a like-for-like benchmark, disruption recovery time, and the proportion of journeys that required an exception at all — the last being the most useful signal that a policy is mis-specified.