Sopact is a technology based social enterprise committed to helping organizations measure impact by directly involving their stakeholders.
Copyright 2015-2026 © sopact. All rights reserved.
Monitoring and evaluation is one system on two cadences. Learn the M&E plan, framework, six design choices, and how to build a system that holds.
Monitoring and evaluation (M&E) is the practice of tracking a program while it runs (monitoring) and judging whether it produced the intended results (evaluation), so an organization can prove impact to funders and improve the program. Monitoring is continuous and asks whether delivery is on track; evaluation is periodic and asks whether the change actually happened, and why.
Most M&E systems separate the two badly: monitoring collects activity counts all year, evaluation arrives as a report months after the program ends, and neither connects back to the framework that was supposed to guide them. With Sopact, M&E is one continuous system built off the theory of change, so the monitoring data and the evaluation evidence are the same clean record rather than two disconnected exercises.
Used by: M&E and MEL leads, program evaluators, foundation program officers, and impact directors who have to satisfy a funder's reporting requirement and improve the program at the same time, from the same data.
Here is the pattern almost every M&E function repeats. Monitoring collects a pile of activity data — attendance, sessions, outputs — throughout the year. Evaluation is commissioned near the end and delivered as an annual report. By the time that report lands, the cohort it studied has already graduated, the assumption that broke broke months ago, and the findings inform a program that no longer exists. The data was collected to prove impact and improve delivery; it did neither in time to matter.
The shift is to design M&E off the theory of change and run it continuously. Every outcome the theory claims becomes an indicator; every assumption becomes a monitoring question watched while the cohort is still running; every instrument links to one persistent participant ID from baseline to follow-up. That is what Sopact makes M&E: a continuous, clean-at-source system rather than a year-end reporting scramble, so a broken assumption surfaces in weeks and the current cohort still benefits. The framework-specific mechanics of wiring a theory of change into monitoring are in the theory of change in monitoring and evaluation guide.
A working M&E system rests on a small set of building blocks, and each one has to connect back to the framework or it collects data for no purpose. Indicators are the measurable signals of change: a good indicator names what changes, in whom, by how much, over what period, and traces to a specific outcome rather than a standard menu. Baseline, midline, and endline are the measurement points: the baseline captured at intake, a midline check while the program runs, and an endline at completion, all on the same instrument so the comparison is valid. Monitoring versus evaluation is the split between continuous delivery tracking and periodic results judgment. Formative versus summative is the split between evaluation that improves the program mid-course and evaluation that judges it at the end.
These blocks only work when they connect to the framework. Indicators derive from the outcomes named in a theory of change or a results framework; assumptions become the monitoring questions; the causal-chain timeline sets the collection calendar. Pick indicators from a standard list first and you measure what is standardized instead of what your program claims. Build the framework, then derive the M&E, the reverse of how most trackers get assembled. A logframe is the matrix that carries indicators, means of verification, and assumptions together, and the monitoring, evaluation and learning practice adds the loop that feeds evidence back into decisions.
Watch: monitoring and evaluation, framework and continuous system. How the M&E building blocks connect to a theory of change and run continuously off one participant record, instead of arriving as a year-end report. Presented by Unmesh Sheth.
Two comparisons cause most of the confusion in M&E. First, monitoring versus evaluation: monitoring is continuous and descriptive, tracking whether activities are delivered and outputs produced, answering “are we on track?” Evaluation is periodic and judgmental, asking whether the outcomes occurred and whether the program caused them, answering “did it work, and why?” Monitoring feeds evaluation with the data trail; evaluation gives monitoring its criteria for what matters. A system that only monitors counts effort; a system that only evaluates learns too late.
Second, the framework formats. An M&E framework is the overall plan that ties indicators, data sources, collection timing, and responsibilities to a program's outcomes. A logframe is a specific four-row matrix (goal, purpose, outputs, activities) with an indicators column and an assumptions column; it is one way to express an M&E framework, favored by many bilateral funders. A results framework maps the hierarchy of results without the assumptions column, favored by USAID-style reporting. All three derive from the same underlying logic; build it once off the theory of change and switch the presentation rather than maintaining three documents by hand. When the question is which software runs this, route to the monitoring and evaluation tools guide; when it is how learning closes the loop, the monitoring, evaluation and learning guide. For the discipline that contains all of this, see impact measurement & management.
M&E earns its keep at four points in the cycle: turning outcomes into indicators, turning assumptions into monitoring questions, collecting a baseline on one persistent ID, and reviewing the evidence every quarter instead of once a year. The animation below runs the loop; the four prompts under it are the ones behind each job.
1 · Build the framework M&E runs on. Start with the theory of change so every indicator has an outcome behind it and every assumption becomes a monitoring question. The walkthrough is in how to build a theory of change.
Academy walkthrough → How to build a theory of change
Build a theory of change from this program description: [PROGRAM URL OR DOC]. For every outcome stage, write the M&E indicator (what changes, in whom, by how much, over what period), name the instrument that measures it, and the baseline collection point. For every assumption, write the monitoring question it becomes. Flag any outcome with no measurable indicator.
2 · Turn the framework into a logframe. Carry the indicators, means of verification, and assumptions into the matrix a funder asks for.
Academy walkthrough → How to build a logframe
From this theory of change or program plan: [PASTE OR LINK], produce a logframe: goal, purpose, outputs, and activities, each row with its indicator, means of verification, and assumption. Note where a means-of-verification or baseline is still missing so the M&E plan is complete.
3 · Structure the results framework for the funder. Roll the outcomes into the results hierarchy USAID-style reporting expects, derived from the same logic rather than rebuilt.
Academy walkthrough → How to build a results framework
From this theory of change: [PASTE OR LINK], build a results framework: goal, intermediate results, and sub-results, with an indicator on each result and a note on which theory-of-change outcome it derives from. Keep it consistent with the underlying logic instead of duplicating it by hand.
4 · Standardize the indicators in a data dictionary. Define each indicator once (name, definition, instrument, collection point) so every wave of data is comparable on one ID.
Academy walkthrough → How to build a data dictionary
From this M&E framework: [PASTE OR LINK], build a data dictionary: for each indicator, give the exact name, definition, data type, instrument, collection point (baseline/midline/endline), and the persistent-ID field it links to. Flag any indicator that is measured inconsistently across waves.
The sections above are the argument; the Academy articles are the practice, each a hands-on companion written to run on your own data. There is no single “build M&E” how-to because a real M&E system is assembled from its backbone frameworks, so start there.
Monitoring and evaluation (M&E) is the practice of tracking a program while it runs and judging whether it produced the intended results, so an organization can prove impact to funders and improve the program. Monitoring is continuous and asks whether delivery is on track; evaluation is periodic and asks whether the change happened and why. In Sopact, M&E is one continuous system built off the theory of change rather than two disconnected exercises.
Monitoring is continuous and descriptive: it tracks whether activities are delivered and outputs produced, answering 'are we on track?' Evaluation is periodic and judgmental: it asks whether the outcomes occurred and whether the program caused them, answering 'did it work, and why?' Monitoring feeds evaluation with the data trail; evaluation gives monitoring its criteria for what matters. Sopact runs both off the same clean participant record instead of collecting counts for one and commissioning a separate report for the other.
An M&E framework is the overall plan that ties indicators, data sources, collection timing, and responsibilities to a program's outcomes. It is usually derived from a theory of change and can be expressed as a logframe (a goal-purpose-outputs matrix with indicators and assumptions) or a results framework (a results hierarchy). In Sopact the M&E framework is built once off the theory of change, so the indicators, instruments, and persistent IDs are wired in before the first participant enrolls.
M&E means monitoring and evaluation, the paired practice of tracking a program as it runs (monitoring) and assessing its results (evaluation). The pairing matters: monitoring without evaluation counts effort but never confirms impact, and evaluation without monitoring arrives too late to steer delivery. Sopact treats M&E as a single continuous system so the two are the same record rather than two separate functions.
Formative evaluation improves the program mid-course, using signals gathered while the cohort is still running so adjustments are still possible. Summative evaluation judges the program at the end, measuring whether the predicted outcomes occurred at completion and follow-up. Both are required and neither substitutes for the other; the theory-of-change causal chain sets the timing of each. Sopact runs formative check-ins and summative outcome instruments off the same persistent participant ID.
Because conventional M&E collects a pile of activity data all year and delivers the evaluation as an annual report months after the cohort has graduated, so the findings inform a program that no longer exists. When M&E is designed off the theory of change and run continuously, with assumptions embedded as mid-program monitoring questions on a persistent ID, the signals arrive in weeks while the current cohort can still benefit. That timing is the whole point of monitoring, and it is what Sopact is built to deliver.
M&E is monitoring and evaluation; MEL adds learning, the explicit loop that feeds monitoring signals and evaluation findings back into program decisions. M&E can produce evidence that no one acts on; MEL closes that gap by making the review and revision step a formal part of the cycle. Sopact supports MEL by surfacing assumption breaks quickly enough to act on, and by keeping every revision on the same record as the evidence that prompted it.