A project's plan and budget only matter if it has the people to deliver them. People data shows whether a project team is the right size, how much it relies on contractors and how many posts are still unfilled.
The Programme and Project Data Standard (PPDS) sets out 8 attributes for the people entity, making it the smallest entity in the standard. But the fields are easy to confuse, because each one counts a slightly different group of people in a slightly different way.
This post covers the three things teams most often miss, how the fields fit together and where to check your people data first.
Current headcount counts people. Every other attribute in the entity counts full-time equivalents (FTE). Two part-time staff working half a week each are a headcount of 2 but 1 FTE. Mixing the two makes the data inconsistent and any comparison between projects unreliable.
The funded and in-post fields count public sector employees only: civil servants and crown personnel. Contracted and contingent workers have a separate field of their own.
The two vacancy fields are different again. They include all approved posts, whether they will be filled by civil servants, crown personnel, contractors or contingent workers. Teams that count only public sector vacancies will understate the gap.
Total project delivery posts records how many FTE posts in the team belong to the project delivery profession. That means roles named in the Project Delivery Capability Framework, or other roles specific to project delivery. Most HR systems do not tag roles this way, so teams may need to map their posts against the framework before they can fill this field.
Take a project team with 30 approved FTE posts. The business case funds 24 of them as public sector posts, and the other 6 are filled by contractors.
| Attribute | Value | What it tells you |
|---|---|---|
| Total approved FTE | 30 | The size of the team the organisation has approved |
| Total funded public sector employees (FTE) | 24 | How many of those posts are civil servants or crown personnel |
| Total public sector employees in post (FTE) | 20 | How many public sector posts are filled today |
| Current contracted and contingent employees (FTE) | 6 | How much the team relies on contractors |
| Total current vacant posts carried (FTE) | 4 | The gap between approved and filled posts |
| Total vacant posts carried (next 12 months) (FTE) | 3 | How many of those vacancies the team plans to fill within a year |
| Total project delivery posts (FTE) | 12 | How many posts belong to the project delivery profession |
| Current headcount | 28 | The number of people, including part-time staff |
The figures should reconcile. Here, 20 public sector and 6 contracted FTE in post, plus 4 vacancies, add up to the 30 approved. Headcount is higher than FTE in post because some staff work part time.
All eight attributes are numeric and updated on change.
| Attribute | What it counts | Who it covers |
|---|---|---|
| Current headcount | Employees employed by the project (people, not FTE) | The project's employees |
| Total approved FTE | Approved positions, as set by organisational headcount controls | All approved posts |
| Total funded public sector employees (FTE) | Posts approved for the team in the most recent relevant business case | Civil servants and crown personnel |
| Total public sector employees in post (FTE) | Posts currently filled | Civil servants and crown personnel |
| Total current vacant posts carried (FTE) | Approved posts not yet filled | All worker types |
| Total vacant posts carried (next 12 months) (FTE) | Unfilled posts planned to be filled within 12 months | All worker types |
| Total project delivery posts (FTE) | Posts aligned with the project delivery profession | All posts in the team |
| Current contracted and contingent employees (FTE) | Contractors and contingent workers currently in post | Contracted and contingent workers |
The standard links the people entity to Government Functional Standard GovS 003: People, which requires organisations to follow the prevailing HR data standards and definitions. Every people attribute lists related HR data standard IDs, held in the NOVA Data Dictionary.
In practice, much of this data should already exist in your HR systems. The main work is likely to be linking HR records to the right project, and agreeing who counts as part of the project team.
Headcount and FTE mixed: the team records one number and uses it for both
Contractors not tracked separately: contracted and contingent workers are missing or counted with civil servants
Vacancies understated: only public sector vacancies are counted, not contractor or contingent posts
Project delivery posts not identified: roles have not been mapped to the Project Delivery Capability Framework
If any of these gaps apply to your people data, start by separating headcount from FTE and contractors from public sector staff, because every other figure depends on those distinctions. Then check that your vacancy counts cover all worker types and map your roles against the Project Delivery Capability Framework.
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 people attributes, with definitions and related HR data standard IDs, head to this link.
Next in this series, we look at project features: the entity that links every other entity in the standard, including the GMPP status field.