Building a consortium for EU framework contracts: structure, roles, and pitfalls

When a consortium is required and when it is optional

Most EU service contracts under the Practical Guide to Contract Procedures for EU External Action (PRAG) and Directive 2014/24/EU do not require a consortium. Single-entity bids are permitted and common. The decision to form a consortium is typically driven by a practical assessment of what the contract requires versus what any single organisation can credibly offer, not by a rule mandating partnership.

A consortium becomes necessary or clearly advantageous in the following situations:

• Geographic multi-country scope: contracts that require active presence, staff deployment, or national-language capability across multiple countries simultaneously. A single firm based in one country can sub-contract, but a consortium with established national partners in the target countries often scores higher on team credibility and geographic knowledge.
• Multi-disciplinary scope: technical assistance contracts that combine sectoral expertise that no single organisation holds. A programme combining public administration reform, digital government, and gender equality components may require a consortium to present a credibly experienced team across all three areas.
• Financial standing thresholds: the selection criteria in the contract notice typically require the bidding entity to demonstrate a minimum annual turnover, often a multiple of the estimated contract value. Smaller organisations that cannot meet this threshold alone can aggregate financial standing across consortium members in most PRAG procedures.
• Technical capacity requirements: where the tender requires a minimum number of completed contracts of a specific type and value, references from consortium members can be pooled. A single firm may lack the required volume of comparable assignments; a consortium of two or three firms typically does not.
• Framework contract lot pre-qualification: some INTPA and NEAR framework lots specify a minimum consortium size or require that the consortium include a local or national partner from the target region. Check the specific lot requirements before assuming a single-entity bid is eligible.

Forming a consortium when it is not needed adds governance complexity and coordination cost without improving the bid. If a single organisation can credibly meet all selection criteria and field a competitive technical team, a single-entity bid is generally preferable.

Lead partner and member roles under PRAG

Under PRAG service contract procedures, the consortium must designate a lead partner (referred to in some contexts as the coordinator). The lead partner is the legal entity that signs the service contract with the contracting authority. It is the primary contractual counterpart for all communications, reporting, and financial claims. The contracting authority deals with the lead partner; other consortium members have no direct contractual relationship with the contracting authority unless the contract explicitly provides otherwise.

The lead partner's responsibilities in practice include:

• Submitting the tender on behalf of the consortium
• Signing the service contract and any contract amendments
• Receiving payments from the contracting authority and distributing to members per the consortium agreement
• Submitting progress reports and financial claims
• Being the primary point of contact for contracting authority requests, audits, and verifications

Consortium members contribute their expertise, staff, and capacity to the delivery. Their obligations to the contracting authority flow through the lead partner; their obligations to each other flow through the consortium agreement. The distinction matters when things go wrong: if a consortium member defaults on their deliverables, the lead partner remains responsible to the contracting authority and cannot point to the internal agreement as a defence.

Consortium members versus sub-contractors

EU procurement distinguishes between consortium members (who are co-signatories of the bid and party to the service contract) and sub-contractors (who are engaged by the lead partner or a member to perform specific tasks but have no direct contractual standing with the contracting authority). The distinction has practical consequences:

• Sub-contractors' references and capacity can be relied upon for selection criteria in most PRAG procedures, but the contracting authority may require a formal declaration of intent to sub-contract and details of the sub-contractor.
• Sub-contractors do not share joint and several liability with the consortium members.
• Sub-contracting above a certain percentage of the contract value must be declared, and some contracting authorities cap the proportion of work that can be sub-contracted.

In practice, smaller specialist firms are often brought into a consortium structure rather than as sub-contractors specifically to allow their references and financial capacity to count toward the selection criteria. Sub-contracting is used when the specialist input is narrowly defined and their capacity is not needed to clear the selection criteria threshold.

Joint and several liability

Under PRAG service contracts, all consortium members are jointly and severally liable to the contracting authority for the full performance of the contract obligations. This is not an optional arrangement or a matter of negotiation with the contracting authority: it is a standard condition of the PRAG general conditions for service contracts.

Joint and several liability means that if one consortium member fails to perform, goes insolvent, or withdraws, the contracting authority can seek full performance and financial remedy from any other member. The lead partner bears the greatest practical exposure because it is the primary contractual counterpart, but all members are exposed. A consortium member who contributes 15% of the contract tasks is potentially liable for 100% of the contract value if the other members cannot perform.

This has direct implications for partner selection and for the consortium agreement. Bringing in an undercapitalised or financially fragile member introduces liability risk that is not proportionate to the contribution they make to the bid. Before signing a consortium agreement, verify the financial standing of each prospective member, their liability insurance arrangements, and whether their legal status permits them to take on joint and several liability in the relevant jurisdiction.

The consortium agreement: key clauses

The consortium agreement is a private contract between the consortium members, separate from the service contract with the contracting authority. It should be signed before the bid is submitted, not after award. An agreement signed post-award creates a window of undefined governance during which disputes or misunderstandings can derail mobilisation.

A robust consortium agreement for an EU service contract should address:

Lead partner authority

Confirm that the lead partner has the authority to sign the service contract, submit claims, receive payments, and communicate with the contracting authority on behalf of all members. Include a power of attorney from each member to the lead partner if required by the PRAG tender dossier (some dossiers require this as part of the bid submission).

Task allocation and work share

Define each member's responsibilities in terms of deliverables, expert days, and percentage share of the contract value. The task allocation should be specific enough to prevent post-award disputes about who is responsible for what. Vague or overlapping descriptions of responsibilities are a common source of internal conflict during implementation. Cross-reference the allocation to the methodology and work plan submitted in the bid so that the consortium agreement and the technical offer are consistent.

Financial arrangements

Specify how the lead partner will distribute payments received from the contracting authority: the timing of on-payments to members, the treatment of advances, the procedure for handling underpayment or delayed payment by the contracting authority, and the handling of final balance payments. For contracts that include a performance-based retention, the agreement should state how the retention is managed across members.

Decision-making and dispute resolution

Define decision-making for key events during implementation: approving significant variations, substituting key experts, responding to contracting authority requests for change, and taking positions in formal discussions with the contracting authority. Specify the dispute resolution mechanism if members cannot agree: escalation, mediation, or arbitration under a named seat of law.

Intellectual property

Most EU service contracts vest the intellectual property rights in deliverables in the contracting authority. The consortium agreement should confirm this and specify what happens with background IP (pre-existing knowledge and tools that members bring to the contract). If a member uses proprietary methodology tools, the agreement should state how those are licensed to the consortium for the contract and whether they revert to the owner after completion.

Exit and replacement

Include provisions for the voluntary or involuntary exit of a member: what triggers exit, how the remaining members absorb or replace the work share, the financial settlement process, and the procedure for notifying and obtaining approval from the contracting authority. A member exit without a planned response can trigger a formal breach of the service contract. Having the procedure pre-agreed reduces response time and demonstrates to the contracting authority that the consortium has governance arrangements in place.

Pooling technical capacity across consortium members

One of the primary reasons organisations form a consortium rather than bidding alone is to aggregate technical and financial capacity for the selection stage. Under PRAG procurement, the selection criteria assess whether the bidding entity has the legal standing, financial health, and technical track record to deliver the contract. These criteria must be met by the consortium collectively, not by each member individually.

For technical capacity, this typically means:

• References from completed comparable contracts can be drawn from any consortium member. If the tender requires three completed contracts in the relevant sector over the last five years, the three references can span all members of the consortium.
• CVs of proposed key experts can come from any consortium member's staff or from staff engaged by sub-contractors declared in the bid. The key expert is assessed on their individual qualifications against the requirements in the Terms of Reference, not on which legal entity employs them.
• Technical accreditations, certifications, and sector registrations held by any member can typically be cited, subject to the specific requirements in the tender dossier.

For financial standing, the standard PRAG approach allows aggregation of turnover across consortium members. Some tender dossiers impose a minimum financial threshold on the lead partner specifically, typically requiring the lead to demonstrate a minimum annual turnover independently. Read the selection criteria section of the contract notice carefully before assuming full aggregation is permitted.

At the award evaluation stage, the technical quality of the proposed team is assessed on the CVs submitted, regardless of which entity employs the experts. A consortium that presents a strong team drawn from across its members will score identically to a single entity presenting the same team. The consortium structure itself is not a source of technical score advantage or disadvantage at award: what matters is the quality of the specific people and the methodology.

Common pitfalls in EU consortium bids

Consortium assembled too late

The most persistent problem in consortium bids is assembling the partnership after the tender has been published, under time pressure. A consortium formed in the final two weeks before submission rarely produces a well-integrated technical offer. Task allocation is rushed, the methodology reads as a set of parallel sections from different firms rather than a coherent approach, and the work plan does not reflect realistic coordination between teams operating in different locations. The result is a bid that looks like a consortium of independent parties rather than a delivery team. Relationships with potential consortium partners should be developed well before specific tenders are published, so that an MOU or framework partnership agreement can be converted into a specific consortium agreement quickly when a target opportunity arises.

Key expert substitution issues post-award

Under PRAG service contracts, the key experts named in the winning bid must be available to deploy as proposed. The contracting authority approved those specific individuals, not generic profiles. If a named key expert is not available at the start of the contract, the lead partner must formally request substitution with a replacement who meets or exceeds the requirements of the original. The contracting authority has the right to refuse a substitution request, and repeated substitution requests can trigger contractual remedies. Proposing a senior expert who is already heavily committed and unlikely to be available is a common problem. Confirm availability with all proposed key experts in writing, including the specific expected start date, before submitting the bid.

Internal disputes on task allocation after award

A consortium agreement that describes task allocation in broad terms creates scope for disputes once implementation begins and the practical workload becomes clear. If the agreement says Partner A is responsible for "technical inputs" and Partner B for "capacity building activities" without defining what that means in terms of deliverables, expert days, and cost, the partnership will spend implementation time renegotiating what was agreed. The task allocation in the consortium agreement should use the same deliverable structure and approximate person-day figures as the approved methodology and work plan.

Undersized or under-resourced members reducing score

Adding a consortium member whose references are weak, whose proposed key expert does not meet the preferred criteria in the evaluation grid, or whose inclusion creates complications in the financial standing calculation without adding capacity to clear the threshold is a net negative for the bid. Each member should be assessed on what they add to the evaluated bid: a member who contributes a key expert that scores below the threshold or provides references that do not meet the comparability requirements will drag the overall technical score down compared to a well-matched single-entity or two-partner bid.

Changes in consortium composition post-submission

Once a bid is submitted naming specific consortium members, those members are part of the evaluated offer. If a member withdraws between submission and award, the bid is materially changed, and the contracting authority may reject it or require a full re-evaluation. Under PRAG procedures, consortium composition declared at submission is generally binding through to contract signature. Any change requires the contracting authority's agreement. Treat consortium membership as a firm commitment once the bid is submitted, and ensure each member has authorised their participation with an appropriate internal approval process before the submission deadline.

Frequently asked questions