Logo_Color
PPDS

Who is responsible for PPDS? The governance model behind the Programme and Project Data Standard

Who is responsible for PPDS? The governance model behind the Programme and Project Data Standard
9:49

One of the most common questions we hear about the new Programme and Project Data Standard (PPDS) is a simple one: who owns it?

It's a fair question - new standards often arrive without a clear owner, and each team assumes responsibility sits elsewhere until a deadline forces the issue.

The good news is that the standard's governance section is unusually clear. It names specific roles and sets out specific responsibilities. The less comfortable news is that those responsibilities reach the top of the organisation.

The governance chain, from the top down

The standard sits within Government Functional Standard GovS 002: Project Delivery, and its governance model follows from that functional standard. It assigns accountability across four levels:

  1. Accounting officers hold ultimate accountability for how their organisation manages information and data. This isn't a new responsibility, because accounting officers already answer for their organisation's operations. However, the standard makes clear that data management falls within that accountability. If an organisation manages its programme and project data poorly, that becomes an issue for the accounting officer.

  2. Chief data officers set clear expectations for managing data and ensure compliance with data and security requirements, including this standard. In effect, the standard makes the chief data officer the internal owner of the compliance framework. They need to understand the standard, communicate it across the organisation and show that the right steps are being taken.

  3. The senior officer accountable for project delivery ensures that the organisation's programme and project data, as a whole, complies with the standard. This person usually leads the project delivery function in the department or arm's length body. In practice, they lead implementation and turn the implementation plan into action.

  4. Portfolio directors and senior responsible owners (SROs) are responsible for the data in their portfolio, programme or project. For most people in delivery roles, this is where the standard becomes personal.

Data owners and data stewards

The standard names the SRO as the data owner for their programme or project. 'Data owner' is a defined term in the standard: it means the person accountable for the overall quality and correct use of the project's data. This is a significant responsibility, not a nominal one.

Most people in project teams will work with the standard as data stewards. The standard defines a data steward as the person who creates, maintains and uses project data in line with the standard, making sure it is accurate, complete and consistent. Any team member can act as a data steward for a specific data entity.

In practice, the person who maintains your risk register is the data steward for the risk entity. Similarly, the person who updates the milestone plan is the steward for milestones, and the person who maintains the benefits tracker is the steward for benefits.

The standard doesn't ask organisations to create new job titles or recruit new people. Instead, it asks them to make existing roles explicit and to make sure the people in those roles understand what the standard requires of their data.

What an implementation plan needs to cover

Where an organisation can't comply immediately, the standard requires an implementation plan. This must be a working document, not a placeholder. It should describe the changes and activities needed for programmes and projects to create and manage data in line with the standard.

A credible implementation plan usually covers three areas:

  1. Current state: the IT systems in use, the data management practices in place and an honest assessment of data maturity.

  2. Gaps: the specific differences between current practice and the standard's requirements, for each data entity and attribute.

  3. Actions: a timeline and set of activities to close those gaps, each with a named owner.

The standard accepts that existing IT systems may make immediate compliance impossible. What it doesn't accept is inaction. Organisations are expected to set out a documented, credible path to compliance.

The data validation rules your stewards need to know

Beyond the attribute requirements, the standard includes 11 data validation rules. These rules check that data is entered correctly and that the relationships between data points make sense. Your data stewards need to know them, and four areas deserve particular attention:

  • Unique identifiers: every ID field, including project, risk, issue, milestone and benefit IDs, must be unique across the organisation. Each ID must also follow a consistent format and length. If your project IDs mix formats and lengths, you already have a compliance gap.

  • Risk ratings: the standard calculates risk ratings by multiplying likelihood by impact. Inherent, current and residual ratings must each equal their likelihood score multiplied by their impact score. If your risk register lets people override the calculated rating manually, your data will fail the consistency check.

  • Risk-to-issue transition: this is perhaps the most significant rule. When a risk's current likelihood score reaches 5, the maximum score, the risk is certain to occur and the standard requires you to reclassify it as an issue. Many teams treat this as a judgement call, but the standard makes it a rule.

  • Date logic: project end dates must fall after start dates. Milestone actual dates must be on or before today's date, and benefit realisation end dates must be on or after their start dates. These rules sound obvious, but validation rules exist because obvious errors still happen at scale.

Why the governance model matters beyond compliance

The governance model isn't only about making sure the right people complete the right checks. It reflects how government project delivery needs to work.

The purpose of a data standard is comparability. When every team records milestones in the same way, you can compare milestone slippage across departments. When teams score risks consistently, you can combine risk profiles across a portfolio. When teams categorise costs in the same way, financial analysis across government becomes meaningful.

That insight supports better decisions and better use of public money. However, it only works when named people in real roles are accountable for the quality of the data. The governance model is what turns the standard's requirements into everyday practice.

What to do now

If you're an SRO, start by identifying which data entities apply to your programme or project. Then identify who in your team acts as data steward for each one, even if that role is currently informal.

If you're a chief data officer or the senior officer accountable for project delivery, assess your organisation's data environment against the standard and write your implementation plan now. The trial ends on 31 December 2026, so don't wait for Version 2.

If you're a project manager or analyst who works with any of the seven data entities, the standard sets specific requirements for your data. Our next articles explain those requirements entity by entity.

Verto works with government project teams to assess, improve and manage programme and project data. If you'd like to understand where your organisation stands against the standard, get in touch. We've already worked through the detail, so you don't have to start from scratch.

Frequently asked questions

Who is accountable for the Programme and Project Data Standard?

Accountability runs across four levels. Accounting officers hold ultimate accountability, chief data officers own the compliance framework, and the senior officer accountable for project delivery leads implementation. Portfolio directors and SROs are responsible for the data in their portfolio, programme or project.

What is a data owner?

A data owner is the person accountable for the overall quality and correct use of a project's data. The standard names the SRO as the data owner for their programme or project.

What is a data steward?

A data steward creates, maintains and uses project data in line with the standard. Any team member can act as a data steward for a specific data entity, such as risks, milestones or benefits.

Do we need to create new roles or recruit new people?

No, the standard doesn't require new job titles or new recruits. It asks organisations to make existing roles explicit and to make sure the people in those roles understand the requirements for their data.

What should an implementation plan include?

A credible implementation plan sets out your current data environment, the gaps against the standard and the actions to close them. Each action should have a timeline and a named owner.

What if our IT systems can't meet the standard yet?

The standard accepts that existing IT systems may prevent immediate compliance. In that case, you need an implementation plan that shows a credible path to compliance.

How many data validation rules does the standard include?

The standard includes 11 data validation rules. They cover areas such as unique identifiers, risk rating calculations, the transition from risk to issue and date logic.

When does a risk need to become an issue?

A risk must be reclassified as an issue when its current likelihood score reaches 5, the maximum score. At that point, the standard treats the risk as certain to occur.

Verto Newsletter

Insights That Move Public Services Forward

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