Program and portfolio governance, explained
What is program governance?
Program governance is the set of roles, decision rights, gates and reviews that keeps a program pointed at its intended outcome. It settles who may approve, change or stop the work, and on what evidence. Project governance does the same for one project. Portfolio governance decides which programs and projects are funded, and in what order.
Governance is one of those words that makes people tired before you have finished saying it. It sounds like committees, templates and approvals that slow everything down. Done well, it is the opposite. Good governance is what lets a leader make a decision in the meeting, on the numbers in front of them, and move on.
This guide explains the three levels of governance, the five parts every framework needs, and how to tell whether yours is working. It applies whether you run a transformation, a strategy office or a project management office, and whether or not you use software to do it.
Three levels, one system
Project, program and portfolio governance are often treated as three separate disciplines with three separate teams. They work best as one system, where each level answers a different question and hands its answers up to the next.
| Project governance | Program governance | Portfolio governance | |
|---|---|---|---|
| The question | Is this project delivering what it promised? | Are these projects together producing the outcome? | Are we funding the right work? |
| Who decides | Sponsor and project board | Program board or steering committee | Executive or investment committee |
| What it looks at | Scope, schedule, cost, risk | Benefits, dependencies, sequence | Fit with strategy, value, capacity |
| How often | Weekly or every two weeks | Monthly | Quarterly |
The levels connect through the numbers. A project reports its progress and its forecast. The program adds them up, checks the dependencies between them and asks whether the outcome is still reachable. The portfolio compares programs against each other and against the strategy, and moves money to where it does the most good.
When the levels use different numbers, the system breaks. The project board sees one forecast, the steering committee sees another, and the investment committee sees a third, rebuilt from both. Most of the cost of poor governance is the time spent reconciling those versions.
Where a transformation fits
A transformation is a program with a financial target, often large, often spread across the whole organization. Its governance leans heavily on value: how much each initiative is worth, how sure we are, and whether the money arrived. That is why transformation offices use value stages, covered in the guide to stage gates and value tracking.
The five parts of a governance framework
Every working governance framework has the same five parts. Frameworks differ in the details, but if one of these five is missing, the framework will not hold.
1. Roles and decision rights
Every decision needs one name next to it. Who proposes a new initiative? Who approves its business case? Who can stop it? Who is told? A committee can advise, but a committee cannot be accountable. The simplest test is to pick any recent decision and ask who made it. If the answer takes more than a sentence, the decision rights are not clear.
A transformation office usually names an executive sponsor, a chief transformation officer, a finance lead, and for each workstream a sponsor, a lead and a finance partner. Each initiative has one owner. Write down which of them approves what, and keep the list short enough to remember.
2. Stage gates
A gate is a point where the work must prove it is ready to go on. Gates stop two common failures: starting work that was never properly checked, and reporting value that was never properly earned. Each gate needs written entry criteria, named approvers and a deadline for the decision. Without the deadline, gates become queues.
3. Status rules
Green, Amber and Red should mean the same thing in every report. Write down what each color means. For schedule, base it on milestones: for example, Red if a critical milestone is more than seven days late. For value, base it on the latest estimate against the plan: Amber when the estimate falls more than 10% below plan, Red when it falls more than 25% below. Once the rule is written, status stops being a matter of mood.
4. A reporting rhythm
Decide which meeting sees which page, and how often. A weekly update from each owner, frozen at a fixed time, feeds a weekly or fortnightly steering committee. A monthly review looks at value against plan. A quarterly review looks at the strategy as a whole. Each meeting should be able to decide something, and each page should be built for that decision.
5. Value tracking
What is the work worth, how sure are we, and did it arrive? Value tracking is the part most often missing from project governance, and the part a transformation cannot do without. It needs one profit metric for the whole program, a plan saved at the point of commitment, a latest estimate kept current, and a confirmation by finance before anything is counted as realized.
Governance is not bureaucracy
The test of good governance is simple. Can a decision be made in the meeting, on the data in front of you? If the answer is yes, the governance is working. If the meeting ends with a request for another deck, it is not.
Bureaucracy grows when governance asks for information nobody uses. Every field on a form, every column in a report and every approval step should earn its place by feeding a decision. If nobody can name the decision, remove it. A short framework that people follow beats a thorough one that they work around.
of strategic initiatives met their original goals and business intent in PMI's 2014 study, which put the loss at US$109 million for every US$1 billion invested.
Source: PMI, Pulse of the Profession: The High Cost of Low Performance, 2014Seven signs your governance is failing
- Every project is green until the month it fails. Status is chosen, not calculated.
- Two versions of the same number reach the board. The levels are not working from one record.
- Nobody can say who approved a change. Decision rights exist on paper only.
- Benefits are claimed and never checked. There is no gate between promised and realized value.
- The review meeting is spent reading slides. The rhythm reports, but does not decide.
- Projects start without a business case. The first gate is missing or skipped.
- Nothing is ever stopped. Gates approve, but never return or close.
A twelve question checklist
Twelve questions a sponsor can ask this week. Each no points to a part of the framework to fix.
- Can I name the one person accountable for each workstream?
- Does every initiative have one owner?
- Are the entry criteria for each gate written down?
- Does every gate decision have a deadline?
- Do Green, Amber and Red follow a written rule?
- Is the plan saved at the point we committed to it?
- Do owners update their status at a fixed time each week?
- Does the steering committee see one version of the numbers?
- Does finance confirm value before we call it realized?
- Is each benefit counted in one place only?
- Have we stopped or returned anything in the last quarter?
- Can I trace a target down to the milestones that deliver it?
Where software helps
A governance framework lives or dies by whether people use it. Software helps when it makes the right way the easy way: when the gate checks itself, the status calculates itself, and the steering committee page builds itself from the weekly updates. It hurts when it adds fields nobody reads.
Centric Governance Central builds these five parts into one record inside Microsoft 365: roles per item, L0 to L5 gates with named approvers, status by rule, a Friday pulse and value tracked from estimate to realized. See how CGC works.
Questions
Frequently asked
What is the difference between governance and management?
Management runs the work day to day. Governance sets the rules the work runs under: who decides, on what evidence, and how progress is reported.
Who should chair a steering committee?
The executive sponsor of the program, with the chief transformation officer or program director running the agenda.
How often should a portfolio be reviewed?
Quarterly for funding and priorities, with monthly checks of value against plan.
What is a governance framework?
A written set of roles, decision rights, gates, status rules, reporting rhythm and value tracking that a project, program or portfolio runs under.
Do not take our word for it. Take Microsoft's.
CGC is listed and transactable on Microsoft Marketplace, co-sell ready with Microsoft, and the subject of a Microsoft partner success story. Centric is a Microsoft Solutions Partner for Data & AI (Azure).
Centric's enterprise-grade platform unifies strategic planning, KPI management, program execution, and governance workflows into a single, secure system of record.

- February 2026Listed on Microsoft MarketplaceCGC goes live on Microsoft Marketplace as a transactable offer.
- May 2026Named in the Microsoft Marketplace blogMicrosoft features CGC among new transactable offers on 26 May 2026.
- October 2026Co-sell ready with MicrosoftMicrosoft sellers can work with Centric on customer purchases.
- November 2026Featured in a Microsoft partner success storyMicrosoft publishes how Centric built CGC into a scalable Marketplace offer, on 13 November 2026.
See it on your own sector's data.
A 30 minute walkthrough, built around a program like yours. No slides, the real product.
