Domain: Governance

Governance is one of two performance domains that are new in PMI®'s PMBOK® Guide, Eighth Edition, and it is the busiest. It holds nine of the 40 processes, more than any other domain, and it is the only domain with a process in every focus area. For an owner, Governance answers the questions that decide most disputes: who can decide what, on what evidence, and how fast. This lesson explains the domain, its processes and its models, then designs decision rights for Northgate.

Learning outcomes

• Explain what the Governance domain covers and how project governance sits inside an organization's own governance.
• Name the nine Governance processes and place each in its focus area.
• Compare common governance models and choose one for a given project.
• Set decision rights, thresholds and an escalation path for Northgate (fictional).

The lesson

What the domain covers

In the Eighth Edition, Governance is about the framework that guides decisions on the project: the structures, roles, decision rights, policies and oversight that keep the work aligned with the organization's strategy and rules. Commentators summarize it as oversight, decision-making, compliance and alignment with organizational policy. It is not the same as reporting. Good governance produces decisions; weak governance produces dashboards.

Project governance does not start from a blank page. The performing organization already has a board, delegated authorities, financial controls and policies, and regulators and lenders add their own conditions. Project governance inherits all of that and adds what the specific project needs. The test is whether it helps the team decide faster and better. If it only adds paperwork, it is the wrong size, and lesson 5 on tailoring applies.

Nine processes, every focus area

Figure 1 places the nine Governance processes against the five focus areas. Read across and you see the project's governance spine. Initiate Project or Phase authorizes the work. Plan Sourcing Strategy and Integrate and Align Project Plans set how the project will be bought and how its plans fit together. Manage Project Execution, Manage Quality Assurance and Manage Project Knowledge keep the work, its quality system and its memory on track. Monitor and Control Project Performance and Assess and Implement Changes watch the whole and decide on change. Close Project or Phase finishes it formally. Lessons 12 to 16 covered each focus area; this domain is the thread through all of them.

Governance models

There is no single right structure. Published commentary on the Eighth Edition describes a range. At one end is structured governance, typical of predictive work, where a sponsor, a board or a PMO oversees performance against the organization's requirements. At the other is self-governance, more common on adaptive teams, where decision-making is spread across the team. Self-governance works only with clear shared objectives, leading indicators and fast feedback; without them, decisions fragment.

Within structured governance, four shapes are common:

• Sponsor-led: one accountable executive decides. Fits smaller, simpler projects.
• Steering board: a small committee decides. Fits larger investments and projects that touch several departments.
• Portfolio-linked: a portfolio body sets priorities across projects. Fits owners running programs.
• Shared with suppliers: owner and supplier governance meet at defined points. Fits any project with major external delivery, which is every construction project.

Most owner building projects combine a steering board inside the owner with shared governance at the contract boundary. The model matters less than three things: clear ownership of each decision, a regular review rhythm, and a known escalation route.

Decision rights, thresholds and escalation

Decision rights say which decisions the project team can make on its own and which must go up. Thresholds make that concrete: a dollar value, a number of days on a key milestone, a risk score. Escalation is what happens when a threshold is crossed. A good escalation is not just "this is red". It states the impact, the options and a recommendation, so the person receiving it can decide in one meeting.

Governance also needs the right measures. Lagging indicators, such as cost to date or milestones achieved, confirm what has happened. Leading indicators, such as submittals overdue, RFIs open past their response time or decisions waiting on the owner, show trouble before it lands. Owners tend to over-report lagging measures because they are easy to count. The "be an accountable leader" principle in lesson 9 is the human side of the same idea: someone owns each decision, and everyone knows who.

Project governance meets contract governance

On a construction project, the contract has its own governance. Under CCDC 2-2020 the Consultant administers the contract, issues instructions, certifies payment and processes changes, and the contract sets notice periods and response times. The owner's internal governance has to fit around that. If the owner's steering committee meets monthly but the contract expects an owner decision within days, the owner will be late, and late owner decisions are a common source of contractor delay claims. Owner governance should be designed to meet the contract's clock, not the other way round.

Northgate worked example

Northgate Distribution Centre (fictional) is a 12,000 m² tilt-up warehouse in Vaughan for Northgate Logistics Inc. (fictional), a private owner-occupier with an owner's project manager and an owner's representative. Halvorsen Builders Ltd. (fictional) builds under CCDC 2-2020 for $34,950,000 and Ridgeline Architects Inc. (fictional) is the prime consultant under OAA 600. The construction budget is $38,000,000 including $3,050,000 owner contingency. See the Northgate fact sheet.

Figure 2 shows an illustrative governance structure: a steering board inside Northgate Logistics, and shared governance at the contract boundary through Ridgeline. The executive sponsor and steering committee are an illustrative design for this lesson; the fact sheet does not fix them.

Decision rights and thresholds

Figure 3 shows illustrative thresholds for changes and contingency. The numbers are teaching values, not a recommendation for any real project; each owner sets its own against its delegated authorities. What matters is the shape. Small, in-budget decisions stay with the owner's PM so the contract's response times can be met. Anything that moves a key milestone goes up regardless of cost, because M9 and M10 drive the owner's business. Cumulative contingency use is watched as well as single changes, so a stream of small changes cannot drain the reserve unnoticed.

View the data

Level	Single change	Milestone effect	Contingency or budget
Owner's project manager	Up to $25,000	None on M9 or M10	Within contingency
Steering committee	$25,000 to $250,000	Any effect on M9 or M10	Cumulative use passes 50% of $3,050,000
Executive sponsor	Over $250,000	Any	Any change to, or forecast over, $38,000,000

Governance processes, Northgate outputs

One check is worth doing at kickoff (M1, Tuesday January 19, 2027): compare the ladder with the contract's clock. If a change touching M9 must go to a monthly steering committee, but the contract expects an owner response within days, the committee needs a way to decide between meetings, such as a standing call or written approval by the sponsor.

Owner's move

• Write decision rights down before kickoff. Put them in the project management plan and tell Ridgeline who can sign what.
• Match governance to the contract's clock. Build a fast path for urgent decisions.
• Escalate with options. Impact, options, recommendation, every time.
• Track leading indicators. Overdue owner decisions are the first sign of a future delay claim.
• Watch cumulative contingency, not just single changes.

Common mistakes

1. Equating governance with reporting. Reports without decisions are overhead.
2. Governance slower than the contract. Late owner decisions become contractor claims.
3. One threshold only. Dollar limits alone miss small changes that move a critical milestone.
4. Unclear authority at the contract boundary. If Ridgeline does not know who can approve, nothing moves.
5. Copying a big-project structure onto a small one. Tailor governance to the risk.

Quick quiz

1. How many of the 40 processes belong to the Governance domain?

   1. 5
   2. 7
   3. 9
   4. 12

2. Which Governance process sits in the Planning focus area?

   1. Initiate Project or Phase
   2. Plan Sourcing Strategy
   3. Manage Project Knowledge
   4. Close Project or Phase

3. A $12,000 change would delay Northgate's M9 by three days. Under the illustrative ladder, who decides?

   1. The owner's PM, because it is under $25,000
   2. The steering committee, because it affects M9
   3. Ridgeline alone
   4. Halvorsen

4. What should a good escalation contain?

   1. A red status flag
   2. The full risk register
   3. Impact, options and a recommendation
   4. A request for more budget only

5. Which is a leading indicator for an owner?

   1. Cost to date
   2. Milestones achieved
   3. Owner decisions overdue
   4. Final cost

Show answers and explanations

1. C. Nine, the most of any domain, with at least one in every focus area.
2. B. Plan Sourcing Strategy and Integrate and Align Project Plans are the Governance processes in Planning.
3. B. Any effect on M9 or M10 goes to the steering committee, whatever the cost.
4. C. Decision-makers need the impact, the choices and the team's recommendation to decide quickly.
5. C. Overdue decisions show trouble before it appears in cost or milestones.

Key terms

Governance domain

The PMBOK Guide 8 performance domain covering the structures, roles, decision rights and oversight that guide a project.

Decision rights

A statement of who may make which decisions, and within what limits.

Threshold

A value, such as a dollar amount or days of delay, above which a decision must be escalated.

Escalation

Moving a decision to a higher authority, with impact, options and a recommendation.

Steering committee

A small group of senior owner representatives that makes decisions above the project manager's authority.

Leading indicator

A measure that signals future performance, such as overdue submittals or decisions.

References

1. Project Management Institute, PMBOK® Guide, Eighth Edition (product page; published November 2025).
2. Project Management Compass, Inside PMBOK® 8: Governance performance domain.
3. PM Exams, PMBOK 8 core governance models, metrics and control processes.
4. Elizabeth Harrin, Rebel's Guide to PM, Project performance domains explained (updated for PMBOK 8) (January 2026, updated July 2026).
5. 4PMTI, PMBOK 8th Edition: principles and key changes.
6. Project Management Academy, PMBOK® 8th Edition: 2026 release date, changes and what to expect (December 2025).
7. Project Together Office, PMBOK 8 focus areas: all 40 processes.

Verified on November 6, 2026.

Next lesson in this trackDomain: Scope