Project Governance: a guide to governing project delivery

Project governance is the framework of decision rights, roles, and accountability that keeps projects directed toward what the organisation is trying to achieve. It's what decides who can approve what, who answers for a project's success, and how decisions get escalated when something needs a call above the project manager's authority. Good governance is the difference between a portfolio of projects that serves the strategy and a collection of initiatives running on their own momentum.

It's worth separating this from corporate governance, which people often mean by "organisational governance." Corporate governance is about how the whole organisation is directed and controlled, the board, the executives, shareholder accountability. Project governance is the delivery-level expression of that: the rules and roles that govern how projects and programmes are run. This guide is about the second, though the two connect, and we'll come back to how.

What a project governance framework contains

A governance framework is the set of structures and rules that control how projects are directed. Most frameworks cover the same core components.

Decision rights. Who can approve what, and up to what threshold. A clear framework says which decisions a project manager can make alone, which need the project board, and which go higher. Ambiguity here is where projects stall or where bad calls get made by people without the authority to make them.

Roles and accountability. Who is responsible for what. The key roles are the sponsor or senior responsible owner (accountable for the project delivering its benefits), the project board (which oversees and steers), the project manager (who runs delivery), and the PMO (which provides assurance and standards). Governance falls apart when these are unclear.

Stage gates. Defined points where a project must be reviewed and approved to continue. Gates force a deliberate decision to keep investing, rather than letting projects drift forward on inertia.

Reporting and escalation. How information flows up and how problems get raised. Governance depends on leadership having a current, honest view, and on there being a clear route for escalating what the project team can't resolve alone.

Assurance. Independent checks that the project is being run properly and its reporting can be trusted. This is often a PMO function.

The roles in project governance

Governance is carried by people in defined roles.

The sponsor or senior responsible owner is accountable for the project overall, especially for it delivering its intended benefits. They own the business case and champion the project at leadership level.

The project board or steering committee provides direction and oversight, making the decisions that sit above the project manager and holding the project to account at the gates.

The project manager runs delivery within the authority the framework gives them, escalating what falls outside it.

The PMO provides the standards, the assurance, and often the reporting that governance runs on. Our guides to what a PMO is and PMO roles cover this in depth.

How to set up a governance framework

Standing up project governance is itself a piece of work, and the goal is to make it proportionate. Too little governance and projects run unchecked; too much and you smother delivery in approvals. The shape of it:

1. Define decision rights. Set out clearly who can approve what, and at what thresholds. This is the foundation everything else rests on.
2. Establish the board and roles. Name the sponsor, set up the project board, and make the accountabilities explicit.
3. Set the gates and reporting. Decide the review points a project must pass and how it reports between them.
4. Right-size it to complexity. A small, low-risk project needs light governance; a large, high-risk programme needs more. Applying the same heavy framework to everything is a common and costly mistake.

Governance at portfolio and strategy level

Everything above governs a single project. Governance becomes more powerful, and more demanding, when it operates across the whole portfolio.

At portfolio level, governance is about more than keeping individual projects on track. It's about whether the organisation is running the right projects at all, whether the portfolio still maps to the strategy, and where investment should move as priorities shift. This is the governance that connects delivery to strategy, and it's where a PMO's role becomes genuinely strategic rather than administrative.

Portfolio governance depends on visibility that single-project governance doesn't. To govern a portfolio you need a current view across every project at once: how each maps to strategic priorities, where resources are committed, which investments are paying off. Assembling that by hand from separate project reports is slow enough that the governance decisions end up made on stale information. Giving leadership a live, portfolio-wide view is one of the things a portfolio management platform is built for, and it's what makes governance at this level workable rather than theoretical.

Common governance failures

Governance goes wrong in recognisable ways. Too much process, where approvals pile up and delivery grinds. Unclear decision rights, where no one knows who can make a call. And governance theatre: boards that meet regularly, review papers, and make no actual decisions, so the governance exists on paper but not in practice. The test of good governance is whether it makes better decisions happen faster, not whether the meetings are in the calendar.

Frequently asked questions

What is project governance?
The framework of decision rights, roles, and accountability that keeps projects directed toward the organisation's goals. It defines who approves what, who is accountable, and how decisions and problems are escalated.

What's the difference between project governance and corporate governance?
Corporate governance is how the whole organisation is directed and controlled (boards, executives, shareholders). Project governance is the delivery-level framework that governs how projects and programmes are run. Project governance sits within, and should support, corporate governance.

Who is responsible for project governance?
It's shared across roles: the sponsor or senior responsible owner (accountable overall), the project board (direction and oversight), the project manager (delivery), and the PMO (standards and assurance).

What is a governance framework?
The set of decision rights, roles, stage gates, reporting, and assurance that control how a project is directed. It should be sized to the project's complexity and risk.