Introduction
Joining a Horizon Europe project as a partner is straightforward on paper. Running one as a coordinator is a different matter entirely.
A consortium is not simply a group of organisations working on the same project. It is a legally constituted partnership with defined roles, shared obligations, internal governance mechanisms, and contractual relationships that run in parallel with — and sometimes in tension with — the Grant Agreement itself.
This article explains how a Horizon Europe consortium is structured, what each role involves, and where coordination most commonly breaks down.
What a consortium is
A consortium is the group of legal entities that jointly submit a proposal and, if successful, jointly execute a Horizon Europe project. Each member is a beneficiary under the Grant Agreement, meaning each organisation has direct legal obligations to the European Commission.
Most collaborative projects under Horizon Europe require a minimum of three independent legal entities established in three different EU member states or associated countries. In practice, many consortia are significantly larger — projects with 10, 15 or even 20 partners are common in the major collaborative schemes under Pillar II.
The consortium is bound together by two parallel legal frameworks:
- The Grant Agreement (GA) — the contract with the European Commission, which defines the project’s objectives, budget, deliverables, reporting obligations, and eligibility rules.
- The Consortium Agreement (CA) — a private contract between the consortium members themselves, which governs internal decision-making, IP ownership, liability, financial flows, and dispute resolution.
Note: The Consortium Agreement is not mandatory under Horizon Europe rules, but it is strongly recommended and is considered standard practice in well-run projects. Its absence creates significant governance risk, particularly in disputes over IP or partner non-performance.
The main roles in a consortium
Coordinator
The coordinator is the consortium member with primary responsibility for the project. Every consortium has exactly one.
The coordinator’s responsibilities include:
- Signing the Grant Agreement on behalf of the consortium
- Managing communication with the European Commission and the Project Officer
- Consolidating and submitting technical and financial reports
- Distributing pre-financing and interim payments to partners
- Monitoring progress across all work packages and flagging deviations
- Managing amendments to the Grant Agreement when required
The coordinator bears disproportionate administrative and legal exposure. If a partner fails to deliver, the coordinator is accountable to the Commission. If funds are mismanaged by a partner, the coordinator may be required to recover them.
This is a role that demands not just scientific or technical leadership, but strong project management, financial oversight, and cross-organisational communication capacity.
Beneficiaries (partners)
All other consortium members are beneficiaries. Each beneficiary:
- Signs the Grant Agreement and is directly bound by its terms
- Is responsible for executing the tasks and delivering the outputs assigned to them in the Annex 1 (Description of Action)
- Must maintain cost records that comply with Horizon Europe eligibility rules
- Reports their costs and progress to the coordinator at each reporting period
- Is subject to audit, regardless of their size or contribution
Being a beneficiary is not a passive role. Each partner carries independent legal and financial obligations, and failure to comply can affect not just that partner’s funding but the project’s overall performance assessment.
Work Package Leaders
Most Horizon Europe projects are organised into work packages (WPs) — thematic or functional groupings of tasks that together constitute the project’s work plan. Each work package has a designated leader, typically one of the consortium partners with particular expertise in that area.
The WP leader is responsible for:
- Coordinating the tasks within their work package
- Tracking progress against the planned timeline
- Ensuring deliverables are produced on schedule
- Consolidating contributions from partners involved in that WP
- Reporting progress to the coordinator
In large consortia, WP leaders effectively act as sub-coordinators. The quality of their management — and their communication with the central coordinator — significantly affects overall project performance.
Associated partners and affiliated entities
Some consortia include associated partners: organisations that contribute to the project but do not receive EU funding directly. Associated partners may carry out tasks, provide access to infrastructure, or contribute expertise, but they are not signatories to the Grant Agreement and operate under different rules.
Affiliated entities are a separate category — organisations legally linked to a beneficiary (such as subsidiaries) that can participate under the beneficiary’s budget. Their costs must be clearly identified and justified.
Internal governance structures
Beyond individual roles, well-run consortia typically establish a formal governance structure to manage collective decisions and escalate issues when they arise.
General Assembly The supreme decision-making body of the consortium, composed of representatives from all partners. Major decisions — amending the Consortium Agreement, adding or removing partners, resolving disputes — are taken at this level.
Project Management Board or Steering Committee A smaller executive body, typically composed of the coordinator and WP leaders, responsible for operational decisions, monitoring progress, and managing day-to-day issues that do not require full consortium involvement.
Project Manager / Project Management Office Many larger consortia appoint a dedicated project manager or establish a PMO function within the coordinating organisation. This role handles administrative coordination, tracks deliverables and milestones, manages documentation, and supports reporting preparation.
The absence of a clear governance structure is one of the most common — and most avoidable — sources of project failure. When decision-making authority is unclear, partners default to inaction; when escalation pathways do not exist, small problems become large ones.
Where consortium coordination most commonly breaks down
Understanding the structure is one thing. The practical reality of running a multi-partner project over three to five years is significantly more demanding.
The most common failure points are:
Uneven partner engagement. Not all consortium partners bring the same level of commitment or capacity. In large consortia, some partners are passive, submitting minimal progress updates and doing the minimum required. The coordinator carries the burden.
Documentation gaps. Partners do not maintain records consistently. When reporting time arrives, evidence is missing, incomplete, or formatted inconsistently. This creates delays and compliance risk.
Communication breakdown. With partners across multiple countries and time zones, coordination through email and shared drives quickly becomes unmanageable. Decisions are made informally, versions are lost, and accountability becomes unclear.
Work package interdependencies. Tasks in one WP frequently depend on outputs from another. When one WP falls behind, the impact cascades — but this is only visible to the coordinator if monitoring is active and real-time.
Financial misalignment. Partners may track their costs differently, use incompatible accounting systems, or misclassify expenditure. By the time discrepancies are discovered at reporting time, corrections are difficult and sometimes impossible.
How Kronis PMO supports consortium coordination
Kronis PMO is designed to address exactly these operational challenges. It provides a shared management layer that structures execution around the Grant Agreement — making work packages, deliverables, partner responsibilities, and evidence requirements visible to everyone involved in the project.
Rather than coordinating through email threads and spreadsheets, consortium teams can use Kronis PMO to track who is responsible for what, monitor progress across partners in real time, and maintain the traceability that reporting and audits require.
For coordinators managing large multi-partner projects — particularly under lump sum schemes where delivery evidence is critical — Kronis PMO provides the operational infrastructure that the project needs from day one.
Final thoughts
A Horizon Europe consortium is only as strong as the governance behind it. The legal structure — Grant Agreement, Consortium Agreement, defined roles — provides the framework. But what determines whether a project actually delivers is simpler and harder to fix: who owns what, who escalates when something goes wrong, and whether the documentation exists to prove that the work was done.
The coordinator carries the weight of all of it. The organisations that manage this well are not necessarily the most experienced — they are the ones that treat governance as a management priority from day one, not an afterthought when the first reporting deadline arrives.
What is Horizon Europe? A plain-language guide for project teams
Cost Amendments in Horizon Europe: When You Can Change Your Budget (And When You Can’t)
