How You Contract Is How You Govern: Rethinking Risk Transfer on Large Capital Projects

Across both mature and emerging economies, investment in large capital projects (energy and process plants, transport networks, mining complexes, water systems and industrial infrastructure) continues to grow in scale and ambition. With that growth comes a familiar instinct among sponsors, boards and lenders: if the risks are large, hand them to someone else. The contract becomes the instrument through which that hope is expressed, and the choice between a lump-sum price, a reimbursable arrangement, a management contract or an alliance is too often treated as a commercial formality settled by procurement specialists late in the front end. Yet the evidence from decades of large capital project experience points in a very different direction. The way a project is contracted shapes who holds information, who carries the consequences of surprise, how honestly numbers are reported and whether the coalition of owners, contractors, financiers and governments can hold together when conditions change. In short, how a project is contracted is how it is governed.

This comprehensive blog will explore the relationship between contract strategy and project governance, unpacking why the appeal of risk transfer so often proves illusory. We will delve into why a lump-sum price behaves more like a floor than a ceiling, how risks can be allocated to the parties best able to carry them, and why the deal and the underlying technical data must come before any choice of contract form. Furthermore, we will examine the full menu of contract forms and what each one demands of the owner, the genuine debate over whether risk should be transferred, shared or absorbed into a wider coalition, the design of incentives that reward honesty, the path by which a low bid turns into a stream of claims, the central role of the owner team, and the governability needed to absorb surprise. Whether you are a project sponsor, owner's representative, government official, investor or project development professional, understanding how contracting choices govern outcomes is key to delivering large capital projects that create the value they promise.

1. The Contract Is a Governance Decision, Not Paperwork

A contract form is, at its core, a mechanism for distributing risk and incentives among the parties to a project. It determines who is rewarded for saving money, who is penalised for delay, who has the right to change the design and who must pay when the ground conditions, the market or the regulator behave unexpectedly. Seen this way, choosing a contract strategy is one of the most consequential governance decisions an owner will make.

It is equally important to recognise the limits of that decision. Studies of large capital projects have found that no contract form can rescue a weak front end. When sponsors are in conflict with one another, when the business case is marginal, or when essential owner functions are missing from the team, the project struggles regardless of whether it is executed under a lump sum, a reimbursable contract or an alliance. The contract can reinforce good preparation; it cannot substitute for it.

A further distinction shapes everything that follows. Risks that can be identified in advance can be insured, hedged or written into contracts. Genuine surprise, the event nobody anticipated, cannot be scripted into a contract ahead of time. Contracts are therefore well suited to allocating known risks and poorly suited to handling the unknown. Any governance arrangement for a large capital project must account for both.

2. The Appeal of Transferring Risk

Few ideas are more attractive to a sponsor under pressure than the promise of making the contractors carry the risk. Research on industrial megaprojects identifies this belief as one of the classic sponsor mistakes. The pressure for a fixed price typically originates with business leaders who want certainty for the board, or with the banks financing the project, who want a predictable cost base against which to lend.

The logic seems sound: agree a price, sign the contract and the overrun becomes someone else's problem. Practitioner guidance on engineering and construction contracts offers an important qualification. A lump-sum contract only protects the owner when the scope is fully defined. Where the definition is incomplete, the fixed price rests on assumptions that will be revisited, and the protection it appears to offer is largely notional.

Industry guidance on integrated delivery describes the traditional approach in similar terms: risk is passed from one party to another rather than shared among them. Each participant seeks to push exposure down the chain, and each prices that exposure accordingly. The result is a set of relationships organised around defending positions rather than solving problems, which is precisely the opposite of what a complex, uncertain project needs.

3. Why a Lump-Sum Price Is a Floor, Not a Ceiling

The central weakness of risk transfer lies in the economics of contracting firms. Contractors are variable-cost businesses with limited balance sheets relative to the size of the projects they build. They cannot absorb very large risks without threatening their own survival. Studies of large capital projects have found that the owner pays a premium for the promise of transfer, yet relatively little risk actually moves. When the losses become large enough, they return to the owner through claims, renegotiation or, in the worst cases, contractor distress.

The consequences can be subtle as well as financial. When a lump-sum contractor approaches the limit of its budget, something must give, and the evidence suggests that operability is often the first casualty. Choices of equipment, materials and finishing that are invisible at handover can determine whether a plant runs reliably for decades. A contractor squeezed by a fixed price has every incentive to meet the letter of the specification rather than its intent.

This is why the lump-sum price is better understood as a floor than a ceiling. It represents the minimum the owner will pay, not the maximum. For risks that are genuinely beyond a contractor's capacity, other instruments are required: equity participation, guarantees, or an agreed path to renegotiate when circumstances change materially. Recognising this early allows sponsors to design for it rather than discovering it in a dispute.

4. Give Each Risk to the Party Best Able to Carry It

If transferring all risk to the contractor is an illusion, what is the alternative? Research across dozens of large engineering ventures points to a clear principle: each risk should sit with the party best able to control it or bear it. Some risks are best managed by the owner, who controls scope, market access and relationships with regulators. Others are best managed by contractors, who control means and methods on site. Still others are best carried by financiers, insurers or governments, whose balance sheets and powers suit particular exposures.

Successful sponsors do not rely on a single hedge. They use layered devices, combining contractual allocation with insurance, financial structuring, partnership arrangements and institutional commitments, so that each risk is matched to an appropriate holder. This layering is what allows a project to withstand shocks that would overwhelm any single party.

Practitioner guidance adds a related principle: responsibility and control should go together, and shared responsibility should be avoided where possible. When two parties each hold part of a responsibility without clear control, neither can act decisively and each can blame the other.

Financing deserves particular attention, because it is itself a form of risk allocation. The choice of lenders, the structure of guarantees and the balance between debt and equity all determine who bears which losses. A guarantee that looks attractive at financial close can later become a political liability, especially when a public body is required to honour it under scrutiny. The allocation of risk must therefore be considered across the whole life of the project, not only at signature.

5. The Deal and the Data Come Before the Form

Before any contract form can work, two foundations must be in place: a settled deal among the sponsors and a sound body of technical data. Research on industrial megaprojects summarises the first point in a single phrase: the deal drives the project. In one documented case, roughly $250 million was spent on a project of around $7 billion before anyone established that there was no secure feedstock. No contract strategy could have saved that project, because the commercial foundation was never there.

The second foundation is Basic Data: the technical record of site conditions, feedstock properties, reservoir or ore characteristics and other fundamentals on which the design rests. When Basic Data is late, incomplete or delegated to a contractor, errors cascade through engineering, procurement and construction. The contract cannot correct for information that was never gathered.

Sequencing also matters. Practitioner guidance recommends selecting the contract form before the specifications are written, because the form determines how the specifications should be drafted, how much the owner needs to define and how changes will be handled. Choosing the form after the documents are complete often forces a mismatch between what has been specified and how it will be procured.

Finally, research on large engineering projects emphasises that the fast execution phase should begin only once there is a package that every party can commit to. A committable package means the coalition is formed, the rights and permits are secured and the allocation of risk is settled. Starting execution before that point does not save time; it moves unresolved questions into the most expensive phase of the project.

6. The Menu of Contract Forms and What Each One Asks of the Owner

Large capital projects draw on a familiar range of contract forms, each placing different demands on the owner:

• EPC lump sum. A single contractor engineers, procures and constructs for a fixed price. It demands complete definition and strong Basic Data from the owner before award, and rigorous control of changes afterwards.
• Reimbursable EPC. A single contractor is paid its costs plus a fee. It demands an owner team capable of controlling cost, schedule and quality in real time, because the contractor's incentive to economise is weaker.
• EPCm. A contractor provides engineering, procurement and construction management, while construction work is let in separate packages. It demands owner involvement in package strategy and interface management.
• Split forms. Engineering and construction are contracted separately. They demand that the owner manage the interface between designer and builder and carry the risk of design errors surfacing on site.
• Alliance or integrated project delivery. Owner and key contractors share risk and reward under a common agreement. It demands a mature owner, aligned commercial terms and leadership capable of sustaining collaboration.

Practitioner guidance frames the basic choice simply: contracts may be divided between an engineer and a constructor, or awarded to a single EPC contractor. Research on large engineering projects adds a broader perspective, describing three models of relationship. In the arm's-length model, the owner specifies and the market competes. In the relational model, the owner works with trusted partners over time. In the mixed model, a coalition of sponsors and partners shapes the project during the front end and then tenders execution at arm's length through EPC contracts. Frame agreements with familiar contractors sit between these models, trading some price competition for familiarity, continuity and lower transaction costs.

Figure 1: The contract-form spectrum, from risk transfer through risk sharing to coalition, and what each form asks of the owner.

7. Where the Evidence Divides: Transfer the Risk, Share It, or Bring the Builders into the Coalition?

The case for sharing risk is substantial. Integrated delivery principles call for mutual respect, shared risk and reward, early involvement of key participants, open communication and collaborative decision-making. The best-known example in the field is Heathrow Terminal 5, which was delivered on time and on budget. There the owner assumed more of the risk itself, used cost-reimbursable contracts with profit tied to milestones, chose suppliers for experience rather than the lowest bid, and aligned incentives around a single shared goal. By contrast, the new Wembley Stadium was marked by conflict, stoppages and litigation, and its cost roughly doubled from £445 million to £900 million.

Studies of industrial megaprojects offer an important caution. Alliances fail when they are adopted as a slogan laid over a deal that has never been properly allocated. Calling a relationship an alliance does not resolve conflicts between sponsors, fill gaps in Basic Data or create the owner capability needed to participate as a genuine partner. Without those foundations, collaborative language can mask the same problems that undermine a lump-sum contract.

The evidence also suggests that the right answer depends on conditions. Research on large engineering projects finds that relational approaches pay off chiefly where there are many feasible ways to design and build the project, so that early collaboration can genuinely improve the solution. Practitioner guidance makes the complementary point that a lump sum suits the owner when the scope is fully defined. The question is not which form is best in general, but which form fits the project's degree of definition, the owner's capability and the nature of its uncertainty.

Terminal 5 is therefore best read as one strong case demonstrating what is possible when collaboration is backed by owner capability and commercial alignment. It is not proof that alliances work in every setting. The disciplined sponsor asks what made the case succeed and whether those conditions are present on the project at hand.

8. Incentives: Honesty Is Something You Design

Large capital projects can be understood as a chain of principals and agents (governments, sponsors, lenders, project companies, contractors and subcontractors), each holding information the others lack. Studies of large project governance argue that this structure invites gaming unless incentives are designed to reward honesty and penalise deception. Recommended measures include shared financial responsibility for outcomes, avoiding full public financing or a full sovereign guarantee so that private parties provide at least one-third of the risk capital, sharing of overruns among those who made the estimates, and independent peer review of forecasts.

The underlying problem has a name. Strategic misrepresentation describes the deliberate underestimation of costs and overestimation of benefits in order to win approval or funding. It differs from honest optimism, although both push forecasts in the same direction. Research on infrastructure decisions has found that transparency, accountability and aligned incentives can reduce deception, because they raise the cost of being caught and make the benefits of inflated promises less attractive.

An alternative view emphasises process over incentives. Studies of industrial megaprojects argue that a properly functioning gate process makes misrepresentation difficult in practice: when each gate requires independent review, defined deliverables and a clear-eyed comparison against prior projects, optimistic or misleading numbers are exposed before they become commitments. The two views are complementary. Well-designed incentives make honesty rewarding, and well-run gates make dishonesty hard.

9. From Bid to Claims: How a Low Number Keeps Going

A low number at approval rarely stays low. Research on cost underestimation in public works describes a pattern sometimes called "salami tactics": costs left out of the approval estimate are introduced later, slice by slice, once the project is committed and stopping it has become politically or financially difficult. Each slice appears modest in isolation; together they can transform the economics of the investment.

The contract form influences how those slices arrive. Practitioner guidance notes that changes under a lump-sum contract are difficult and costly, because every departure from the defined scope must be priced, negotiated and documented. A fixed price built on incomplete definition therefore becomes a steady source of change orders and claims, with each party's commercial team working to protect its position.

Studies of industrial megaprojects add a less obvious finding. On most projects, good cost controls are associated with fewer operability problems after start-up. On lump-sum projects, that association does not hold. Strong cost control under a fixed price does not translate into a better-performing asset, because the contractor's incentives to protect its margin can work against the owner's interest in long-term reliability.

Figure 2: From low bid to claims: how an incomplete front end and a fixed price turn into change orders, disputes and lost operability.

10. The Owner Team Is the Real Counterparty

Whatever the contract form, the owner team is the counterparty on which everything depends. Studies of industrial megaprojects have found that when the owner team has done its preparation properly, contractor teams rarely fail. The converse is equally clear: staffing the owner side with a skeleton team is, in effect, planning to fail.

Research on the leadership of complex projects describes what an effective owner team looks like. It is integrated, meaning every owner function the project needs is present, including operations, maintenance, engineering, commercial and project controls. Its members are empowered to make decisions, and there is continuity of people from the front end into execution, so that the knowledge built during definition is not lost at the point of award.

Recent industry analysis of resource deployment adds practical guidance on which roles the owner should keep. Operations, maintenance and the project manager roles are core owner functions that should not be handed to third parties. Other functions may be supplemented with external support, but the owner must retain the capacity to make and own the key decisions.

The responsibility runs both ways. Front-end planning research cautions that a contractor should not treat thin owner definition as if it were complete. A contractor that accepts weak definition without challenge is participating in the same illusion as the sponsor who believes the risk has been transferred.

11. Governability: Contracts That Can Absorb Surprise

Because surprise cannot be written into a contract in advance, large capital projects need a further quality: governability, the capacity of the coalition to hold together and respond when the unexpected happens. Research on large engineering projects identifies four elements that support it:

• Reserves: financial and schedule contingencies held deliberately to absorb shocks.
• Triggers for joint action: agreed conditions under which the parties must come together to decide on a response.
• Flexibility: options built into the design, the contracts and the financing that allow the project to change course.
• Generativity: the ability of the coalition to debate openly and invent new responses rather than retreat into contractual positions.

Public–private arrangements deserve particular care. They are more exposed to opportunism on all sides, and contracts alone do not prevent arbitrary actions by governments, whose powers extend beyond any agreement they sign. Governability in these settings depends on institutional arrangements, relationships and credible renegotiation mechanisms as much as on contractual terms.

It is useful to distinguish governability from governance in a narrower sense. Studies of industrial megaprojects describe owner governance as the set of gate rules by which the owner decides whether to proceed, supported by a technical authority with the power to stop the project if standards are not met. Both matter. Governance determines whether the project should go ahead; governability determines whether the coalition can survive what happens once it does.

Figure 3: Allocating each risk to the party best able to carry it, and the governability elements that handle what no contract can foresee.

12. What to Do Differently

The evidence across these themes points to a set of practical commitments for sponsors and owners:

• Settle the deal first. Agree how value and risk will be shared among sponsors before choosing a contract form, and confirm the commercial foundations, such as feedstock, market and rights, are secure.
• Get the Basic Data in. Gather the technical fundamentals during the front end and keep ownership of them rather than delegating them to a contractor.
• Complete front-end loading before award. Match the contract form to the degree of definition actually achieved, not the degree hoped for.
• Choose the form before writing the specifications. Let the contract strategy shape how the scope is defined and how change will be managed.
• Allocate each risk to the party best able to carry it. Use layered devices, combining contracts, insurance, equity, guarantees and renegotiation paths, rather than relying on a single transfer.
• Agree renegotiation rules early. Define triggers for joint action and reserves while commitments are still inexpensive to change.
• Align incentives beyond approval. Ensure promoters, estimators and contractors continue to carry downside after the investment decision.
• Staff a real owner team. Keep operations, maintenance and project management in-house, and maintain continuity of people from the front end into execution.
• Restore a sensible owner–contractor relationship. Treat contractors as partners in delivery within a clear allocation of risk, not as the place where risk is sent to disappear.

Conclusion

The appeal of risk transfer is understandable. It offers the comfort of a number and the hope that someone else will be accountable if things go wrong. Yet the experience of large capital projects shows that risk is rarely transferred away. It is priced, shared or hidden, and when it is hidden it returns at the worst possible moment, often through claims, disputes or an asset that never performs as intended.

The contract is not paperwork prepared after the important decisions have been made. It is the way the project will be governed: who knows what, who decides what and who pays for what. Sponsors who treat contracting as a governance decision, founded on a settled deal, sound data, a capable owner team and arrangements that can absorb surprise, give their projects a far better chance of delivering the value they were approved to create.

References

1. American Institute of Architects & AIA California Council. (2007). Integrated Project Delivery: A Guide. AIA / AIA California Council.
2. Benator, B., & Thumann, A. (2003). Project Management and Leadership Skills for Engineering and Construction Projects. The Fairmont Press / Marcel Dekker.
3. Construction Industry Institute. (2006). Front End Planning: Break the Rules, Pay the Price (RT-213). Construction Industry Institute.
4. Flyvbjerg, B. (2021). Top ten behavioral biases in project management: An overview. Project Management Journal, 52(6), 531–546.
5. Flyvbjerg, B., Garbuio, M., & Lovallo, D. (2009). Delusion and deception in large infrastructure projects: Two models for explaining and preventing executive disaster. California Management Review, 51(2), 170–193.
6. Flyvbjerg, B., & Gardner, D. (2023). How Big Things Get Done. Currency.
7. Flyvbjerg, B., Holm, M. S., & Buhl, S. (2002). Underestimating costs in public works projects: Error or lie? Journal of the American Planning Association, 68(3), 279–295.
8. Lovallo, D., Cristofaro, M., & Flyvbjerg, B. (2023). Governing large projects: A three-stage process to get it right. Academy of Management Perspectives, 37(2).
9. Merrow, E. W. (2024). Industrial Megaprojects: Concepts, Strategies, and Practices for Success (2nd ed.). John Wiley & Sons.
10. Merrow, E. W., & Nandurdikar, N. S. (2018). Leading Complex Projects: A Data-Driven Approach to Mastering the Human Side of Project Management. John Wiley & Sons.
11. Miller, R., & Lessard, D. R. (2000). The Strategic Management of Large Engineering Projects: Shaping Institutions, Risks, and Governance. MIT Press.
12. Wallace, L. (2025, September 29). Managing Resource Deployment in a Constrained Environment. Independent Project Analysis.