How Many Partners Should an EU Consortium Have? What the Data Says by Programme

The short answer: use the smallest consortium that can credibly deliver the work, cover the required countries, and satisfy the action rules. For Erasmus+ Cooperation Partnerships, the formal floor is three organisations from three countries. For Small-scale Partnerships, the floor is two organisations from two countries. Horizon Europe usually rewards a wider technical and geographic mix, but even there, every extra partner must earn its place.

Start with eligibility, then move quickly to evidence

Eligibility is only the first gate. It tells you the consortium can be submitted. It does not prove the consortium is convincing, manageable, or sized for impact.

For the Erasmus+ action many applicants call KA two-twenty, the minimum is three organisations from three countries. That minimum works best when the project has a tight scope, clear learning outputs, and partners with distinct delivery roles. For Small-scale Partnerships, two organisations from two countries can be enough, especially where the project is a first cooperation step or a focused exchange between complementary organisations. The Erasmus+ Programme Guide is the source to check before you lock the design.

The practical question is different: how many partners make the proposal stronger without making delivery weaker. Our consortium graph covers 83,490 funded projects and 461,953 participation links across Erasmus+, Horizon 2020, and Horizon Europe. The pattern is clear: funded consortia are not sized by ambition alone. They are sized by the work plan, the trust network, the programme culture, and the coordinator’s capacity to run the group.

What funded projects suggest by programme

The graph contains 24,823 Erasmus+ projects, 35,389 Horizon 2020 projects, and 23,278 Horizon Europe projects. When we inspect partner counts by programme and action type, the distributions separate into recognisable shapes rather than one universal norm.

Erasmus+ partnerships tend to cluster close to a compact partnership model. Small-scale Partnerships are usually built around a narrow cooperation logic: two organisations can exchange practice, test a method, or prepare a larger collaboration. Cooperation Partnerships are broader, but the strongest ones still show clear role discipline: lead, content owner, pilot site, evaluation partner, dissemination partner, or community access partner. Adding another organisation just for a country flag weakens the story.

Horizon projects show a wider spread. That makes sense. They often need research capacity, industry validation, data infrastructure, policy connection, user pilots, and exploitation routes. Horizon Europe continues that pattern, with consortia shaped around the whole value chain rather than a single exchange model.

The main lesson is simple. Do not copy a partner count from another programme. An Erasmus+ cooperation project that behaves like a large research consortium can look heavy. A Horizon proposal that lacks technical depth, validation capacity, or end-user access can look thin.

Where oversized consortia appear

Oversized consortia usually appear when the proposal team confuses reach with delivery. The partner list grows because each partner brings a network, a region, a letter of support, or a previous relationship. Those are useful inputs, but they are not work packages.

In Erasmus+ Cooperation Partnerships, oversizing often shows up in duplicated roles. Several partners promise stakeholder outreach. Several partners promise training. Several partners promise dissemination. The proposal then struggles to explain who owns the method, who tests it, who adapts it, and who maintains the result after funding. Evaluators can see the difference between a consortium and a mailing list.

In Horizon Europe, oversizing appears in another form. The consortium has all the right institution types, but decision-making becomes slow. Technical partners wait for policy partners. Pilot partners wait for platform partners. Exploitation partners wait for evidence. The plan may look impressive, yet the coordination model has not caught up with the partner count.

A larger consortium needs visible operating design. That means clear governance, named decision rights, shared data routines, issue escalation, and a rhythm for producing evidence. If those mechanisms are missing, the proposal should probably be smaller.

A practical sizing method for coordinators

A defensible consortium size starts with the work, not with names. Before inviting another partner, write the delivery map in plain language. Then test each possible organisation against that map.

Use a short sizing check:

• Start with the eligibility minimum for the action.
• Add a partner only if it owns a distinct capability, audience, geography, dataset, test site, or delivery responsibility.
• Remove partners whose role can be covered by an advisory group, subcontract, associated stakeholder, or dissemination contact.
• Check whether the coordinator can realistically support the meetings, reporting, evidence collection, approvals, and partner onboarding.
• Write one sentence in the proposal explaining why the consortium is this size.

That final sentence matters. It can say that the partnership is compact because the action focuses on method transfer and piloting. It can say the consortium is broader because the project requires several validation contexts or a full research-to-market chain. The point is to show intent.

For Cooperation Partnerships, compact often reads as mature when the roles are sharp. For Horizon Europe, breadth reads as mature only when integration is explicit. In both cases, the right size is the one where every partner has a necessary job and the coordinator has a believable operating model.

Turn partner count into a proposal argument

Partner count should appear in the proposal as evidence of design quality. Treat it as part of your implementation argument, not an administrative detail.

A simple paragraph can do a lot of work. State the minimum rule, then explain why your consortium is above it, close to it, or deliberately wider. Connect each partner type to a work package, output, pilot setting, user group, or dissemination route. If the consortium is large, add the management reason: steering group, task leads, reporting cadence, shared workspace, data collection routine, and decision process. If it is small, add the coverage reason: why the selected partners still represent the target communities and why the outputs can travel beyond the partnership.

This is also where partner intelligence helps. Before fixing the list, check whether the organisations have coordinated before, whether they are regular participants, and how they connect to the wider funding network. Our graph includes 114,731 organisations, including 25,915 that have coordinated at least once and 1,717 that appear in five or more projects. That context helps you separate credible delivery partners from decorative names.

If you are preparing a consortium now, make the next step concrete: draw the role map, remove duplicates, then test the list against funded patterns from the relevant programme.

Where this comes from

This article is based on our consortium graph, built from open CORDIS and Erasmus+ data, and on the operating work we do with cooperation communities. At StrandsUnited, we design, build, and operate platforms for EU projects and communities, including knowledge bases, member areas, and AI assistants that answer with sources. Running Impactful has also taught us that consortium design only works when the platform, governance, and evidence routines match the people doing the work.