The consortium is the foundation of any Erasmus+ project. Get the composition right and you have a credible, deliverable project. Get it wrong — wrong number of partners, wrong country mix, wrong organisational types, or roles that do not match the work plan — and you risk both rejection at the eligibility stage and a low score on partnership quality.
This guide explains exactly what Erasmus+ requires from a consortium: the eligibility rules, the difference between coordinator and partner responsibilities, what evaluators look for when they assess the partnership, and the most common consortium mistakes that cost applicants points or get applications rejected outright.
|
2
Minimum partner organisations required for KA210 — from 2 different Erasmus+ programme countries
|
3
Minimum partner organisations required for KA220 — from 3 different Erasmus+ programme countries
|
1
Coordinator per consortium — the only organisation that submits the application and holds the grant contract
|
30
Points available for Relevance — consortium composition and complementarity directly affect this score
|
📋 In This Guide
- What Is an Erasmus+ Consortium
- Eligibility Requirements by Key Action
- Programme Countries vs Partner Countries
- Coordinator vs Partner: Roles and Responsibilities
- What Evaluators Look for in a Consortium
- Required Consortium Documentation
- Most Common Consortium Mistakes
- Consortium Requirements Checklist
1. What Is an Erasmus+ Consortium
An Erasmus+ consortium is the group of organisations that jointly apply for and deliver a project. Every consortium has one coordinator — the organisation that submits the application, holds the grant contract and is legally responsible to the National Agency — and one or more partner organisations that contribute to project delivery under the terms of a partnership agreement.
The consortium is not simply a list of organisations attached to an application. In the eyes of the evaluation, it is the evidence that the right organisations are in the room to deliver the right project for the right target group. Each member of the consortium must have a clearly justified reason for being there — a specific expertise, a target group they bring access to, or a work package they are best placed to lead.
A consortium that exists purely to meet the minimum country requirement — where partners have no genuine contribution to make and no specific role in the work plan — will score poorly on partnership quality regardless of how strong the project idea is.
2. Eligibility Requirements by Key Action
The eligibility requirements for consortium composition vary by Key Action. Failing to meet any of the following criteria results in automatic rejection — these are not evaluation criteria, they are gates. Check every item before submitting.
| Requirement | KA1 Mobility | KA210 Small-Scale | KA220 Cooperation |
|---|---|---|---|
| Minimum organisations | 1 (sending organisation only in some actions; host organisations required for others) | 2 organisations from 2 different programme countries | 3 organisations from 3 different programme countries |
| Country requirement | Applicant must be based in a programme country; host country rules vary by action | All partners must be from Erasmus+ programme countries | All partners must be from Erasmus+ programme countries; partner country organisations may participate in some sectors under specific conditions |
| Eligible organisation types | Any public or private organisation active in education, training or youth in a programme country | Any public or private organisation active in education, training or youth; informal groups of young people eligible in Youth sector | Any public or private organisation with legal personality active in education, training or youth; informal groups not eligible |
| Coordinator eligibility | Must be based in the programme country submitting the application; accredited organisations required for some KA1 actions | Any eligible organisation can coordinate; no accreditation required | Any eligible organisation can coordinate; must demonstrate sufficient administrative and financial capacity |
| Same organisation in multiple roles | Not applicable for single-applicant KA1 actions | An organisation cannot appear as both coordinator and partner in the same application | An organisation cannot appear as both coordinator and partner; each legal entity can appear only once per application |
| Affiliated entities | Allowed in some KA1 actions; check Programme Guide for specific action rules | Affiliated entities may participate but do not count toward the minimum partner requirement | Affiliated entities may participate, receive funding and contribute to activities but do not count toward the minimum 3-partner requirement |
⚠️ Eligibility Is Checked Before Evaluation Begins
Applications that do not meet the minimum consortium requirements are rejected at the admissibility and eligibility check stage — before any evaluator reads the content. A strong project idea cannot compensate for a consortium that does not meet the basic rules. Verify every eligibility criterion before submission, not after.
3. Programme Countries vs Partner Countries
Erasmus+ distinguishes between programme countries — the 33 countries that are full members of the programme — and partner countries, which are neighbouring and other countries that can participate in certain actions under specific conditions.
Programme countries include all 27 EU Member States plus Iceland, Liechtenstein, Norway, North Macedonia, Serbia, and Türkiye. Organisations from programme countries are fully eligible for all Key Actions as coordinators and partners. This is the standard consortium composition for the vast majority of KA210 and KA220 projects.
Partner countries — formerly called neighbourhood countries — include Western Balkans, Eastern Partnership countries, South Mediterranean countries and others. In KA220, organisations from partner countries may participate as partners (not as coordinators) in some sectors, subject to specific conditions set out in the Programme Guide. Their participation must add clear value that cannot be provided by a programme country organisation.
💡 Balkans and SEE Organisations: Check Eligibility Carefully
If you are building a consortium that includes organisations from Western Balkans or South-East Europe, verify their eligibility status against the current Programme Guide for your specific sector and Key Action. Eligibility rules for partner country organisations vary by sector (school education, VET, youth, higher education) and are updated annually. Do not assume eligibility based on previous call rules.
4. Coordinator vs Partner: Roles and Responsibilities
The distinction between coordinator and partner is not just administrative — it reflects a fundamentally different level of responsibility, workload and legal exposure. Both roles must be clearly understood and accepted before the application is submitted.
| Responsibility | Coordinator | Partner |
|---|---|---|
| Application submission | Submits the application in the Beneficiary Module; legally responsible for all content submitted | Provides mandate letter, organisational data and contribution to proposal content; does not submit |
| Grant contract | Signs the grant agreement with the National Agency; is the sole legal counterpart to the NA | Signs a partnership agreement with the coordinator; has no direct contractual relationship with the NA |
| Financial management | Receives the full grant; distributes funds to partners according to the partnership agreement; responsible for financial reporting to the NA | Receives its budget share from the coordinator; maintains its own financial records; reports expenditure to coordinator |
| Reporting | Submits all progress and final reports to the NA; consolidates input from all partners into a single report | Provides activity reports, financial records and output documentation to the coordinator by agreed internal deadlines |
| Legal liability | Legally liable for the proper use of the entire grant, including funds distributed to partners | Liable for its own share of the budget; coordinator bears residual liability for partner non-compliance |
| Project implementation | Leads WP1 (Project Management); coordinates overall timeline, communication and quality assurance | Leads assigned work packages; delivers activities and outputs according to agreed timeline; participates in consortium meetings |
| Required capacity | Must demonstrate sufficient administrative, financial and operational capacity in the application | Must demonstrate capacity to deliver their assigned role; lower threshold than coordinator |
5. What Evaluators Look for in a Consortium
Once eligibility is confirmed, evaluators assess the quality of the consortium as part of the Relevance and Quality of Project Design criteria. They are asking four questions — and your application must answer all four explicitly.
Is the consortium composition justified? For each partner, the application must explain why that organisation is in the consortium — what specific expertise, experience or target group access they bring that is necessary for the project. A partner described only as “an experienced NGO from Country X” is not justified. A partner described as “the leading VET provider in Country X with 15 years of experience training disadvantaged youth and direct access to 300 active learners” is justified.
Is the partnership genuinely complementary? Evaluators look for diversity — of organisation type, sector experience, geographic coverage and methodological approach. A consortium of three youth NGOs with identical profiles from three countries is not complementary. A consortium of a youth NGO, a VET provider and a research institute from three countries — each contributing different expertise — is.
Are roles distributed fairly and logically? Each partner should lead at least one work package and have a budget allocation proportionate to their workload. A partner who only appears as a contributor to meetings — with no WP leadership and a token budget — raises the question of whether they are genuinely needed. Evaluators expect to see a clear, logical connection between each partner’s profile and their assigned responsibilities.
Does the coordinator have the capacity to manage? The coordinator’s profile is scrutinised most carefully. Evaluators look for evidence of previous project management experience, financial management capacity and the administrative infrastructure needed to handle a multi-partner, multi-year grant. A first-time coordinator with no documented project history is a risk that evaluators will note.
6. Required Consortium Documentation
Beyond the application form itself, a consortium must produce and maintain several documents — some required before submission, others before or after grant signature. Missing or late documentation is one of the most common reasons for delays in grant processing.
Mandate letters (required at submission for KA220). Each partner organisation must provide a signed mandate letter authorising the coordinator to submit the application and act on their behalf. The mandate letter is uploaded as part of the application in the Beneficiary Module. Missing mandate letters result in an incomplete application.
Legal entity and financial identification forms. Each partner must be registered in the EU Funding and Tenders Portal (formerly ECAS). Their legal entity form and — for organisations receiving over €60,000 — a financial identification form must be completed and verified before grant signature.
Partnership agreement. Once the project is approved, all partners sign a partnership agreement that sets out roles, responsibilities, budget shares, reporting obligations and procedures for managing changes or partner withdrawal. This is a binding internal document — it is not submitted to the NA but must exist before the first payment is made.
Letters of intent (recommended for KA210 at submission). While KA210 does not require formal mandate letters at application stage in all sectors, a letter of intent from each partner — confirming their commitment to participate — strengthens the application and protects you if a partner withdraws before the project starts.
7. Most Common Consortium Mistakes
Partners added to meet the country minimum rather than the project need. Recruiting a partner from a required country without a genuine project role produces a weak consortium. Evaluators read the partner profiles and the work plan together — if the connection between a partner’s profile and their assigned activities is thin, the partnership quality score suffers.
Coordinator without sufficient management capacity. A small NGO coordinating a €300,000 KA220 project for the first time — with no previous grant management experience, no finance officer and one part-time project manager — is a risk profile that evaluators will flag. The coordinator profile must demonstrate the capacity to manage the full grant, not just deliver activities.
All partners from the same sector with identical profiles. A consortium of five youth NGOs with no diversity in organisation type, methodology or target group access does not demonstrate complementarity. Build in variety — at minimum, different organisation types (NGO, educational institution, research body, public authority) across the partnership.
Partner profiles described generically in the application. Describing a partner as “an active organisation in the field of education with relevant experience” is not a partner justification — it is a placeholder. Every partner profile must include the organisation’s specific expertise, its role in this project, and why it is the right organisation for that role.
Missing or late mandate letters. In KA220, the application is incomplete without signed mandate letters from all partners. Chasing partners for signatures in the final days before a deadline — or discovering a partner has not signed — is a preventable crisis. Set an internal deadline for mandate letters at least two weeks before the submission deadline.
Budget shares not discussed with partners before submission. Partners who discover their budget allocation after the application is submitted — and disagree with it — create serious problems during implementation. Discuss and agree budget shares with every partner before the application is finalised. Document the agreement in writing.
8. Consortium Requirements Checklist
- ✅ Minimum partner numbers confirmed: 2 organisations for KA210, 3 for KA220
- ✅ All partners based in Erasmus+ programme countries — or partner country eligibility verified against current Programme Guide
- ✅ Each partner organisation has a distinct, justified role in the project
- ✅ No two partners with identical profiles — complementarity demonstrated across the consortium
- ✅ Each partner leads at least one work package or activity with a specific deliverable
- ✅ Coordinator has documented project management and financial capacity
- ✅ Partner profiles described specifically in the application — not generically
- ✅ Budget shares discussed and agreed with all partners before submission
- ✅ Mandate letters (KA220) or letters of intent (KA210) collected from all partners
- ✅ Internal mandate letter deadline set at least 2 weeks before submission deadline
- ✅ All partners registered in EU Funding and Tenders Portal
- ✅ Partnership agreement process initiated — roles, responsibilities and budget shares documented
🏛️ Need Help Building Your Erasmus+ Consortium?
GrowthProjects.eu supports organisations with consortium design, partner matching and proposal development for KA210 and KA220 — ensuring your partnership is eligible, complementary and evaluation-ready from day one.
✅ Not Sure If You Qualify for Erasmus+?
Check your eligibility for free in 2 minutes — no sign-up required.


