A Theory of Change (ToC) explains how and why a set of activities is expected to lead to a desired long-term change. It makes the project’s causal logic explicit: what must happen first, what results should follow and what assumptions need to hold.
UNICEF guidance describes a theory of change as explaining how inputs or activities produce a series of results that contribute to the final goal or impact. It also emphasizes assumptions, risks and the broader context affecting whether the pathway will work.
The basic Theory of Change chain
Problem → Activities → Outputs → Outcomes → Long-term impact
The real value is in the arrows between those boxes. Your team should be able to explain why one result is expected to lead to the next.
What a strong Theory of Change includes
- A clearly defined problem.
- The target population and context.
- Activities or strategies.
- Immediate outputs.
- Short- and medium-term outcomes.
- Long-term impact.
- Key assumptions.
- Major external risks or conditions.
- Evidence supporting important causal links.
Example
If an NGO trains unemployed youth, the training itself does not automatically create employment. The ToC should identify the assumptions between training and employment: training quality, market-relevant skills, employer demand, access to job-search support and other conditions.
Theory of Change vs logframe
A Theory of Change explains the causal pathway in depth. A logframe usually summarizes the results hierarchy, indicators, evidence and assumptions in a structured matrix. They can complement each other.
Common Theory of Change mistakes
- Drawing arrows without explaining causal logic.
- Assuming activities automatically create impact.
- Ignoring external conditions.
- Using vague outcomes.
- Creating a diagram that does not match the proposal narrative.
Use the Program Fundability Checker to test whether your project logic is strong enough before translating it into a donor-facing ToC.
Free Theory of Change Template
Map the pathway from activities to outcomes and make the assumptions behind your project logic visible.
Frequently Asked Questions
Does every grant need a Theory of Change?
No. Some donors require one explicitly; others use different program-design formats.
Should a Theory of Change be a diagram?
It can be a diagram, narrative or both. The causal logic matters more than the visual style.
Who should develop it?
Ideally the program team, MEL staff, relevant partners and stakeholders contribute so assumptions are tested rather than invented by one writer.
Can a ToC change?
Yes. Learning during implementation can reveal that assumptions or pathways need revision.
Is a ToC the same as a results framework?
No. A results framework usually organizes expected results and indicators, while a ToC focuses more explicitly on causal pathways and assumptions.
Conclusion
A Theory of Change makes the hidden logic of a project visible. Strong versions do more than connect boxes: they explain why change should happen, what assumptions must hold and what evidence supports the proposed pathway.
