At a Glance
| Theory of Change | Logframe | Results Framework | |
|---|---|---|---|
| What it is | A narrative and visual model of how change happens | A matrix linking results to measurable indicators | A visual diagram of the results hierarchy |
| Format | Diagram + narrative document | Table (4x4 or wider matrix) | Flowchart or hierarchy diagram |
| Level of detail | Why change happens, assumptions, causal pathways | What to measure, how, and how much | Which results connect to which |
| Primary use | Program design, strategic thinking, stakeholder alignment | Measurement, reporting, performance management | Communication, alignment, proposal design |
| Typical length | 1-5 page narrative + 1 page diagram | 1-3 page matrix | 1 page diagram |
| Main donor | FCDO, many INGOs | EU, ECHO, many bilaterals | USAID |
The Key Difference
A theory of change answers: "Why do we believe our activities will lead to the changes we want?" It maps the causal logic, surfaces assumptions ("farmers will have access to markets to sell improved crops"), and identifies the conditions that must hold for change to happen. A good ToC forces you to think about why your program should work, not just what it will do.
A logframe answers: "What will we measure to know if our program is on track?" It takes your results chain and attaches indicators, baselines, targets, data sources, and verification methods. A good logframe is a management tool. You can look at it quarterly and know whether your program is performing as expected.
They serve different purposes, and neither replaces the other.
How They Complement Each Other
Design phase: Start with the Theory of Change. Map your causal pathways. Identify your assumptions. Get stakeholder buy-in on the logic. This is where you decide what your program should achieve and why you believe your approach will work. A ToC built with stakeholders catches flawed logic early. If your team cannot agree on the causal pathway, you are not ready to write a logframe.
Structuring phase: Once the causal logic is agreed, translate it into a results framework. The results framework takes the narrative and turns it into a visual hierarchy: goal at the top, outcomes in the middle, outputs at the bottom. This step forces you to prioritize. A ToC can have ten causal pathways. A results framework makes you commit to the three or four you will actually measure.
Measurement phase: Then build the logframe. For each level of your results chain (impact, outcomes, outputs), define indicators, set baselines and targets, and specify how you will collect the data. This is where you decide how you will know if the program is working. Every row in the logframe should trace back to a pathway in the ToC. If a logframe row has no corresponding ToC pathway, you are measuring something you never designed for.
Implementation phase: Use the logframe for routine monitoring and reporting. Return to the Theory of Change when you need to revisit your assumptions, when the context changes, or when evaluation findings challenge your causal logic. When you update the ToC, check whether the logframe still matches. A mid-term evaluation that invalidates a key assumption should trigger changes in both documents, not just a paragraph in a report.
The flow: ToC (thinking) --> Results Framework (structure) --> Logframe (measurement)
This is not a one-time sequence. Good adaptive management means cycling back through these tools as you learn. The logframe generates data. The data tests the ToC. The revised ToC reshapes the logframe.
Worked Example: School Feeding Program
The same program looks different in each framework. Here is a school feeding program expressed as all three.
As a Theory of Change
Children in rural districts miss school because of hunger. If the program provides daily meals at school (activity), then enrollment and attendance will increase (short-term outcome), because families will send children to school when a meal is guaranteed (assumption). As attendance increases and children are better nourished, their learning outcomes will improve (medium-term outcome), provided that teachers are present and the curriculum is adequate (assumption). Over time, improved learning leads to higher completion rates and better livelihoods for graduates (long-term impact).
The key assumptions are: (1) families prioritize the meal enough to change behavior, (2) food supply chains remain functional, and (3) school quality is sufficient that attendance translates to learning.
As a Logframe
| Level | Result Statement | Indicator | Target |
|---|---|---|---|
| Goal | Improved livelihoods for children in target districts | Primary school completion rate | 70% completion by Year 5 |
| Outcome 1 | Improved learning outcomes for enrolled students | Average test scores (math and reading) | 15% increase from baseline by Year 3 |
| Output 1 | Daily school meals provided | # of schools serving meals on all school days | 120 schools by Year 2 |
| Output 2 | Increased enrollment and attendance | Average attendance rate in target schools | 85% average attendance by Year 2 |
Each row also includes a data source column (school records, standardized tests, program delivery reports) and an assumptions column, but the core structure is this: results linked to measurable indicators and time-bound targets.
As a Results Framework
Picture a one-page diagram. At the top sits the goal: "Improved livelihoods for children in target districts." Below it, two outcome boxes: "Improved learning outcomes" and "Increased enrollment and attendance." Below those, four output boxes: "Daily meals provided," "Supply chain established," "Community awareness campaigns conducted," and "School infrastructure upgraded." Arrows flow upward from outputs to outcomes to goal. No indicators, no targets, just the hierarchy of results and how they connect.
The results framework is the bridge. It is more structured than the ToC narrative but less detailed than the logframe matrix. Use it to align partners on what the program is trying to achieve before diving into measurement specifics.
A Note on Program Size
Not every program needs all three frameworks. A $50K, single-activity project does not need a full Theory of Change. A simple logframe is sufficient. The causal logic for a small project is usually obvious, and the overhead of building a ToC is not justified. Save the ToC for programs with multiple pathways, complex assumptions, or system-level change ambitions. As a rule of thumb: if your program has fewer than three outputs feeding a single outcome, a logframe alone will do the job.
Three-Way Comparison
Theory of Change
- Strengths: Forces rigorous thinking about causal pathways; makes assumptions explicit; works for complex programs; useful for stakeholder dialogue
- Weaknesses: Can become overly complex; no standardized format; hard to use for routine reporting; can be vague without a logframe to anchor it
- Best for: Complex, multi-pathway programs; adaptive management; programs working on systemic change; initial program design
Logframe
- Strengths: Clear, structured, universal format; ties directly to indicators and reporting; donors understand it; forces specificity
- Weaknesses: Linear thinking (cause-effect chains); can be rigid; does not capture complexity well; assumptions column often ignored; can become a compliance exercise
- Best for: Defined, predictable programs; donor reporting; programs with clear outputs and outcomes; performance management
Results Framework
- Strengths: Visual and easy to communicate; shows the "big picture" of results; good for multi-component programs; less intimidating than a logframe
- Weaknesses: No indicators or targets; too high-level for operational M&E; can oversimplify
- Best for: Proposals requiring visual clarity; communicating strategy to non-technical audiences; aligning multiple implementing partners around shared results
Donor Preferences
| Donor | Primary Tool | Also Requires |
|---|---|---|
| USAID | Results Framework | Performance Management Plan (similar to logframe), sometimes ToC |
| EU (DG INTPA) | Logframe (mandatory) | ToC increasingly requested |
| FCDO (UK) | Theory of Change (mandatory) | Logframe for measurement |
| GIZ | Results Model (similar to RF) | Logframe for indicators |
| ECHO (humanitarian) | Logframe (mandatory) | Simplified, focused on immediate results |
| SIDA (Sweden) | Results Framework | ToC for complex programs |
| Global Fund | Performance Framework | Modular, indicator-heavy |
| Private foundations | Varies widely | Often ToC; some accept narrative results |
When the donor template says "logframe" but you believe a ToC would strengthen the proposal: Include the required logframe, and add a 1-page ToC diagram as an annex. Most donors appreciate this; none will penalize you for it.
Common Mistakes
Mistake 1: Building a logframe without a Theory of Change. If you jump straight to indicators without thinking through your causal logic, you risk measuring the wrong things. The logframe should flow from your ToC, not precede it.
Mistake 2: A Theory of Change with no logframe. A ToC alone cannot tell you if your program is working. Without indicators and targets, you have a nice diagram but no way to measure progress. "We believe training will lead to behavior change" is not M&E; it is a hypothesis.
Mistake 3: Overcomplicating the Theory of Change. A ToC with 40 boxes and 80 arrows is not more rigorous; it is less useful. Aim for 3-5 causal pathways, each with 3-5 steps. If it cannot fit on one page, simplify.
Mistake 4: Treating the logframe as fixed. Logframes should be living documents. When context changes or evaluation findings challenge your assumptions, update the logframe. A logframe that was written in the proposal and never revised is a compliance artifact, not a management tool.
Mistake 5: Ignoring the assumptions column. The assumptions column in a logframe is where your Theory of Change meets reality. "Farmers will have access to markets" is an assumption. If it fails, your entire results chain collapses. Monitor your assumptions, not just your indicators.
Mistake 6: Confusing "results framework" with "logframe." A results framework is a one-page visual hierarchy. It is not a logframe. When a program officer asks for a results framework, they want a diagram, not a matrix. When they ask for a logframe, they want the matrix, complete with indicators, baselines, targets, assumptions, and means of verification.
Decision Guide
- Starting a new program design? Begin with a Theory of Change. Map your causal pathways. Test your assumptions with stakeholders.
- Writing a proposal? Check the donor template. Include whatever they require (logframe, RF, or both). Add a 1-page ToC if they do not ask for one.
- Setting up your M&E system? Build a logframe from your ToC or results framework. Define indicators, baselines, targets, and data sources.
- Managing an ongoing program? Use the logframe for quarterly performance tracking. Return to the ToC annually to revisit assumptions and causal logic.
- Small, simple project? A logframe is enough. Do not over-engineer the design framework for a straightforward intervention.
- Confused about which you need? You probably need both. The ToC is your thinking tool; the logframe is your measuring tool. Try the Logic Model Builder to get started.