Project features looks like the simplest entity in the Programme and Project Data Standard (PPDS). It has 11 attributes, most of which teams already record: a project ID, a name, an SRO, start and end dates.
But it is also the entity everything else depends on. Every risk, issue, milestone, benefit, cost and people record must link back to a Project ID. If that ID is inconsistent, none of the other data joins up.
This post covers the three things teams most often miss, how project features connects the other entities and where to check your data first.
The Project / Programme ID must be unique across your organisation, not just within a team or directorate. The standard also requires every project ID in the organisation to follow the same format and character length.
Many organisations have several numbering schemes: one in the finance system, another in the portfolio office, another in each directorate's tracker. Under the standard, these need to converge on a single format, used in every entity.
The standard defines project dates by lifecycle stage. The start date should be the beginning of the Feasibility Stage, after the Policy Stage ends. The end date should be the end of the Operation Stage. Many teams use a different start point, such as business case approval, contract award or mobilisation.
The end date is also the only attribute in the standard that is updated quarterly, and it must always be later than the start date. The project start and end milestones in the milestone entity must match these dates too.
The Parent ID and Child ID fields record where a project sits: which programme it belongs to, and which projects sit beneath it. Without them, portfolio offices cannot roll project data up to programme level or see how projects relate to each other.
The standard's foreign key rule requires the Project ID to exist in every related entity. That makes project features the hub of the data model. Three connections matter most:
Project ID in every record: each risk, issue, milestone, benefit, cost and people record must carry the Project ID, so all data about a project can be brought together
Dates that match the milestone entity: the project start and end dates must match the corresponding Delivery milestones
Finance and HR identifiers: the Project ID, project name, project category and parent and child IDs all have related government data standard IDs, which link project data to finance and HR systems
The SRO name field matters too. Under the standard, the SRO acts as the data owner for the project, with ultimate accountability for all the data it creates.
| Attribute | What it holds | Updated |
|---|---|---|
| Project / Programme ID | Unique alphanumeric code (for example, HMTPROJ0001) | Once |
| Project / Programme name | A unique, brief title for the project | Once |
| Parent ID | The ID of the parent project or programme, if applicable | Once |
| Child ID | The ID of any child project or programme, if applicable | Once |
| Lead organisation | The main government organisation delivering the project, from the GOV.UK list of departments, agencies and public bodies | Once |
| Project category | Infrastructure and construction, Military capability, Digital and data, Transformation and service delivery, or International | Once |
| GMPP status | Yes or No: whether the project is in the Government Major Projects Portfolio | On change |
| Project start date | The beginning of the Feasibility Stage | Once |
| Project end date | The end of the Operation Stage | Quarterly |
| Programme director name | The name of the programme director | On change |
| Senior responsible owner name | The name of the SRO | On change |
The project categories come from section 10.3 of the Teal Book.
Several ID schemes: different systems or directorates number projects in different ways
Project ID missing from other records: risks, milestones or cost lines cannot be traced back to their project
Start dates that don't match the lifecycle: the start date reflects approval or contract award, not the beginning of the Feasibility Stage
No parent or child IDs: projects are recorded in isolation, with no link to the programme they belong to
Start with the Project ID. Agree one format for the whole organisation, then make sure every record in every other entity carries it. Without that, compliance work on the other entities will not join up. Then align your start and end dates with the lifecycle stages and add parent and child IDs.
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 project features attributes, with definitions and related data standard IDs, head here.
This is the final post in our series on the seven data entities in the standard.