The project is finished. Where are the savings?

The system is live. The delivery team has handed it over. The project is marked complete, but the saving that justified the investment is still sitting in next year's forecast.

Closing a project and achieving its benefits are different events. The board needs to know what must happen between them, who is responsible and when the result should become visible.

Be precise about what was promised

Consider an illustrative automation project expected to release 100 hours of work each month. If employees use that time to serve more customers, the business may gain useful capacity. Its payroll has not necessarily fallen.

Time released, spending avoided and costs removed are different benefits. Each can be valuable. Reporting all three as cash savings makes the outcome difficult to assess.

Return to the original case. Was the promise a lower operating cost, faster service, fewer errors or additional capacity? Agree how each result will be evidenced, and when it can reasonably be expected.

Keep the starting point visible

A claimed improvement needs a credible comparison. Establish the previous cost, workload or service level and explain the assumptions used.

If volumes rise after implementation, total spending may increase even when the cost per transaction falls. If service quality deteriorates, a lower cost may come with consequences the original case did not allow for.

Ask finance and the operational owner to agree the measurement. Where the starting data is incomplete, acknowledge the limitation and use a defensible estimate. Quietly changing the baseline makes the reported improvement less trustworthy.

Find the operational change behind the number

A new tool may make a saving possible without delivering it on its own. Contracts may need to end, duplicate work may need to stop and teams may need to adopt a different process.

List those actions and give each a responsible owner. Someone with authority over the operation should be accountable for the overall result after the project team leaves.

If a planned action is no longer sensible, revisit the benefit openly. Keeping an obsolete saving in the forecast does not preserve the investment case. It conceals a decision that now needs attention.

Report the net result, including the costs that remain

Training, support, licence fees, parallel running and additional controls can affect the outcome. Separate one-off implementation costs from ongoing costs and explain how they enter the calculation.

Also check whether two programmes are claiming the same saving. A reduction in manual work cannot be counted twice because two teams contributed to it.

Give the board a clear view of what was promised, what has been achieved and what remains dependent on further action. Show a revised expectation where the evidence warrants one.

The next question should be specific: which remaining action would turn the forecast benefit into an actual result, and who can make it happen?

Further reading: the UK Government's Government Efficiency Framework, which discusses the distinction between types of savings and how they are evidenced.