Talha Asif — Infrastructure & PMO Executive

Blog

  • 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.

  • The Right Stakeholders Problem: Why Governance Readiness Determines Progressive Contracting Success

    The Half of the Equation Nobody Talks About

    When infrastructure professionals discuss progressive contracting, the conversation focuses almost entirely on the model. Which framework? CMAR or Alliance? PDB or IPD? How do you structure the GMP? What does the pain/gain sharing look like? These are important questions. They are also, in my experience, only half the question.

    The other half — the half that actually determines whether the model delivers — is organizational readiness. The governance structures, decision-making culture, and stakeholder capabilities that sit behind the contract form.

    I have watched a well-designed progressive contract underperform because the owner’s organization was not set up to participate collaboratively. And I have seen a relatively simple delivery model produce excellent results because the right people were empowered to make decisions quickly and held accountable for outcomes. The model matters. The organization matters more.

    What Collaborative Preconstruction Actually Requires

    Progressive models are built on a core assumption: that the owner, the contractor, and the designer will work together during design to share information, solve problems jointly, and make better decisions than any one party could make alone. That assumption sounds reasonable. In practice, it requires something that many organizations do not have — a governance structure that actually allows people to make decisions in real time.

    If the owner’s organization requires every significant design decision to pass through three committees, two review panels, and a 60-day approval cycle, then the collaborative preconstruction phase that makes CMAR valuable becomes a bottleneck instead of an accelerator. The Construction Manager is ready to provide input. The designer is ready to iterate on design alternatives. But the owner’s internal process cannot keep pace with the tempo of collaboration that the contract is designed to produce.

    I saw this firsthand on a major North American transit program. The progressive contract was well-structured. The financial model was sound. The CM had genuine preconstruction capability. But the owner’s governance framework was built for a traditional procurement environment where decisions could be sequential and deliberate. When that framework met a contract model that demanded fast, empowered, collaborative decision-making, the friction was immediate and persistent. The governance did not adapt to the contract. The contract’s potential was constrained by the governance.

    The Contractor Readiness Problem

    Owner governance is not the only readiness gap. The contractor matters equally. A CMAR arrangement requires a Construction Manager with genuine preconstruction expertise — not just a general contractor who wants early project access and will figure out preconstruction deliverables as they go.

    Real preconstruction capability means cost estimators who can maintain an open-book rolling estimate as design evolves, constructability specialists who can review drawings critically and propose alternatives, procurement strategists who can identify long-lead risks and develop mitigation strategies, and schedule analysts who can build and maintain a construction programme that reflects how the project will actually be sequenced. When that capability is thin, the preconstruction phase becomes a billing exercise rather than a value creation exercise. The owner is paying preconstruction fees without getting preconstruction value. The result is a GMP that does not reflect reality, followed by construction phase surprises that should have been resolved during preconstruction.

    The Designer’s Cultural Shift

    The designer is the third party in the readiness equation. In a traditional design environment, the designer is the technical authority and the contractor is the party who builds what the designer specifies. That hierarchy does not serve a collaborative preconstruction process. The CM needs to be able to say ‘this will be very difficult to build as drawn’ and the designer needs to be willing to explore alternatives rather than defend completed design decisions.

    That cultural shift — from technical authority to collaborative partner — is one that not every design firm has made, and not every project team can make it mid-project if it was not established at the beginning of preconstruction.

    Assessing Readiness Before Selecting a Model

    For anyone evaluating which delivery model to use on their next program, my advice is direct: spend as much time assessing your organization’s readiness to execute a progressive contract as you do assessing which progressive contract to select. The best model in the world will underperform if the stakeholders behind it are not ready.

    That readiness assessment should cover decision-making authority (who can approve what, and how quickly), governance design (how will the collaborative management team be structured and empowered), procurement culture (can the owner’s procurement framework accommodate a qualifications-based selection), and organizational capacity (does the owner’s team have the bandwidth to actively participate in preconstruction).

    Getting this right at the beginning is cheaper than correcting it mid-program.

  • 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.

  • The Blind Spot in Infrastructure Delivery: OT Cybersecurity and the Triton Attack

    The Attack That Targeted Physical Destruction

    In 2017, a cyberattack hit a petrochemical facility in Saudi Arabia. Not the corporate network. Not the email server. The Safety Instrumented System — the engineered last line of defence designed to prevent explosions, chemical releases, and loss of life when process conditions exceed safe operating limits.

    The malware was called Triton. Also known as TRISIS. It was purpose-built to compromise Schneider Electric’s Triconex safety controllers — systems installed in facilities precisely because they are supposed to be the failsafe when everything else goes wrong. The intent of the attack was not data theft. It was not ransomware. It was physical destruction of the facility and harm to the people working in it.

    The only reason it did not succeed was a coding error in the malware that triggered a plant shutdown before the payload fully deployed. The attackers were sophisticated enough to develop malware targeting a specific safety controller platform. They made a programming mistake that triggered an emergency shutdown — which alerted the facility’s security team to the intrusion.

    That was 2017. The capability that failed in 2017 has had eight years to improve.

    This Is Not an Isolated Event

    In 2021, an attacker gained access to the SCADA system of a water treatment plant in Oldsmar, Florida, and attempted to increase sodium hydroxide levels to 100 times the safe concentration. The attack was spotted by an operator watching his screen in real time. There was no automated alert. No intrusion detection system. No OT network monitoring. Just a human who happened to be looking at the HMI at the right moment.

    In 2015 and 2016, coordinated cyberattacks on Ukraine’s power grid caused blackouts affecting hundreds of thousands of people. The attackers did not target the utility’s IT network primarily. They targeted the operational technology systems that control circuit breakers and distribution substations — the systems that physically switch power on and off across the grid.

    These are not IT security problems that the IT department should have caught and prevented. They are attacks on the Operational Technology systems that control physical processes — and they are successful precisely because OT environments are almost never designed with cybersecurity as a requirement.

    The Design Gap That Creates the Vulnerability

    Most infrastructure facilities being designed, built, and commissioned today have the following in common: the engineering team designed the SCADA architecture. The controls integrator programmed the PLCs and DCS. The facility was commissioned and handed over. And at no point in that process did anyone assess whether the OT network is properly segmented from the corporate IT network, whether the HMI workstations are running patched operating systems, whether the remote access paths used by the controls vendor for ongoing support are secured against unauthorized access.

    This is not a technology gap. The technologies for OT network segmentation, OT-appropriate access control, and OT network monitoring exist and are proven. It is a design gap. OT cybersecurity requirements are not included in project scope because they are not understood as engineering design requirements — they are perceived, incorrectly, as an IT operational concern that someone else will handle after commissioning.

    Why the Middle East Is a High-Priority Target

    The combination of factors that makes the Middle East a high-value target environment for OT-focused threat actors is well documented in the threat intelligence community. Concentration of critical infrastructure — energy, water, petrochemical, transport — in a geopolitically significant region. Rapid digitalization and connectivity of operational systems that were previously air-gapped. A geopolitical environment that motivates state-sponsored threat actors with the capability and patience to conduct sophisticated OT attacks.

    Triton targeted a Saudi facility. The most capable OT malware ever publicly analysed was built specifically to attack infrastructure in this region. That is not a coincidence, and it is not a threat that has diminished since 2017.

    What Infrastructure Engineers Need to Do Now

    OT cybersecurity should be on every infrastructure project’s risk register, from early design through commissioning and into operations. Not as a future consideration. Now. Specifically, this means including OT security requirements in the project scope at the design stage, engaging OT security specialists to review the control system architecture before it is locked, and ensuring that commissioning procedures include OT security validation alongside process safety validation.

    The frameworks exist. IEC 62443 provides the international standard for industrial control system security. In Saudi Arabia, the NCA’s Operational Technology Cybersecurity Controls (OTCC) establish the regulatory baseline that critical infrastructure operators are expected to meet. Understanding and designing to these frameworks is a professional responsibility for anyone delivering infrastructure in this region.

    Concept Dash’s OT cybersecurity team — working through our partnership with a NACSA-licensed cybersecurity firm — provides OT gap assessments and security design services for infrastructure projects in Saudi Arabia and the GCC. The cost of an assessment at design stage is a fraction of the cost of a compliance finding, a breach, or a physical safety incident after commissioning.

  • 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.

  • BIM in Progressive Contracts: How Digital Modelling Transforms Collaborative Project Delivery

    The Core Argument: BIM and Progressive Contracting Are Made for Each Other

    Progressive contract models exist because the construction industry realized that collaboration produces better results than adversarial competition. When owners and contractors work together during design — sharing cost data, construction knowledge, and risk — the project that emerges is more buildable, more accurately priced, and more likely to deliver on schedule.

    BIM — Building Information Modelling — exists because the construction industry realized that information sharing produces better decisions than information silos. When all parties work from a shared, intelligent model rather than isolated 2D drawings, coordination improves, errors are identified earlier, and the cost of change drops dramatically.

    These two ideas are not coincidental. They are the same idea applied to different dimensions of the construction problem. Progressive contracting fixes the relationship structure. BIM fixes the information structure. Together, they address the two most persistent sources of large-scale construction failure.

    3D Coordination: Clash Detection During Preconstruction

    In a traditional Design-Bid-Build project, the first time the structural engineer, mechanical engineer, electrical engineer, and contractor’s field team genuinely compare their work is often after construction has started. The result — discovered clashes that require field modifications, rework, and change orders — is one of the most predictable and preventable sources of construction cost overrun.

    3D BIM coordination changes this entirely. When all design disciplines model in BIM from the beginning, clash detection software (Navisworks, Revit) identifies the conflicts before they become physical. A pipe running through a structural beam is caught in the model, not in the field. The resolution costs a design revision, not a concrete saw and a change order.

    In a CMAR or Alliance arrangement, where the contractor is engaged during design, 3D coordination becomes a collaborative activity rather than a design review exercise. The CM’s construction team reviews the coordinated model for constructability — not just clash detection, but sequencing, access, and buildability — and the input improves the model before it is committed to construction drawings.

    4D Scheduling: Time-Linked Models for Sequence Validation

    4D BIM links the 3D model to the project schedule, creating an animated visualization of the construction sequence. At any point in the project timeline, the 4D model shows what has been built, what is being built, and what is planned next — in three dimensions, at the scale of the actual site.

    The value of 4D for progressive delivery is primarily in the preconstruction phase. The Construction Manager’s field team uses the 4D model to validate the proposed construction sequence before it is committed to the schedule baseline. Conflicts that would not be visible in a Gantt chart — two work fronts competing for the same crane radius, a staging area that gets consumed before materials have been offloaded — become visible in the 4D simulation.

    I saw an owner’s project director spot a sequencing risk in a 4D simulation that the construction team had missed — because the visualization made it visible and the progressive contract made it safe to raise. In a traditional contract, raising a sequencing concern that wasn’t in the tender documents would have been a commercial negotiation. In the CMAR environment, it was a collaborative problem solved before construction started.

    5D Cost Modelling: Real-Time Cost Visibility

    5D BIM connects the 3D model to cost data, enabling automatic quantity takeoff and cost updating as design evolves. When a wall changes from concrete block to precast — a design decision that has cost implications — the 5D model updates the quantity and cost estimate automatically, rather than requiring a manual takeoff and estimating exercise.

    In CMAR delivery, 5D BIM is particularly powerful during the GMP development process. The CM’s open-book cost estimate should reflect the actual design, not a schedule of rates applied to approximate quantities. 5D BIM provides the quantity certainty that makes the GMP genuinely reflect reality rather than the CM’s best guess from limited information.

    A 6-8 week cost reporting lag is enough to burn through contingency without anyone noticing. 5D BIM eliminates that lag — design changes trigger immediate cost impact updates, keeping the project’s financial picture current.

    Digital Twins: From Asset Delivery to Asset Management

    A digital twin is a real-time, connected replica of the physical asset — updated continuously with operational data from sensors, IoT devices, and maintenance systems. In infrastructure delivery, the digital twin represents the handover of the construction BIM model to the operations team, enriched with as-built data, commissioning records, and asset management information.

    For progressive delivery models, the digital twin creates a direct line between the collaborative effort invested in design and construction, and the long-term operational performance of the asset. Assets designed and built with BIM can be handed over with complete, accurate as-built information. Assets managed with digital twins provide the operational data that informs future projects and programs.

    The Saudi Arabia infrastructure boom — with its scale, its pace, and its emphasis on smart and sustainable assets — is one of the most significant digital twin deployment opportunities in the world. Concept Dash’s digital twin practice is directly focused on this opportunity.

  • 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.

  • Breaking Into the GCC Infrastructure Market as a Foreign Professional: What Nobody Tells You

    The Expo Circuit Is Not the Market

    I have been to the Saudi Big 5, Future Projects KSA, Saudi Rail Expo, Cityscape, Biban, and half a dozen more events since relocating to Riyadh. Every time, the scale of ambition on display is genuinely staggering. NEOM, Diriyah, Red Sea, Qiddiya, ROSHN — programs at a scale that simply does not exist anywhere else in the world right now.

    What the expo circuit does not prepare you for is the gap between the event floor and actual business development in the Kingdom. Walking a tradeshow, collecting business cards, and attending panel discussions is one form of market engagement. Building the kind of trust-based relationships that generate real commercial opportunities is a fundamentally different activity, operating on a fundamentally different timeline.

    What Actually Matters in the Saudi Market

    The Saudi construction and infrastructure industry values track record above almost everything else. Not credentials — track record. The distinction matters. Credentials tell someone what you have been certified to do. Track record tells them what you have actually done. In a market where the consequence of choosing the wrong advisor or partner can be measured in hundreds of millions of riyals, the preference for demonstrated capability over claimed capability is entirely rational.

    The second thing the market values is genuine commitment. There is a meaningful difference — visible and felt — between professionals who are present for the market and professionals who are passing through it. My family is settled in Riyadh. My wife teaches at SEK International School. I am building infrastructure here, not extracting from it. That difference is noticed.

    The third factor is cultural patience. North American business culture operates on a relatively compressed relationship development timeline. A professional meeting, followed by a capabilities presentation, followed by a proposal, followed by a commercial engagement — compressed into six to eight weeks — is a reasonable expectation in Toronto or Calgary. In Riyadh, the first meeting is genuinely just the first meeting. The relationship needs to breathe before business becomes a natural topic. Professionals who try to accelerate past that stage consistently underperform those who invest in it.

    What I Brought to the Table

    I arrived in the Saudi market with 20 years of infrastructure delivery experience, a specific and verifiable track record in progressive contracting models, and the professional credentials that signal seriousness in the Canadian and international engineering community — P.Eng, PMP, RMP, DASM. What I did not have was regional relationships, Arabic language capability, or 15 years of GCC-specific project experience.

    My approach was to be explicit about both sides of that equation. I know progressive contracting. I know rail and highway delivery. I know how to build and run project controls systems for complex programs. I do not know the Saudi market as well as someone who has been here for 20 years, and I do not pretend otherwise. That combination — genuine expertise in specific areas, combined with intellectual honesty about what I am still learning — has been more effective than an approach that overstates regional knowledge I do not have.

    What I Have Learned About the Market

    The Saudi engineering and project management community is more sophisticated, more internationally trained, and more analytically demanding than I expected. The conversations are substantive from the first meeting. I encountered PhDs and MBAs, PMPs and chartered engineers, professionals with experience across four or five continents. The assumption that Canadian technical standards are automatically superior to Saudi practice does not survive contact with this reality.

    The pace of organizational decision-making at the senior level is, in some contexts, faster than I experienced in Canadian public sector environments. When the right principal is in the room with authority to move, decisions that would take weeks of committee review in a Canadian government context happen in hours. The bottlenecks are different — relationship establishment rather than bureaucratic process — but the ceiling, once cleared, can be high.

    The scale of what is being built here has recalibrated my reference frame for what constitutes a major program. A $500 million project that would be considered transformational in an Ontario context is mid-tier in Riyadh. That recalibration has been professionally valuable.

    My DMs remain open. If you are an infrastructure professional in the GCC — whether you have been here 20 years or 20 days — I would genuinely like to hear your perspective. The learning is ongoing and deliberately so.

  • The Strait of Hormuz Disruption Is a Construction Story: What Risk Managers Need to Watch

    What Regional Conflict Means for Construction Delivery in the GCC

    When geopolitical instability disrupts the Strait of Hormuz, the conversation in financial markets focuses on oil prices. But for infrastructure professionals delivering projects across the GCC, the more relevant story is what happens to construction costs, supply chains, and contract risk.

    Nearly 20% of global petrochemical capacity flows through the Strait of Hormuz. Steel, PVC, bitumen, polymers — the raw materials that build our projects — are all tied to petrochemical feedstock. When that supply pathway is disrupted, the effect on construction inputs is direct and significant.

    Material Cost Escalation

    The relationship between oil price and construction input costs is not linear, but it is real and material. Bitumen, which is a refinery residual product, tracks crude oil prices closely. PVC and polymer-based materials — used extensively in waterproofing, piping, and conduits — are directly petrochemical-derived. Structural steel, while not petrochemical, relies on energy-intensive manufacturing processes that become more expensive when energy costs spike.

    A 15-25% increase in key construction inputs over a 6-12 month horizon following a major disruption is a realistic planning assumption. For a $500 million program, that translates to significant budget exposure if contract language does not provide for price escalation.

    Supply Chain Route Disruption

    Shipping route diversions around the Cape of Good Hope add 10-15 days to delivery schedules. For projects with procurement windows calibrated to just-in-time delivery logic — increasingly common in complex construction programs — that delay is not an inconvenience. It is a schedule risk that needs to be quantified in the project risk register and addressed through procurement strategy.

    The practical response for program managers is to conduct a procurement vulnerability analysis: which long-lead materials are sourced through routes affected by the disruption? What is the schedule exposure if those materials are delayed? Are there alternative suppliers or stockpiling strategies that reduce the exposure at acceptable cost?

    Labour Mobility Risk

    Visa processing delays, flight route disruptions, and regional security concerns affect the movement of skilled labour across the GCC. For programs that rely on specialized crews from affected regions — whether that’s construction workers from South Asia, specialist engineers from Europe, or equipment operators from Southeast Asia — build contingency into resource plans.

    This is a risk that is often underweighted in project risk registers because it is less visible than material costs and supply chain delays. But labour mobilization failures have derailed more than a few GCC programs that were otherwise well-structured.

    Contract Implications: Force Majeure and Price Escalation

    The legal and commercial dimension of geopolitical disruption is where many programs are most exposed. Force majeure clauses, price escalation provisions, and delay notification requirements vary enormously between standard contract forms. GCC public sector contracts often follow FIDIC, which provides relatively clear force majeure language. But the interpretation of that language in specific circumstances, and the notification and documentation requirements that activate it, need to be reviewed proactively rather than in the heat of a dispute.

    Price escalation provisions — sometimes called fluctuations clauses — are included in some contracts and absent from others. In a fixed-price lump sum environment, material cost escalation above threshold levels falls on the contractor unless the contract provides otherwise. When the escalation is driven by geopolitical events rather than market cycles, the distinction between force majeure relief and escalation relief becomes important.

    Saudi Arabia’s Resilience

    Saudi Arabia’s construction pipeline remains one of the most resilient in the world. $196 billion in contract awards in 2025 alone. The fundamentals of Vision 2030 — the programs, the political commitment, the sovereign financial capacity — have not changed. What has changed is the risk profile, and that demands better risk management practice, not a reassessment of the market’s fundamental attractiveness.

    The projects that weather geopolitical disruption are the ones with robust project controls, proactive risk registers calibrated to the specific exposures of the program, and contract models built with enough flexibility to absorb uncertainty without triggering adversarial claims dynamics. Progressive contracting models, which distribute risk more rationally and keep parties aligned around shared outcomes, have structural advantages in high-uncertainty environments compared to traditional fixed-price approaches.

    This is not a moment for panic in the GCC infrastructure market. It is a moment for better professional practice.

Powered by
►
Necessary cookies enable essential site features like secure log-ins and consent preference adjustments. They do not store personal data.
None
►
Functional cookies support features like content sharing on social media, collecting feedback, and enabling third-party tools.
None
►
Analytical cookies track visitor interactions, providing insights on metrics like visitor count, bounce rate, and traffic sources.
None
►
Advertisement cookies deliver personalized ads based on your previous visits and analyze the effectiveness of ad campaigns.
None
Powered by