After the Handover: A Five-Question Review That Makes Programme Closure Useful

A programme closes and the business exhales. The steering group stands down, the project manager moves to the next assignment, and the closure report is filed. What often does not happen is a deliberate check on what the programme actually changed in the operating business. The result is familiar: benefits are asserted at closure, costs surface later in the budget, and the same governance weaknesses reappear in the next initiative.

For UK owner-managers, a short post-implementation review is not an assurance exercise and should not be treated as a second audit. It is a management review, completed while memory is still fresh, that converts closure into usable evidence. In my work with owner-managed firms, the reviews that pay for themselves are rarely elaborate. They are disciplined, time-boxed and blunt.

Why the annual accounts are too late

Annual accounts and board packs aggregate. They show the effect of many decisions, not the cause of one. By the time a recurring licence cost or a weakened supplier relationship appears in management information, the programme team has dispersed and the reasoning behind key choices has gone.

A review completed within four to six weeks of formal closure captures detail that later reporting cannot. It also gives the owner-manager a chance to correct course before the next budget cycle fixes a new cost base in place. The purpose is not to relitigate delivery. It is to establish what is now true.

Question one: Which benefits have actually appeared?

The first question is not whether outputs were delivered. It is which benefits are visible in routine management information. A new system may have gone live, but has invoice processing time fallen? Has stock accuracy improved? Has the compliance risk been reduced in a way that can be evidenced?

Ask for the baseline, the current measure and the source of the evidence. Where no measure exists, record that gap rather than accepting a narrative. A benefit that cannot be seen in the ordinary running of the business is not yet a realised benefit; it is a claim awaiting confirmation. The owner-manager should hear this from the business owner of the benefit, not only from the programme sponsor.

Question two: What new operating costs have arrived?

Programmes create recurring costs that are easy to miss at closure: licences, support contracts, training refreshers, data quality effort, additional administration and shadow processes that sit outside the new system. Some are legitimate. Others are symptoms of an incomplete handover.

A practical prompt is to ask what appears in the 2026 budget that did not exist before the programme. For each item, record the amount, the budget owner and whether it is funded. Also ask which manual work has been created to compensate for a process that did not land as intended. Hidden operating costs are not necessarily a failure, but they must be owned. An unowned recurring cost will eventually find its way to the owner-manager anyway.

Question three: Where did decision quality hold or slip?

Select two or three material decisions made during the programme: the timing of the start, a scope reduction, a supplier selection, a change request or a go-live date. Ask what information was available at the time, what was assumed, and what would be decided differently with the benefit of hindsight.

This is not a personal critique. It is a search for patterns. Did the business approve changes without understanding the operating impact? Did it accept supplier estimates without a challenge route? Did it delay a difficult decision until the cost of delay became the main issue? The answers should inform how the next programme is governed, not simply be recorded as lessons learned.

Question four: How did suppliers perform beyond the contract?

Contractual compliance matters, but it is not the whole relationship. Ask how suppliers performed on responsiveness, knowledge transfer, change requests, issue resolution and exit provisions. Did the business become more dependent on a supplier than the business case assumed? Is the support renewal quote likely to arrive with little competitive tension?

Use evidence from issue logs and meeting records rather than recollection alone. The aim is a short, fair assessment that informs the next sourcing decision and the contract register. Supplier performance is a management fact, not a matter of liking or disliking the account manager.

Question five: What would we do differently, and what changes now?

This question must produce action, not a list of general observations. Ask for at least one operational change and one governance change, each with an owner and a date. If nothing will change, record why. A review that ends with no alteration to how the business selects, sponsors or closes programmes has not paid for itself.

A one-page record

Keep the output to a single page. Record the programme name, closure date, review date and reviewer. Add a benefits table with benefit, measure, baseline, current position, evidence and owner. Add a short table of recurring costs and their budget owners. Note the decisions reviewed, the supplier assessment and the changes adopted. Attach evidence separately rather than expanding the page.

Circulate the record to the board or management team alongside the closure report, not months later. File it where it can be found when the next similar programme is proposed. Over time, these one-page records become a useful management memory for an owner-managed business.

The review should take half a day for a modest programme and perhaps a day for a larger one. That is a small commitment against the cost of repeating the same governance mistakes. Programme closure is a natural moment to ask what the business now knows. The five questions above are a way to make that moment useful.