Category: Infrastructure Essentials

  • Availability Payment Regimes: How Performance Deduction Frameworks Shape Concessionaire Behaviour

    Why Availability Payments Work

    The availability payment model is the payment structure that makes P3 infrastructure delivery function in contexts where demand risk transfer to the private sector is inappropriate or unaffordable. Instead of the concessionaire earning revenue from users — and bearing the risk that those users will not appear in the numbers the financial model assumes — the government pays a service fee conditional on the asset being made available and performing to defined service standards.

    The model elegantly separates the risks the private sector can genuinely manage (construction quality, lifecycle maintenance, operational performance) from the risks it cannot (user demand, which is driven by public sector service and policy decisions). A hospital P3 concessionaire has no control over whether the clinical services in the hospital attract enough patients to justify the facility’s size. They do have control over whether the facility is clean, well-maintained, and operationally available to deliver whatever level of clinical service the health authority chooses to provide. The availability payment pays for the latter. The clinical activity risk stays with the health authority.

    How the Deduction Framework Works

    The availability payment is not a fixed annual fee. It is a baseline payment subject to deduction when the facility fails to meet the performance standards defined in the contract. The deduction framework is the mechanism through which the payment structure creates operational incentives for the concessionaire.

    Well-designed deduction frameworks share several characteristics. They are proportionate — the deduction for each performance failure reflects the severity of that failure’s impact on service delivery, not an arbitrary penalty that may be too small to motivate performance or too large to be commercially sustainable. They are certain — the concessionaire can calculate the financial consequence of any performance failure precisely, which allows them to make rational investment decisions about maintenance and operational staffing. They are focused — monitoring a small number of indicators that genuinely drive service quality produces better outcomes than monitoring a large number of indicators that create reporting burden without improving performance.

    Poorly designed deduction frameworks produce predictable problems. If deductions are too small relative to the cost of compliance, the concessionaire will rationally choose to accept deductions rather than invest in performance. If deductions are too large, the concessionaire will adopt risk-averse operational strategies that reduce service flexibility and add cost. If the monitoring framework is too complex, disputes about measurement methodology consume governance resources that should be focused on service delivery.

    The Response Time Trap

    One of the most common deduction framework design errors is calibrating response time requirements to the availability of resources in a high-performing major city. A requirement to restore a failed HVAC system in a hospital to full operation within 4 hours might be achievable in London or Toronto, where specialist maintenance contractors are available 24 hours. In a remote location, or during extreme weather, or during a period of supply chain disruption, that same requirement may be structurally impossible to meet regardless of how capable and well-resourced the concessionaire is.

    Deduction frameworks that do not account for location, access constraints, and supply chain realities produce deduction charges that the concessionaire disputes — correctly — as arising from conditions outside their control. The disputes consume governance resources. The relationship deteriorates. The contract’s commercial framework is undermined by provisions that were not designed for the actual operating environment.

    Designing for Saudi Arabia’s Infrastructure Context

    Saudi Arabia’s P3 program is deploying availability payment structures across a diverse portfolio of infrastructure types and geographic locations — from urban social infrastructure in Riyadh to remote industrial facilities in the Eastern Province. Calibrating deduction frameworks to the specific context of each concession — not importing frameworks developed for European urban programs and applying them to desert-climate, remote-location Saudi facilities — is essential for producing frameworks that actually incentivize performance rather than incentivize disputes.

    The frameworks being developed for Saudi Arabia’s water sector — building on three decades of BOOT experience — provide a valuable starting point. The commercial discipline embedded in those frameworks, and the institutional knowledge of what works and what does not in the Kingdom’s operational environment, should inform the structures being developed for new sectors as the NPS expands P3 delivery beyond water into health, education, and transport.

  • The Preconstruction Phase: Where Progressive Contracting Wins or Loses

    What Preconstruction Actually Is

    The most expensive mistake on a CMAR or Progressive Design-Build program is treating preconstruction as a formality — a period of CM engagement before the ‘real’ project starts. Preconstruction is not a courtesy invitation. It is the core delivery mechanism through which progressive contracting produces better outcomes than traditional procurement.

    Everything that makes progressive contracting superior happens in preconstruction — or it does not happen at all. Design decisions get informed by construction knowledge. Costs get tracked as they develop rather than discovered at tender. Risks get identified and mitigated while there is still design flexibility to address them. The GMP reflects reality rather than optimism. When preconstruction is done properly, construction proceeds with fewer surprises, fewer disputes, and better alignment between the cost committed and the cost delivered.

    Five Core Preconstruction Activities

    Constructability reviews are the foundational preconstruction activity. The CM’s construction specialists review design documents at each milestone with a single purpose: to identify design decisions that will create problems during construction. Not aesthetic issues. Not scope additions. Design decisions that are going to be difficult or expensive to build as drawn, or that will create safety, sequence, or access problems in the field.

    The value of constructability review is almost entirely a function of timing. A constructability comment at schematic design — before structural and mechanical systems are sized, before details are drawn — costs almost nothing to incorporate. The same issue identified at 90% design development requires a change to coordinated drawings, updated structural calculations, revised specifications, and a change order notice. The same issue identified after construction starts costs a change order, a delay, a crane stand-down, and a relationship problem. Early identification is where the value is created.

    Cost estimating in preconstruction is not a point-in-time activity. It is a continuous process, run in parallel with design development, that maintains a current and accurate assessment of where the project cost is tracking against the owner’s budget. The CM’s estimating team builds and updates the open-book estimate as design decisions are made, keeping the project’s financial trajectory visible in real time rather than as a surprise at GMP establishment.

    Value engineering is one of the most misunderstood activities in preconstruction. Genuine value engineering is not cost cutting. It is a structured analysis of design alternatives that identifies ways to achieve the same functional outcome with a different approach — one that costs less, takes less time, carries less risk, or is more buildable. When done properly, it produces alternatives that the designer and owner evaluate on their merits. When done poorly — which is common when the CM treats VE as a GMP negotiation tactic — it produces a list of scope reductions that the owner rejects and the CM uses as justification for a higher contingency.

    Schedule development in preconstruction means building a construction programme that reflects how the project will actually be sequenced and executed, not a theoretical schedule that satisfies a contract requirement. The CM’s planning team should be developing the construction method and sequence, identifying the critical path, and calibrating the programme against the resources that will actually be available. A schedule built this way is actionable. A schedule built to show the owner what they want to see is noise.

    Procurement planning addresses the materials, equipment, and subcontract work that need to be initiated before construction starts. Long-lead items — mechanical equipment, specialty materials, manufactured components — that require 16-24 weeks of lead time after order need to be identified and potentially ordered before the GMP is established, or the procurement timeline will control the construction schedule in ways that no amount of good programme management can resolve.

    GMP Timing: When to Commit

    The question of when to establish the GMP is one of the most important decisions in CMAR delivery. Establish it too early — at 40-50% design development — and the estimate is too uncertain, contingency is too high, and the GMP does not reflect reality. Establish it too late — at 95% design development — and the benefit of early contractor involvement has been largely consumed without the price certainty that the owner needs.

    The industry-standard range is 60-90% design completion, calibrated to the specific project type. Complex underground infrastructure warrants waiting for higher design maturity before committing. More straightforward above-ground programs can establish the GMP at lower design completion with acceptable contingency levels.

    Failure Modes

    The CM treats preconstruction as business development rather than delivery. They are focused on winning the GMP rather than producing value during preconstruction. Constructability reviews are thin. Cost estimates are padded. The schedule is aspirational. Problems that should be resolved during preconstruction arrive as construction-phase change orders.

    The owner is not available to make decisions. Preconstruction requires the owner to participate, not observe. When the owner’s governance process requires six weeks of review for every design decision, the collaborative tempo that makes CMAR valuable is impossible to achieve.

    The designer and CM do not genuinely collaborate. Constructability review degrades into a formality. The designer presents completed design. The CM comments. The designer’s response is minimal. The opportunity for genuine improvement is lost.

    For Saudi Arabia’s infrastructure programs — where the pressure to compress timelines and accelerate delivery is constant — the temptation to shortcut preconstruction is real and persistent. Resist it. The cost of rigorous preconstruction, typically 2-5% of total project value, is repaid many times over through cost certainty at GMP, reduced construction-phase change orders, and better schedule performance.

  • Risk Allocation in P3 Infrastructure: Getting It Right Before Financial Close

    Why Risk Allocation Is Everything in P3

    A Public-Private Partnership is fundamentally an agreement about who bears which risks over the life of the concession. Every other element of the P3 structure — the financial model, the performance framework, the governance arrangements — is built on top of the risk allocation. If the risk allocation is wrong, everything built on it is compromised.

    Getting risk allocation right means identifying every significant risk category, assessing which party is best positioned to manage it (which is almost never the same as which party should be forced to accept it), pricing the risk transfer correctly, and building the contract language that translates the intended allocation into operational reality.

    Getting it wrong means creating perverse incentives, pricing excessive contingency into the concession structure, and building the conditions for disputes, renegotiations, or financial distress that will persist for the full 25-30 year concession term.

    The Risk Categories That Matter Most

    Construction risk — cost overruns, schedule delays, quality failures — is the risk category that the private sector is consistently better positioned to manage than government, when the project is properly scoped. The contractor-financier relationship in a P3 consortium creates aligned incentives: the equity investor’s return depends on the asset being delivered on time and on budget. That alignment produces delivery performance that consistently outperforms equivalent government-delivered programs.

    The condition for effective construction risk transfer is that the scope must be well enough defined at financial close for the private sector to price the risk intelligently. Transferring construction risk on an inadequately scoped project does not eliminate the risk — it produces overpriced contingency and, when conditions vary from assumptions, a claims and renegotiation dynamic that transfers the risk back to government anyway, at higher cost.

    Demand risk — the risk that the asset will not be used as intensively as the financial model assumes — is the risk category that the private sector is generally not well positioned to manage, despite pressure from governments to transfer it. Demand for a hospital, a school, a water treatment plant, or a transit system is primarily driven by public sector decisions: population policy, service location, complementary infrastructure, and economic conditions. Transferring demand risk to a concessionaire does not give them control over those drivers. It gives them financial exposure to risks driven by decisions made by others.

    Australia learned this lesson expensively through a series of toll road concessions that failed when traffic forecasts proved optimistic. The concessionaires had accepted demand risk without having any mechanism to manage it. The result was financial distress, government bailouts, and significant damage to the P3 program’s political credibility.

    Interface risk — the risk of delays and costs arising from the interface between the P3 project and other projects, systems, or decisions being made by the public sector — is one of the most commonly misallocated risks in P3 structures. The concessionaire is exposed to risk created by public sector decisions they cannot influence. That exposure either gets priced as contingency (expensive) or becomes a dispute (more expensive).

    Force majeure risk — extreme events outside any party’s control — needs to be carefully defined in the contract. The trend in modern P3 documentation is toward explicit enumeration of force majeure categories rather than catch-all language, combined with clear allocation of financial consequences for events in each category. Geopolitical disruption — particularly relevant in the GCC context — deserves specific attention in Saudi Arabia P3 contracts.

    The Saudi Arabia Context

    Saudi Arabia’s National Privatization Strategy is creating P3 frameworks across sectors — transport, water, health, education, and municipal services. The risk allocation principles being embedded in these frameworks will shape outcomes for the next generation of public assets.

    The sectors where Saudi Arabia’s P3 experience is deepest — water (BOOT and IWPP structures that go back 40 years) — provide a template for risk allocation that has been tested and refined through operational experience. Construction risk rests with the private sector. Offtake risk rests with the government through long-term purchase agreements. The model works because the risk allocation reflects who can actually manage each risk.

    The challenge as the NPS expands P3 into new sectors is to apply those allocation principles consistently, rather than being tempted by the apparent fiscal attractiveness of maximum risk transfer. Risk that cannot be managed by the party bearing it will be paid for — either in the form of premium contingency built into the concession price, or in the form of renegotiation costs when reality diverges from assumptions.

    Practical Guidance for P3 Developers in the Kingdom

    The risk allocation principles that consistently produce good outcomes are clear from global P3 experience: transfer risks to the party best positioned to control them, retain risks driven by public sector decisions, price residual risks explicitly rather than hoping they do not materialize, build structured variation mechanisms for anticipated scope changes, and design the contract to maintain a functional working relationship between authority and concessionaire across the full concession term.

    These principles are not complex. What is complex is the discipline to apply them under pressure from financing parties, procurement timelines, and political imperatives that can all pull toward risk allocation decisions that serve short-term objectives at the cost of long-term program performance.

  • CMAR Is the Most Misunderstood Model in Progressive Contracting — Here’s How It Actually Works

    What CMAR Actually Is

    Construction Manager at Risk is the progressive contract model I managed hands-on during the Bowmanville Train Line Extension — a $2 billion rail extension in Ontario, Canada, delivered under one of the most ambitious CMAR engagements in North American transit history.

    The model is two-phased, and understanding both phases is essential to understanding why CMAR produces the outcomes it does — both the successes and the failure modes.

    Phase 1: Preconstruction

    The owner selects a Construction Manager based on qualifications and fee — explicitly not on lowest bid price. This is the first and most important distinction from traditional contracting. The CM is chosen for who they are and what they can contribute during design, not for how aggressively they will price the work at tender.

    Once engaged, the CM joins the design process as an active participant. Their core preconstruction deliverables are constructability reviews (applying field construction knowledge to design decisions before they are locked), cost estimating (building and maintaining an open-book estimate of the project as design evolves), value engineering (identifying alternative approaches that reduce cost or improve buildability without compromising the owner’s requirements), schedule development (building a construction schedule that reflects how the project will actually be built, not a theoretical programme), risk identification (surfacing and quantifying construction risks while there is still time and design flexibility to mitigate them), and procurement planning (identifying long-lead materials and subcontracting strategies that reduce cost and schedule risk).

    This phase is where the value of CMAR is created. The contractor’s field knowledge shapes the design before it gets locked in. Problems that would have become change orders in traditional contracting get solved collaboratively during preconstruction.

    Phase 2: GMP and Construction

    When the design reaches sufficient maturity — typically 60-90% complete, depending on the project type and the owner’s tolerance for residual uncertainty — the CM and owner negotiate a Guaranteed Maximum Price. The GMP is built on transparent, open-book cost data: the actual cost of the work (labour, materials, subcontractors, equipment), plus the CM’s fixed fee (typically 3-8% of cost of work), plus shared contingency.

    The financial logic of the GMP is based on transparency and shared risk. If the project comes in under the GMP, the savings are shared between owner and CM in a pre-agreed ratio — this is the ‘gain.’ If the project exceeds the GMP, the CM absorbs the overage — this is the ‘pain.’ This structure fundamentally changes the CM’s incentive compared to traditional contracting. They are now motivated to find efficiencies and avoid problems, not to identify claim opportunities.

    What Conditions CMAR Requires

    CMAR is not a magic fix for construction delivery. It is a model with specific conditions that need to be in place for it to perform. When those conditions are absent, CMAR can actually underperform traditional contracting — because you have added cost and time without getting the collaborative benefit.

    The owner needs to be capable of active participation in preconstruction. An owner who treats the preconstruction phase as a contractor activity to be observed rather than a collaborative process to be participated in will not get the benefit of early contractor involvement. The design decisions that preconstruction is supposed to inform get made without the CM’s input, and the preconstruction becomes a billing exercise.

    The CM needs to have real preconstruction capability — not just estimators who can produce a GMP, but constructability specialists, procurement strategists, and schedule analysts who can genuinely contribute to design development. A general contractor who wants early access to a project but has thin preconstruction capability will deliver thin preconstruction value.

    The governance structure needs to allow fast decision-making. One of the most persistent failure modes I saw in CMAR delivery was an owner’s governance framework designed for traditional procurement — sequential decisions, multi-committee approval — meeting a contract model that required collaborative, fast decisions during preconstruction. The friction was immediate and ongoing. The contract’s potential was constrained by the governance.

    The contract needs clear GMP amendment procedures. CMAR does not freeze scope at GMP establishment. When the owner adds scope or conditions change, the GMP needs to be adjusted through a clear, pre-agreed process. Ambiguity in this process is the single most common source of CMAR disputes I have observed.

    What Goes Right and What Goes Wrong

    When these conditions are in place, CMAR produces outcomes that traditional contracting consistently fails to achieve: cost certainty at GMP establishment, fewer change orders during construction, faster problem resolution, and a project team that functions as a partnership rather than an adversarial relationship.

    When the conditions are absent — and they often are, particularly on first CMAR engagements — the model creates overhead without creating value. I will continue to share specific failure modes from my experience in coming articles, because understanding what goes wrong is as important as understanding what the model is designed to do.

  • Why Traditional Design-Bid-Build Is Failing Large Infrastructure: A Structural Analysis

    The Pattern That Plays Out on Most Large Traditional Contracts

    The owner’s consultant produces a drawing set. The contractor bids on it — lowest price wins. Handshake. Construction starts. Then reality shows up.

    The drawings do not match site conditions. The contractor sends an RFI. The designer takes three weeks to respond. Crews are standing around burning daylight. A change order goes in. The owner pushes back. The contractor files a claim. Lawyers start circling. The project finishes 14 months late and 40% over budget.

    This pattern plays out on most large traditional contracts around the world. Not occasionally. Most. And it’s not because of bad people or incompetent organizations. It is a structural problem — one built into the design of the contract itself.

    Failure Mode 1: Misaligned Incentives

    In a Design-Bid-Build arrangement, the contractor profits by building fast and cheap. The designer’s fee is fixed regardless of how buildable the design is. The owner wanted quality but awarded on lowest price. Everyone optimizes for their own outcome — not the project’s.

    The contractor who wins on lowest price has, by definition, left the least contingency in the estimate. When risks materialize, there is no buffer. The rational response — from the contractor’s perspective — is to recover through change orders and claims. The contract structure created that incentive. Blaming the contractor for using it is like blaming water for flowing downhill.

    The designer, whose fee was set at appointment and who bears no financial consequence for an uncoordinated or unbuildable design, has no financial incentive to invest additional effort in coordination or constructability. Their incentive is to produce drawings that meet the technical standard of care with the resources their fee supports. What happens in the field after the drawings are issued is legally someone else’s problem.

    Failure Mode 2: Late Knowledge Transfer

    The contractor — the party with the most detailed construction knowledge — has zero input during design. By the time they see the drawings, the design is fully developed. Any construction knowledge they could contribute has been locked out by the procurement timeline. Every improvement to buildability after tender requires a change order, which requires approval, which burns time and degrades the owner-contractor relationship.

    This is not just an inefficiency. It is a fundamental misallocation of expertise. The contractor knows how to sequence work safely and efficiently. They know what local labour can actually achieve, which materials are reliably available, where the coordination problems between trades typically emerge. None of that knowledge informs the design, which is developed entirely by a design team whose expertise is technical design — not construction execution.

    Failure Mode 3: Adversarial Risk Allocation

    The traditional contract pushes nearly all risk to the contractor through fixed-price lump sum structures. When risks materialize — site conditions differ from geotechnical assumptions, regulatory changes affect scope, supply chain disruptions delay materials — the only path available to the contractor within the contract framework is to file claims.

    The adversarial dynamic that results is not a failure of professional character. It is the predictable output of a contract structure that gives parties no collaborative mechanism for resolving problems. Every risk event that falls within a grey zone of the contract language becomes a commercial dispute, because that is what the contract designed it to be.

    Failure Mode 4: No Shared Ownership of Outcomes

    When the project fails — and overruns are the norm rather than the exception on large traditional contracts — everyone points in a different direction. The designer blames execution quality. The contractor blames drawing quality. The owner blames both. Nobody owns the outcome because the contract never gave anyone shared ownership of it.

    I have sat on both sides of this table — as a contractor managing rail corridors and highway programs, and as an owner’s representative overseeing billion-dollar transit programs. The adversarial dynamic is not a personality problem. It is a contract design problem. And it has a solution.

    Progressive models do not eliminate disagreements. They create structures where the default response to a problem is to solve it together — not to call a lawyer. That shift matters more than most people in infrastructure delivery yet appreciate.

  • The Five Progressive Contract Models Reshaping Global Infrastructure Delivery

    The Contract Is the Biggest Risk on Your Project

    After 20 years of watching infrastructure projects succeed and fail — across rail corridors in Ontario, highway rehabilitation programs for MTO, transit station delivery at Metrolinx, and now the Saudi construction market — I keep returning to the same conclusion: the single biggest factor in project outcome is how the parties agreed to work together before a single shovel hit the ground.

    Not the engineering. Not the workforce. The contract. Specifically, whether the contract aligns the financial interests of all parties around a shared outcome, or pits them against each other in a zero-sum game that guarantees adversarial behaviour when risks materialize.

    CMAR: Construction Manager at Risk

    CMAR is the model I managed hands-on during the Bowmanville Train Line Extension — one of Canada’s largest progressive contract programs at $2 billion.

    The mechanics are two-phased. In Phase 1, the owner selects a Construction Manager based on qualifications and fee — not lowest bid. The CM joins during design and contributes constructability reviews, cost estimating, value engineering, schedule development, risk identification, and procurement planning. This is where the value of early contractor involvement is created: field knowledge that shapes design decisions before they become expensive to change.

    In Phase 2, when the design reaches sufficient maturity (typically 60-90% complete), the CM and owner negotiate a Guaranteed Maximum Price. The GMP is built on open-book cost data — the CM’s actual cost of the work, plus a fixed fee (typically 3-8%), plus shared contingency. If the project comes in under GMP, the savings are shared. If it exceeds GMP, the CM absorbs the overage. This pain/gain structure fundamentally realigns the contractor’s incentive — from maximizing change orders to finding efficiencies.

    Alliance Contracting

    Alliance contracting takes the collaborative principle further than CMAR. All parties — owner, designer, and contractor — operate as a single entity under a unified agreement with a shared risk/reward pool. There is no claims process. No disputes mechanism in the traditional sense. If the project loses money, everyone loses. If it makes money, everyone benefits.

    Australia has the most mature Alliance contracting practice in the world, developed over three decades for complex infrastructure — remote resource projects, tunnels, bridges, and social infrastructure. The model produces exceptional outcomes when the parties are genuinely committed to the collaborative culture it requires. When they are not — when a party enters Alliance contracting with a traditional contractor mindset — the model fails spectacularly because there is no claims mechanism to fall back on.

    Progressive Design-Build (PDB)

    Traditional Design-Build selects a single entity (designer + contractor) on a competitive basis at a fixed price, giving the owner a single point of accountability for design and construction. PDB retains the single-entity accountability but changes the selection and pricing approach entirely.

    Under PDB, the design-builder is selected on qualifications and approach — not price. Scope, design, and cost are then developed collaboratively between the owner and design-builder through a structured process, with the price not locking until the design is sufficiently mature to price reliably. This eliminates the design compression that characterizes traditional Design-Build, where the winning team is often selected before the design is developed enough to price accurately.

    Early Contractor Involvement (ECI)

    ECI is the most accessible entry point into progressive contracting for owners who are not yet ready for CMAR or Alliance. Under an ECI arrangement, the contractor is engaged under a separate preconstruction agreement — before the main construction contract is signed — to provide constructability input, cost advice, schedule development, and procurement planning.

    The preconstruction agreement defines what the contractor will deliver, at what fee. At the conclusion of preconstruction, the owner decides whether to negotiate a construction contract with the ECI contractor or proceed to competitive tender. The knowledge developed during ECI informs whichever path is chosen.

    Integrated Project Delivery (IPD)

    IPD is the most ambitious and least widely adopted of the progressive models. It combines a multi-party contract — owner, designer, and contractor as parties to a single agreement — with financial incentives tied directly to project performance against shared targets.

    Each party’s profit is at risk against the project’s performance. Exceptional performance produces shared gain. Poor performance produces shared pain. The alignment is total. So is the organizational and cultural commitment required to make it work.

    IPD has seen its most successful adoption in healthcare construction in the United States, where the complexity of hospital delivery programs and the long-term owner relationships with design and construction partners create conditions the model needs. In infrastructure delivery, it remains emerging.

    Choosing the Right Model

    The question I am most often asked is: which progressive model should I use? The answer is always: it depends on your project, your organization, and your market conditions. None of these models is universally superior. Each requires specific conditions to perform. The coming weeks will develop a framework for making that choice in the GCC context.

  • The Construction Industry Has a $1.6 Trillion Problem — And Traditional Contracting Is Making It Worse

    The Productivity Crisis in Construction

    McKinsey’s research on global construction productivity is worth sitting with. Large construction projects typically take 20% longer than planned and run up to 80% over budget. The World Economic Forum puts global construction productivity growth at just 1% annually over the past 20 years — while manufacturing has grown at 3.6% over the same period. The construction industry manages approximately $10 trillion of economic activity annually, and its fundamental inefficiency is one of the most significant and underaddressed productivity problems in the global economy.

    The causes of this underperformance are multiple and interconnected. But one structural factor stands above the others: how we contract.

    What Traditional Contracting Does to Projects

    The Design-Bid-Build model — owner designs, contractor bids lowest price, adversarial relationship ensues — was developed in an era when construction projects were simpler, supply chains were local, and the pace of design development was slow enough that a complete design before bidding was achievable and meaningful.

    None of those conditions reliably apply to large infrastructure programs today. Designs are complex and interdependent. Supply chains span continents. The world changes between schematic design and construction completion in ways that no set of contract documents can fully anticipate.

    The traditional model’s response to this complexity is to push risk onto the contractor through fixed-price lump sum contracting. The assumption is that competition at tender will produce an efficient price, and that forcing the contractor to absorb risk will make them manage it efficiently. In practice, the assumption fails regularly.

    Fixed-price contracting on complex infrastructure does not eliminate risk. It relocates it — to the contractor’s contingency, to the claims and disputes process, and ultimately to the schedule and budget outcomes that the owner cares about most. A contractor who has absorbed risks they cannot manage will not manage them efficiently. They will manage them legally, through change orders and claims that shift liability back to the owner at the worst possible time.

    What Progressive Models Change

    The defining characteristic of progressive contract models — CMAR, Alliance, PDB, ECI, and IPD — is that they bring the contractor into the project before the design is complete, under terms that align their financial interests with project outcomes rather than against them.

    Construction Manager at Risk engages the contractor during design under an open-book preconstruction agreement, culminating in a Guaranteed Maximum Price negotiated on the basis of real cost data rather than competitive desperation. Alliance Contracting creates a single entity from owner, designer, and contractor with a shared risk/reward pool that eliminates the claims dynamic entirely. Progressive Design-Build selects the delivery team on qualifications and develops scope and cost collaboratively before the price is locked. Early Contractor Involvement brings field expertise into planning before the design is committed. Integrated Project Delivery ties the financial outcomes of all parties to the project’s performance against shared targets.

    Each model addresses the same underlying problem — the adversarial, information-poor, incentive-misaligned dynamic of traditional contracting — through a different structural mechanism.

    The Global Shift

    The adoption of progressive models is accelerating globally. Australia pioneered Alliance contracting for infrastructure and has three decades of institutional experience with it. The UK is rebuilding its PPP framework after the political collapse of PFI. Canada has adopted CMAR and Progressive Design-Build for transit delivery, with Metrolinx’s programs among the most ambitious implementations. The GCC is deploying PPP models across 98+ projects in Saudi Arabia alone, with a National Privatization Strategy targeting 220 transactions by 2030.

    The shift is real, and the evidence base supporting it is growing. But the honest version of this story — which I will continue to tell in this series — includes the failure modes. Not every progressive model works in every situation. Picking the wrong model, or applying the right model without the governance, stakeholder readiness, and organizational capability it requires, can produce outcomes worse than traditional contracting.

    The coming weeks of this series will break down each model, examine global case studies of both success and failure, and provide a framework for selecting and implementing progressive contracting in the Saudi and GCC context. This is the honest version. Not the sales pitch.