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 a coordinated system for tracking implementation and assessing results. Monitoring follows delivery and indicators continuously; evaluation examines effectiveness, relevance, and why results occurred at defined points. Both use a common results framework and evidence base, while evaluation may add research questions, methods, and comparison data.
The failure most M&E systems share is timing: the evaluation arrives too late to change anything. Monitoring data sits in one tool, evaluation surveys in another, and the report is assembled at year-end, after the cohort has left and the decision it should have informed is already made. The fix is not more indicators; it is one system that reads on arrival.
Watch: the M&E building blocks — indicators, baseline, and one system on two cadences.
Key takeaways
A usable M&E system makes six decisions explicit: results, indicators, unit of analysis, baseline and comparison, method and cadence, and use. The framework becomes operational only when a team can answer all six for every important result.
1. Results: What change should occur, for whom, and by when? 2. Indicators: What observable measure would show progress? 3. Unit of analysis: Is the record a participant, household, grantee, project, facility, or portfolio company? 4. Baseline and comparison: What starting point and comparison support the judgment? 5. Method and cadence: Which quantitative and qualitative evidence is collected, and when? 6. Use: Who reviews the finding and what decision can it change?
The sixth decision is the one many plans omit. An indicator without a named decision becomes reporting inventory. Sopact connects each measure to an owner and use, so a signal can change delivery before the reporting period closes.
The illustrative workforce plan below separates the target, collection method, cadence, owner, and decision. The values are examples, not benchmarks. Each row is useful because the measure has an action attached to it.
Monitoring asks whether attendance, readiness, and follow-up are moving on schedule. Evaluation asks whether employment outcomes changed, for whom, under what conditions, and what evidence explains the pattern. Learning happens when the owner uses either finding to change curriculum, outreach, or employer partnerships.
| Measure | Baseline → target | Method / cadence | Owner / use |
|---|---|---|---|
| Employment within 90 days | 28% → 55% | Follow-up survey + case notes; monthly | Program manager; adjust employer partnerships |
| Readiness score | 2.8/5 → 4.0/5 | Intake and exit assessment | Training lead; revise curriculum |
| Completion rate | 64% → 80% | Attendance record; weekly | Case manager; contact participants at risk |
Monitoring answers a fast question — is the program on track — and evaluation answers a slow one — did it work and why. The temptation is to build them as two projects: a dashboard for monitoring, a study for evaluation, each with its own data. That split is where the report ends up late and the two halves disagree on the numbers.
Sopact calls the connected operating model One System, Two Cadences. Monitoring evidence remains available for evaluation, and evaluation can add interviews, comparison groups, research questions, or other methods when the judgment requires more than routine indicators. The theory of change is covered on the theory of change page, and the measurement practice on impact measurement.
The building blocks are shared across both cadences: indicators tied to the theory of change, a baseline against which change is read, and a persistent identifier that links each unit across waves. The unit may be a participant, household, grantee, project, facility, or portfolio company. Choosing the tool is a separate decision, covered on the monitoring and evaluation tools page.
A practical sequence is: 1) clarify the decision the evidence must support; 2) confirm the theory of change; 3) define results; 4) select a small set of indicators; 5) choose the unit of analysis; 6) set the baseline and comparison; 7) combine quantitative and qualitative methods; 8) assign cadence and ownership; 9) test data quality and traceability; and 10) schedule the review and action loop.
A baseline shows the starting condition and supports before-and-after comparison. A baseline alone does not establish that the program caused a later change. Causal attribution requires an appropriate design; many evaluations instead assess contribution using multiple sources of evidence.
A practical workflow imports or defines the theory of change and indicators; creates intake, monitoring, exit, and follow-up instruments; keeps each unit on a persistent record; analyzes quantitative and qualitative evidence together; flags emerging risks; and produces a source-traceable report for human review.
Sopact is a strong fit for multi-program organizations that need longitudinal quantitative and qualitative evidence without replacing every system of record. A one-off anonymous poll with no follow-up, identity, or learning cycle usually needs a survey tool rather than a full M&E system.
A theory of change explains how and why change is expected; a results framework arranges intended results; a logframe connects results, indicators, verification, and assumptions; an M&E framework defines what will be measured and how the parts relate; and an M&E plan operationalizes frequency, ownership, analysis, reporting, and use.
These artifacts should align, but they are not interchangeable. The table below maps each to its job. The matrix format lives on logframe and the hierarchy on results framework.
Watch: why the logframe is not the problem, but a disconnected framework that cannot trace indicators to current evidence is.
These artifacts should connect without being collapsed into one another. A theory of change supplies causal logic, while each framework or plan organizes a different part of design, measurement, management, or reporting.
| Framework | What it organizes | Best for |
|---|---|---|
| Theory of change | The causal logic and assumptions | The substance every other format draws from |
| Logframe | Indicators, assumptions, verification, in a matrix | Institutional and government funders |
| Results framework | The outcome hierarchy, goal to activity | Showing how outcomes ladder up |
| M&E framework | Measures, methods, sources, and relationships | Designing the evidence system |
| M&E plan | The cadence, methods, and responsibilities | Running the system day to day |
The artifacts align through shared result definitions, measure definitions, and evidence lineage. They do not need identical contents: an evaluation plan can add questions and methods, while a logframe may remain focused on indicators, verification, and assumptions.
The value of a monitoring signal is highest while the program can still respond to it, and an evaluation is most useful before the decision it informs is made. Reading the data as it arrives means a broken assumption surfaces in weeks, not in the year-end report. That is the premise of the Loop, Sopact's method for continuous impact intelligence: collect clean at the source, analyze the moment data arrives, improve while you can still act.
The Loop is also what makes an M&E claim defensible. Every indicator traces back to the response and the baseline it came from, so an evaluation finding resolves to its source. That standard has its own chapter in traceability and transparency.
One method, three moves that never stop
Then the cycle runs again, a little sharper each cycle. Read the method: the Loop methodology →
The fastest way to make M&E one system is to build both cadences off one theory of change and one dictionary. Each prompt below pastes into Sopact Sense's Assistant, or reasons through with your team; the arrow above each links the Academy walkthrough that shows the expected output and the tips.
Academy walkthrough → Derive indicators from the theory
From this program's theory of change, derive the M&E indicators: [PASTE THEORY OF CHANGE]. For each outcome, give the indicator, the assumption it tests, the baseline needed, and whether it is a monitoring (continuous) or evaluation (periodic) indicator. Flag assumptions with no indicator behind them. Return a table.
Academy walkthrough → Turn indicators into a logframe
Turn these indicators into a logframe matrix: [PASTE INDICATORS]. For each, give the indicator, the means of verification, the assumption, and the collection cadence. Keep the wording identical to the data dictionary so the same field feeds monitoring and evaluation. Return the matrix.
Academy walkthrough → Define every indicator once
Build a data dictionary for this M&E system so monitoring and evaluation use the same definitions: [PASTE INDICATORS]. For each field give the definition, the unit, the wave schedule, the denominator rule, and the persistent identifier it links to. Flag any indicator two teams would compute differently. Return a table.
Academy walkthrough → Show how outcomes ladder up
Arrange these outcomes into a results framework hierarchy from goal to activity: [PASTE OUTCOMES]. Show which monitoring indicators roll up to which evaluation outcomes, and flag any level with no indicator. Return the hierarchy with indicators mapped to each level.
Each walkthrough is short and practical: what to do, the prompt to run, the output to expect, and the tips that keep it reliable.
Monitoring continuously tracks implementation and results, while evaluation periodically examines effectiveness, relevance, and why results occurred. Both use a common results framework and evidence base, although evaluation may add research questions, methods, and comparison data. Sopact's One System, Two Cadences keeps that evidence connected and available in time to act.
Monitoring is continuous and operational: is the program on track this month? Evaluation is periodic and judgmental: what is the merit, worth, or significance of the results, and why did they occur? Evaluation can use monitoring evidence while adding questions, methods, and comparison data. Sopact keeps the common evidence connected without treating the two activities as identical.
An M&E framework defines what will be measured, the methods and sources used, and how the evidence relates to intended results. An M&E plan operationalizes that framework through frequency, ownership, analysis, reporting, and use. Sopact keeps both connected to the same longitudinal records and data dictionary.
A results framework organizes intended results; a logframe connects results, indicators, verification, and assumptions; and an M&E framework defines the broader measurement and evaluation system. An M&E plan then assigns frequency, ownership, analysis, reporting, and use. Sopact connects these artifacts through shared definitions and traceable evidence without treating them as interchangeable.
Start from the theory of change, derive the indicators and the assumptions each one tests, capture a baseline, assign a persistent participant identifier, and decide which indicators run continuously versus periodically. Then choose the format a funder needs. Sopact builds both cadences off one record, so the system holds together rather than fragmenting into a dashboard and a study.
M&E tools range from spreadsheets and survey platforms to dedicated M&E software; they differ on whether monitoring and evaluation data share one participant record and whether open-ended evidence is analyzed. The tool comparison is on the monitoring and evaluation tools page. Sopact's point is that the tool should keep One System, Two Cadences rather than splitting M&E into disconnected exports.
A baseline is the measurement taken before or at the start of a program, against which later change is read. A baseline supports change measurement but does not by itself prove the program caused the change. Sopact keeps baseline and later waves on the same persistent record, so the comparison is traceable rather than hand-matched.
M&E is the wider system of continuous monitoring and periodic evaluation. Impact evaluation examines contribution or causation; a formal counterfactual is used in experimental or quasi-experimental designs, not in every impact evaluation. Sopact keeps monitoring and evaluation evidence connected so the chosen design can use a consistent, traceable evidence base.
The World Bank Independent Evaluation Group explains why monitoring information supports but does not replace evaluation. BetterEvaluation's planning guidance distinguishes an evaluation plan for a discrete study from an M&E framework spanning a program or portfolio.
Next: derive the indicators on the theory of change page, or examine causal designs on the impact evaluation page.
