Over the last few months, I've had countless conversations with government organisations about the Programme and Project Data Standard.
Some are well underway in understanding what it means for them. Others are only just beginning to explore the implications.
What I've noticed is that many teams are still viewing the standard as a compliance exercise. After all, there are deadlines to consider and adoption plans to prepare. But focusing only on compliance risks missing the much bigger opportunity.
The Programme and Project Data Standard isn't simply about satisfying a requirement. It's about creating better-quality data that enables better decisions across government portfolios.
And increasingly, it's also about preparing organisations for the next generation of AI-enabled portfolio management.
Most government organisations already hold huge amounts of project and programme information, and the challenge is around consistency of how it is collated, managed and reported on.
Different teams use different terminology. Projects are reported in different formats. Status information is captured differently between programmes. Data is often duplicated across multiple systems and spreadsheets.
The result is familiar to many portfolio leaders:
The Programme and Project Data Standard aims to solve this by creating a common language for programme and project delivery across government.
When everyone is capturing information in a consistent way, reporting becomes simpler, assurance becomes easier and decision-makers gain greater confidence in the information they're seeing.
AI is becoming an increasingly important topic across government but AI is only as good as the data it can access.
If programme data is fragmented, inconsistent or poorly governed, even the most sophisticated AI tools will struggle to provide meaningful insights.
If data is accurate, structured and governed effectively, AI becomes significantly more valuable.
At a portfolio level, this can mean:
The data standard helps create the foundations that make these outcomes possible.
Some departments may find that much of their data already aligns closely with the standard whilst others may discover gaps in their data structures, reporting processes or technology platforms.
Before creating a roadmap, it's important to understand your current position.
That's why we work with organisations to carry out gap analysis activities, helping them understand:
For many organisations, this brings much-needed clarity to what can initially feel like a complex challenge.
Rather than creating additional processes around existing systems, many organisations are looking at how they can embed the standard directly into the way work is managed and reported.
At Verto, we've developed a version of our platform that aligns with the Programme and Project Data Standard, which means organisations can begin their journey with confidence that the underlying structures already support the requirements of the standard.
Instead of treating compliance as a separate workstream, teams can focus on delivering projects and programmes while working within an environment designed to support the future direction of government delivery.
The December 2026 milestone is about establishing a plan, which creates the opportunity to step back, understand your current maturity, identify where improvements are needed and put the right foundations in place for the years ahead.
The real value of the Programme and Project Data Standard is better data, better decisions and a stronger foundation for the effective use of AI across government portfolios.
If you're attending the CGPN this October, and would like to discuss your organisation's current position, I'd be delighted to continue the conversation.