Theory of change vs logic model - what each shows, the seven points where they differ, when to use each, and why most programs need both.
A theory of change explains why a program should work: the assumptions, the pathways, and the conditions that have to hold for change to happen. A logic model lays the same program out as a linear grid of inputs, activities, outputs, and outcomes. The theory of change is the reasoning; the logic model is the summary. Both only prove anything when their indicators trace to evidence on the record.
The pain is that most teams treat the choice as a formatting decision, build one diagram, drop it in a proposal appendix, and never connect its indicators to data. A logic model with no numbers behind its outcomes is a wish list in a grid; a theory of change with no evidence for its assumptions is a story. The diagram got made. Nobody checked whether it was true.
Use a theory of change when you are designing or questioning a program: it forces you to state the assumptions between an activity and an outcome, and to name the conditions that have to hold for the pathway to work. It is the better tool for strategy, for a mid-course rethink, and for arguing why a result is plausible before you have all the data. It is harder to fit on one page, which is its cost.
Use a logic model when you need to summarize and report: it lays the program out as inputs, activities, outputs, and outcomes a funder can scan in a minute, and it maps cleanly onto a logframe for indicators and targets. Many teams build the theory of change first to get the logic right, then derive the logic model from it, so the two stay consistent. A ready structure is on the logic model template.
A theory of change and a logic model are usually built once, in a slide tool or a template, for a proposal. They look finished, so they stop being touched. The assumptions in the theory of change are never revisited; the outcome rows in the logic model are never filled with actual numbers. A year later the program has changed and the diagram has not, and no one can say whether either was ever true.
The one test that separates a living framework from a wall poster is this: pick any outcome in the logic model or any assumption in the theory of change, and ask to see the evidence behind it. If the answer is a folder of PDFs nobody has read, the framework is decorative. Sopact keeps each indicator connected to the participant response on the Evidence Thread, so the test has a real answer, which is the whole point of monitoring and evaluation.
A framework earns its keep when its indicators are wired to data that arrives while the program runs. Sopact reads each participant response on arrival and ties it to the indicator it answers, so an outcome row in a logic model shows the number and the reason beside it, and an assumption in a theory of change can be confirmed or challenged by what participants actually say.
That turns a static diagram into a live account of whether the program is working, and it is the bridge from a framework to impact measurement. The theory of change explains the why, the logic model summarizes the what, and the Evidence Thread supplies the proof that either one holds.
The short version: a theory of change is the reasoning behind a program, a logic model is its linear summary, and both only matter when their indicators trace to evidence. Use the theory of change to design and question, the logic model to summarize and report, and one record to prove either. The table below sets the two side by side.
See each in depth on theory of change and logic model, or start from the logic model template.
An annual impact report is a lagging artifact: it summarizes a year that is already over, and its figures are assembled from data nobody read while there was still time to change anything. The value of impact evidence is highest while a program is running, when a weak result can still be improved. That is the premise of the Loop, Sopact’s method for continuous intelligence: collect clean at the source, analyze the moment data arrives, improve while there is still time to act.
Watch
The Loop is also what makes an impact claim defensible: every figure in a report traces back to the participant response it came from, the standard detailed in Loop traceability, so a funder or an investor can follow any number to its source rather than taking it on trust.
The fastest way to tell a live framework from a dead one is to make it answer for its evidence. Sketch your theory of change and logic model, then paste the prompts below into Sopact Sense’s Assistant, or reason through them with your team. The arrow above each prompt links the Academy walkthrough with the expected output and tips.
Academy walkthrough → Build a theory of change
Here is our program description and the data we already collect: [DESCRIBE + ATTACH]. Draft a theory of change: the long-term outcome, the pathways to it, the activities that drive each pathway, and the assumptions that have to hold for each step, and mark which assumptions we currently have evidence for and which we do not.
Academy walkthrough → Build a logic model
Here is our theory of change and program data: [ATTACH]. Derive a logic model from it — inputs, activities, outputs, and outcomes in a linear grid — keep it consistent with the pathways in the theory of change, and for each outcome name the indicator that would show whether it happened.
Academy walkthrough → Audit a theory of change
Here is our theory of change and our participant responses on one set of IDs: [ATTACH]. For each assumption, quote the participant evidence that supports or contradicts it, flag any assumption with no evidence behind it, and tell me which pathway the data most calls into question.
Academy walkthrough → Build a logframe
Here is our logic model and the data we collect: [ATTACH]. Turn the outcome rows into a logframe with indicators, baselines, and targets, and for each indicator tell me which participant response it would trace to, so every target has a real source rather than a placeholder.
Each walkthrough is short and practical: what to do, the prompt to run, the output to expect, and the tips that keep it reliable.
A theory of change explains why a program should work — its pathways and assumptions; a logic model summarizes the same program as a linear grid of inputs, activities, outputs, and outcomes. The theory of change is the reasoning, the logic model is the summary. Sopact keeps the indicators of both traced to evidence on one record.
Use a theory of change to design and question a program, and a logic model to summarize and report it. Most teams build the theory of change first to get the logic right, then derive the logic model from it. Sopact ties the indicators of either to the participant responses behind them.
A logic model is usually the linear summary of a theory of change: the theory of change lays out the full causal reasoning and assumptions, and the logic model compresses it into a grid a funder can scan. Sopact lets you derive one from the other so they stay consistent, and connects both to evidence.
Yes, and most programs should. The theory of change carries the assumptions and pathways for design and strategy; the logic model carries the compact summary for reporting. Sopact keeps them consistent and ties each indicator to a response on the Evidence Thread so neither goes stale.
Because they are usually built once for a proposal and never connected to data, so the assumptions are never revisited and the outcome rows are never filled with real numbers. Sopact reads participant responses on arrival and ties them to each indicator, so the framework stays a live account of whether the program works.
By connecting each assumption to the participant responses that confirm or challenge it. Sopact reads those responses on the Evidence Thread and quotes the evidence behind each assumption, so a theory of change can be audited against what participants actually report rather than taken on faith.
A logframe extends a logic model with indicators, baselines, and targets, so it is the natural next step when you need to measure. Sopact ties each logframe indicator to the response it traces to, so a target has a real source instead of a placeholder.
A theory of change and a logic model define what to measure; monitoring and evaluation checks whether it happened. Sopact keeps the indicators of both traced to evidence on one record, so monitoring and evaluation reads from the framework rather than from a separate spreadsheet.
Next: go deeper on theory of change and logic model, add indicators with a logframe, or connect it all on impact measurement.
