Module 1: M&E Foundations
Monitoring Versus Evaluation
Every project makes promises. A water project promises cleaner water, a youth training programme promises jobs, a farmer support scheme promises better harvests. Monitoring and evaluation (M&E) is how you find out whether those promises are being kept, and why or why not. Managers use M&E to steer the work, funders use it to decide whether to keep paying, and the people the project serves benefit when problems are spotted early. Before you can do M&E well, you need to be clear about the two halves of the term, because they answer different questions and are done in different ways.
What monitoring is
Monitoring is the routine, continuous collection and use of information about a project while it is running. It asks: Are we doing what we said we would do, on time and within budget, and are the early results appearing? Monitoring is mostly done by the project team itself, as part of normal work. It tracks things like activities completed, people reached, money spent and short-term changes.
Typical monitoring data includes attendance registers, distribution lists, weekly activity reports, stock records, expenditure against budget and simple follow-up surveys. Monitoring is frequent (weekly, monthly or quarterly) and the information is used quickly to fix problems: a training venue that is too far away, a supplier who delivers late, a village where turnout is low.
What evaluation is
Evaluation is a periodic, more in-depth assessment of a project's design, implementation and results. It asks bigger questions: Did the project achieve its objectives? Was it the right thing to do? Was it good value? Will the benefits last? What caused the changes we see? Evaluations happen at specific points, commonly at mid-term, at the end of a project, or some time after it ends. They are often carried out or led by someone independent of the project team so that the findings are credible.
Many organisations use a set of evaluation criteria to structure these questions. A widely used set, from the OECD Development Assistance Committee, covers relevance, coherence, effectiveness, efficiency, impact and sustainability. You will meet these again later in the course.
Comparing the two side by side
| Feature | Monitoring | Evaluation |
|---|---|---|
| Main question | Are we on track? | Did it work, why, and was it worth it? |
| Timing | Continuous, routine | Periodic: baseline, mid-term, end, post-project |
| Who does it | Mostly project staff | Often external or independent evaluators |
| Focus | Activities, outputs, early outcomes | Outcomes, impact, value for money, sustainability |
| Main users | Project managers and field teams | Senior management, funders, policy makers |
| Typical product | Monthly or quarterly progress reports, dashboards | Evaluation report with findings and recommendations |
The two depend on each other. Good monitoring data makes evaluation cheaper and more reliable, because the evaluator does not have to reconstruct what happened. And evaluation findings feed back into how future monitoring is designed.
Worked example: a youth tailoring programme in Kisumu
Imagine a community organisation running a 12-month programme that trains 200 young people in tailoring and helps them start small businesses.
- Monitoring in month four shows that only 60 of the planned 100 trainees in the first cohort are attending regularly. The field officer reports that many trainees cannot afford daily transport. The manager introduces a small transport allowance and attendance rises the next month. That is monitoring doing its job: spotting a problem early and allowing a quick fix.
- Evaluation at the end of the programme, led by an independent consultant, looks at whether graduates are actually earning from tailoring six months later, whether women and men benefited equally, what the cost per graduate was, and whether the businesses are likely to survive without support. It recommends adding a savings-group component in the next phase.
Notice that the evaluation could only answer its questions because the monitoring system had kept good records of who was trained, when and with what support.
Common mistakes to avoid
- Treating M&E as reporting for the funder only. If data only flows upward and is never used by the team, staff stop taking it seriously and quality falls.
- Waiting for the evaluation to learn anything. By the end of the project it is too late to fix problems that monitoring could have caught.
- Calling a monitoring report an evaluation. Counting activities does not tell you whether the project made a difference.
- Collecting data no one uses. Every piece of information should have a clear user and purpose.
Keep this simple test in mind: monitoring helps you manage the project today; evaluation helps you judge and learn from it.
Exercise
Pick a project you know, at work or in your community. Write down three things that should be monitored routinely and how often, then write two questions an evaluation of that project should answer. For each item, note who would use the information.
Key points
- Monitoring is routine tracking during implementation; evaluation is periodic, in-depth assessment.
- Monitoring asks whether you are on track; evaluation asks whether it worked, why, and whether it was worth it.
- Good monitoring data makes evaluation cheaper and more credible.
- Every piece of data you collect should have a clear user and purpose.