About this guide
If you have ever stared at a logframe matrix unsure where to start, this guide explains why — and walks you through the cause-and-effect logic that makes a project structure actually hold together.
Turning a project idea into a structured, donor-ready proposal is where most NGOs struggle. The logical framework approach (LFA) helps you organise your project into a clear results chain — from what you do to what actually changes. It is widely used in EU and international funding because it allows evaluators to quickly assess whether your project is logical, measurable, and realistic.
But understanding LFA is not the same as applying it. Many teams can explain activities, outputs, and outcomes — yet still end up with logframes that are unclear, inconsistent, or difficult to evaluate. This guide shows how the logical framework approach works in practice, and how to use it to build a structured, fundable project.
What Is the Logical Framework Approach?
The logical framework approach is a structured method for designing projects by clearly linking what you do to the results you want to achieve. Instead of describing a project in narrative form, LFA organises it into a cause-and-effect chain — showing how activities lead to measurable change.
In practice, LFA is presented as a logframe matrix, which breaks a project into four levels:
- Activities — the actions you carry out
- Outputs — the direct results produced
- Outcome — the change created by those results
- Goal (Impact) — the long-term effect the project contributes to
These are supported by:
- Indicators — how results are measured
- Means of verification — where the data comes from
- Assumptions — external factors that affect success
Together, this structure forms a complete model of how your project works — from implementation to impact.
Key insight: A logframe is only as strong as the logic behind it — not the format.
Why the Logical Framework Approach Exists
The logical framework approach was developed to solve a very specific problem in project design: projects were being approved without a clear link between what was done and what actually changed. Proposals described activities in detail but failed to demonstrate how those activities would lead to measurable results. This made projects difficult to evaluate, compare, and monitor.
LFA addresses this by forcing a different question. Instead of asking "What will we do?" it asks "What will change — and how do we prove it?"
This shift is critical in EU and international funding, where proposals are assessed on:
- Clarity of outcomes
- Logical connection between activities and results
- Measurability through indicators
- Feasibility under real-world conditions
A well-structured logframe lets evaluators understand all of this quickly. A weak one raises questions immediately — even if the project idea itself is strong.
The Real Challenge: Building a Consistent Results Chain
In practice, the difficulty is not filling in a logframe matrix. It is building a consistent results chain where every part connects:
- Activities directly support outputs
- Outputs combine to produce an outcome
- Outcomes reflect real, measurable change
When this structure is built correctly, the logframe becomes clear and easy to evaluate. When it is not, problems appear immediately:
- Outputs that do not lead to outcomes
- Indicators that measure activity instead of change
- Assumptions that are generic or disconnected
These are structural gaps — and one of the main reasons proposals lose credibility during evaluation.
Key insight: The template does not fix the structure. It exposes it.
How the Logical Framework Approach Works (The Results Chain)
At the core of LFA is a simple idea: a project should be designed as a chain of cause-and-effect relationships where each level leads logically to the next. This is the results chain.
Activities — What You Do
These are the specific actions carried out during the project. Examples:
- Conduct field assessments
- Deliver training sessions
- Implement restoration activities
Activities are fully within your control — but they do not represent success on their own.
Outputs — What You Produce
Outputs are the direct, tangible results of your activities. Examples:
- Number of people trained
- Hectares restored
- Workshops completed
Outputs describe what the project delivers — not what it changes.
Outcome — What Changes
The outcome reflects the actual change created by your project. Examples:
- Farmers adopt improved practices
- Coastal erosion is reduced
- Communities apply new knowledge
This is where many projects become weak. Outcomes must reflect real change — not just completed activities.
Goal (Impact) — What It Contributes To
The goal is the broader, long-term impact your project supports. Examples:
- Increased climate resilience
- Improved ecosystem health
- Sustainable livelihoods
The project contributes to this level but does not fully control it.
Why the Results Chain Matters
The logical framework approach is not about listing these levels. It is about ensuring they connect logically. Each level depends on the one before it:
- If activities are poorly designed → outputs will be weak
- If outputs are unclear → outcomes will not be achieved
- If outcomes are vague → impact cannot be justified
Logframe Example (Environmental NGO)
To understand how the logical framework approach works in practice, here is a real project structured into a clear results chain.
Project context: A small environmental NGO is addressing coastal degradation in three villages, where mangrove loss has increased erosion and reduced natural protection against storms.
| Level | Narrative | Indicators | Means of Verification |
|---|---|---|---|
| Goal | Increased climate resilience of coastal communities | % reduction in storm-related damage over 5 years | Climate risk reports; government data |
| Outcome | Reduced coastal erosion and improved shoreline stability in 3 villages | % reduction in shoreline erosion after 12 months | Satellite imagery and GIS mapping |
| Output 1 | 50 hectares of mangroves restored | Survival rate of mangrove seedlings after 12 months | Field monitoring reports |
| Output 2 | 120 community members trained in restoration techniques | % of trained participants applying techniques 6 months later | Training records; follow-up surveys |
| Activities | Site assessments; community nurseries; planting campaigns; training workshops | Activities completed on schedule | Project progress reports |
Why This Logframe Works
- Activities directly produce defined outputs
- Outputs lead to a measurable outcome
- The outcome contributes to a broader goal
- Indicators focus on results, not activity completion
- Assumptions are realistic and linked to actual risks
Common Mistakes When Applying the Logical Framework Approach
Even when NGOs understand LFA, many proposals still fall short. These are not formatting issues — they are problems in how the logic is built.
1. Confusing Outputs with Outcomes
One of the most common mistakes is treating delivered activities as results:
- Output: 100 farmers trained
- Outcome: Farmers adopt improved agricultural practices
Outputs describe what the project produces. Outcomes describe what actually changes.
2. Indicators That Do Not Measure Real Change
Indicators are often written based on what is easy to track rather than what matters. Common issues:
- Counting participation instead of behavioural change
- Measuring delivery instead of results
- Using vague terms like "increased awareness"
3. Weak Links Between Levels
Activities, outputs, and outcomes are listed but not clearly connected. When these links are weak, the results chain breaks down — even if the template appears complete.
4. Generic or Irrelevant Assumptions
Assumptions are sometimes included as standard statements rather than real conditions:
- "Political stability remains unchanged"
- "Stakeholders remain engaged"
When assumptions are not clearly linked to risks or outcomes, they reduce credibility without adding value.
Key insight: Most weak logframes are not incomplete. They are misaligned.
How to Apply the Logical Framework Approach (Step-by-Step)
Strong logframes are not built by filling in a template from top to bottom. They are built by following a clear sequence where each element is defined in relation to the others.
Step 1: Start With the Outcome
Define the change your project is intended to create. This should reflect a real shift in behaviour, systems, or conditions — not just completed activities. A clear outcome anchors the entire structure.
Step 2: Define Outputs That Lead to That Outcome
Identify the results required to achieve your outcome. Each output should have a direct and necessary contribution to the change you defined. If an output does not clearly support the outcome, it weakens the structure.
Step 3: Define Activities That Produce Those Outputs
Only after outputs are clear should activities be defined. This ensures each activity has a clear purpose and is directly linked to results. When activities are defined too early, the structure becomes activity-driven instead of results-driven.
Step 4: Add Indicators That Measure Change
Indicators should reflect the outcome and key outputs — not just activity completion. They must capture observable, measurable change aligned with M&E requirements.
Step 5: Define Means of Verification
Specify where your data will come from: monitoring systems, reports, surveys. This ensures results are credible and verifiable.
Step 6: Identify Assumptions
Define the external conditions that influence success. These should be realistic and directly related to your outcome and outputs.
Frequently Asked Questions
What is the logical framework approach? The logical framework approach (LFA) is a structured method for designing projects by linking activities to outputs, outcomes, and impact through a clear cause-and-effect chain. It is widely used in EU and international development funding.
What is the difference between LFA and a logframe? The logical framework approach is the methodology — the thinking process for designing a coherent project. A logframe (logical framework matrix) is the output of that process — the structured table presenting the results chain with indicators, verification methods, and assumptions.
Why do NGOs use the logical framework approach? Because funders require it. EU programmes, bilateral donors, and major foundations all expect proposals to demonstrate a clear link between what is done and what changes. LFA provides the structure to show that link systematically.
What are the four levels of the logical framework approach? Activities (what the project does), Outputs (direct results produced), Outcome (change created by outputs), and Goal/Impact (long-term contribution). Each level must logically lead to the next — this is the results chain.
Is the logical framework approach the same as a theory of change? No — but they are closely related. A theory of change explains the causal logic and assumptions behind it. A logframe operationalises that logic into a measurable structure with indicators and verification methods.
Related pages: Logframe template · How to write a logframe · Logframe example · Logframe indicators · Theory of change template
NGO Toolkit Lab
Generate your logframe