A risk written into somebody else's contract column has not disappeared from the project system.
Week 8 repeatedly links procurement models with risk allocation. Traditional construction places significant construction responsibility with the contractor while retaining design responsibility with the client. Design and construct transfers additional design responsibility. Management-led models retain more client involvement. Alliancing shares more risk. PPP structures can distribute risk across design, finance, construction and operation.
This is useful only if leaders avoid a common error: confusing contractual transfer with enterprise elimination.
The Strategic Context
Every procurement model creates a different boundary between buyer and supplier.
The boundary determines who is contractually responsible for particular events.
But the project outcome still depends on the combined system.
If a supplier fails, the buyer may have contractual remedies and still miss the program milestone.
If design risk is transferred badly, the supplier may price large contingency or dispute whether the event was actually within its responsibility.
If the buyer retains critical interfaces, no clause can remove the need to manage them actively.
Risk allocation is therefore an economic and governance decision, not a disappearing act.
What Leaders Commonly Misread
The first mistake is assuming the party that bears contractual liability is the only party affected by the risk.
The second is transferring risks to suppliers that they cannot control.
The third is retaining risks without retaining the capability to manage them.
The fourth is assuming collaborative models contain less commercial discipline because risk is shared.
The fifth is treating a broad fixed-price promise as evidence that every delivery uncertainty has been transferred.
Reframing the Issue
A better question is:
Which party can understand, control, absorb or insure this risk most effectively?
That question should be applied risk by risk.
Design risk may sit with the party controlling detailed design.
Ground-condition risk may depend on access to site information and investigative ability.
Price-escalation risk may sit poorly with either party over a long duration unless an adjustment mechanism exists.
Interface risk may remain fundamentally shared even where contracts allocate specific responsibilities.
This produces more disciplined risk architecture.
Strategic Analysis
Consider a hypothetical infrastructure program.
The client issues a fixed-price design-and-construct contract and declares that “all risk is transferred”.
The contractor controls detailed design and construction, but the client retains approvals, site access and interfaces with a separate utility provider.
A late utility relocation delays the contractor.
The project still suffers even if the contract eventually establishes which party owes money.
The real enterprise question is not merely who pays.
It is whether the system had the capability and incentives to prevent or reduce the delay.
Contractual risk allocation influences behaviour, but project resilience depends on governance across the whole system.
Executive Trade-offs
Transferring more risk can improve accountability and cost predictability.
It can also increase tender prices, reduce bidder participation or encourage contractual defensiveness where suppliers believe the allocation is unmanageable.
Retaining more risk may produce lower contingency and greater flexibility.
It also requires stronger buyer capability, governance and financial tolerance.
Shared-risk models can improve cooperation around interdependent uncertainty.
They also require transparent cost information, aligned incentives and mature relationship behaviour.
No position on the continuum is automatically superior.
Decision Framework
Test each material risk across five dimensions.
Control
Who can influence whether the risk occurs?
Information
Who has the best information about probability and consequence?
Capacity
Who can financially absorb the event?
Incentive
Which allocation encourages prevention and efficient response?
System consequence
Who else is affected even if the contract assigns liability?
Risks that fail these tests should not be transferred merely because a standard contract allows it.
From Strategy to Execution
Immediate action: connect the project risk register with the procurement risk-allocation schedule.
Medium-term capability building: review whether transferred risks are actually controllable by the supplier and whether retained risks have capable internal owners.
Long-term strategic positioning: analyse recurring disputes to identify risks that the organisation repeatedly allocates poorly.
This converts contract experience into enterprise learning.
Signals to Monitor
Watch for tenderers heavily qualifying risk clauses, unusually large contingencies, disputes over client-caused delay, buyer teams saying “that's the contractor's risk” while milestones deteriorate and retained risks with no internal owner.
Another signal is suppliers refusing to bid despite strong market interest in the work itself.
Questions for the Leadership Team
- Which risks are truly transferred and which only appear transferred?
- Can the supplier control the risks we expect it to carry?
- What retained risks require stronger buyer capability?
- Where are project outcomes exposed regardless of contractual liability?
- What risk allocation is reducing competition or increasing contingency?
- Which risks are too interdependent to manage effectively through simple transfer?
Closing Perspective
The objective of procurement is not to transfer the maximum amount of risk.
It is to allocate risk so that prevention, pricing, response and accountability work together.
A well-written contract can allocate liability.
Only a well-designed delivery system can reduce the underlying enterprise exposure.
Related article: Procurement Planning Is Where Delivery Risk Is Designed
Related article: Alliance Contracting: When Shared Risk Is More Rational Than Artificial Risk Transfer
About EraNorth Insights
EraNorth Insights publishes practical analysis on strategy, projects, operations, transformation and decision intelligence for professional and organisational use. About EraNorth.