What should a benefits realisation plan include?

Define the work needed to realise the benefits

A benefits realisation plan explains the work and conditions needed for intended improvements to occur, how evidence will be obtained and how people will review the result. It connects delivery with the operational changes that make the investment worthwhile.

A project schedule may show when a new capability becomes available. A benefits register records the improvements being managed. A benefit profile explains one claim in more detail. The realisation plan coordinates what people must do across those records; it need not copy every source into another document.

Begin with the material benefits, their owners and expected timing. Work backwards from each improvement to the adoption, operating practice, enabling work and measurement readiness it depends on. Ask what must be true before a forecast is credible.

The UK Teal Book includes realisation planning within benefits management. The compact approach below is a management aid to adapt to the programme, its decisions and applicable governance, rather than a prescribed planning method.

Include the commitments that make the plan usable

Keep the plan short enough to maintain, with links to detailed schedules, profiles and evidence definitions. Include the following information for each material benefit or connected group of benefits.

Distinguish a benefit milestone from a delivery milestone. A system going live can enable improvement without establishing that people use it correctly or that the intended result has occurred.

Likewise, a planned observation date is not evidence that source data will be available. Rehearse collection and allow for source delays before committing a review to information nobody can obtain.

Work through a fictional two-benefit programme

Consider a programme introducing a clearer application route and a revised exception-handling process. It aims to reduce incomplete routine submissions and reduce avoidable staff handling effort. The programme also depends on a separate reference-data clean-up initiative.

All timings and values are illustrative. The expected incompleteness rate moves from 18% to 10%, while average handling time moves from twelve to nine minutes by the end of Month 4. Those expectations still require evidence of feasibility. Reduced handling effort is a capacity claim unless a separate financial effect is established.

This is a sequence of realisation commitments, not a claim that every programme should use these weeks or a limited rollout. It shows why launch alone is insufficient: reference data, changed practice and usable evidence all affect whether the improvements can emerge.

The two benefits may be connected. Fewer incomplete submissions can reduce staff rework. Keep that relationship visible and check for overlap before describing both as separate additions to a financial total.

Make dependencies and ownership actionable

For each dependency, record the condition required, the responsible person, when it is needed and the evidence that will establish readiness. A link to another project does not show whether the specific condition is met.

In the example, a late reference-data clean-up could make validation less useful or increase exceptions. The programme needs a response: restrict the initial scope, provide a workable alternative or reconsider rollout timing. Identify who can decide, rather than leaving the dependency as a note beside an unchanged forecast.

Use the portfolio benefit dependencies guide for shared contributions and enabling projects. This plan records the resulting commitments and decision points.

Keep benefit accountability distinct from delivering an action or submitting a value. An analyst can supply an accurate measure without controlling adoption or owning the improvement. The ownership and regular updates guide provides the contributor arrangements that support the plan.

Review readiness and respond to what changes

At each material review, test whether the plan still describes an achievable route to the intended improvement.

1. Are enabling conditions and operational changes ready, with evidence rather than completion labels alone?

2. Do owners and contributors have the capacity, authority and source access needed for the next period?

3. Are baseline, target, current forecast and actual observations distinguishable?

4. What missing evidence, adverse effect or dependency changes the next action or decision?

5. Who will follow through, and when will the result of that action be reviewed?

When expectations change, retain the earlier decision context and explain the revision. A revised forecast does not automatically change an agreed target. Avoid using a plan update to make a deteriorating outlook disappear.

An action may be to obtain evidence, change adoption support, limit rollout or revisit the investment decision. The plan should make the response usable, rather than simply produce another reporting cycle.

Carry the plan into operational use

Agree the continuing benefit responsibilities before the delivery team disperses. Include the evidence source, review forum, outstanding actions and the reasoning behind expectations. Project closure should not silently remove work that the benefit still needs.

New Zealand Treasury’s investment realisation guidance provides context for reviewing performance in operational use. Its jurisdiction-specific reporting arrangements are not a universal monitoring period. Set the continuing review to suit the benefit and applicable requirements.

Use the post-closure benefits tracking guide for the detailed handover and ongoing collection arrangements. Keep the plan connected to those arrangements, and revise or retire activities deliberately when they no longer support a useful decision.

The plan can use existing documents and systems. Its value comes from clear commitments, available evidence and accountable decisions; maintaining a document alone does not establish that a benefit has been realised.