A project can be delivered on time, within budget and with every milestone ticked off - then still fail to deliver the value it was funded to create. That is the gap a benefits realisation review is designed to expose. It asks a straightforward question: did this investment change the business in the way we said it would?
For CEOs, CFOs and program sponsors, this is not an administrative exercise at project close. It is a commercial control. When benefits are unclear, delayed or quietly disappearing, leaders need facts early enough to make a decision - not a retrospective report when the budget has already been spent.
What is a benefits realisation review?
A benefits realisation review is a structured assessment of whether a project, program or transformation is producing its intended outcomes. It compares the benefits set out in the business case with actual results, identifies what is preventing value from being realised, and assigns clear action to close the gap.
The review should cover financial outcomes, but it should not stop there. A cyber security uplift may reduce exposure rather than generate revenue. A community housing system may improve tenant service and compliance. A new operating model may shorten approval times, improve staff retention or make regulatory reporting more reliable.
The key is turning those broad intentions into evidence. If the expected benefit was a 20 per cent reduction in manual processing, the review needs to establish the baseline, measure current performance and determine whether the change is holding. If no one can explain how a benefit will be measured, it is not yet a benefit that can be managed.
Why projects lose benefits after delivery
Most projects do not lose value because the delivery team failed to build the agreed solution. Value is usually lost in the handover between delivery and business operations.
A platform goes live, but teams continue using spreadsheets because processes were never redesigned. A new customer portal launches, but customers are not told how to use it. A compliance change is technically complete, but controls are inconsistently applied across business units. The project is closed, ownership becomes unclear, and the benefit becomes someone else's problem.
This is especially common in complex change programs where benefits sit across several functions. Technology may deliver the system, operations may need to change workflows, finance may validate savings, and an executive sponsor may need to remove barriers. Without a named owner and a regular reporting rhythm, each group can reasonably assume another group is tracking the outcome.
There is also a timing issue. Some benefits are immediate, such as avoiding a regulatory deadline breach. Others may take six, 12 or 18 months to emerge. A good review distinguishes between benefits that are genuinely delayed and benefits that were optimistic, poorly defined or dependent on changes that never occurred.
When to conduct a benefits realisation review
The strongest approach is not to wait until project closure. Benefits should be reviewed at the points where leaders can still intervene.
At business case stage, test whether proposed benefits are specific, measurable and owned. During delivery, check whether the work remains connected to the outcome rather than becoming a race to complete scope. Before go-live, confirm that operational teams are ready to adopt the change. After implementation, measure actual performance at agreed intervals.
The exact cadence depends on the nature of the investment. A digital product may warrant monthly benefit tracking because customer behaviour shifts quickly. A major property, infrastructure or operating-model change may need formal reviews at three, six and 12 months after implementation. For a regulatory program, the focus may be on control effectiveness and evidence quality rather than a conventional financial return.
A review is also warranted when warning signs appear: projected savings have not reached the profit and loss statement, adoption is lower than expected, frontline teams have developed workarounds, or the sponsor cannot clearly articulate who owns the outcome. These are not reasons to assign blame. They are signals that the organisation needs to reset its plan for capturing value.
How to run a benefits realisation review that leads to action
A useful review is disciplined, evidence-based and focused on decisions. It should not become a workshop where stakeholders restate the business case and leave with no commitments.
Start with the original promise
Bring together the approved business case, benefits map, baseline measures, delivery scope and any previous status reports. Identify each intended benefit, its original target, the expected timing and the assumptions that sat behind it.
This step often reveals a fundamental problem: the business case described an outcome, but never identified a reliable measure. In that situation, do not invent precision. Agree a practical proxy measure, document the limitation and establish a baseline now. Imperfect measurement is preferable to no measurement, provided leaders understand what it can and cannot prove.
Measure actual performance, not activity
Completed training sessions, configured systems and published policies are delivery outputs. They may be necessary, but they are not benefits.
Look for operational evidence. Has the average processing time fallen? Has revenue increased from the new channel? Have avoidable errors reduced? Has the organisation met its required compliance standard? Has customer satisfaction improved in the affected service journey?
Use both quantitative and qualitative information where appropriate. Data may show that a new process takes less time, while interviews reveal that staff are carrying hidden rework outside the formal workflow. Both findings matter. Leaders need the full operating picture before they declare success or redirect investment.
Test the assumptions behind the gap
When results fall short, separate the cause from the symptom. Low adoption may reflect insufficient change support, but it could also mean the solution does not solve the frontline problem it was meant to solve. Missed savings may come from delayed process changes, inaccurate baselines or costs that were excluded from the original estimate.
This is where independent delivery experience matters. Teams close to a program can become invested in the original plan. A capable review creates room to challenge assumptions without turning the exercise into a critique of individuals.
Assign ownership and recovery actions
Every benefit needs one accountable business owner with the authority to influence the outcome. Finance can validate financial measures, project teams can coordinate actions, and a PMO can report progress, but ownership must sit with the operational leader who can change day-to-day behaviour.
For each gap, agree a recovery action, owner, due date and measure of success. The actions might include simplifying a workflow, improving communications, resolving a system defect, changing performance measures or retiring legacy processes that are undermining adoption. Keep the plan proportionate. Not every benefit gap needs a new workstream, but every material gap needs a decision.
What good governance looks like after the review
Benefits realisation is sustained through governance, not a single meeting. A concise benefits dashboard should show the target, current position, trend, forecast, owner and recovery action for each material benefit. It should also make dependencies visible.
For example, a cost reduction may depend on a new system being adopted, an old process being retired and roles being redesigned. Reporting only the projected dollar figure hides the real delivery risk. Reporting the dependencies gives sponsors something they can actively manage.
Governance also needs the right escalation threshold. If a benefit is marginally behind plan but has a credible recovery path, the owner should manage it. If a key benefit is unlikely to materialise, or the underlying assumptions have materially changed, the sponsor needs to decide whether to alter scope, extend the change effort or formally revise the business case.
That decision can be uncomfortable. It is still better than carrying an unachievable number through monthly reports because no one wants to challenge it.
Benefits realisation review: where external delivery support helps
An embedded project leader can bring structure when internal teams are stretched or the program has lost visibility. The role is not to produce a glossy assessment and disappear. It is to establish the measures, bring the right people into the room, drive decisions and maintain the follow-through that turns findings into results.
This is particularly valuable in recovery situations, cross-functional transformations and programs with heightened regulatory or stakeholder scrutiny. JJPH works alongside client teams to strengthen governance and delivery discipline while keeping the focus on the value the organisation set out to achieve.
The best time to ask whether benefits are being realised is before the project is labelled complete. Keep the original promise visible, measure what has changed, and act quickly when the evidence says the value is at risk.
