What Governance Actually Is
The most common misconception about P3 governance is that it is a passive function — the public authority monitoring compliance, reviewing reports, approving change orders, and waiting for things to go wrong. This misconception produces governance structures that are technically present but operationally ineffective.
Effective P3 governance is active management of a long-term commercial relationship. The distinction is not semantic. Passive oversight asks: is the concessionaire meeting the contract? Active management asks: is the concession delivering the outcomes the public needs, and what can the public authority do to support and improve that delivery?
An authority that only monitors compliance and processes deductions is performing a fraction of the governance function that a P3 concession requires. Over a 25-30 year concession term, the difference between passive oversight and active management compounds into an enormous gap in outcomes — for the public authority, for the concessionaire, and for the communities whose services depend on the asset.
The Four Functions of Effective P3 Governance
Performance monitoring is the function that most programs establish first and most visibly. The public authority tracks availability metrics, performance indicators, and deduction calculations against the contract framework. On an availability payment P3, this is where the payment mechanism operates. The failure mode is over-complication: monitoring frameworks that track fifty indicators for a single facility generate data without generating insight. Design the monitoring regime around the metrics that drive payment outcomes and asset performance.
Risk management is the function that governance frameworks most commonly underinvest in during the operational phase. The risk register was built during procurement. It gets reviewed annually if the program is disciplined, and ignored entirely if it is not. On a 25-year concession, risks that were theoretical at financial close will materialize in various forms: demand assumptions that prove wrong, technology that changes operational requirements in unexpected ways, geopolitical conditions that create force majeure events. Governance that treats risk management as a procurement-phase activity will always be reactive when these events occur.
Relationship management is the governance function that receives the least formal attention and has among the highest impact on concession outcomes. The relationship between the public authority and the concessionaire across 25-30 years determines whether problems get solved collaboratively or litigated expensively. Governance structures should include mechanisms for regular senior-level engagement — not just performance reviews and deduction disputes, but genuine dialogue about operational challenges and emerging risks.
The UK’s PFI experience demonstrates what happens when this dimension deteriorates. By the midpoint of many PFI concessions, the relationship between authority and operator had become adversarial enough that routine variation requests were treated as commercial battles. The governance framework had no mechanism to reset the relationship. The cost of that deterioration accumulated over years of sub-optimal concession management.
Change management is the fourth governance function — technically the most complex and most consequential in rapidly changing markets. A hospital P3 signed in 2005 needs to manage new clinical technologies, changing bed configurations, updated infection control requirements, and evolving maintenance standards across its remaining concession period. Each change requires a variation mechanism that is pre-agreed, fairly priced, and fast enough to keep pace with operational reality. Programs that establish clear variation procedures at contract execution manage change as a normal operational activity. Programs that do not, renegotiate every change under conditions where the concessionaire holds significant leverage.
The Metrolinx Governance Lesson
The experience I described in earlier articles — where the Bowmanville CMAR program’s collaborative delivery model met Metrolinx’s traditional governance framework — illustrates this point clearly. The organization had rigorous oversight processes: multiple committee reviews, external advisors, approval layers designed to protect public expenditure. These served an important purpose. But when applied to a progressive contract model that required collaborative decision-making at the pace of design and construction, the oversight framework became a delivery constraint. Decisions that needed to be made in days took weeks. The contract was structured for collaborative speed. The governance was structured for sequential control. They were not designed to work together.
That mismatch is not unique to Metrolinx. It is one of the most common delivery problems on complex programs globally. And it is entirely preventable if governance is designed as part of the delivery model, not imposed on top of it.
What Saudi Arabia’s P3 Program Needs
The NPS is creating a P3 program at scale. The transactions being procured now will require governance capability that many Saudi government entities are still developing. Several foundations are particularly important.
Owner capability must be developed in parallel with transaction volume. Dedicated P3 governance units with appropriately skilled commercial managers, technical monitors, and legal advisors with concession experience need to be operational before the operational phase of the first concessions begins.
Standardized governance frameworks across sectors reduce the cost of capability development and produce more consistent outcomes across the portfolio. The programs Saudi Arabia builds over the next decade will operate for 25-30 years each. The governance capability established at the start of that period shapes every outcome across its duration.