As central government departments move towards compliance with the updated programme delivery standards, many are discovering that the challenge is not understanding the requirements. It is operationalising them.
On paper, the expectations are clear. Consistent reporting, structured governance, transparent risk management, and ongoing benefits realisation are all well established principles of good delivery.
In practice, however, many organisations are still working within systems and processes that were never designed to support this level of consistency, visibility, or control.
The result is a growing gap between what the standards require and what teams are realistically able to deliver without significant effort.
Across government, most delivery environments have evolved over time. Tools have been added, processes adapted, and local ways of working developed to meet immediate needs.
That has created flexibility, but it has also introduced complexity.
Data is often fragmented across multiple systems. Projects are managed using a mix of Excel, SharePoint, legacy platforms and bespoke trackers. Bringing together time, cost, risk, benefits, dependencies and resource data frequently requires manual consolidation.
This is not just inefficient. It introduces errors, creates version control issues, and delays reporting at the very point where timely insight is most needed.
At the same time, project maturity varies significantly across portfolios. Some programmes operate with clear baselines, structured business cases and defined benefits profiles. Others are less developed, with gaps in planning and documentation.
When these projects are brought together into a single reporting view, the inconsistency becomes visible. Portfolio-level reporting becomes harder to trust, and decision-making becomes less certain.
The updated standards place a strong emphasis on governance, accountability and assurance. In particular, they require clear Senior Responsible Owner accountability, defined governance structures and robust evidence to support decisions.
For many departments, this is where pressure begins to build.
Governance arrangements are not always consistently applied, and project managers often find themselves trying to gather information that SROs are formally accountable for but do not have the time to compile themselves.
For time-poor SROs, new reporting templates can feel administratively heavy rather than enabling. Without the right systems in place, the burden of compliance risks falling on already stretched delivery teams.
The standards also expect a level of discipline in benefits management and risk reporting that many organisations are still developing.
Benefits are often treated as something defined in the business case rather than actively tracked and managed throughout delivery. Ownership is not always clear, and there can be confusion between hard and soft savings. As a result, benefits reporting can lack credibility or consistency.
Risk management presents a similar challenge. While most organisations have risk processes in place, scoring and reporting often vary between teams. Some projects under-report risk to avoid scrutiny, while others over-report to protect themselves.
This creates noise rather than clarity. Instead of enabling better decisions, risk reporting can become harder to interpret at a portfolio level.
For complex government programmes, understanding dependencies is critical. Yet cross-programme and cross-department dependencies are rarely tracked in a structured way.
Without clear visibility, reporting becomes based on assumptions rather than evidence. Downstream impacts are missed, and portfolio views become less reliable.
Resource planning adds another layer of complexity. Government workforces are highly matrixed, with individuals working across multiple initiatives. Visibility of capacity and demand is often limited, making it difficult to produce meaningful forecasts.
Financial and commercial data presents a similar issue. Information is frequently held outside delivery teams, sitting with finance or commercial functions. Reporting cycles are not always aligned, which leads to delays in understanding variances, commitments and forecasts.
One of the more significant changes in the updated standards is the expectation to report beyond delivery itself. Teams are now required to consider transition to business as usual, operational readiness and eventual disposal.
For many project leaders, this is unfamiliar territory.
Operational teams are not always engaged early enough, and transition planning can become a rushed activity at the end of delivery rather than a structured workstream throughout the lifecycle.
Alongside these structural challenges, there are also cultural factors at play.
Departments are already managing multiple reporting requirements across Treasury, Cabinet Office, IPA and internal governance structures. New templates can be perceived as additional workload rather than an opportunity to simplify.
This can lead to duplication, where teams complete multiple reports rather than aligning them into a single source of truth.
There can also be a reluctance towards fully transparent reporting. In environments where negative updates are associated with increased scrutiny, teams may feel pressure to present a more positive picture. Over time, this undermines the value of reporting altogether.
Underlying all of these challenges is a common theme: a lack of automation.
Many departments are still heavily reliant on manual processes to produce reports. Project managers spend significant amounts of time gathering data, updating templates and reconciling information across systems.
This creates an administrative burden that detracts from actual delivery. It also means that by the time reports are produced, they may already be out of date.
None of these challenges are new. But the introduction of updated programme delivery standards brings them into sharper focus.
The question for departments is no longer whether these issues exist, but how they can be addressed in a way that is sustainable and scalable across complex portfolios.
The good news is that this is not about starting from scratch. With the right approach, it is possible to create consistency, strengthen governance and improve visibility without adding further administrative burden.
Platforms like Verto provide a practical way to do this. By bringing data into a single, structured environment, organisations can establish a true source of truth for project, programme and portfolio delivery. Governance, reporting and assurance become embedded into the way teams work, rather than layered on top.
This creates a more consistent approach across portfolios, improves confidence in reporting, and gives leaders the visibility they need to make informed decisions.
Ultimately, meeting the standards is not just about compliance. It is an opportunity to move towards a more transparent, connected and effective model of delivery, where information is trusted, processes are aligned and teams can focus on outcomes rather than administration.
These expectations have been introduced through Government Project Delivery’s updated standards, which set a clear direction for how data, governance and reporting should operate across government.