Why MEAL matters
Every project makes a promise: if we do these activities, these changes will happen for these people. MEAL is how you check that promise. Without it, a team can deliver every planned activity and still not know whether anything improved. With it, you can show results, fix problems early, and decide what to fund next.
What does each letter mean?
| Part | Main question | When it happens | Typical outputs |
|---|---|---|---|
| Monitoring | Are we doing what we planned, on time? | All the time, during the project | Indicator tracking, activity reports, field reports |
| Evaluation | Did it work, and why? | At set points: midterm, final, after the project | Evaluation reports, recommendations |
| Accountability | Can the people we serve influence what we do? | All the time | Feedback and complaints logs, responses, community meetings |
| Learning | What will we change because of the evidence? | At planned review points | Action plans, updated designs, lessons logs |
Monitoring
Monitoring is the routine collection of data on activities and results. You compare actual figures against targets for each indicator and each reporting period. Good monitoring is regular, simple and close to the work. It tells a manager this month that a distribution is behind, not next year.
Evaluation
Evaluation steps back and asks bigger questions: was the project relevant, effective, efficient, and are the changes likely to last? Many organizations use the OECD-DAC criteria to structure these questions. Evaluations can be internal or external. They use monitoring data, but they also collect new evidence, often qualitative.
Accountability
Accountability to affected populations means people can tell you what they think, raise complaints safely, and see what happens next. In practice this needs a complaints and feedback mechanism (CFM): channels people trust, a log, a response time, and a way to close the loop. See our guide to setting up a complaints and feedback mechanism.
Learning
Learning turns evidence into change. It is the part most teams skip, because no report forces it. Give learning a fixed time (for example, a quarterly review), an owner, and a short written output: what we learned, what we will change, who will do it.
How do the four parts connect?
Think of MEAL as one loop inside the project cycle:
- Plan. Define your results and choose indicators with baselines and targets.
- Collect. Gather data from the field on a set schedule.
- Check. Review and approve figures before they count as results.
- Listen. Log feedback and complaints, and respond.
- Analyse. Compare results with targets and read the feedback beside them.
- Decide. Agree what to change, and record it.
- Report. Share approved results with managers, donors and communities.
The loop repeats each reporting period. Evaluation sits on top of it at key points.
Who does MEAL work?
In a larger organization, a MEAL team designs the system and supports quality. But MEAL is not only the MEAL team’s job:
- Field staff collect data and hear feedback first.
- Project managers use monitoring data to run the project.
- Reviewers check figures before they are reported.
- Senior managers own the learning decisions.
Common MEAL problems, and what to do
- Too many indicators. Teams collect data for 40 indicators and use five. Cut the list to what managers and donors will actually read.
- Data nobody checks. Figures go straight from a field form into a report. Add a review step, so a second person approves each figure before it counts.
- Feedback with no answer. People stop using a feedback channel when nothing happens. Track response times, and tell communities what changed.
- Learning at the end only. A final evaluation is too late to change the project it evaluates. Hold short reviews during the project.
How to start with a small team
You do not need a large system to begin:
- Choose five to ten indicators that the project manager will actually use. An indicator library helps you start from tested definitions.
- Set one feedback channel that the community trusts, and log every message.
- Add an approval step so only checked figures become results.
- Hold one review meeting per quarter, and write down three decisions.
Where EMPOBase fits
EMPOBase includes a MEAL module with Monitoring, 3W Coverage, Reporting, Risk & Learning, and Complaints & Feedback (CFM), plus a library of 235 humanitarian indicators across 8 sectors. Field submissions through collection links wait in a review queue, and only approved values become indicator actuals. The field-to-results workflow shows each step. Field reporting is online; offline capture is not part of the product.