The gap between activity and benefit
Most airline transformation programmes are honestly run and genuinely busy. That is precisely the problem. Programme reporting is built around what the programme controls — initiatives launched, process changes implemented, systems cut over — and boards receive dashboards dense with green status. Meanwhile the question the audit committee and CFO care about goes quietly unanswered: has the cost base actually moved, and has the revenue line actually improved, by the amount the business case promised?
The gap is rarely deliberate. It emerges from mechanics. Benefits are estimated at initiative level by the teams sponsoring the initiative, aggregated by a programme office that has no independent means of validation, and reported against a baseline that was set once and never revisited. Each step is defensible in isolation. Together they produce a benefits number that nobody would sign an accounts note on.
The four ways reported benefits inflate
When we examine transformation benefit claims, the same four mechanisms account for most of the inflation:
- Double counting. Two initiatives claim the same saving — a procurement renegotiation and a consumption-reduction initiative both book the full reduction in the same cost line. Nobody reconciles claims back to a single ledger view.
- Baseline drift. The "before" position was set at business-case approval and never adjusted for fleet changes, network changes, fuel price movement or inflation. Savings are measured against a world that no longer exists.
- Optimistic phasing. Benefits scheduled to land in later quarters slide forward in every re-plan, but the cumulative total is never restated. The curve keeps its shape; only the calendar moves.
- Gross-for-net substitution. Implementation costs, transition costs and benefit erosion (staff re-hired under different headings, discounts recontracted) are excluded, so gross benefit is reported where net benefit was promised.
None of these requires bad faith — only the absence of anyone whose job is to disbelieve the number.
Anchor every claim to the ledger
The single most useful discipline in a benefit review is ledger anchoring: every claimed benefit must be traceable to a specific general-ledger line, cost centre or revenue stream where the movement should be visible. If an initiative claims a reduction in ground-handling cost per turn, the review asks: which stations, which contracts, which invoice population — and does the trend in that population, adjusted for volume, show the movement?
A benefit that cannot be found in the ledger is not a benefit. It is a forecast wearing a delivered badge.
Ledger anchoring also forces the baseline conversation. To say a cost line moved, you must state what it would have been without the programme — which means the baseline has to be maintained as a living model, adjusted for capacity, traffic and input prices, not a frozen spreadsheet from the approval paper.
Designing an independent benefit review
A credible review is neither an audit of the programme office nor a re-run of the business case. It is a targeted examination of the largest and most fragile claims. In practice that means:
- Ranking claimed benefits by size and by evidential weakness, and reviewing the intersection first.
- Rebuilding the benefit calculation independently for the top claims, from source data rather than programme submissions.
- Testing for double counting by mapping every claim to the ledger lines it touches and flagging overlaps.
- Restating the phasing history — what was promised for each quarter at each re-plan — so the committee can see slippage as a pattern rather than a series of isolated adjustments.
- Distinguishing run-rate benefit from one-off benefit, and reporting them separately.
Independence matters more here than in most assurance work, because the people best placed to validate benefits usually report to the executives sponsoring the programme. Internal audit can hold the mandate; where it lacks the commercial or operational depth, it should borrow it rather than dilute the review.
What the board should ask
An audit committee does not need to re-perform the analysis. It needs to ask questions that only survive contact with a real benefits process. Which ledger lines will move, and have they? Who validated this number, and do they report to the programme? What has been removed from the benefits total since approval, and why does the total not fall? When phasing slips, does the end-state claim slip with it? A programme that can answer these fluently is probably measuring itself honestly. A programme that answers with dashboard extracts is measuring activity. The committee should also insist that the benefits total appears in the CFO's own reporting, reconciled to budget and forecast — because a number the CFO will not own in the financial plan is a number the board should not accept in the programme pack.
Where to start
Take the current benefits report and pick the three largest claims. For each, ask for the ledger line, the baseline adjustment logic and the name of the person outside the programme who verified it. The quality of those three answers will tell you whether you need a full independent review — and in our experience of how these programmes behave, it usually will.