Can small and medium projects be structured as alliances?

Yes, formally. In practice, the alliance contract architecture overhead pays off only from roughly EUR 10 million CAPEX with high interface complexity. For smaller projects, partnering contracts or collaborative standard contracts often work better.

What's the difference between project alliance and general-contractor model?

In the general-contractor model, the GC carries sub-trade risk; the owner sits outside the contract chain. In the alliance, owner and sub-trades sit in one contract — the risk logic is inverted. The alliance demands more steering willingness from the owner but gives direct visibility and direct co-control.

Does a project alliance work without BIM?

Yes, in principle. In practice BIM and alliance reinforce each other: BIM provides the data base for alliance steering, the alliance creates the incentive to keep data consistent and truthful.

[ Guides ]

Project Alliances / IPA explained

In classical construction contracts, owner and supplier carry their risks separately — and in opposite directions. The result: change orders, dispute, escalation, schedule slippage. A project alliance (internationally: IPA, Integrated Project Alliance) inverts this logic. It brings owner and key trades into a single multi-party contract with a shared cost pool: everyone wins together, everyone loses together. This guide explains what a project alliance technically is, when it pays off, which contract structures exist (ÖNORM alliance models in Austria, IPA templates in Australia and the UK), and which risks the model carries. Audience: industrial investors and public-sector owners with large projects and high interface complexity.

Written by Ing. Andreas Huemer MSc, MBA — owner and managing director.

What is a project alliance?

Contract structure — Owner and key trades carry the project jointly in a single multi-party contract — not in a chain of bilateral contracts.
Cost pool — Shared target pool: shared pain (pain share), shared gain (gain share). Incentives across all alliance members align.
Open books — Cost transparency for all partners, controlled by an audit clause.
No blame, no sue — No mutual claims except for gross negligence or intent. Conflicts resolve through the alliance steering body.
Alliance steering body — Joint steering committee with representatives of all alliance members, consensus decision logic.

When does a project alliance pay off?

An alliance pays off under high project-start uncertainty (industrial-plant CAPEX projects, special-machinery, infrastructural large projects), high interface complexity (multiple trades, international supply chain), and when shortened total schedule, schedule integrity or execution-phase innovation are priorities.

It does not pay off on standard projects with clear requirements specs, low complexity and established trade relationships — there the alliance contract architecture overhead exceeds the methodological benefit.

Contract structures (examples)

ÖNORM alliance model (Austria) — In preparation respectively piloted. Locally adapted to Austrian construction and contract law.
NEC4 Alliance form (UK) — Established British multi-party standard contract with alliance clauses. Strong in public infrastructure.
Australian IPA standard contract suite — Established since around 2000, frequent in public infrastructure. Comparatively mature practice.
US Integrated Project Delivery (IPD) — Related concept from the US market, with focus on BIM integration and collaborative planning.

Risks and limits

The risk assessment across alliance partners must be levelled, otherwise one party carries disproportionately. Open books can collide with trade secrets — that needs to be contractually solved. First-time alliance contracts need experienced contract architecture, otherwise a vague-everything contract emerges. Methodologically, classical PM methodology remains; the alliance is a contract and governance layer above it, not a replacement for PRINCE2 or comparable methodology.

Methodological foundation

The guide references ÖNORM alliance projects (AT), NEC4 Alliance (UK), the Australian IPA standard contract suite, and the PODBIM methodology for on-site steering during the alliance phase.

Frequent questions

Can small and medium projects be structured as alliances? — Yes, formally. In practice, the alliance contract architecture overhead pays off only from roughly EUR 10 million CAPEX with high interface complexity. For smaller projects, partnering contracts or collaborative standard contracts often work better.
What's the difference between project alliance and general-contractor model? — In the general-contractor model, the GC carries sub-trade risk; the owner sits outside the contract chain. In the alliance, owner and sub-trades sit in one contract — the risk logic is inverted. The alliance demands more steering willingness from the owner but gives direct visibility and direct co-control.
Does a project alliance work without BIM? — Yes, in principle. In practice BIM and alliance reinforce each other: BIM provides the data base for alliance steering, the alliance creates the incentive to keep data consistent and truthful.