Every business case quantifies its benefits. Tracking whether those benefits materialise after delivery is often much harder.
The Programme and Project Data Standard (PPDS) will not solve that on its own. But it gives organisations a consistent way to record benefits, so they can be tracked and compared across projects.
The benefit entity has 15 attributes, a classification system drawn from the Green Book and a validation rule for realisation dates.
This post covers the three things teams most often miss, how the Green Book classification works and where the common gaps are.
The standard asks you to classify each benefit twice: by category (where the benefit is realised) and by class (how it is measured). Both must use the standard's fixed lists, not free text. Without consistent classification, benefits cannot be combined meaningfully across a portfolio.
The standard's validation rule for benefits is simple: the realisation end date must be on or after the realisation start date. This is a mandatory rule. It matters most when dates shift during a project and one date is updated without the other.
The standard has fields for both forecast and actual full-year value. Many organisations capture the forecast in the business case but never fill in the actual, because nobody tracks realised value after delivery.
The same applies to ownership. The standard lists the benefit owner as set once, but it also says data stewards should decide the actual update frequency with their data owner. Update frequencies are a minimum. When ownership passes from the SRO to a business owner at project closure, record the change.
Direct public sector: realised within the organisation running the project, such as lower staff costs or freed-up capacity
Indirect public sector: realised in other public sector bodies, such as a digital service that reduces admin for local police forces
Wider benefits to UK society: realised outside the public sector, such as economic growth from infrastructure or less regulatory burden on businesses
Cash releasing: reduces spending directly, such as ending a contract, so the saving shows in the budget
Monetisable non-cash releasing: has a credible monetary value but does not reduce the budget, such as time saved by citizens using an online service
Quantifiable but not monetisable: can be measured in numbers but not in pounds, such as satisfaction scores or error rates
Qualitative unquantifiable: real but not measurable in numbers, such as greater public trust in a service, so it should be clearly described
The standard points to section 5.1 of the Green Book to support this classification.
The realisation start and end dates set the window in which a benefit is delivered. For many benefits, that window opens after the project closes.
The realisation timeframe is the number of years between the two dates. For example, a benefit that starts on 1 April 2027 and ends on 31 March 2030 has a timeframe of 3 years. Across a portfolio, this shows whether investment is generating short-term or long-term value.
Both dates are updated on change. Realisation windows often move during complex projects, and the data should reflect the current expectation rather than the original estimate.
The benefit owner is the named person responsible for the benefit, not just for defining it in the business case. Many projects make the SRO the owner during delivery and assume ownership will transfer at closure.
The standard does not set out how that transfer should happen. But if the owner field is blank, or names someone who has moved on, nobody is visibly accountable when benefits are reviewed after the project ends.
These two fields record who benefits, not who delivers. The beneficiary group uses a fixed list: Public, Government department, Local government, Overseas or Other. The beneficiary names the specific organisation or group. Together, they show whether investment creates value for the delivering department, other public bodies or citizens.
The two objective fields link each benefit back to the decisions behind it. The related business case objective records which objective in the business case the benefit supports, so reviewers can check that the benefits being tracked are the ones the investment was approved for. The related strategic objective links the benefit to the wider organisational or policy goal.
Both fields are updated on change, because business cases get revised and strategic objectives shift during long projects.
| Attribute | What it holds | Updated |
|---|---|---|
| Benefits ID | Unique alphanumeric code (for example, PRJ1_BEN001) | Once |
| Benefit title | A short name for the benefit | Once |
| Benefit description | A summary of the benefit, including what will deliver it | Once |
| Green Book benefit category | Direct public sector, Indirect public sector or Wider benefits to UK society | Once |
| Green Book benefit class | Cash releasing, Monetisable non-cash releasing, Quantifiable but not monetisable or Qualitative unquantifiable | Once |
| Benefit owner | The person responsible for the benefit | Once |
| Related business case objective | The business case objective the benefit supports | On change |
| Related strategic objective | The strategic objective the benefit relates to | On change |
| Full-year value (forecast) | Forecast full-year value in £m | On change |
| Full-year value (actual) | Actual full-year value in £m | On change |
| Realisation start date | When realisation begins | On change |
| Realisation end date | When realisation is complete | On change |
| Benefit realisation timeframe | Years between the start and end dates | On change |
| Beneficiary group | Public, Government department, Local government, Overseas or Other | On change |
| Beneficiary | The specific stakeholder who receives the benefit | On change |
When we assess benefits data against the standard, the same five gaps come up most often:
No Green Book classification: benefits are described in narrative without a category or class
No realisation dates: the business case names benefits but not when they will start and finish
Forecasts but no actuals: the forecast value is recorded, but the actual value is never filled in
No owner after closure: the SRO is listed as owner, with no plan for who takes over when the project ends
No beneficiary: the benefit is defined, but not who receives it
If any of these gaps apply to your benefits data, start there. Classify every benefit by Green Book category and class first, because portfolio reporting depends on it. Then add realisation dates, agree who owns each benefit after closure and set up a process for recording actual values.
The standard is in a 12-month internal government trial. Version 2 is due in early 2027, and organisations are expected to comply before 2030. That gives teams time to plan, but these gaps are worth addressing now.
For the full list of benefit attributes, with definitions, formats and examples, click the link.
Next in this series, we look at the people entity: headcount, FTE, vacancies and contractor visibility. After that, we cover project features, the entity that links every other entity in the standard.