About this guide
Seeing a finished logframe is useful. Understanding why it works is what actually helps you build one. This guide breaks down a real example at the level where most proposals go wrong.
Most NGOs do not struggle with completing a logframe. They struggle with understanding what a strong logframe actually looks like.
Two projects can follow the same structure. One is clear, measurable, and easy to evaluate. The other is inconsistent, difficult to assess, and raises questions immediately. The format is identical. The difference is in the structure.
A logframe example exposes this. It shows whether:
- Outputs actually lead to outcomes
- Outcomes reflect real, measurable change
- Indicators capture results instead of activity
- Assumptions reflect real conditions
This is what evaluators assess — not whether the template is filled, but whether the logic holds together.
Most issues are not visible while building the logframe. They become visible when the full structure is reviewed. Outputs that do not lead to outcomes, indicators that measure delivery instead of change, assumptions that are generic or disconnected — these are structural gaps, not formatting issues. A completed logframe can still fail under evaluation for this reason.
This page shows what a logframe looks like when the structure is aligned — and where most attempts break down.
Simple Logframe Example (Structure Only)
Before looking at a complete example, it is useful to isolate the structure.
| Level | Narrative |
|---|---|
| Goal | Improved climate resilience of coastal communities |
| Outcome | Reduced coastal erosion in target villages |
| Outputs | Mangroves restored and communities trained |
| Activities | Conduct restoration activities and training sessions |
This reflects the standard results chain: Activities → Outputs → Outcome → Goal.
At a glance, the structure is correct. But this is where most logframes become misleading. Each level is present. The relationships are not clearly defined:
- Outputs are not quantified
- The outcome is not measurable
- Indicators are not specified
- Assumptions are missing
The structure appears complete. The logic is not. This is the point where many logframes pass internal review — but fail under evaluation.
Key insight: A logframe is not assessed based on whether levels exist. It is assessed based on whether those levels connect.
Full Logframe Example (Environmental NGO)
To understand how a strong logframe works, the structure must be viewed as a complete 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 | Assumptions |
|---|---|---|---|---|
| Goal | Increased climate resilience of coastal communities in the target region | % reduction in storm-related damage over 5 years | Climate risk assessments; government vulnerability data | Climate patterns remain within historical range |
| Outcome | Reduced coastal erosion and improved shoreline stability in 3 villages | % reduction in shoreline erosion after 12 months | Satellite imagery and GIS mapping | No extreme weather events disrupting restoration during project period |
| Output 1 | 50 hectares of mangroves restored | Survival rate of mangrove seedlings after 12 months; hectares confirmed restored | Field monitoring reports; aerial photography | Seedling availability and appropriate planting conditions |
| Output 2 | 120 community members trained in restoration techniques | % of trained participants applying techniques 6 months after training | Training records; follow-up surveys | Continued participation from local communities |
| Activities | Conduct site assessments; establish community nurseries; implement planting campaigns; deliver training workshops | Activities completed on schedule and within budget | Project progress reports | Support from local authorities; no land tenure disputes |
How the Structure Connects
Each level leads clearly to the next:
- Activities produce defined outputs
- Outputs combine to create a measurable outcome
- The outcome contributes to a broader goal
There are no gaps between what is done and what changes as a result.
Each level has a distinct role:
- Activities define implementation — what will be done
- Outputs define delivery — what the project produces
- Outcome defines change — what improves because of the outputs
- Goal defines long-term contribution — what the project helps achieve
When these distinctions are clear, the structure becomes easy to assess.
Indicators (Measuring Change)
Each level is supported by indicators that reflect observable results:
- Percentage reduction in shoreline erosion after 12 months
- Survival rate of mangrove seedlings after one year
- Percentage of trained participants applying restoration techniques
These indicators measure change — not activity. See logframe indicators explained for how to write strong indicators at each level.
Means of Verification (Proving Results)
Each indicator is linked to a defined data source:
- Satellite imagery and GIS mapping
- Field monitoring reports
- Training records and follow-up surveys
This allows results to be verified, not assumed.
Assumptions (Recognising External Factors)
A realistic logframe identifies external conditions that influence success:
- No extreme weather events disrupting restoration
- Continued participation from local communities
- Support from local authorities
These assumptions reflect real conditions, not ideal scenarios.
Key insight: A strong logframe is not just structured. It is logically consistent, measurable, and grounded in real conditions. All of these are visible at a glance.
Why This Logframe Works (Evaluator Perspective)
A logframe is not assessed section by section. It is assessed as a complete structure. What matters is not whether each part is filled — but whether the relationships between them are clear and consistent.
Clear Results Chain
The progression from activities to impact is easy to follow:
- Activities lead directly to defined outputs
- Outputs contribute to a specific outcome
- The outcome reflects measurable change
There are no gaps between levels. Each step depends on the one before it.
Outcome Reflects Change, Not Delivery
The outcome defines what changes: Reduced coastal erosion and improved shoreline stability. It does not describe what was done. This distinction is critical. Outputs describe delivery. Outcomes describe results.
Indicators Measure What Matters
The indicators are aligned with the outcome:
- Environmental change (erosion reduction)
- Sustainability (seedling survival)
- Behaviour change (application of techniques)
They measure results, not activity.
Verification Is Defined
Each indicator is supported by a specific data source. This allows evaluators to determine whether results can be measured and whether results can be verified. Without this, the structure loses credibility.
Assumptions Reflect Real Conditions
The assumptions are directly linked to the project context. They identify external factors that affect success. This shows that the structure is grounded in real conditions — not ideal scenarios.
Weak vs Strong Logframe (What Actually Gets Funded)
Two logframes can follow the same structure and still lead to very different evaluations. The difference becomes visible when the logic is examined.
Outcome
- Weak: Improve community resilience
- Strong: Reduced coastal erosion and improved shoreline stability in 3 villages within 24 months
The weak version is broad and difficult to assess. The strong version defines what changes, where, and within what timeframe.
Outputs
- Weak: Conduct training and restoration activities
- Strong: 50 hectares of mangroves restored and 120 community members trained in restoration techniques
The weak version describes activity. The strong version defines measurable results.
Indicators
- Weak: Communities improve environmental conditions
- Strong: Percentage reduction in shoreline erosion after 12 months
The weak version is not measurable. The strong version defines a clear metric.
Means of Verification
- Weak: Project reports
- Strong: Satellite imagery, GIS mapping, field monitoring reports
The weak version does not support validation. The strong version provides credible evidence sources.
Assumptions
- Weak: Community participation continues
- Strong: No extreme weather events; continued community engagement; support from local authorities
The weak version is generic. The strong version reflects real conditions.
Key insight: A weak logframe is rarely incomplete. It is structurally unclear. This difference is visible in seconds during evaluation.
Where Logframes Break Down
Most logframes do not fail because sections are missing. They fail because the relationships between sections are weak. These issues are rarely visible while building the logframe — they become visible when the structure is reviewed as a whole.
Outputs That Do Not Lead to Outcomes
Outputs are defined, but their contribution to change is unclear. Activities are completed, outputs are delivered, but the outcome does not logically follow. The results chain breaks at this point.
Indicators That Measure Activity Instead of Change
Indicators are often based on what is easy to track:
- Number of participants
- Number of workshops delivered
- Number of activities completed
These measure delivery. They do not measure results. The logframe shows what was done, but not what changed.
Weak Links Between Levels
Activities, outputs, and outcomes are listed — but not clearly connected. Activities are not directly tied to outputs. Outputs do not clearly support the outcome. The structure appears complete. The logic does not hold.
Generic or Irrelevant Assumptions
Assumptions are included as standard statements rather than real conditions:
- "Stakeholders remain engaged"
- "External conditions remain stable"
When assumptions are not linked to actual risks, they do not strengthen the structure.
Overloaded or Unfocused Outputs
Too many outputs included in an attempt to show scope. This leads to reduced clarity, difficult measurement, and weak contribution to outcomes. A focused structure is easier to assess.
What a Good Logframe Always Has
A logframe is not judged by how it looks. It is judged by how well the elements connect. This is how evaluators quickly assess whether a structure holds together.
Clear outcome (not activity-based) The outcome reflects a real change — behaviour, systems, or conditions. It does not describe completed activities. If the outcome reflects delivery, the structure is already weak.
Logical flow (no gaps in the results chain) The progression is consistent: Activities → Outputs → Outcome → Goal. Each level leads directly to the next with no missing links.
Measurable indicators Indicators define observable change: quantitative (percentages, numbers, timeframes), specific to the outcome and outputs. Vague terms such as "improved" or "increased" are not sufficient without measurement.
Verifiable data sources Each indicator is supported by a credible source: surveys, monitoring data, reports with defined methodology. This ensures that results can be validated.
Realistic assumptions Assumptions reflect actual external conditions: environmental risks, stakeholder behaviour, institutional support. They are specific and directly linked to the outcome and outputs.
Context-specific language The logframe reflects the actual project environment: target group, location, type of intervention. Generic language reduces clarity and weakens credibility.
Where Logframe Examples Can Mislead
Logframe examples are useful for understanding structure. They do not ensure that a logframe is correct. Used incorrectly, they create a false sense of completeness.
Copying Structure Without Understanding Logic
An example shows how a logframe is written. It does not show how decisions were made. Without that, outputs may not lead to outcomes, indicators may not measure real change, and assumptions may not reflect actual risks.
Generic Language Appears Acceptable
Many examples include phrases such as "improve livelihoods" or "increase resilience." These appear valid in isolation. Without defined target groups, specific timeframes, and measurable indicators, they cannot be evaluated clearly.
Context Is Not Transferable
A logframe that works for coastal restoration does not apply directly to agricultural systems or community livelihood programmes. Each requires different outcomes, indicators, and assumptions. Reusing structure without adapting logic leads to weak proposals.
Key insight: A logframe example shows what a strong structure looks like. It does not ensure that your structure works. That depends on how well the elements connect within your specific project.
Frequently Asked Questions
What is a logframe example? A logframe example is a completed logical framework matrix showing how a project is structured — from activities and outputs to outcomes and impact, including indicators, means of verification, and assumptions.
What makes a good logframe example? A strong logframe example demonstrates a clear distinction between outputs and outcomes, logical connections between all levels, measurable indicators, verifiable data sources, and realistic assumptions grounded in the project context.
Can a logframe example be reused directly? A logframe example can guide structure and quality, but should not be copied without adaptation. Each project requires its own logic, indicators, and assumptions based on its specific context and target population.
Why do some logframe examples look correct but fail under evaluation? Because the structure may be complete while the internal logic is weak. Common issues: outputs that do not lead to outcomes, indicators that measure activity instead of change, and assumptions that are generic rather than context-specific.
What is the difference between outputs and outcomes in a logframe? Outputs are what the project delivers — training delivered, hectares restored, systems established. Outcomes are what changes as a result — behaviour shifts, environmental improvements, adoption of new practices. This is one of the most critical distinctions in the entire logframe.
Is there a faster way to build a logframe from scratch? Instead of adapting an example manually, you can generate a structured logframe where outputs, outcomes, and indicators are aligned from the start.
Related pages: Logical framework approach · Logframe template · How to write a logframe · Logframe indicators
NGO Toolkit Lab
Generate your logframe