If you have ever opened a grant application call from the EU, USAID, or the United Nations, you have almost certainly seen the line: “Please attach a Logical Framework Matrix (Logframe).” Many first-time applicants close the document at this point. In reality, the Logframe is not a bureaucratic formality – it is a planning tool that forces clear thinking: what you are doing, why, how you will measure success, and what external conditions need to hold. This guide explains the Logframe from scratch, with a complete filled example and an Excel template to download.
| Difficulty levelBeginner | Reading time~15 minutes | Suitable forNGOs, universities, businesses | What’s insideTheory + example + Excel template |
Find the grant that needs this Logframe
GetGrant updates its database of active grant competitions for NGOs, universities, and businesses daily – with AI-powered matching to your profile.
What the Logical Framework Matrix is and why it matters
The Logical Framework Matrix (Logframe, LFM) is a planning table that describes the complete logic of a project: what you do, why, how you will measure success, and what external conditions need to hold. USAID developed the tool in 1969, and it has since become the standard for most major international donors. Today the Logframe sits at the core of EU Project Cycle Management (PCM) methodology, recommended by the European Commission for all grant-funded projects.
A Logframe is required by EU programmes (Horizon Europe, Erasmus+, CERV, Creative Europe), USAID and its implementing partners (IREX, Pact, DAI), UN agencies (UNDP, UNICEF, UNHCR), bilateral donors (Sweden, Norway, Netherlands), the World Bank, and the EBRD. Even when donors do not require it explicitly, the Logframe often underpins the Methodology, Work Plan, and Performance Indicators sections.
The Logframe is useful even when donors do not require it. Building one forces you to answer questions that are easy to skip: is there a genuine cause-and-effect relationship between what you do and the result you expect? Can you realistically measure that result? What could go wrong? According to World Bank analysis, 80% of failed projects suffered from unclear objectives, missing indicators, incorrect assumptions, and unrealistic budgets – exactly the problems the Logframe surfaces at the planning stage.
Five stages before the matrix: what to do before opening the template
One frequently overlooked point: the Logframe is the conclusion of an analytical process, not its starting point. Before filling in the matrix, EU methodology provides for five preparatory stages.
Stage 1. Stakeholder analysis
Identify everyone who influences the problem or is affected by it: target groups (those at whom project activities are directly aimed), final beneficiaries (those who will benefit long-term), partners, authorities, and the donor. This shapes the project team and partnership arrangements.
Stage 2. Problem analysis – the problem tree
State the central problem as a negative assertion. Around it, place causes (levels below) and consequences (levels above). The cause-and-effect relationships between problems form the “tree”. This analysis provides the rationale for the entire project plan.
Stage 3. Objectives analysis – the objective tree
Restate every negative assertion from the problem tree as a positive one: the central problem becomes the Specific Objective; consequences become the Overall Objective; first-level causes become Outputs; second- and third-level causes become Activities. The objective tree is a positive mirror image of the problem tree.
Stage 4. Project strategy selection
The objective tree consists of several “branches” – alternative strategies. Select the one that best fits donor priorities, is realistic within your budget and timeframe, and matches your organisation’s experience. Remove branches that do not meet these criteria.
Stage 5. Building the Logframe
Only after the four preceding stages do you transfer the chosen strategy into the matrix table. Data from the objective tree fills the Intervention Logic column. Assumptions, indicators, and sources of verification are then added in the specific order described below.
The matrix structure: 4 rows and 4 columns
The four project levels (rows)
| Level | What it describes | Key question |
|---|---|---|
| Overall Objective (Goal) | The broad social change the project contributes to. Your project is one of many factors, not the sole cause. | What large-scale problem are we helping to solve? |
| Specific Objective (Purpose) | The concrete change the project creates directly. This is what you are accountable to the donor for. | What specific change will we create in the target group? |
| Outputs (Results) | Concrete products and services the team delivers. Fully within your control. | What specifically will we deliver? |
| Activities | Concrete tasks the team carries out to produce the outputs. The basis of the work plan. | What exactly will we do? |
The four columns – with a critical exception for the Activities row
The matrix has four columns. But the Activities row is filled differently from the three rows above it – this is one of the most common errors even among experienced applicants.
| Level | Column 1 Intervention Logic |
Column 2 | Column 3 | Column 4 |
|---|---|---|---|---|
| Overall Objective | Description | Indicators (SMART) | Sources of Verification | NOT FILLED |
| Specific Objective | Description | Indicators (SMART) | Sources of Verification | Assumptions |
| Outputs | Description | Indicators (SMART) | Sources of Verification | Assumptions |
| Activities | List of activities | MEANS (Resources) |
COSTS (Budget) |
PRE-CONDITIONS |
Column 2 – Means: human resources (staff, trainers, consultants), materials, equipment, services, transport – everything needed to carry out the activities.
Column 3 – Costs: total budget and breakdown by cost category.
Column 4 – Pre-conditions: external conditions that must be met BEFORE the project starts (not during implementation). Example: “Cooperation agreements signed with partner institutions”.
Overall Objective row: the Assumptions column is left empty – assumptions are not defined at this level.
The two logics of the matrix: vertical and horizontal
Vertical logic – read bottom-up
This is the cause-and-effect chain between levels:
IF Pre-conditions are met → the project can begin Activities
IF Activities are carried out → Outputs are produced
IF Outputs are delivered + Assumptions hold → the Specific Objective is achieved
IF Specific Objective is achieved + Assumptions hold → contribution to the Overall Objective
Check: read the chain upwards. If any IF–THEN link feels uncertain, either an output is missing or the specific objective is framed incorrectly.
Horizontal logic – read left to right (for each level separately)
Intervention Logic → what we claim we will achieve or deliver
Indicators → what that looks like in measurable terms (SMART)
Sources of Verification → where the evidence that the indicator is met comes from
Assumptions → what must be true at this level for the transition to the next level to happen
Check: can you realistically collect data from the sources you listed, within your project budget? If not, revise the indicator or identify existing external data sources.
The filling algorithm: 15 cells in the right order
EU methodology recommends a specific order for filling the cells – numbered 1 to 15 in the standard matrix template. The sequence prevents the most common logical errors.
Cells 1–4: Fill the Intervention Logic column top-to-bottom
First formulate the Overall Objective, then the Specific Objective, then Outputs, then Activities. All data comes from the chosen objective tree. Number activities by reference to their parent output: 1.1, 1.2 → Output 1; 2.1, 2.2 → Output 2. This numbering carries through every project document.
Cell 5: Pre-conditions for the Activities row
Identify external conditions that must be in place before project activities can begin. Examples: “Land ownership confirmed before construction starts”, “Cooperation agreements signed with partners”, “Import permits for equipment obtained”. If a pre-condition seems too risky – convert it into a project activity.
Cells 6–7: Assumptions for Outputs and Specific Objective (bottom-up)
First fill assumptions for the Outputs row (conditions needed to obtain results on schedule), then for the Specific Objective row (conditions beyond project management’s control but necessary for the objectives to be met). The Overall Objective row – left empty. State assumptions positively (“Partners provide premises on time”) and risks negatively (“Customs delays may affect the equipment delivery schedule”).
Cells 8–13: Indicators and Sources of Verification (top-down)
Overall Objective (cells 8–9): indicators typically come from external statistics; sources are official data outside the project. For the Specific Objective (10–11): indicators of change in the target group; sources include both external and internal data. For Outputs (12–13): specific quantitative indicators per output; sources are primarily internal project documentation. Each indicator must be SMART: Specific, Measurable, Achievable, Relevant, Time-bound.
Cells 14–15: Means and Costs for the Activities row
Means (14): list all required resources – human (staff, trainers, consultants), material (equipment, consumables), and services. Costs (15): total budget and breakdown by cost category. Fill these cells last – only after completing the project budget. Full alignment between the budget document and cells 14–15 is mandatory.
Filled Logframe example: a digital literacy project
Below is a complete Logframe for a hypothetical project “Digital Literacy for Adults in Communities”. Pay particular attention to: the Overall Objective row – Assumptions column is not filled; the Activities row – instead of Indicators and Sources, it contains Means and Costs, and the fourth column shows Pre-conditions instead of regular Assumptions.
| Level | Intervention Logic | Indicators / Means | Sources / Costs | Assumptions / Pre-conditions |
|---|---|---|---|---|
| OVERALL OBJECTIVE | Increased digital inclusion of adults in 5 communities of Lviv and Ivano-Frankivsk oblasts by end of 2027. | By 31.12.2027: share of adults regularly (≥1×/week) using online government services rises from 23% to 55% (survey, n=500). | SSSU data; representative survey pre and post project; Ministry of Digital Transformation reports. | NOT FILLED |
| SPECIFIC OBJECTIVE | Adult residents of target communities independently use digital government services (Diia, e-health) in daily life. | By 30.11.2027: 80% of course participants score ≥70/100 in final test; 70% use Diia at least once a month. | Pre/post-test data; Diia registration data; focus group minutes (4 sessions). | ASSUMPTIONS: Participants have access to a device and Internet after training. Government services do not undergo radical interface changes. |
| OUTPUTS | O.1: 200 adults complete course (40 hrs) O.2: 5 digital learning centres equipped O.3: Materials adapted for people aged 50+ |
O.1: 200 certificates by 31.10.2027 O.2: 5 centres open by 30.06.2027, each ≥10 PCs O.3: 3 modules validated by 31.03.2027 |
Attendance registers; equipment handover certificates; certificate scans. | ASSUMPTIONS: Partner institutions support centres after project completion. Trained trainers remain in the community. |
| ACTIVITIES | 1.1 Develop curriculum 1.2 Train 10 trainers 1.3 Run 10 sessions (20 each) 2.1 Purchase and install equipment 2.2 Sign partner agreements 3.1 Develop adapted materials |
MEANS: Staff: 1 PM, 10 trainers, 3 consultants Equipment: 50 PCs, Wi-Fi Materials: 200 training booklet sets Services: translation, transport |
COSTS: Total: USD 180,000 Personnel – 35% Equipment – 30% Training – 25% Admin – 10% |
PRE-CONDITIONS: Agreements with 5 partners signed before project start. Training premises confirmed. Equipment import permits obtained. |
Download the Logframe template (Excel)
4 sheets: blank template and filled example in Ukrainian and English. Correct Activities row structure (Means + Costs + Pre-conditions).
7 common mistakes in a Logframe
1. Specific Objective = Output
“10 trainings delivered” is an output, not an objective. The specific objective describes the change in people or systems that your outputs cause. Ask: “What will change in our beneficiaries once all outputs are delivered?” – that is your specific objective.
2. Indicators without numbers or dates
“Improved participant knowledge” is not an indicator. “80% of participants score ≥70/100 in the final test by 31 October 2027” is an indicator. Every indicator must contain: what you measure + a number or percentage + a deadline.
3. Activities row filled like the three rows above it
The most common technical error, even among experienced applicants. In the Activities row, columns 2 and 3 contain Means and Costs – not indicators and sources of verification. Column 4 contains Pre-conditions, not regular ongoing assumptions.
4. Assumptions filled in for the Overall Objective
Per EU PCM methodology, the Assumptions column in the Overall Objective row is not filled in. Leave it empty or mark it “not applicable”.
5. Sources of verification that are unrealistic to collect
If verifying an Overall Objective indicator requires a $50,000 survey and the total budget is $80,000, something has to change. Either budget the data collection into the project, or use existing external data (official statistics, partner research).
6. Assumptions that are trivial or catastrophic
“The sun rises” is not an assumption. “All partners go bankrupt” is not an assumption – it is a reason not to run the project. Assumptions should reflect real external risks of moderate probability that you monitor but do not fully control. If a risk is too large, convert it into a pre-condition or output.
7. Activities not numbered relative to their outputs
All activities must carry numbering linked to their parent output: 1.1, 1.2 → Output 1; 2.1, 2.2 → Output 2. This numbering runs through every project document – application, budget, and reports. Without it, the connection between Outputs and Activities becomes impossible to track.
For advanced readers: Output, Outcome, Impact, and Theory of Change
These terms appear frequently in EU and USAID documentation and map directly onto Logframe levels:
| Term | Logframe equivalent | Example |
|---|---|---|
| Output | Output / Result | 200 people complete the training and receive a certificate. |
| Outcome | Specific Objective | Training participants independently use digital services. |
| Impact | Overall Objective | The region’s overall digital inclusion level increases. |
Theory of Change (ToC) is an expanded version of the Logframe’s vertical logic. Where the Logframe shows what will happen, the ToC explains why: through which mechanisms, in what context, under what conditions. Some donors request a ToC as a separate document. Your Logframe is its foundation – expand it into flowing prose that explains the causal mechanisms at each level.
Baseline data: an indicator reading “from 23% to 55%” is convincing only when you have the starting-point data. If you do not have a baseline, either build a baseline study into the start of the project and budget for it, or use existing external data. Applications with a substantiated baseline consistently score higher in evaluation.
Find the grant – put this Logframe to use
GetGrant updates its database of grant competitions every day. AI-powered matching selects the right opportunities for your profile.