Project Management guide · Risk, quality and control
Project Governance: Framework, Structure and Roles
Project governance is the framework of roles, decision rights and controls that directs a project and holds it to account. It answers three questions: who can decide what, how those decisions are made, and how the organisation knows the project is still worth doing. This guide explains the structure, the key mechanisms and how to set up governance that is proportionate to your project.
Key takeaways
- Project governance decides direction and holds the project to account; project management plans and delivers the work.
- A typical structure has a sponsor, a steering committee or project board, a project manager, a PMO and some form of independent assurance.
- Clear decision rights, tolerances and escalation routes let senior people manage by exception instead of approving everything.
- Stage gates and a regularly re-checked business case stop projects drifting on after they stop being worthwhile.
- Good governance is proportionate: a small internal project needs a one-page framework, a major programme needs much more.
What is project governance?
Project governance is the set of roles, responsibilities, decision rights, processes and controls that directs and oversees a project on behalf of the organisation that funds it. It defines who is accountable, who can approve what, how progress is reported and how the project is checked against its business case.
Governance sits above day-to-day delivery. Its job is to make sure the organisation is doing the right project, doing it in the right way, and stopping or changing course when the case for the project changes. Done well, it speeds decisions up, because everyone knows who decides and on what information.
Many practitioners describe governance with a simple three-pillar model. It is a useful way to check a framework is complete, though it is a teaching model rather than a formal standard:
- Structure: the decision-making bodies and how they relate, such as the sponsor, steering committee, project board and PMO.
- People: the named individuals in those roles, with the authority, time and skills to fill them.
- Information: the reports, logs and reviews that give decision-makers an honest view of progress, risks and benefits.
Project governance vs project management
The two are closely linked but they are not the same. Governance directs and oversees; management plans and delivers. A project manager works within the authority that governance delegates.
| Project governance | Project management | |
|---|---|---|
| Purpose | Direct, authorise and hold to account | Plan, organise and deliver |
| Key question | Is this still the right project, run the right way, and is it worth continuing? | How do we deliver the agreed outcomes within the agreed limits? |
| Who | Sponsor, steering committee or project board, PMO, assurance | Project manager, team leads and the project team |
| Typical decisions | Approve funding and stage progression, accept major risks, approve significant changes, stop or close the project | Assign work, manage day-to-day issues, approve changes within tolerance |
| Time horizon | Whole life of the project and the benefits after it | Current stage, sprint or work package |
Project governance vs PMO
A project management office (PMO) supports governance but is not the governing body. It typically sets standards and templates, consolidates reporting and may carry out assurance reviews. Decisions such as approving funding or stopping a project normally sit with the sponsor, the board or a portfolio committee, not with the PMO itself.
Project governance vs corporate and portfolio governance
Corporate governance is how the whole organisation is directed and controlled by its board. Portfolio governance decides which projects and programmes to fund and how to balance them. Project governance applies those rules to a single project. The three should connect: a project's tolerances, reporting and stage gates should reflect the organisation's wider policies.
Project governance structure and roles
Titles vary between organisations and methods, but most governance structures contain the same roles. On a small project one person may hold several; on a large one each may be a group.
Project sponsor
The sponsor owns the business case and is ultimately accountable for the project delivering its benefits. They secure funding, chair or sit on the steering committee, make or escalate the big decisions, and champion the project with senior stakeholders. An absent sponsor is one of the most common causes of weak governance.
Steering committee or project board
A small group of senior people who give direction, approve each stage and resolve issues the project manager cannot. In PRINCE2 the project board has three roles: the executive (who represents the business and owns the business case), the senior user (who represents the people who will use the outputs) and the senior supplier (who represents those designing and building them). Keep it small; a board of 12 rarely decides anything quickly.
Project manager
Runs the project day to day within delegated authority: planning, coordinating the team, managing risks and issues, and reporting honestly upwards. When a forecast breaches tolerance, the project manager escalates with options rather than solving it alone.
PMO
Sets methods and templates, supports planning and reporting, maintains the portfolio view and often runs health checks. In some organisations a portfolio PMO also prepares information for investment committees.
Project assurance
Independent checks that the project is being run properly and that reports reflect reality. Assurance may come from the PMO, internal audit, an external reviewer or, in PRINCE2, from assurance roles appointed by the board. It should be independent of the project manager.
Change control board
On larger projects a change control board, or the steering committee itself, decides on changes above the project manager's authority.
Write the roles down. A RACI matrix is the simplest way to show who is responsible, accountable, consulted and informed for each key decision; our free RACI matrix template gives you a ready-made layout.
Decision rights: who decides what
The most practical governance document is a short table of decision rights. It removes the question 'can I approve this?' and stops small decisions travelling to the board. The thresholds below are an illustration only; set your own to match your organisation's financial delegations and the project's risk.
| Decision | Project manager | Sponsor | Steering committee / board |
|---|---|---|---|
| Re-plan tasks within a stage | Decides | Informed | - |
| Change within tolerance (for example up to £10,000 or 1 week) | Decides and logs | Informed | - |
| Change beyond PM tolerance but within stage tolerance | Recommends | Decides | Informed |
| Forecast breach of stage tolerance | Raises exception report | Recommends | Decides |
| Approve the next stage | Prepares end-stage report | Recommends | Decides |
| Accept a high residual risk | Recommends | Decides or escalates | Decides if above sponsor's limit |
| Stop or close the project | Recommends | Recommends | Decides |
Record every significant decision in a decision log: what was decided, by whom, when, which options were considered and why. It protects the project manager, helps new team members understand history and feeds lessons learned at the end.
Key components of a project governance framework
A governance framework is the documented set of rules for one project, usually agreed at initiation and recorded in the project charter or project initiation document. These are the components most frameworks include:
| Component | What it does | Typical document |
|---|---|---|
| Business case | Justifies the investment and is re-checked at each stage gate | Business case |
| Roles and terms of reference | Defines who sits on each body, what it decides and how often it meets | Charter, terms of reference, RACI |
| Decision rights | Sets who can approve what, with financial and time thresholds | Delegation table |
| Stage gates | Formal go / no-go points between phases | End-stage report, gate checklist |
| Tolerances | Agreed limits for time, cost, scope, quality, risk and benefits | Charter or project plan |
| Escalation routes | How and when issues move up a level | Escalation path, exception report |
| Reporting | Regular, honest information for decision-makers | Status reports, dashboards |
| Risk, issue and change control | How threats, problems and changes are logged and decided | RAID log, change log |
| Assurance | Independent checks on health and compliance | Health check or gateway review |
| Benefits review | Confirms whether the expected value arrives | Benefits plan, post-project review |
If you are starting from scratch, our free business case template and RAID log template cover two of the documents governance relies on most.
Project governance in PMBOK and PRINCE2
Both major standards treat governance as central, though they describe it differently.
- PMBOK Guide, eighth edition: PMI published the eighth edition in November 2025. It organises the guide around seven performance domains, and governance is the first of them, alongside scope, schedule, finance, stakeholders, resources and risk. One of its six principles is to lead accountably. See our PMBOK Guide overview.
- PRINCE2 (7th edition): governance runs through its seven principles, several of which are governance rules: ensure continued business justification, define roles, responsibilities and relationships, manage by stages and manage by exception. The organising practice sets out the project board and assurance roles, and tolerances can be set for time, cost, scope, quality, benefits, risk and sustainability.
- Agile frameworks: the Scrum Guide does not describe project governance, but it gives the product owner clear accountability for maximising value and makes progress visible every sprint, which governance bodies can use directly.
Our own view: take the vocabulary from whichever method your organisation uses, but judge your framework by whether decisions are fast, well informed and recorded.
How to set up project governance step by step
- Check what already exists. Ask the PMO or finance team for the organisation's delegation limits, stage-gate rules and reporting standards. Do not invent a parallel system.
- Confirm the sponsor. Agree one accountable sponsor with the authority and time to do the job.
- Size the governance. Decide how much control the project needs based on cost, risk, complexity and visibility (see the scaling table below).
- Form the decision-making body. Name the steering committee or project board members, write short terms of reference and set a meeting rhythm.
- Agree decision rights and tolerances. Fill in a delegation table and set tolerances for time, cost and scope at project and stage level.
- Define stage gates. Choose the decision points, usually at the end of each project phase, and what evidence each gate needs.
- Set up reporting and logs. Agree the status report format and frequency, the escalation path and where the RAID log, change log and decision log live.
- Plan assurance. Decide who will run independent health checks and when.
- Record and communicate it. Put the framework in the charter, share it with everyone involved and include it in the communication plan.
- Review it at each gate. Tighten or lighten governance as the risk profile changes.
Project governance framework template
Copy this table into your charter and replace the example content. The figures are illustrative.
| Element | Example content |
|---|---|
| Sponsor | Operations director: owns business case and benefits |
| Steering committee | Sponsor (chair), finance business partner, head of customer service, IT supplier lead; meets monthly and at each stage gate |
| Decision rights | PM approves changes up to £10,000 and 1 week; sponsor up to £50,000 and 4 weeks; board above that |
| Project tolerances | Cost ±10%; end date +6 weeks; mandatory scope fixed |
| Stage tolerances | Cost ±5%; stage end date +2 weeks |
| Stage gates | End of initiation, design, build and test; go / no-go recorded in the decision log |
| Reporting | Weekly status to sponsor; monthly highlight report to board; exception report within 2 working days of a forecast breach |
| Escalation path | Issue owner → project manager → sponsor → steering committee |
| Risk and change | RAID log reviewed weekly; change requests via the change log |
| Assurance | PMO health check at the end of each stage; independent review before go-live |
| Key documents | Charter, business case, project plan, RAID log, change log, decision log |
Our project charter template and change request template give you a starting point for the charter and the change log.
Tolerances, escalation and management by exception
Tolerances are the agreed amount a project or stage can deviate from plan before the next level of authority must be involved. Management by exception, a core PRINCE2 principle, means senior people do not review every decision; they set tolerances, receive regular reports and step in only when a forecast breaches those limits. This keeps the board focused on decisions only it can make.
When a forecast goes beyond tolerance, the project manager raises an exception report that explains the cause, the impact and the options, with a recommendation. The board then chooses an option, and the result is recorded in the decision log.
Worked example
A £2 million office relocation sets a cost tolerance of ±5% (£100,000). In month four the project manager forecasts an overrun of £140,000 because of extra electrical work. As this is outside tolerance, she sends an exception report to the board with three options: absorb the cost from contingency, reduce the scope of meeting-room technology, or delay the move by six weeks to retender the electrical work.
The board approves £90,000 from contingency and trims £50,000 of scope, which brings the forecast back within tolerance. The decision is logged, the plan is re-baselined and the tolerance for the remaining stages is confirmed. The whole exchange took a week, because everyone knew the threshold, the format and who decided.
Scaling governance to the size of the project
Too little governance lets projects drift; too much slows every decision. Match the weight of governance to the project's cost, risk and visibility.
| Project type | Typical governance |
|---|---|
| Small internal project | Named sponsor, one-page charter with decision rights, fortnightly status note, simple issue and risk log |
| Medium project | Sponsor plus small steering group, stage gates at major phases, weekly status, RAID and change logs, PMO check at go-live |
| Large or high-risk project | Formal project board, full delegation table and tolerances, monthly board and exception reporting, independent assurance at each gate |
| Programme or portfolio | Programme board above project boards, benefits management, portfolio prioritisation and consolidated reporting through a PMO |
Governance in Agile projects
Agile teams still need governance, but it looks different. Instead of approving detailed plans up front, governance bodies review working product often and fund outcomes over time.
- Fund products or value streams, not fixed scope. Agree a budget and a goal, then review value delivered at regular intervals.
- Use the product owner's accountability. The product owner makes most scope decisions; governance sets the boundaries.
- Make reviews the evidence. A sprint review or quarterly planning event shows real progress, which is better evidence than a written status report.
- Keep gates light and frequent. Short, regular decision points replace long phase gates.
- Set guardrails, not approvals. Agree security, architecture and spending rules the team can apply themselves.
- Adapt the PMO. An agile PMO supports teams with metrics and coaching rather than document checks.
Hybrid projects often keep formal stage gates for funding and contracts while running delivery in sprints. That works well as long as the gate criteria use the same evidence the team already produces.
Signs of weak governance and common mistakes
| Warning sign | What to do about it |
|---|---|
| Nobody can say who can approve a particular change | Publish a delegation table and a RACI for key decisions |
| The sponsor is absent or delegates everything | Agree the sponsor's time commitment up front; escalate to the portfolio owner if it is not met |
| The project continues after the business case has failed | Re-check the business case at every gate, and treat stopping as a valid outcome |
| Reports stay green until a sudden crisis | Define RAG ratings against tolerances and reward early bad news |
| The board discusses detail and avoids decisions | Send papers in advance with a clear decision requested and options |
| Small decisions take weeks | Raise the project manager's tolerances and use management by exception |
| Decisions are made in corridors and forgotten | Keep a decision log and confirm decisions in writing |
Most of these problems are cultural as much as procedural. A framework only works if the sponsor and board take part, and if the project manager feels safe reporting problems early. Good stakeholder management helps with both.
Tools that support project governance
Governance mostly depends on people and clear rules, but software makes the information side easier. Look for portfolio dashboards, approval workflows, audit trails, permission controls and a single place for the RAID, change and decision logs.
Among the tools we review, Wrike is a strong fit for organisations that want cross-project dashboards, request forms and approval flows in one place, and Smartsheet suits teams that prefer a spreadsheet-style approach with portfolio reporting.
Free templates for this topic
Frequently asked questions
What is project governance?
Project governance is the framework of roles, decision rights, processes and controls that directs and oversees a project, so the organisation knows who decides what and whether the project is still worth doing.
What are the three pillars of project governance?
A widely used model describes three pillars: structure (the decision-making bodies), people (who fills each role) and information (the reports and reviews that inform decisions). It is a helpful checklist rather than a formal standard.
What is the difference between project governance and project management?
Governance sets direction, authorises funding and stages, and holds the project to account. Project management plans and delivers the work within the authority that governance delegates.
Who is responsible for project governance?
The sponsor is ultimately accountable, supported by a steering committee or project board. The PMO and assurance functions support governance, and the project manager works within it.
What is a project governance framework?
The documented rules for a specific project: roles, decision rights, tolerances, stage gates, escalation routes, reporting, logs and assurance. It is usually recorded in the project charter or initiation document.
What does a steering committee do in project governance?
It gives direction, approves stages and significant changes, resolves escalated issues and decides whether the project should continue. It should be small enough to make decisions quickly.
What is the difference between a PMO and project governance?
Governance is the decision-making framework. A PMO is a team that supports it by setting standards, consolidating reports and often running assurance, but it does not normally own the major decisions.
What is a stage gate?
A formal decision point at the end of a phase where the board reviews progress, risks and the business case before approving the next phase, changing direction or stopping.
What are tolerances in project governance?
Permitted deviations from plan, for example ±5% on cost or two weeks on a stage end date, within which the project manager can act without escalating. PRINCE2 also allows tolerances for scope, quality, benefits, risk and sustainability.
What is management by exception?
A principle, central to PRINCE2, where senior managers set tolerances and step in only when a forecast breaches them. It saves their time and speeds up routine decisions.
How does project governance work in Agile?
Agile governance funds outcomes over time, relies on the product owner for scope decisions, uses frequent reviews of working product as evidence and replaces long phase gates with lighter, more frequent decision points.
What is a decision log?
A record of significant decisions showing what was decided, by whom, when, which options were considered and why. It supports accountability, audits and lessons learned.
How much governance does a small project need?
Usually a named sponsor, a one-page charter with decision rights and tolerances, a short regular status update and a simple risk and issue log. Add more only if cost, risk or visibility justify it.
What happens to a project without governance?
Decisions stall or are made by the wrong people, risks go unescalated, scope grows without approval and projects can continue long after they have stopped being worthwhile.