Results Framework Template for NGOs (Structure, Examples + Builder)

A results framework is not a project summary. It is not a logframe. And it is not a monitoring checklist.

It is the structured map that shows, at a glance, how everything your project does connects to the change you are claiming to produce.

Most NGO teams struggle with results frameworks not because the concept is difficult — but because most guidance conflates it with adjacent tools. You search for a results framework template, and what you find is either a generic box diagram, a simplified logframe, or a narrative description that does not help you build anything.

The result is a framework that looks organised but lacks structural integrity. It shows levels and labels. It does not show verified connections.

This matters more than it appears. Funders — particularly development banks, foundations, and EU programmes — use the results framework to assess whether your project logic is sound. A weak results framework signals weak project design, regardless of how strong the activities are.

This guide explains what a results framework is in the context of NGO grant projects, how it differs from adjacent tools, what a complete template looks like, and how to build one that functions under evaluation.

What This Guide Covers

• What a results framework is and what distinguishes it from a logframe
• The core components of a results framework template
• Common structural failures and how to avoid them
• A worked example for an environmental NGO project
• What major funders (World Bank, EU, USAID) require from results frameworks
• How to integrate your results framework with your logframe and M&E plan

If you want to build a connected results chain with indicators and verification:

What Is a Results Framework?

A results framework is a structured diagram or matrix that maps the causal logic of a project — showing how inputs and activities lead to outputs, outcomes, and long-term impact, and how progress at each level will be measured.

It is used widely in international development by organisations including the World Bank, USAID, the Gates Foundation, and major EU programmes. Different organisations use different terminology, but the core structure is consistent: a hierarchy of results linked by causal logic and supported by indicators.

Results Framework vs Logframe: Key Differences

The terms are often used interchangeably, but they serve different functions:

In practice, a results framework and a logframe should be fully consistent — they represent the same results logic at different levels of detail.

What a Results Framework Is Not

Understanding what a results framework is requires being clear about what it is not:

• Not a narrative description of project activities
• Not a monitoring plan (it defines what to track, not how to track it)
• Not a theory of change diagram (though it should be consistent with one)
• Not a work plan (it shows results, not tasks)

Key Insight: A results framework shows whether your project is logically designed. A monitoring plan shows whether it is being correctly implemented. They answer different questions.

Core Structure of a Results Framework

A standard results framework template includes the following components:

1. Impact Statement (Goal)

The highest-level result the project contributes to. This is typically a long-term change in conditions, systems, or well-being that the project alone cannot achieve but contributes toward.

Key characteristics:

• Describes a change in the world, not a project output
• Is credibly connected to the project's outcomes
• Is measurable at the portfolio or programme level

Examples:

• Improved ecological integrity of Mediterranean coastal ecosystems
• Reduced greenhouse gas emissions from smallholder agricultural systems
• Increased resilience of rural communities to climate-related hazards

2. Outcome(s)

The medium-term changes that the project is directly responsible for producing. This is the core commitment of the project.

Key characteristics:

• Specific to the project's geographic and thematic scope
• Measurable within the project timeline
• Attributed to the project's activities and outputs

A project typically has one primary outcome and one or two secondary outcomes. More than three outcomes at a single project level is usually a sign of scope that is too broad.

3. Outputs

The direct, tangible results produced by project activities. Outputs are fully within the project's control.

Key characteristics:

• Concrete and countable
• Directly produced by defined activities
• Necessary but insufficient to produce outcomes on their own

The critical question to test every output: If this output is delivered but the outcome does not occur, what assumption failed?

4. Activities

The work the project does. In a results framework, activities are often summarised rather than listed in full — the focus is on what they produce, not the operational detail.

5. Indicators at Each Level

Each level of the results framework is supported by at least one indicator.

6. Baselines and Targets

For each indicator, a baseline value (pre-project) and a target value (end-of-project) must be specified.

Without these, indicators are structurally incomplete. The framework shows what is being measured but not whether improvement occurred.

7. Data Sources and Frequency

For each indicator, a specific data source and measurement frequency must be assigned.

Weak sources (should not be sole evidence for outcome indicators):

• Internal project reports
• Anecdotal field observations

Strong sources:

• Independently conducted surveys
• Government administrative data
• Satellite or sensor-derived measurements
• Published scientific assessments

Results Framework Template (Standard Format)

Simple Results Framework Matrix

This template shows the minimum viable results framework structure. It confirms:

• Each level is connected to the one above
• Each level has at least one indicator
• Baselines and targets are specified
• Data sources are named

Extended Results Framework with Assumptions

For EU-funded and development bank projects, assumptions should be included:

Assumptions explicitly stated are assumptions that can be monitored and managed. Assumptions left unstated are risks waiting to become failures.

Common Structural Failures in Results Frameworks

Failure 1: Activities Listed as Outputs

Many results frameworks include activities — things the project does — in the outputs row.

Examples that are activities, not outputs:

• "Conduct awareness campaigns"
• "Provide training to communities"
• "Carry out environmental assessments"

These describe work, not results. The outputs of these activities would be:

• "200 community members demonstrating awareness of biodiversity protection measures" (outcome of campaigns)
• "120 community members certified in ecological restoration techniques" (output of training)
• "Environmental baseline data for 3 target sites" (output of assessments)

When activities are listed as outputs, the results chain is broken at the foundation.

Failure 2: Outcomes That Are Actually Outputs

The most common confusion in results frameworks is placing output-level results at the outcome level.

An output is something the project delivers. An outcome is a change that occurs because of what the project delivered.

Example of the confusion:

When outcomes are actually outputs, the results framework has no genuine accountability for change.

Failure 3: Indicators That Cannot Demonstrate Change

The most persistent problem in results frameworks is the use of indicators that confirm delivery rather than demonstrating change.

Ask of every outcome indicator: If the project runs perfectly but nothing changes in the target population or environment, would this indicator still be met?

If yes, it is an output indicator masquerading as an outcome indicator.

Failure 4: Missing Baselines

A results framework without baselines is structurally incomplete. It can report final states. It cannot demonstrate improvement.

The baseline gap is particularly critical for environmental projects where change is measured against natural conditions that are continuously shifting. A vegetation cover figure at project end means nothing without a vegetation cover figure before the project began.

Key Insight: Without baselines, a results framework is a description of what you hope to achieve. With baselines, it is evidence of what you actually changed.

Results Framework Example: EU Biodiversity Project

Programme context: LIFE Nature and Biodiversity project targeting the restoration of degraded peatland habitats in a lowland agricultural zone.

Funder requirements: Mandatory Core Performance Indicators (CPIs) aligned with LIFE programme targets; after-LIFE sustainability plan required.

Results Framework

Why This Framework Works

• Output 1–3 are tangible deliverables within project control
• Outcomes measure hydrological and ecological change — not delivery
• Baseline values are specified (water table depth, species presence)
• Data sources are independent and verifiable (piezometer network, botanical survey)
• Frequency matches what is operationally feasible
• Impact level is connected to EU-level reporting obligations

What Major Funders Require from Results Frameworks

World Bank

The World Bank uses a Results Framework and Monitoring (RFM) approach as a core part of project design. It requires:

• A clearly defined project development objective (PDO)
• PDO-level indicators with baselines, targets, and intermediate milestones
• Intermediate results indicators for each component
• A data sheet specifying definition, source, frequency, and methodology for each indicator

USAID

USAID's Program Cycle uses a project logic model and performance monitoring plan that functions as an integrated results framework. Requirements include:

• Standard Performance Indicators where applicable
• Disaggregation by gender, age, and geography
• Data quality assessments for key indicators

EU LIFE Programme

LIFE project results frameworks require:

• Mandatory Core Performance Indicators (CPIs) from the predefined LIFE indicator list
• Quantitative output and outcome targets at proposal submission
• After-LIFE plan demonstrating sustainability beyond the project period
• Complementarity and replicability measures

Gates Foundation

The Gates Foundation uses a results framework as the basis for all grant reporting. Its requirements include:

• A results framework diagram showing the causal logic
• Key milestones tied to the results chain
• Explicit gender equality considerations in indicator design

Key Insight: Most major funders require results frameworks to be submitted with the grant application — not built during implementation. By the time the project starts, the framework must already be credible.

Connecting Your Results Framework to Your Logframe and M&E Plan

A results framework, logframe, and M&E plan must be consistent. They are three representations of the same project logic:

When these documents are inconsistent — when the logframe includes indicators not in the results framework, or when the M&E plan tracks measures not referenced in either — the project design becomes incoherent.

This is most commonly a problem when documents are developed by different team members at different times without a common reference point.

The solution is to build from a single results chain. Everything else follows from it.

Building a Results Framework

The sequence for building a credible results framework:

1. Define the impact — What broader change does the project contribute to?
2. Define the outcome — What specific change will this project produce?
3. Define the outputs — What must be delivered for that outcome to occur?
4. Define the activities — What must be done to produce those outputs?
5. Assign outcome indicators — How will the change be measured?
6. Assign output indicators — How will delivery be confirmed?
7. Define baselines — What is the starting point before the project begins?
8. Set targets — What change is expected by what date?
9. Assign data sources — How will evidence be collected and verified?
10. Identify assumptions — What external conditions must hold for the logic to work?

This sequence produces a results framework that is internally consistent and externally credible.

The most common shortcut that undermines frameworks is starting at step 4 (activities) and working backwards. When you define what you plan to do first, the results chain tends to reflect what you are doing rather than what you are trying to change.

Build a results framework where every level is connected, every indicator measures real change, and every claim can be independently verified.

Related pages: Monitoring and evaluation framework · M&E plan template · Logframe template · Logframe indicators

Results Framework Template: Practical Notes for NGO Teams

Keeping the Results Framework Updated During Implementation

A results framework is not a static document. It should be reviewed and updated when:

• The project scope changes significantly
• An outcome is revised due to unforeseen circumstances
• New data reveals that baselines or targets are unrealistic
• A significant assumption fails and the pathway needs to be adjusted

The most common failure in results framework management is treating it as a proposal document that is filed after submission and not revisited until reporting time. By then, the framework may describe a project that no longer resembles what is being implemented.

Build a review schedule into the project workplan:

• Mid-term review: assess whether targets are achievable and whether assumptions are holding
• Annual review: update baseline-to-date progress on each indicator
• Final evaluation: assess achievement against targets and explain significant variances

Connecting Results Frameworks to Reporting

The results framework is the basis for all progress reporting. Each reporting period, the project team should:

• Report current values against each indicator target
• Explain progress or lack thereof
• Note any assumption changes that have affected the results chain
• Update targets if scope changes have been formally agreed with the funder

Most EU funders (including LIFE and Horizon) require progress reports at defined intervals. The results framework indicators directly correspond to what is reported.

Frequently Asked Questions: Results Framework Template

What is the difference between a results framework and a logic model?

The terms are sometimes used interchangeably. A logic model typically emphasises a linear flow from inputs through activities to outputs, outcomes, and impact. A results framework is similar but emphasises the measurement system — baselines, targets, indicators, and data sources. In practice, both represent the same underlying results chain; the emphasis and terminology differ by funder and region.

How detailed should outcome indicators be in a results framework?

Outcome indicators should be specific enough that two different people measuring them independently would reach the same result. This means: the parameter is clearly defined, the measurement unit is specified, the methodology is referenced, the target population is named, and the time period is stated.

Can a results framework include qualitative indicators?

Yes. Not all relevant changes can be quantified. A results framework may include qualitative indicators — particularly for outcomes related to governance, institutional change, or community dynamics. The key is that qualitative indicators have a defined assessment method (e.g., structured interviews, focus groups with defined scoring criteria) and are not just subjective impressions.

Should the results framework be the same document as the logframe?

Not necessarily — but they must be consistent. The logframe provides operational detail including activities, assumptions, and means of verification. The results framework provides a strategic overview of the results hierarchy with indicators. Some organisations use one integrated document; others maintain both. The critical requirement is that the same outcomes, outputs, and indicators appear in both.