Build a Theory of Change for M&E in your browser. Six-component live builder, worked examples, indicator mapping.
A theory of change in monitoring and evaluation is a map of how a program is expected to produce its outcomes, where every link in the map is tied to an indicator and every indicator traces to evidence on the participant record. It is only useful in M&E when it is a living model checked against data, not a diagram drawn once and filed. Sopact keeps that check on the Evidence Thread, so each outcome in the theory of change points to the participant responses behind it.
Most teams build a theory of change for a proposal, hang it in a slide, and never return to it. The phrase practitioners use is that the diagram “sits in a drawer.” The gap is not the model; it is that the outcomes it promises were never wired to data anyone actually collects, so nobody can say whether the causal story held.
A theory of change earns its keep when the assumptions it makes are tested against what participants actually experience. A diagram becomes dead weight the day the causal links stop being questions and start being decoration. The pathway from activity to outcome is a hypothesis, and a hypothesis with no data behind it is a claim, not evidence.
The reason the model goes stale is architectural. The outcomes it promises live outside the program, in what participants do at 90 or 180 days, while most M&E systems only capture what happened inside the room. Sopact keeps the model connected to reality on the Evidence Thread, where every indicator resolves to the participant responses that feed it, so a broken assumption surfaces in the data rather than in a post-mortem. The pathway itself is defined on the theory of change page, and the indicators that test it are tracked on outcome tracking software.
In monitoring and evaluation, a theory of change becomes usable when each link carries an indicator and each indicator carries a source. An output indicator counts what the program delivered; an outcome indicator measures the change the pathway predicts, read on the same participant record over time. Without the trace, an M&E report can only assert that the theory held.
Sopact is evidence-centric: an outcome figure in the model is a query that resolves to the responses on a persistent record, so an evaluator can follow any number back to the participant who gave it. That is the difference between a theory of change used in evaluation and one used in a brochure, and it is what makes the practice on outcome evaluation and impact measurement defensible.
Teams usually draw a theory of change in a DAG or diagramming tool, track indicators in a spreadsheet, and roll the whole thing up in a generic M&E platform. Each layer works on its own: the diagram is tidy, the spreadsheet has columns, the platform makes a dashboard. What none of them do at the category level is keep the diagram, the indicators, and the participant evidence on one record, so the model and the data it is supposed to test stay in separate systems that never rejoin.
The one test that separates a filed diagram from a working model: pick any outcome in your theory of change and ask the system to show the participant responses behind its indicator. A DAG tool returns a shape; a spreadsheet returns a number with no source. Sopact answers from the Evidence Thread, because the outcome resolves to the responses on the record.
Keep it useful by wiring every outcome in the model to an indicator that traces to evidence on the participant record, and checking the pathway against that data continuously. The table sets a filed diagram against a living model on the Evidence Thread.
See the pathway itself on theory of change, and how it is judged on outcome evaluation.
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.
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 make a theory of change useful is to test it against your own program. Export your pathway and the indicators feeding it, then paste the prompts below into Sopact Sense’s Assistant, or reason through them with your team. The arrow above each links the Academy walkthrough with the expected output and tips.
Academy walkthrough → How to build a theory of change
Here is our program and the change we expect it to produce: [DESCRIBE + ATTACH]. Draw the theory of change from activities to outputs to outcomes, and for every link, name the indicator that would test it and the evidence on the participant record that would confirm it, so the model is testable rather than decorative.
Academy walkthrough → How to audit a theory of change
Here is our current theory of change and the indicator data behind it: [ATTACH]. For each assumed link between an activity and an outcome, tell me whether the data supports it, contradicts it, or has no evidence at all, and quote the participant responses behind each verdict so the audit traces to the record.
Academy walkthrough → How to build a logframe
Turn this theory of change into a logframe: [ATTACH]. For each outcome, define the exact indicator wording, the baseline, the wave schedule, and the source on the participant record, so every row in the logframe traces to evidence rather than to an assertion.
Academy walkthrough → Write a cited funder narrative
Here is our program data and open-ended responses on the same participant IDs: [ATTACH]. Draft a short M&E narrative that walks the theory of change link by link, and after each claim quote the participant evidence behind it, marking any pathway where the evidence is thin.
Each walkthrough is short and practical: what to do, the prompt to run, the output to expect, and the tips that keep it reliable.
Watch: impact as continuous, traceable evidence on one record, not an annual report figure.
It is a map of how a program is expected to produce its outcomes, wired so every link carries an indicator and every indicator traces to evidence. Sopact keeps that trace on the Evidence Thread, so each outcome in the theory of change points to the participant responses behind it rather than standing as an assertion.
A theory of change explains why the causal links should hold; a logframe operationalizes them into indicators, baselines, and targets. Sopact keeps both connected to the participant record on the Evidence Thread, so the logframe tests the theory of change against data instead of restating it.
Because the outcomes they promise were never wired to data anyone collects, so the diagram is filed and never checked. Sopact keeps the model alive by tracing every indicator to evidence on the Evidence Thread, so a broken assumption surfaces in the data rather than in a post-mortem.
Attach an indicator to every link and a source to every indicator, then read the data against the pathway continuously. Sopact does this on the Evidence Thread, where each outcome resolves to the participant responses behind it, so the causal story can actually be checked.
Monitoring tracks whether the indicators move; evaluation judges whether the theory of change held and why. Sopact supports both by keeping indicators and participant evidence on one record, so an evaluation traces its conclusions to responses rather than to a detached dashboard.
Yes. Because each outcome indicator resolves to the responses on the Evidence Thread, Sopact can show whether the data supports, contradicts, or leaves untested each link in the theory of change, and quote the participants behind the verdict.
No. A logic model is the simpler linear version; a theory of change adds the assumptions and the why. Sopact works with either, wiring each outcome to evidence on the Evidence Thread so the model is a working M&E instrument rather than a slide.
Continuously, not once a year. Sopact reads each response as it arrives through the Loop methodology, so the theory of change is checked against evidence throughout the program, catching a failing pathway while there is still time to act on it.
Next: see the pathway on theory of change, the indicators on outcome tracking software, or the full practice on impact measurement.
