Skip to content

04Consortium formation · Prequalification

Partner and Consortium Alignment

Identifying and aligning developers, EPC contractors, engineering firms, investors, suppliers and technology providers.

SponsorEPC contractorEngineering partnerInvestor or financierTechnology provider

What this capability is

A consortium is not a list of capable firms. It is a commercial structure that has to survive prequalification scrutiny, hold together through negotiation, and still function three years into execution when the original goodwill has worn off. Alignment work is building that structure deliberately, rather than assuming shared ambition is enough to hold it together.

Complex infrastructure is delivered by combinations of parties, and the quality of those combinations often decides the outcome before engineering begins. A technically strong consortium with misaligned commercial roles fails prequalification. A credible sponsor with the wrong delivery partners loses years.

MZA works across this interface. We identify and qualify the developers, contractors, engineering firms, investors, suppliers and technology providers a programme actually requires, then align them around roles, responsibilities and commercial positions that hold together under procurement scrutiny.

The work draws on an international ecosystem built over decades, spanning European and international delivery organisations and regional counterparties across EMEA. The result is not an introduction service. It is structured consortium development: parties selected against programme requirements, aligned through defined workplans, and coordinated through the stages where partnerships are tested.

The work in practice

How MZA aligns a consortium

01

Selecting on verified capability, not reputation

Partner searches run on brand recognition produce consortiums that look credible on paper and fail on delivery. We qualify counterparties against the specific technical, financial and track-record requirements of the programme in question: reference projects of comparable scale and complexity, financial capacity to carry their share of risk, and genuine (not claimed) availability for the timeline in question.

02

Allocating roles, risk and reward before allocating trust

Consortiums fail after formation more often than during it, because roles, risk allocation and commercial reward were agreed in principle but never defined precisely enough to survive the first disagreement. We structure role matrices and commercial positions early (who carries which risk, on what terms, for what share) so the arrangement holds when it is tested rather than only when it is convenient.

03

Designing for the scrutiny prequalification actually applies

Prequalification panels test consortium structures for exactly the weaknesses that get built in under bid deadline pressure: financial interdependency that isn't disclosed, technical capability spread too thin across too many bids, or local partnership arrangements assembled in the final weeks. We build consortium structures to withstand that scrutiny from the outset, not to survive a first read.

04

Coordinating the relationship through to the point it is tested

Alignment does not end when a memorandum of understanding is signed. Interfaces between technical, commercial and legal workstreams keep shifting through prequalification and tender, and a consortium's internal coordination is often what a client or evaluator is actually assessing. We stay engaged through those stages, managing the interface and governance framework so the parties present a coherent position when it counts.

Why clients bring MZA in

Where consortiums come apart

01

Consortiums assembled for a single bid with no commercial alignment, collapsing under prequalification scrutiny.

02

Technically strong teams failing because roles, risk and reward were never properly allocated.

03

Partner searches run on reputation rather than verified capability against programme requirements.

04

Local partnership requirements addressed late, forcing rushed and weak arrangements.

How we engage

Typical scope of support

  1. 01Counterparty identification and qualification
  2. 02Consortium structure and role definition
  3. 03Commercial alignment between parties
  4. 04Interface and responsibility mapping
  5. 05Coordination through prequalification and tender stages

What you receive

Typical outputs

  1. Counterparty shortlists
  2. Consortium structures and role matrices
  3. Alignment memoranda and workplans
  4. Interface and governance frameworks

Related project environments

View all projects →

Discuss this capability

Speak with MZA about partner and consortium alignment for a specific programme or market.