Theory of Change Example: What a Strong Pathway to Impact Looks Like

Most teams understand what a theory of change is supposed to do. Fewer can tell the difference between one that works and one that doesn't.

Two theories of change can include the same elements — activities, outputs, outcomes, impact — and lead to completely different evaluations. One is clear, causally coherent, and immediately credible. The other raises questions the moment you read it. The difference is not presentation. It is logic.

A theory of change example exposes this. It shows whether:

• The causal pathway is explicit and testable
• Outputs realistically lead to the stated outcomes
• Assumptions reflect real-world conditions rather than optimism
• The pathway holds together as a complete system — not just a list of intentions

This guide provides concrete theory of change examples across different project types, breaks down what makes each pathway strong or weak, and explains how to apply those lessons to your own project design.

If you want to move from example to building your own structured theory of change:

What a Theory of Change Example Actually Shows

Before examining examples, it is important to clarify what you are looking for when you review one.

A theory of change is not assessed by how it looks. It is assessed by whether the pathway it describes is logically valid.

When evaluators review a theory of change, they are asking:

• Is the pathway traceable? Can you follow each step from activity to impact?
• Is the change plausible? Do the outputs realistically lead to the stated outcomes?
• Are the assumptions honest? Do the conditions required for success reflect real risks?
• Is it internally consistent? Does the same logic appear throughout — in the diagram, in the narrative, and in the logframe?

A theory of change example that illustrates these qualities is more valuable than a template. It shows what the decisions behind the structure look like — not just the format.

Key Insight: A theory of change example teaches you what the structure should feel like. A template only shows you what it should look like.

Simple Theory of Change Example

Before examining a complete project example, it helps to isolate the core structure.

Every theory of change describes the same basic logic:

We will do [activities], which will produce [outputs], which will lead to [outcomes], which will contribute to [impact] — provided that [assumptions] hold.

A simple environmental example:

💡

Activities: Train smallholder farmers in agroforestry techniques and provide tree seedlings.

Outputs: 300 farmers trained; 15,000 seedlings distributed and planted.

Outcome: 300 farmers adopt agroforestry practices, increasing tree cover on agricultural land.

Impact: Improved soil health, carbon sequestration, and household income in the target region.

Key Assumptions: Farmers have sufficient land and labour; seedlings survive initial establishment; land tenure is secure enough to invest in trees.

At a glance, this pathway is traceable. Each step connects to the next. The assumptions are specific, not generic.

But notice what would make this weak:

• If the outcome said "improved environmental awareness" instead of a behaviour change — that is a measurable output, not an outcome
• If the assumption said "farmers are motivated" — that is an aspiration, not a condition
• If there were no connection between agroforestry adoption (outcome) and soil health improvement (impact) — the causal link is assumed, not explained

The structure looks the same. The quality of the logic determines whether it holds.

Full Theory of Change Example: Environmental Restoration (LIFE Programme Context)

Project Context: A Mediterranean coastal NGO is applying for LIFE Nature funding to restore degraded coastal dune habitats and remove invasive plant species across three protected areas.

The Problem: Coastal dunes in the target areas have been degraded by invasive alien plant species, reducing the surface area of priority habitats under the EU Habitats Directive. Existing protected area management lacks the capacity and technical resources to address the invasion at scale.

Theory of Change Pathway

Long-term Impact (10+ years): Restoration of favourable conservation status for priority coastal dune habitats (EU Habitats Directive Annex I types 2110, 2120, 2130) across the target protected areas.

Outcome (by project end, Year 4): Invasive alien species cover reduced to below 5% of target dune habitat areas, with native dune plant communities reestablishing in restored zones.

Outputs:

1. 150 hectares of invasive alien species removed through mechanical and manual clearance
2. 50 hectares of native dune vegetation planted and monitored
3. 25 protected area rangers trained in habitat management and monitoring
4. Management protocols developed and adopted by 3 protected area authorities

Activities:

• Conduct baseline habitat assessment and invasive species mapping
• Implement mechanical clearance operations across target sites
• Establish nursery for native coastal plant species
• Execute native planting campaigns with community volunteers
• Deliver training programme for rangers and site managers
• Develop and publish evidence-based management protocols
• Conduct regular monitoring and adaptive management reviews

Critical Assumptions:

• Land access agreements with private landowners are maintained throughout the project
• Invasive species propagule pressure is manageable (no new major introduction events)
• Protected area authorities maintain management commitment after project end
• Weather conditions during planting seasons are within normal parameters
• EU Habitats Directive reporting confirms habitat type classifications

Why This Example Works

The causal chain is explicit:

Clearance (activities) → Invasive species removed at scale (output 1) → Native vegetation able to reestablish (mechanism) → Invasive cover below 5% (outcome) → Native communities recovering (indicator of outcome) → Habitat returning to favourable conservation status (impact)

Each arrow represents a causal claim that can be assessed for plausibility. The chain does not skip steps.

The outputs are direct and countable:

• "150 ha cleared" is verifiable through GPS mapping
• "50 ha planted" is verifiable through planting records and survival monitoring
• "25 rangers trained" is verifiable through training records

The outcome is specific and measurable:

• "Invasive species cover below 5%" is quantifiable through habitat surveys using standard EU monitoring protocols
• "Native communities reestablishing" is observable through vegetation surveys

The assumptions reflect real risks:

• Land access (not assumed — requires ongoing agreements)
• Propagule pressure (not assumed stable — requires monitoring)
• Management commitment (identified as a sustainability risk)

These are not generic reassurances. They are real conditions that, if violated, would cause the pathway to fail. Naming them shows that the project design is honest about its risks.

Full Theory of Change Example: Community Development Project

Project Context: A rural development NGO is designing a livelihoods project targeting women smallholder farmers in a dryland agricultural region to improve food security and income through diversified farming systems.

The Problem: Women farmers in the target region rely on a single rain-fed crop, making them highly vulnerable to drought. They lack access to technical support, inputs, and markets for alternative crops.

Theory of Change Pathway

Long-term Impact: Reduced vulnerability to food insecurity among smallholder farming households in the target region.

Outcome: Women farmers adopt diversified, drought-resilient farming practices, improving household food security and income.

Outputs:

1. 400 women trained in diversified crop production and water harvesting techniques
2. 10 demonstration plots established showing viable alternative crop varieties
3. 400 women connected to market linkages for alternative crops
4. Community savings and input credit groups established in 15 villages

Activities:

• Partner with agricultural extension service to deliver training curriculum
• Establish and maintain demonstration plots with lead farmers
• Facilitate market access through aggregation and trader linkage events
• Support formation and operation of village-level savings groups

Critical Assumptions:

• Agricultural extension service partner maintains capacity and commitment
• Alternative crop varieties are appropriate for local soil conditions
• Market prices for alternative crops remain viable
• Women have decision-making authority over their farming plots
• Rainfall is sufficient for establishing demonstration plots

Analysis: What Works and What Risks Remain

Strong elements:

• The causal chain connects training → demonstration → adoption → diversification → food security
• Outputs 1–4 are each necessary for the outcome; none is sufficient alone
• The assumption about women's decision-making authority identifies a real gender-specific risk

Vulnerabilities to flag:

• The pathway from "market linkages" (output 3) to "diversified practices adopted" (outcome) requires an explicit mechanism — farmers need not just access but economic incentive that makes adoption rational
• "Market prices remain viable" is an assumption that should be tracked, not just stated

Improvement needed: The theory of change should explicitly state why market access enables practice change — otherwise evaluators may question whether training and market access alone are sufficient to overcome barriers to adoption.

Key Insight: A theory of change example is most valuable when it shows you not just what a good pathway looks like, but where a plausible-seeming pathway can still fail.

Full Theory of Change Example: Institutional and Policy Change

Project Context: An environmental law NGO is developing a project to strengthen enforcement of water pollution regulations by supporting national environmental authorities in three countries.

The Problem: Legal frameworks for water quality protection exist but enforcement is weak. Regulatory agencies lack capacity, monitoring equipment, and inter-agency coordination.

Theory of Change Pathway

Long-term Impact: Improved water quality in freshwater ecosystems in three target countries.

Outcome: National environmental authorities demonstrate improved capacity to detect, respond to, and sanction water pollution violations.

Outputs:

1. 90 enforcement officials trained in water quality testing and regulatory procedures
2. 15 monitoring stations equipped with water quality testing equipment
3. Inter-agency coordination protocols developed and adopted in all 3 countries
4. Policy advocacy inputs provided to 3 legislative review processes

Activities:

• Design and deliver training curriculum for environmental officers
• Procure and install water quality monitoring equipment
• Facilitate inter-agency workshops and protocol development processes
• Prepare policy briefs and engage with parliamentary committees

Critical Assumptions:

• National governments maintain political commitment to water quality enforcement
• Budget is allocated for ongoing maintenance of monitoring equipment after project end
• Inter-agency coordination protocols are formally adopted (not just developed)
• Trained officials remain in post (staff turnover risk)

Why This Example Is More Difficult

The causal chain at the outcome level is long:

Training + equipment + protocols → improved capacity → improved enforcement → improved water quality

Each step requires a separate mechanism. The gap between "improved capacity" (what the project produces) and "improved water quality" (long-term impact) is large. Funders may reasonably ask what additional conditions are needed to close that gap.

For a theory of change to work at this level:

• The outcome must be specific enough to be attributed to the project (capacity improvement, not water quality)
• The impact must be plausibly connected to the outcome, with the connection explained
• The assumptions must address the political economy risks (political commitment, inter-agency competition) explicitly

This example shows that more complex causal chains require more explicit justification — not just longer lists of outputs.

What Makes a Theory of Change Example Strong: Summary

Having examined three concrete examples across different sectors, the distinguishing characteristics of strong theories of change are consistent:

Common Mistakes in Theory of Change Design

1. Confusing Outputs with Outcomes

The most persistent error. An output is something the project delivers. An outcome is something that changes as a result.

The corresponding outcomes would be:

• "300 farmers apply improved techniques"
• "Findings incorporated into sector guidance"
• "Policy provisions amended"
• "Farmers adopt practices demonstrated at plots"

2. Assumptions That Are Not Monitored

Assumptions listed in a theory of change serve no purpose if they are not tracked during implementation.

Every critical assumption should be:

• Assessed for likelihood at the design stage
• Monitored regularly during implementation
• Flagged if conditions change

If an assumption fails, the pathway changes. The theory of change must be updated.

3. Theory of Change That Contradicts the Logframe

If the theory of change describes one causal pathway and the logframe presents a different structure — different outcomes, different indicators, different scope — evaluators will notice immediately.

These tools must be consistent. The theory of change explains the logic. The logframe operationalises it. They describe the same project.

4. Missing the Mechanism

The most subtle failure. Stating that "training leads to adoption" without explaining why does not constitute a theory. The mechanism — the reason the causal step holds — must be made explicit.

Does the training lead to adoption because it changes knowledge? Builds confidence? Provides financial incentives? Reduces risk through demonstration? The pathway must specify the mechanism, not just the step.

Using Theory of Change Examples to Build Your Own

The most effective use of a theory of change example is to test your own pathway against it.

After reviewing the examples above, apply these questions to your project:

1. Can you trace a single, unbroken causal chain from your activities to your impact?
2. Are your outcomes genuinely different from your outputs — do they describe change rather than delivery?
3. Are your assumptions specific enough that you could monitor whether they hold?
4. If one critical assumption fails, which part of the pathway would break?
5. Is the mechanism between each step — the reason it works — explicitly stated?

If you cannot answer these questions clearly, the theory of change needs further development before it is ready for submission.

Build a theory of change where the causal pathway is explicit, every outcome is specific and measurable, and every assumption is honest about the conditions your project depends on.

What to Do With a Theory of Change Example

Reviewing theory of change examples serves a specific purpose: not to copy the structure, but to internalise the quality standards and apply them to your own project design.

After reviewing the examples in this guide, the most productive exercise is to evaluate your own theory of change against the same questions applied to each example:

Causal chain test: Can you draw a direct line from each activity to a specific output, and from that output to the outcome? If any step requires "and then somehow..." — that is the gap.

Output vs outcome test: Read every element you have labelled as an "outcome." Ask: Is this something the project delivers, or something that changes in the world as a result? If it is the former, it is an output.

Assumption quality test: Read every assumption. Ask: Is this specific enough to monitor? Would I know within the project period if this assumption was failing? If not, it is not a functional assumption — it is a hope.

Mechanism test: For every arrow in the pathway, write one sentence beginning "This connection holds because..." If you cannot write that sentence, the connection is not yet theorised — it is assumed.

These four tests, applied systematically to any theory of change, will reveal structural weaknesses that would otherwise surface only under evaluation.

Theory of Change Examples Across Different Project Scales

Theory of change logic scales — but the quality criteria remain consistent regardless of project size.

Small Grant (€20,000 – €50,000)

A simple community-level project can have a rigorous theory of change. Example:

💡

Problem: Plastic waste is accumulating on three kilometres of community beach due to absent waste collection infrastructure.

Activities: Community litter picks, installation of waste collection bins, engagement of local authority on collection contract.

Outputs: 15 bins installed; community group operational with 40 regular volunteers; letter of commitment from municipal council on waste collection.

Outcome: Visible plastic waste on target beach reduced by 80% within 12 months.

Impact: Improved beach ecosystem health and community environmental stewardship.

Assumptions: Municipal council follows through on waste collection commitment; community group maintains participation.

Even at small scale, the outcome is specific, the mechanism is clear (bins + collection contract + volunteers), and the assumption identifies the critical risk.

Large Programme (€5M+)

Larger projects require theories of change that handle greater complexity without losing coherence.

Key principles for complex theories of change:

• Use nested theories of change — a high-level pathway diagram with more detailed sub-theories for each component
• Be explicit about which outcomes the project directly claims and which are contributions to broader change
• Acknowledge the programme theory (what the funder believes about how change happens at portfolio level) and align with it
• Use scenario planning to acknowledge that pathways may evolve

Theory of Change Example: Common Questions

How long should a theory of change be?

The diagram should be understandable in under two minutes. The supporting narrative — explaining the mechanism, justifying assumptions, and connecting to evidence — is typically 2–5 pages for a project-level theory of change. For EU proposals with a formal theory of change requirement, follow the word limit specified in the call.

Should a theory of change be finalised before or after the logframe?

Before. The theory of change tests the causal logic. The logframe operationalises it with indicators and verification mechanisms. Developing the logframe first creates a risk of embedding operational detail without first confirming that the underlying logic is sound.

Can a theory of change have more than one outcome?

Yes — but each additional outcome adds complexity and requires its own causal chain. Most projects are stronger with one primary outcome. A second outcome is acceptable if the causal chains are clearly differentiated and the project has sufficient resources to pursue both simultaneously.

How do you test whether a theory of change is good?

The most practical test: present it to someone unfamiliar with the project and ask them to identify, in their own words, what change this project will produce and why it will happen. If they can do this accurately after a single reading, the theory of change is communicating correctly. If they cannot, revision is needed before submission.

Frequently Asked Questions

What is a theory of change example? A theory of change example is a completed causal pathway showing how a specific project's activities lead through outputs and outcomes to long-term impact — including the assumptions required at each step. Examples are most useful for testing whether your own pathway is logically sound.

How long should a theory of change be? The diagram should be readable in under two minutes. The supporting narrative is typically 2–5 pages. For EU proposals with a formal theory of change requirement, follow the word limit in the call guidelines.

What is the difference between an output and an outcome in a theory of change? An output is something the project delivers (training delivered, hectares restored). An outcome is a change that occurs because of that delivery (farmers adopt improved practices, vegetation cover increases). The theory of change must show how outputs lead to outcomes — not just list both.

How do I know if my theory of change is strong? Present it to someone unfamiliar with the project and ask them to describe what change will occur and why. If they cannot do this accurately after one reading, the pathway needs clarification before submission.

Does a theory of change need to be in the proposal itself? For Horizon Europe proposals: yes, explicitly. For LIFE and most foundation proposals: the logic must be present, even if not labelled as a "theory of change." For bilateral donors: a logic model or results framework serves the same function.

Related pages: Theory of change template · Theory of change diagram · Theory of change for NGOs · Grant writing template