Why functional standards matter and how they help us deliver better projects

If you’ve worked in or around government projects, you’ve probably heard of the functional standard for project delivery. Maybe you’ve used it to shape a business case, guide a delivery team, or check your governance framework. But where did it come from? And why does it matter?

With the latest update to Government Functional Standard GovS 002: Project Delivery now live, it’s a good time to take a step back and look at the bigger picture.

What are functional standards?

Functional standards are a bit like the glue that holds government together. They set out how we do important things – like managing money, hiring people, or delivering projects – in a consistent, coherent way.

They’re not about red tape or box-ticking. They’re about helping us work smarter, reduce risk, and deliver better outcomes for the public.

Each standard is owned by a government function and reflects the collective wisdom of experts across departments, arm’s length bodies, and professions. They’re written by the people who use them, for the people who use them.

And yes, they’re mandatory for central government. But they’re also designed to be flexible, scalable, and useful; whether you’re running a major transformation programme or a small local project.

A quick history lesson

The first functional standards were introduced in 2017, starting with project delivery. Since then, the suite has grown to cover everything from digital to security to internal audit.

In 2021, they became mandatory across central government. That was a big moment and a signal that we were serious about raising the bar and building a more capable, confident Civil Service.

The standard for project delivery has been at the heart of that journey. It’s now in its fifth iteration, and it’s more relevant than ever.

So, what’s the functional standard for project delivery all about?

The standard sets out what good looks like when it comes to delivering portfolios, programmes and projects in government. It covers everything from governance and assurance to planning, benefits management, and solution delivery.

It’s not a methodology or a checklist. It’s a set of expectations – the “what” and the “why” – that help us make better decisions, manage risk, and stay focused on outcomes.

It’s used by:

• senior leaders, to create the right environment for delivery success
• senior responsible owners and project teams, to guide delivery from start to finish
• assurance bodies, to test whether best practice is being followed
• methodology owners, to align tools and processes across government

And it applies to all types of projects – digital, infrastructure, transformation, military capability, and more – regardless of delivery approach.

What’s new in version 2.1?

The latest update builds on feedback from across government. It includes:

• stronger links to policy and evaluation, recognising the importance of evidence-based decision making
• a new clause on the role of the senior officer accountable for project delivery in each organisation
• clearer expectations for governance roles, now mandatory for portfolios, programmes and projects
• new content on transition, use and disposal of solutions
• updated references to The Teal Book, our definitive guide to project delivery in government

In short, it’s more complete, more practical, and more aligned with how we actually work.

Why it matters

Let’s be honest, government projects can be hard. They can be complex, high-stakes, and come under intense scrutiny. But they’re also how we turn policy into reality and improve people’s lives.

The functional standard for project delivery helps us do that better. It gives us a shared language, a common framework, and a clear set of expectations. It helps us avoid reinventing the wheel. And it gives confidence to ministers, to Parliament, and to the public that we’re doing things properly.

It also supports professional development. If you’re part of the project delivery profession, the standard is your north star. It links directly to the Project Delivery Capability Framework, and underpins the standards, guidance, training, tools and support available through the Government Projects Academy and the Government Project Delivery Library.

Built by the community, for the community

One of the best things about the functional standard for project delivery is that it’s not written in a vacuum. It reflects the experience and insight of hundreds of people across government – from delivery teams to directors general.

Every update is shaped by real-world feedback. Every clause is tested against what works in practice. And every word is there to help us deliver better outcomes, not just better processes.

What’s next?

We’ll continue to evolve the standard as the world changes, whether that’s new technologies, new delivery models, or new challenges. But the core principles will stay the same: clarity, consistency, and a relentless focus on value for money and public good.

If you haven’t looked at the functional standard for project delivery recently, now’s a great time to dive in. You’ll find it on projectdelivery.gov.uk, alongside The Teal Book and other helpful resources.

And if you’ve got feedback, ideas or questions we’d love to hear from you.