The logical framework — often called the logframe — is one of the most useful tools in EU project design, and one of the most misunderstood by Erasmus+ applicants. It isn’t a section of the KA210 or KA220 application form itself, and Erasmus+ doesn’t require you to submit one. But the logic it forces you to work through — how activities lead to outputs, how outputs lead to real change — is exactly what evaluators are checking for when they score your Relevance and Quality of Project Design sections.
Applicants who skip this thinking, or treat it as a simple summary of activities, tend to submit proposals where the logic doesn’t hold together — and that costs points, even when the individual sections read well in isolation. This guide explains what a logframe is, why it’s worth building even though nobody asks for it, and how to use it to plan a stronger Erasmus+ KA210 or KA220 application.
|
25–30
Points available for Relevance (25 for KA220, 30 for KA210) — the criterion your logic most directly supports
|
4
Levels a well-structured project logic should address
|
4
Columns in a complete logframe matrix
|
85+
Score typically needed to be competitive in a funding round — a clear project logic helps get there
|
📋 In This Guide
1. What Is the Logical Framework — and Why Erasmus+ Doesn’t Ask For One
The logical framework is a structured matrix that maps the logic of your project in a single table. It shows how your project’s activities lead to outputs, how outputs lead to outcomes, and how outcomes contribute to the overall goal — and what evidence you will use to prove it happened.
To be clear: the KA210 and KA220 e-forms do not have a “logical framework” section, and you will not submit a logframe matrix as part of your application. But the logic it represents runs through the entire form regardless — in Context & Rationale, Objectives, Work Plan, and Impact. When evaluators score Relevance and Quality of Project Design, they are essentially checking whether that underlying logic holds up, whether or not you ever wrote it down as a formal matrix. Organisations that build a logframe first, purely as an internal planning document, consistently produce more coherent proposals — because it forces the “if this, then that” thinking before you start writing prose.
💡 How to Use This
Build your logframe before you start writing the application form sections. Use it as your internal planning document — then let it guide what you write in Context & Rationale, Objectives, Work Plan, and Impact sections. Nobody at the National Agency will ever see the matrix itself; what they’ll see is a proposal where everything connects.
2. The Four Levels of the Logframe
A logframe is read from bottom to top — activities are at the bottom and the overall goal is at the top. Each level feeds into the one above it. Think of it as an “if-then” chain: if we carry out these activities, then we will produce these outputs; if we produce these outputs, then we will achieve this outcome.
| Level | Erasmus+ Term | What It Means | Example |
|---|---|---|---|
| Level 1 (top) | Overall Goal / Impact | The long-term societal change your project contributes to. Your project alone cannot achieve this — it contributes to it. | Improved digital inclusion of youth across Europe |
| Level 2 | Specific Objective / Outcome | The change your project directly achieves by the end of the project period. This is what you are accountable for. | Youth workers in 3 countries have improved digital facilitation competencies |
| Level 3 | Outputs / Results | The concrete deliverables your project produces — training programmes, toolkits, reports, events, platforms. | 1 digital competence training programme; 1 open-access toolkit; 3 transnational workshops |
| Level 4 (bottom) | Activities | The specific tasks your consortium carries out to produce the outputs. These map directly to your work plan and budget. | Needs assessment; curriculum development; pilot training; evaluation; dissemination events |
3. The Four Columns: What Goes in Each One
Each row in the logframe matrix has four columns. Together they answer the same question at every level: what will change, how will we measure it, how will we prove it, and what do we assume?
| Column | What to Write | Common Mistake |
|---|---|---|
| Narrative Summary | A concise description of the goal, outcome, output or activity at each level | Writing vague statements like “improve skills” instead of naming who benefits and what specifically changes |
| Indicators (OVIs) | Measurable, specific signals that prove each level has been achieved — include quantity, quality, target group and timeframe | Using unmeasurable indicators like “participants will be satisfied” — evaluators cannot verify this |
| Means of Verification | The data sources or documents that will prove your indicators have been met — surveys, reports, attendance lists, published outputs | Listing generic sources like “project reports” without specifying what data they will contain |
| Assumptions | External conditions outside your control that must hold true for your project logic to work — be honest and specific | Writing blanket disclaimers like “political stability” — name the specific assumptions relevant to your project context |
4. Ready-to-Use Logframe Template with Example
Below is a complete logframe example for a fictional KA220 project on digital competence for youth workers. Use it as a structural template — replace the content with your own project details, keeping the same logic and format.
| Level | Narrative Summary | Indicators (OVIs) | Means of Verification | Assumptions |
|---|---|---|---|---|
| Overall Goal | Improved digital inclusion and participation of young people across partner countries | Increase in digital literacy rates in target regions (Eurostat Digital Economy Index, 3 years post-project) | Eurostat reports; national digital strategy reviews | EU digital policy priorities remain stable; demand for digital youth work continues to grow |
| Specific Objective | Youth workers in Greece, Portugal and Poland demonstrate measurably improved digital facilitation competencies by project end | 80% of 60 trained youth workers score ≥70% on post-training competency assessment; 3 organisations formally adopt new digital methods | Pre/post competency assessments; partner self-evaluation reports; institutional adoption declarations | Youth workers are able to participate in transnational training; partner organisations maintain commitment throughout project |
| Output 1 | 1 validated digital competence training programme for youth workers (open access, available in 3 languages) | Programme published by Month 18; minimum 200 downloads in first 6 months post-publication | Programme hosted on project website; download analytics report | Translation quality is maintained; target users have internet access |
| Output 2 | 3 transnational pilot workshops delivered (1 per country), training 60 youth workers | 3 workshops completed by Month 22; minimum 20 participants per workshop; ≥80% satisfaction rate | Attendance lists; post-workshop satisfaction surveys; workshop reports | Venue availability; participant travel is feasible; no major public health restrictions |
| Activities | 1.1 Needs assessment survey · 1.2 Curriculum design · 1.3 Peer review · 1.4 Translation · 2.1 Workshop planning · 2.2 Pilot delivery · 2.3 Evaluation | All activities completed within timeline; budget spent as planned | Progress reports; financial statements; meeting minutes | Partners have sufficient staff capacity; key personnel do not leave during project |
✅ Want This Done For You?
Working through this logic for your specific project — and turning it into a full proposal — is exactly what our Proposal Development service covers, from €795 depending on your Key Action.
5. The Most Common Logframe Mistakes
These are the errors that show up most often in proposals that lose significant points on Relevance and Quality of Project Design.
Confusing outputs with outcomes. An output is something you produce — a training module, a report, a platform. An outcome is a change that results from that output — improved skills, changed behaviour, new institutional practice. Many applicants describe outputs when evaluators are looking for outcomes at the Specific Objective level.
Unmeasurable indicators. “Participants will have better skills” is not an indicator. A strong indicator names a quantity, a quality standard, a target group and a timeframe: “80% of 60 participants score ≥70% on the post-training assessment by Month 22.”
Activities that don’t connect to outputs. Every activity must produce something. If you cannot identify which output an activity contributes to, either the activity is unnecessary or you are missing an output.
Generic assumptions. Writing “political stability” or “partner commitment” as assumptions without any project-specific context signals to evaluators that the logic was filled in quickly, not thought through carefully.
Logframe and work plan don’t match. Evaluators cross-check the logic and language of your Objectives and Impact sections against your actual work plan and budget. Inconsistencies — an activity described in one section but not appearing in the budget, or vice versa — are a fast way to lose points.
6. Practical Tips for Scoring Higher
Write the logframe before the application form. Use it as your planning blueprint. Every section of the form — Context, Objectives, Work Plan, Impact — should reflect the logic you have established in the logframe.
Use the “if-then” test. Read your logframe bottom to top: if we carry out these activities, then we will produce these outputs; if we produce these outputs, then we will achieve this outcome. If any link in that chain feels weak, fix it before writing the form.
Keep indicators SMART. Specific, Measurable, Achievable, Relevant and Time-bound. Aim for 1–2 strong indicators per level rather than a long list of weak ones.
Cross-check against the budget. Every activity in the logframe must have a corresponding budget line. Run this check before submitting — it is one of the fastest ways to catch inconsistencies that cost points.
Align your Overall Goal with an EU priority. The goal level of your logframe is where you connect your project to the broader Erasmus+ programme priorities — inclusion and diversity, environment and the fight against climate change, digital transformation, or participation in democratic life. Name the priority explicitly rather than paraphrasing it.
Need Help Structuring Your Erasmus+ Project?
GrowthProjects.eu can build your project logic, structure your concept, and develop your full proposal — for a growing number of funded projects across Europe.
✅ Not Sure If You Qualify?
Check your Erasmus+ eligibility for free — takes 2 minutes, no sign-up required.