Logo_Color
PPDS

Risk data under the new standard: the three rules most teams miss

Risk data under the new standard: the three rules most teams miss
6:08

Risk is the data entity most project teams think they have under control. A register exists, risks are scored, someone owns the document. Job done.

The Programme and Project Data Standard (PPDS) takes a different view. It sets out 25 attributes for the risk entity, three separate scoring tiers and eight response categories. It also includes validation rules that will change how most risk registers work.

This post covers the three rules teams most often miss, how the scoring model works and where the common gaps are.

The three rules most teams miss

1. Risk ratings must be calculated, not typed in

The standard requires every risk rating to equal its likelihood score multiplied by its impact score. This applies to all three tiers: inherent, current and residual. If your register lets people type a rating directly, rather than calculating it from the two component scores, that is a compliance gap.

2. A likelihood of 5 turns a risk into an issue

A current likelihood of 5 means the risk is now certain to occur. At that point, the standard requires you to reclassify it as an issue. This is a data validation rule, not guidance.

From then on, you manage it under the issue entity's attributes, including issue status, response description and issue owner. For issues escalated from risks, the standard notes that the issue cause category could relate to the original risk cause category.

Most project tools do not make this switch automatically. Your risk data steward needs a simple process: each monthly update, flag any risk with a current likelihood of 5 and convert it in the same cycle.

3. Categories must come from the Orange Book list

Three attributes use the same list of 13 categories from Annex 4 of the Orange Book: risk cause category, risk event category and risk impact category. The 13 permitted values are:

  • Strategy

  • Governance

  • Operations

  • Legal

  • Property

  • Financial

  • Commercial

  • People

  • Technology

  • Information

  • Security

  • Project or Programme

  • Reputational

Three fields can hold different values for the same risk. For example, a risk might have a People cause, a Financial event and a Reputational impact.

Free text is not permitted. If your register describes categories in narrative, you will need to remap every record to this list.

How the three-tier scoring model works

The standard scores every risk three times. Likelihood uses a 1–5 scale, where 5 means certain, and each rating is likelihood multiplied by impact. Each tier answers a different question.

  • Inherent risk: how bad could this be if we did nothing? You score it once, when you first identify the risk, and never change it. It gives you a fixed baseline.

  • Current risk: where does the risk sit today? You update both scores every month, with current controls in place. Comparing current to inherent shows whether your controls are working.

  • Residual risk: where will it land once our response is complete? You update it when the response plan changes. Comparing residual to current shows how much you expect your response to achieve.

A worked example

Take a threat: a key supplier may deliver components late, delaying installation.

Tier Likelihood Impact Rating Updated
Inherent 4 5 20 Once
Current 4 4 16 Monthly
Residual 2 4 8 On change

The current rating of 16 shows that existing controls have reduced the impact, but not the likelihood. The residual rating of 8 shows the team expects its planned response, such as securing a second supplier, to halve the likelihood.

Choosing the right response category

The standard allows eight response categories, defined in Table 20.1 of the Teal Book. Choosing the right one matters, because each drives a different management approach and feeds into risk data aggregated across your organisation.

For threats and general use:

  • Avoid: change the plan to remove the threat

  • Treat: reduce the likelihood or impact to an acceptable level

  • Transfer: pass the financial consequence to a third party, usually through insurance or contract

  • Share: split the risk between parties, for example in a joint venture

  • Accept: take no specific action and accept the consequence if it occurs

  • Reject: assess the risk and formally decline to manage it, with a recorded rationale

For opportunities only:

  • Exploit: act to make the opportunity more likely to happen

  • Enhance: increase the opportunity's likelihood or positive impact

Most tools will let you apply any category to any risk. Using Exploit on a threat, or Avoid on an opportunity, weakens the quality of your aggregated data.

Four common gaps in risk registers

When we review risk registers against the standard, the same four gaps come up most often:

  • No unique ID system: risks are numbered by spreadsheet row, so their IDs change when rows are moved or filtered

  • One-tier scoring: teams track a single score instead of separate inherent, current and residual tiers

  • Free-text categories: cause, event and impact are described in narrative instead of mapped to the Orange Book list

  • No monthly update cycle: scores are reviewed at project board meetings, sometimes quarterly, instead of every month

Where to start

If any of these gaps apply to your register, start there. Fix the ID system and the scoring tiers first, because every other attribute depends on them. Then remap your categories and set a monthly update cycle with a named data steward.

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 25 risk attributes, with definitions, formats and update frequencies, see the full attribute checklist or the standard.

 

Verto Newsletter

Insights That Move Public Services Forward

Discover tools, stories, and insights that help leaders deliver meaningful change across their organisations.