What is PPDS? What the Programme & Project Data Standard means for your team
- by Laura Watts, Marketing Manager
- 18 November 2026
- Approx 5 min. read
In December 2025, Government Project Delivery published Version 1 of the Programme and Project Data Standard (PPDS) for a 12-month trial across government. The trial ends on 31 December 2026, and Version 2 follows in early 2027, when the standard becomes mandatory.
The launch didn't make headlines, but if you run, manage or report on government programmes and projects, the standard will change how you work. The priority this side of December 2026, is a credible implementation plan.
At Verto, we've studied the standard in detail. This article explains what it means for your team and where to focus first.
What is a data standard?
A data standard sets out rules for how specific information should be defined, formatted and maintained. It tells you which fields to record, what each field should contain and how often the data needs updating.
Until now, every department, team and project management tool has taken its own approach. A milestone in one team's tracker might differ in structure and definition from a milestone in the next. Risk scores couldn't be compared, cost categories varied, and benefits were measured in ways that made it very hard to combine data across government.
PPDS addresses this by giving the government a common language for the data at the heart of project delivery.
The seven data entities
Version 1 of the standard covers seven core data entities. An entity is a main category of information about a programme or project. Each entity has a set of required attributes: the specific fields you must record, in the correct format and at the required frequency.
The seven entities are:
-
Project features
-
Risk
-
Issue
-
Milestone
-
Benefit
-
Cost
-
People
Together, they cover the core data that teams use to plan, manage and control their work.
The standard doesn't ask you to create data for the sake of it. Well-run teams already capture most of these attributes. What changes is how they capture them: consistently, with agreed definitions and in formats that allow comparison across government.
Who the standard applies to
The standard applies to all programmes and projects within or across government departments and their arm's length bodies. It covers major projects in the Government Major Projects Portfolio as well as smaller initiatives. It spans digital, infrastructure, transformation, service delivery, military capability, property and regulatory compliance work.
Smaller programmes and projects don't always need every entity. If a project genuinely doesn't need cost tracking or benefits management, it isn't expected to produce that data. However, this exception is narrower than many teams might hope.
The standard also makes accountability clear. For each portfolio, the portfolio director is responsible for compliance. For each programme or project, that responsibility sits with the senior responsible owner.
The six data quality dimensions
The standard links directly to the Government Functional Standard for Digital (GovS 005), which requires data quality to be assessed against six dimensions. These dimensions translate into practical requirements for your team:
-
Completeness: all required records and values are present.
-
Uniqueness: each record appears once and has a unique identifier.
-
Consistency: related data points don't contradict each other.
-
Timeliness: data is updated at least as often as the standard requires.
-
Validity: data is in the correct format and within expected ranges.
-
Accuracy: data reflects reality, supported by common definitions and formats.
If your current approach has gaps against any of these dimensions, the standard now gives you a clear framework for improvement.
The timeline that should drive your planning
The 12-month trial ends on 31 December 2026. During the trial, departments and arm's length bodies are expected to plan how they will adopt the standard. Government Project Delivery plans to publish Version 2 in early 2027, reflecting feedback from the trial, and the standard then becomes mandatory.
Government Project Delivery recognises that some organisations will need time to adapt their IT systems and data management practices. In those cases, it expects an implementation plan that shows a credible path to compliance. You don't need to be compliant on day one, but you do need a documented commitment to get there.
Organisations are expected to be fully compliant before 2030. Those that plan now will be far better placed than those that treat the standard as background noise.
What this means if you're running a project today
Most teams won't need to start again, but most will need to do some work. The gaps we see most often fall into four areas:
-
Unique identifiers: the standard requires a unique alphanumeric ID for every project, risk, issue, milestone and benefit. Many teams don't yet follow a consistent ID convention.
-
Category lists: many attributes must be recorded from a fixed list of permitted values, such as risk categories, milestone types and benefit classifications. If your data uses free text where the standard requires a category, you have a gap.
-
Update frequencies: the standard sets out how often each attribute must be reviewed and updated. For example, current risk scores need monthly updates, project end dates need quarterly updates and many other attributes need updating whenever they change.
-
Metadata: the standard expects every record to capture who created it, when, and who last modified it. Good project management software records this automatically, but not every tool does it well.
The bottom line
The Programme and Project Data Standard is one of the biggest changes to government project data in recent years. It has been several years in development, was piloted across government and is endorsed by the Data Standards Authority. From 2027, it will be mandatory.
The question for every government project team is simple: will you start 2027 with a plan, or spend it catching up?
Over the coming weeks, we'll publish a detailed guide to each data entity, covering the required attributes and the validation rules your data must meet. Follow Verto on LinkedIn to read the series as it's published.
We help departments and arm's length bodies assess their data against the standard and build a credible implementation plan. If you'd like to understand where your organisation stands, get in touch.
Frequently asked questions
What is the Programme and Project Data Standard?
The Programme and Project Data Standard is a government standard that sets out how programme and project data should be defined, formatted and updated. It gives every department a common way to record data on project features, risks, issues, milestones, benefits, costs and people.
When does the standard become mandatory?
The trial of Version 1 ends on 31 December 2026. Government Project Delivery plans to publish Version 2 in early 2027, when the standard becomes mandatory. Organisations are expected to be fully compliant before 2030.
Who does the standard apply to?
The standard applies to all programmes and projects within or across government departments and their arm's length bodies. This includes everything from major projects in the Government Major Projects Portfolio to smaller initiatives.
Does the standard apply to local government or the NHS?
The standard formally applies to government departments and their arm's length bodies. However, Government Project Delivery notes that other public sector organisations may find it useful.
Who is accountable for compliance?
The portfolio director is accountable for each portfolio. The senior responsible owner is accountable for each programme or project.
What should we do now?
You should write an implementation plan, which Government Project Delivery describes as the first step towards adopting the standard. Start by mapping the data entities and attributes your teams already use.
Do we need new project management software?
You may not need new software. Check whether your current tools support unique IDs, fixed lists of permitted values, required update frequencies and automatic metadata. If they don't, you'll need to adapt them or plan a change.
How does the standard relate to GovS 002?
The data standard complements the Government Functional Standard GovS 002: Project Delivery. GovS 002 sets out how to deliver programmes and projects, while the data standard sets out how to record the data about them.