Custody of the Claim: Auditing Who Owns a Business Case Once the Project Ends

Most UK organisations subject a business case to considerable scrutiny before approval. Finance challenges the assumptions, the delivery team stress-tests the plan and an approving body satisfies itself that the investment is justified. The weakness tends to appear afterwards. Once the programme has delivered its outputs and the project team has dispersed, the benefits that justified the spend can become a set of orphaned claims. They remain in a document, but they no longer have a custodian.

This is rarely a failure of intent. It is a structural consequence of project governance ending before operational accountability begins. A benefits register may exist, but a register is not an owner. A forecast is not a measurement. A reporting line on a slide is not a route into management action. The practical question for UK organisations is therefore not whether the business case was convincing at approval, but whether its claims have an afterlife.

Why the claim loses its custodian

Business cases are usually written by the people closest to the change, at the point of greatest optimism and least operational distraction. They define benefits in the language of the project: improved processing capacity, reduced manual effort, better compliance, lower cost per transaction. When the project closes, those definitions are handed to an operational manager who may never have seen the original case. The senior responsible owner moves on. The programme management office archives the papers. Finance continues to track spend, but not necessarily the outcome the spend was meant to buy.

The result is a familiar gap. Outputs are delivered and evidenced. Outcomes are assumed. The benefits register becomes a historical artefact rather than a live control. In some organisations the gap is invisible because no one asks a simple question: who is accountable for this benefit today, and what evidence would tell us whether it is being realised?

Three tests of benefit custody

A thirty-day audit should begin with three tests. They are deliberately practical. The aim is not to produce a perfect benefits framework but to establish whether the claims made in approved business cases have custody.

1. A named owner with capacity and authority

A named owner is not a job title in a governance diagram. It is a person who can describe the benefit, its baseline, its target and the tolerance around it. That person should have accepted accountability in writing, should have the authority to act when performance drifts and should have enough operational capacity to pay attention. A common error is to assign ownership to the programme director or the PMO because they understand the case. The better question is who will still be accountable six months after closure.

2. A measurement method that can produce a current value

The audit should ask for the current value of each material benefit. If the organisation cannot produce that value within five working days, the measurement method is not operational. Definitions such as improved efficiency or enhanced service are not measurable until they are translated into a data source, a frequency and a baseline. The data owner matters as much as the definition. A benefit measured from a spreadsheet maintained by one person is fragile, particularly when that person changes role.

3. A reporting route that reaches a decision-maker

The third test is whether the benefit appears in a management routine that can act. A benefits report that goes only to the project board during delivery is not a reporting route after closure. The audit should trace the benefit into an existing performance review, executive meeting or finance report. It should also test the decision trigger: if the benefit falls below tolerance, who is expected to do what, and by when? A route that cannot prompt action is a reporting fiction.

A thirty-day audit sequence

The audit can be completed in four working weeks without creating a new bureaucracy.

Week one: inventory and mapping. List every business case approved or refreshed in the last twenty-four months that is still within its benefit-realisation period. Extract the claimed benefits, baselines, targets and named owners exactly as written. Do not accept revised claims at this stage. Map each benefit to the operational area that should now own it. The output is a short list of orphaned or ambiguous claims.

Week two: evidence and interviews. Request the current value for each material benefit. Hold twenty-minute interviews with the named owner or the most plausible operational owner. Ask what they are accountable for, what data they see, how often they see it and what happens if the benefit misses its target. Rate each benefit red, amber or green on ownership, measurement and reporting.

Week three: route testing. Trace the reporting route into minutes, agendas and performance packs. Confirm whether the benefit has been reported since project closure. Identify the decision forum that would act on a variance and whether it has the authority to do so. Check that finance, operations and the PMO are not each assuming the others hold the benefit.

Week four: decisions and transfer. Classify each benefit as keep, repair or retire. Keep means ownership, measurement and reporting are working. Repair means a named owner must be assigned and a measurement method established within sixty days. Retire means the benefit is no longer material, has been superseded or cannot be evidenced; record the write-off and the reason. For repaired benefits, issue a short benefit transfer note signed by the receiving manager. Report the results to the executive team.

What to do when the answer is no

When the audit finds that a benefit has no owner, the wrong response is to create a larger register that nobody uses. Start with the small number of benefits that are material to current decisions. Assign each to an operational manager, not to the PMO by default. Put the benefit into that manager's objectives and delegated authority. Give them the data and a tolerance. Schedule the first review in an existing performance meeting rather than a new one. If no owner can be found, escalate the benefit to the executive sponsor for a keep, repair or retire decision.

UK organisations already understand post-investment review in principle. HM Treasury's Green Book expectations and the scrutiny applied by finance teams provide a foundation. The missing discipline is custody between approval and closure. A business case is a promise; the audit tests whether the promise has a person, a measure and a route.

Closure should mean custody

A project is not closed when its outputs are delivered. It is closed when its material benefits have custody. Add that condition to the closure checklist: a named owner has accepted in writing, measurement is live, reporting is scheduled and the first post-closure review has a date. If those conditions cannot be met, either the project remains open or the benefit is formally retired. No owner, no closure. That single rule would prevent more orphaned business cases than any additional template.