Alliance contracting is not a softer version of contracting. It is a different governance system for situations where uncertainty cannot be managed well through conventional risk transfer alone.
The Week 10 material presents alliancing as a model built around collaboration, open-book costing, shared risk and reward, good-faith behaviour and integrated project teams. The Victorian model Alliance RFP goes further by defining formal leadership, management and delivery layers, including an Alliance Leadership Team, Alliance Manager, Alliance Management Team and Alliance Project Team.
That architecture matters because trust by itself is not governance.
Trust can improve the quality of interaction. It cannot decide who has authority, how performance is measured, how commercial decisions are approved, how risk is escalated or what happens when participants disagree.
The strategic value of alliancing therefore lies not in removing structure, but in replacing fragmented structure with an integrated one.
The Strategic Context
Conventional contracting often assumes that project risk can be divided, priced and transferred between separate organisations. That model works well where scope is mature, interfaces are understood and accountability can be assigned clearly.
Some projects do not fit that condition.
Complex infrastructure, brownfield work, uncertain ground conditions, rapidly evolving design, major stakeholder constraints or high interface density can make aggressive risk transfer expensive and counterproductive. Suppliers price uncertainty into contingencies. Parties defend contractual positions. Information is withheld because transparency may weaken a later claim. Decisions slow because responsibility sits across several organisational boundaries.
Alliancing responds by changing the commercial and governance logic.
The participants work within a shared framework that seeks to align commercial outcomes with project outcomes. Risk and reward are shared. Cost information is more transparent. Integrated teams work across organisational boundaries. Decisions are expected to be made in the interests of the project rather than through constant bilateral negotiation.
But the model only works if governance is strong enough to support that level of integration.
What Leaders Commonly Misread
A common misconception is that alliances depend primarily on trust.
Trust is important, but it is a consequence of reliable behaviour as much as a prerequisite for it.
Another mistake is assuming that “no blame” means weak accountability. In a serious alliance, poor performance still has consequences. The difference is that the system is designed to resolve problems collectively rather than turning every deviation into a positional dispute.
Leaders can also underestimate the burden placed on senior representatives. Alliance governance asks them to act within an integrated project structure while remaining accountable to their own organisations.
That tension cannot be solved by goodwill alone.
It requires clear authority, delegation, escalation and decision rules.
Reframing the Issue
The better question is not:
Do the parties trust each other enough to form an alliance?
It is:
Can the parties create a governance system strong enough to sustain collaboration when pressure, uncertainty and commercial tension increase?
That reframes alliancing from a relationship philosophy into an operating model.
The Victorian template illustrates this clearly. It separates strategic leadership from day-to-day management and delivery. The Alliance Leadership Team establishes strategic direction and accountability. The Alliance Manager leads the management system. The Alliance Management Team coordinates operational leadership. The Alliance Project Team delivers the work.
This creates a shared project institution rather than a loose collection of contractors.
Strategic Analysis
The strength of this model is integration.
The weakness is that integration can blur accountability if the structure is not disciplined.
A conventional contract may tell the owner exactly which party carries a particular risk. An alliance may instead treat the same risk as a shared delivery problem.
That can improve problem solving, but it also creates a new question:
Who is accountable for managing the risk today?
Shared commercial exposure does not eliminate the need for operational ownership.
Similarly, “Best for Project” decision-making can be powerful because it directs leaders towards system-level outcomes rather than narrow corporate optimisation. But the phrase is meaningful only when the project has clearly defined objectives, value-for-money criteria and governance boundaries.
Otherwise, “Best for Project” can become a slogan used to justify whichever decision is most convenient.
The alliance must therefore make decision rights explicit.
The Enterprise View
From an executive perspective, alliancing changes several important things at once.
First, it changes the nature of supplier selection. Leadership capability, cultural alignment, team behaviour and collaborative problem solving become more important than in a conventional price-led tender.
Second, it changes the commercial control model. Open-book costing gives the owner greater visibility, but also requires stronger internal commercial capability to interpret what it sees.
Third, it changes risk governance. The question moves from “who owns the contractual risk?” to “who is best placed to manage the underlying cause and consequence?”
Fourth, it changes organisational boundaries. Staff from several entities may work as one integrated team while still retaining different employers, incentives and corporate obligations.
Those are governance issues, not soft issues.
Decision Framework
Leaders considering an alliance should test six conditions.
1. Is uncertainty genuinely difficult to allocate?
If scope and risks are well understood, a conventional model may remain more efficient.
2. Does the outcome depend on integrated problem solving?
Alliancing is more compelling where design, construction, operations, stakeholders and risk cannot be separated cleanly.
3. Can the owner govern an open-book environment?
Commercial transparency is useful only if the owner can challenge cost, margin, contingency and productivity.
4. Are decision rights clear?
The alliance must define which decisions sit with the leadership team, management team, project team and parent organisations.
5. Can the participants behave as one team without losing accountability?
Integrated delivery must not become diffuse responsibility.
6. Is the organisation willing to invest in relationship capability?
Facilitation, workshops, behavioural alignment and collaborative leadership require time and deliberate effort.
From Strategy to Execution
Immediate action: define the governance model before finalising the commercial model. Clarify leadership roles, delegated authority, escalation points and the meaning of “Best for Project”.
Medium-term capability building: build internal capability in alliance leadership, open-book commercial management, facilitation and collaborative risk governance.
Long-term strategic positioning: compare alliance outcomes with other delivery models not only on time and cost, but on risk resolution, decision speed, innovation, disputes, lifecycle performance and capability transfer.
The objective is to learn where alliance governance creates superior enterprise value and where it merely adds complexity.
Signals to Monitor
Early warning signs include leadership meetings dominated by organisational self-interest, unresolved ambiguity over authority, project teams escalating routine decisions because delegation is weak, commercial transparency without effective cost challenge, or “no blame” language being used to avoid difficult performance conversations.
Another warning sign is cultural alignment existing only at senior level while subcontractors and delivery teams continue to operate adversarially.
Questions for the Leadership Team
- Which project uncertainties justify integrated governance rather than conventional risk transfer?
- What does “Best for Project” mean in measurable terms?
- Who has authority to bind each participant on major alliance decisions?
- How will shared risk be translated into clear operational ownership?
- Can the owner challenge open-book costs independently?
- What behaviours would cause the alliance model to fail even if the contract is technically sound?
- How will alliance performance be compared with credible alternative delivery models?
Closing Perspective
Alliance contracting does not remove the need for control.
It relocates control from fragmented contractual interfaces into an integrated governance system.
The leaders who treat alliancing as a trust exercise risk creating ambiguity. The leaders who treat it as a governance model can use collaboration, transparency and shared incentives as disciplined mechanisms for managing uncertainty that conventional contracting may handle poorly.
Related article: “Best for Project” Requires Decision Rights: Governing the Alliance as a Virtual Organisation
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.