Project Governance Explained: Who Decides What, and Why

Ask three people on the same project what governance means and you will usually get three lists: the steering group, the monthly report, the change control form. Those are the visible parts. Governance itself is quieter, and most teams notice it only when it is missing. A decision arrives, everyone in the room has a view, and nobody can say who is actually entitled to make it.

Project governance is the arrangement of decision rights, oversight and accountability that determines which decisions belong to the delivery team, which belong to the project manager, which belong to the sponsor or a steering group, and which sit above the project altogether. It also determines what those decision-makers are shown, and when. Meetings and reports are the machinery that serves all of this.

Governance is a decision system, not a meeting schedule

Four elements do most of the work.

Decision rights determine who may commit money, change a date, accept a deliverable, alter an agreed scope boundary, or accept a risk on the organisation's behalf. They attach to the type of decision, and seniority alone does not confer them.

Thresholds mark the point at which a decision stops belonging to one level and moves to the next. A threshold is only useful if it exists before the pressure arrives, and if it is expressed in something measurable: value, duration, risk exposure, contractual effect, reputational reach.

Accountability settles who answers for the result once the decision is taken. This is not always the person who made it, which is precisely why it needs stating.

Information is what a decision-maker needs to see in order to decide well, and how fast it can reach them. A steering group that meets monthly and receives a five-page pack the night before does not have a governance problem with its terms of reference. It has one with its information flow.

Project governance also sits inside the organisation's wider governance: the delegated authorities, policies and boundaries that apply whether or not a project exists. The project inherits that authority and then interprets it within the boundaries it has been given.

Section 2.1 of the PMBOK® Guide Eighth Edition treats governance as a performance domain running the whole length of the project, from authorising the work through integrated planning, oversight of execution, assurance, performance monitoring, change decisions and closure. That framing is worth holding on to, because governance is often mistaken for something that happens at the start and then recedes.

Three questions that settle who decides what

When a decision lands and the route is unclear, three questions resolve most cases faster than a search through the project management plan.

The first is what is actually being decided. Distinguish between interpreting something already agreed, making a new commitment, changing a commitment, and accepting a consequence. Interpretation usually stays with the team. New and changed commitments usually do not.

The second is what the decision consumes. Money is the obvious answer, and a decision can also consume contingency, float, goodwill, someone else's capacity, or the organisation's risk appetite. A change with no cost effect can still be well outside your authority if it moves a liability.

The third is who holds authority for that specific commitment, whether it is written down, and what that person would need in front of them to decide well. If you cannot answer the first part of that without making a phone call, you have found a governance gap worth recording, because the same gap will reappear. Routing a decision correctly and then presenting it badly wastes the authority you have just invoked.

The second question is the one most often skipped. Delegated financial limits are easy to check, and they encourage people to size a decision by its number rather than by what it changes.

When the threshold has not been set in advance

Consider a substation upgrade on a regional utility programme. Four weeks into construction, the contractor proposes a change to the switchgear layout. It recovers six weeks of programme, costs an additional £180,000, and shifts responsibility for one warranty element from the manufacturer to the contractor. The contractor needs an answer within five working days. The project manager holds a delegated approval limit of £50,000 against contingency. The programme board meets in three weeks.

The instinctive move is to check the number, see that £180,000 exceeds £50,000, and forward it upward with a covering note. That is incomplete, and it treats governance as a filter rather than a decision system.

A stronger reading starts with what is being committed. The warranty transfer is the significant element here, because it changes who carries a defect liability into operations long after the project has closed. That almost certainly falls outside a delegated financial authority regardless of the figure attached to it, and it brings in people the project manager may not have thought to consult: commercial, asset operations, possibly legal.

The five-day deadline then becomes a governance question in its own right. Waiting three weeks for a scheduled meeting is a decision to decline the change by default. The project manager's job is to establish whether an out-of-cycle decision is available, who can convene it, and what those people need in front of them: the options including doing nothing, the cost and programme position, the warranty implication stated plainly, a recommendation, and the consequence of the deadline passing.

Governance identified where the decision belonged. The project manager still had to work out what to do about a route that would not produce an answer in time.

What changes when the delivery approach changes

Governance is often assumed to be a predictive concern. The elements do not change across approaches, but what they attach to does.

In predictive delivery, decision rights cluster around baselines and phase transitions. The question is usually whether an approved commitment should change, and formal change control exists so that the answer is deliberate rather than incremental.

In adaptive delivery, authority attaches to prioritisation and release. A product owner may reorder a backlog freely, and that should never be routed through change control. Funding, release into a live environment, regulatory sign-off and contractual acceptance frequently sit elsewhere. Empowerment operates within boundaries, and those boundaries are governance.

Hybrid delivery fails in a specific way. Teams are told they are empowered to reprioritise, but nobody has said what they may not reprioritise: a regulatory commitment date, a contractual milestone, an integration window that another programme depends on. The team is not being difficult when it moves something it should not have moved. It was never told where the edge was.

Governance intensity should be proportionate to risk, value and complexity. Its clarity should not vary at all.

Reading the authority in the situation

For a PMP® candidate, governance questions rarely turn on definitions. They present a situation and expect you to work out which level a decision belongs to, and what the project manager should do first. The 2026 Examination Content Outline puts establishing project governance in the Business Environment domain, which carries 26 per cent of exam items, and the task covers escalation paths and thresholds as well as structure, reporting and success metrics. The useful preparation habit is to reason from delegated authority and from what is being committed, rather than from job titles. Governance scenarios are one of the places where candidates most often answer from seniority, and working through them alongside a tutor and other candidates is one of the practical benefits of structured PMP® Exam Preparation.

On a live project, the test is simpler. Write down the five decisions most likely to arrive in the next quarter. For each one, name the person who can make it, the threshold that moves it, and how long it takes to reach them. Any row you cannot complete is a decision that will stall when it matters, and it is far cheaper to settle it now than during the week it arrives.

Andre Malowney

Interested in going further?

Reading a situation for where a decision belongs, rather than for who happens to be senior, is a skill that develops through practice on realistic scenarios. Omega's structured preparation works through governance, escalation and authority questions in exactly that way, with the reasoning made explicit.

The Governance Performance Domain in the PMBOK® Guide Eighth Edition sets out how oversight, decision-making and accountability run across the full life of a project.

Ad · Amazon affiliate link.

References

A091: Project Governance vs Organisational Governance: What’s the Difference?
A092: How Projects Create Value Through Governance
A096: How to Recognise a Governance Question on the PMP Exam
A097: Governance Without Bureaucracy
A098: PMO Value: What Should a Project Management Office Actually Deliver?

PMP and PMBOK are registered marks of the Project Management Institute, Inc.