The four states of a benefit: identified, validated, forecast, realised

Not all benefits are equal, and treating them as if they are is how a forecast loses its credibility.

Ask a transformation office what its portfolio is worth and you will usually get a single number. Ask how much of that number is real, and the conversation gets harder. Most benefit tracking collapses four very different things into one figure.

Identified

An identified benefit is a claim. Someone believes there is value here. It belongs in the pipeline, but it has not been tested. Counting identified benefits as if they were committed is the most common way portfolios overstate their worth.

Validated

A validated benefit has a baseline, an owner, an assumption set and a method that Finance has reviewed. It is not yet delivered, but it is credible. The line between identified and validated is where most double counting is caught.

Forecast

A forecast benefit is validated value with a delivery path attached. It should move as the initiative moves. When a dependency slips, the forecast moves with it, in real time, not at the next reporting cycle.

Realised

A realised benefit has landed in the numbers, with evidence connecting it back to the initiative, the decision and the operational change that produced it. This is the only category that should ever be reported as fact.

Why the states matter

Keeping the four states separate does two things. It stops the portfolio from claiming value it has not earned, and it makes erosion visible. When a benefit slides from forecast back toward validated, that is a signal, and it is one you want weeks early, while recovery is still possible.