Theory of Change vs Logframe: Two Tools, One Programme
The debate "theory of change vs logframe" comes up in almost every proposal workshop: the programme team wants a theory of change, the finance team wants the logframe the donor asked for, and somebody asks whether both are really necessary. They are. The two documents answer different questions, at different moments of the project cycle, for different readers. A theory of change explains why you believe your programme will produce change; a logframe states what you commit to deliver and how it will be measured. Treating them as rivals is the surest way to end up with a strategy nobody monitors and a results matrix nobody believes in.
What a theory of change is
A theory of change (ToC) is a reasoned description of how and why a desired change is expected to happen in a given context. It starts from the long-term change you aim for and works backwards: which intermediate outcomes must occur first, which actors must behave differently, and which activities or contributions make that plausible. Three features define it:
- Causal pathways: it maps the chain "if we do X, then Y, because Z", often with several parallel or converging pathways rather than one straight line.
- Explicit assumptions: every arrow carries a hypothesis about context, behaviour or other actors. Making those hypotheses visible is the whole point, because they are what you will test during implementation and impact evaluation.
- Non-linear and narrative: it is usually a diagram plus a written narrative, it can include feedback loops, and it describes contribution rather than attribution.
A ToC belongs to the organisation or the programme, not to a single grant. It is a strategic document first, and it can cover a whole country strategy or a consortium's shared ambition.
What a logframe is
The logical framework, or logframe, is a four-level matrix: overall objective (impact), specific objective (outcome), results (outputs) and activities. For each level it lists objectively verifiable indicators, sources of verification and the assumptions that must hold to move up to the next level. If you need a full walkthrough, see our guide to building and tracking a logframe.
Unlike the ToC, the logframe is a contractual object. When EU, ECHO, AFD or UN agencies approve a project, the logframe in the annex becomes the reference for progress reports, mid-term reviews and final evaluation. It is deliberately linear, bounded by the grant period, and measurable at every level: that is what makes it usable for indicator tracking with baselines, targets and measured values.
Theory of change vs logframe side by side
| Criterion | Theory of change | Logframe |
|---|---|---|
| Purpose | Explain how and why change happens; test the logic | Commit to results and show how they will be verified |
| Shape | Diagram with pathways and loops, plus narrative | Four-level matrix with four columns |
| Level of detail | Strategic; outcomes and assumptions, few numbers | Operational; indicators, baselines, targets, sources |
| Flexibility | Revisable at any review; meant to evolve | Changes require a formal amendment with the donor |
| Who asks for it | Foundations, consortia, strategy reviews, some institutional donors | Nearly every institutional donor (EU, ECHO, AFD, USAID, UN) |
| When in the cycle | Programme design, before any specific proposal; revisited at reviews | Proposal stage, then frozen at signature; reported against throughout |
| How it is monitored | Through outcome evidence, learning sessions and evaluations | Through indicator values collected on a MEAL plan schedule |
When to use which follows from the table. Use a theory of change for strategy work, complex or system-change programmes, multi-year interventions, consortia where partners need a shared logic, and foundation funding that values learning over fixed targets. Use a logframe for any funded project with an institutional donor, because it will be required and because it is the backbone of your MEAL plan. In a mature programme, the ToC exists once and several logframes hang from it, one per grant.
From theory of change to logframe in five steps
The logframe is not written from scratch at call for proposals time; it is extracted from the ToC. The process is mechanical once the ToC is solid:
- Pick the pathway the grant funds. A ToC usually has three to five pathways; a single grant rarely funds them all. Select the one or two the donor's priorities cover and leave the rest to other funding.
- Turn outcomes into objectives. The long-term change on the selected pathway becomes the overall objective; the intermediate outcome the grant can realistically reach within its duration becomes the specific objective. One specific objective per logframe, not three.
- Turn outputs into results and activities. The deliverables on the pathway (services provided, capacities built, mechanisms installed) become results; what the team does to produce them becomes activities, with their budget lines.
- Carry the assumptions across. The hypotheses attached to the arrows of the ToC become the assumptions column of the logframe, and the most fragile ones feed the risk register. If the ToC says "assuming local authorities keep the clinics open", that sentence belongs in the matrix, not only in the narrative.
- Define indicators at each level with baseline and target. Outputs are easy to count; outcome indicators need a baseline study or secondary data. Set a measurement frequency and a source of verification for each one, and check that the data collection effort is budgeted.
Three common mistakes
The theory of change as a poster. The diagram is produced during a two-day workshop, printed, hung on the office wall and never opened again. No review meeting tests its assumptions, so after two years nobody can say whether the logic held.
The logframe with nothing behind it. The matrix is written straight from the donor template without a ToC. The result is almost always a logframe whose indicators measure outputs only ("3,000 people trained", "12 sessions held") because nobody articulated what the outputs were supposed to change. The donor then asks about outcomes at the final evaluation, and there is no data.
Two documents that contradict each other. The ToC promises behaviour change among youth; the logframe's specific objective is about infrastructure. Each was written by a different person at a different time. Evaluators notice, and so do donors during a field visit. The fix is traceability: every line of the logframe should point to an element of the ToC.
Keeping both alive with Abvius
The hardest part is not writing the two documents but keeping them connected during implementation, when reports, no-cost extensions and staff turnover pull them apart. The Abvius MEAL module anchors the logframe in the same system as the budget and the documents, so the data needed to revisit the ToC is already there at review time:
- Results and indicators as structured records: each project carries its logframe levels, and each indicator has a baseline, targets by period and a measurement method, not a cell in a spreadsheet.
- Values with evidence: every measured value is entered with its date, its source and the supporting document (attendance sheet, survey export, photo), collected offline in the field if needed.
- Link to the budget: activities and results are tied to budget lines by donor, so a review can read spending and progress side by side instead of reconciling two files.
- Review-ready outputs: indicator progress by level exports directly into donor reports and into the annual or mid-term review where the ToC assumptions are discussed with real data.
Our complete MEAL guide and the article on setting up a MEAL system cover how this fits into a wider monitoring, evaluation, accountability and learning practice.
In practice
Write the theory of change once, at programme level, with the people who will implement it. Derive a logframe from it for each grant, keep the two visibly linked, and put a date in the calendar to test the assumptions with data at every review. The question is never theory of change vs logframe but how well one feeds the other. If your indicators and evidence currently live in scattered spreadsheets, start a free trial of Abvius or read our complete guide to project management for NGOs to see how the MEAL module fits into your project cycle.