Logo_Color
PPDS

Issue data under the new standard: three things most teams miss

Issue data under the new standard: three things most teams miss
5:07

Risks are what might happen. Issues are what has happened. Under the Programme and Project Data Standard (PPDS), the line between the two is no longer a judgement call: a risk that becomes certain must move to the issue log.

The issue entity is one of the smaller entities in the standard, with 11 attributes. But it is where your risk data lands, so the two need to work together.

This post covers the three things teams most often miss, how an issue record differs from a risk record and where to check your issue log first.

Three things most teams miss

1. A certain risk must become an issue

If a risk's current likelihood score reaches 5, meaning it is certain to occur, the standard requires it to be reclassified as an issue. This is a mandatory validation rule.

In many registers, a risk at likelihood 5 stays where it is because moving it feels like extra admin. Under the standard, your issue log needs a clear route in: each monthly risk update, flag any risk at likelihood 5 and create the matching issue in the same cycle.

2. Cause and impact use the Orange Book categories

The issue cause category and issue impact category use the same list of 13 categories from Annex 4 of the Orange Book as the risk entity: Strategy, Governance, Operations, Legal, Property, Financial, Commercial, People, Technology, Information, Security, Project/Programme and Reputational.

For issues escalated from risks, the standard notes that the issue cause category could relate to the original risk cause category. Using the same list across both entities keeps your data consistent as risks turn into issues.

3. Status has three options, and closure needs a reason

Issue status can only be Open, Paused or Closed. When you close an issue, the issue closure reason records why. Without it, nobody reviewing the log later can tell whether an issue was resolved, overtaken by events or closed in error.

How an issue record differs from a risk record

When a risk becomes an issue, the record changes shape. The issue entity has no scoring, no proximity and no response categories, because the event has already happened.

  Risk record Issue record
Describes Cause, event and impact that may occur Cause, event and effect that have occurred
Categories Cause, event and impact (Orange Book) Cause and impact (Orange Book)
Scoring Inherent, current and residual ratings None
Response Category, description, owner and due date Response description
Ownership Risk owner, response owner and raised by Issue owner and issue identifier
Lifecycle Updated monthly until closed or reclassified Open, Paused or Closed, with a closure reason

Most issue fields are set once, when you create the record. The standard expects only the issue owner and issue status to change over time, so it pays to describe the issue clearly at the start.

The 11 attributes at a glance

Attribute What it holds Updated
Issue ID Unique alphanumeric code (for example, PRJ1_ISS001) Once
Issue event description What has happened, at a level of detail where it can be managed Once
Issue cause The specific factors that caused the event Once
Issue cause category One of the 13 Orange Book categories Once
Issue effect The effect on objectives Once
Issue impact category One of the 13 Orange Book categories Once
Issue identifier The person or body who raised the issue Once
Issue owner The person or people managing the issue On change
Issue response description The corrective action needed Once
Issue status Open, Paused or Closed On change
Issue closure reason Why the issue was closed Once

The standard also requires Issue IDs to be unique across your organisation, not just within a project.

Four gaps worth checking in your issue log

  • No route from the risk register: risks at likelihood 5 stay in the risk register instead of moving to the issue log

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

  • Non-standard statuses: the log uses its own options, such as Resolved or On hold, instead of Open, Paused and Closed

  • No closure reason: issues are closed without a record of why

Where to start

If any of these gaps apply to your issue log, start with the route from your risk register, because it is the only mandatory rule specific to issues. Then align your statuses and categories with the standard's lists, and make the closure reason a required field.

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 issue attributes, with definitions, formats and examples, access the Data Standard here. 

Verto Newsletter

Insights That Move Public Services Forward

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