Why write a MEAL plan?
A project without a MEAL plan still collects data. The trouble is that each person collects different data in a different way, and nobody can say later what the project achieved. A MEAL plan fixes that. It is the agreement, before work starts, on what success looks like and how you will know.
Many donors ask for a MEAL plan in the first months of a grant. Even when they do not, the plan saves time. Staff stop debating what to count, and the reports write themselves from agreed sources.
What are the core parts of a MEAL plan?
Most plans hold the same nine parts. You can use this list as a checklist.
- Project summary. The goal, the target group, the location and the time frame, in half a page.
- Results framework. The chain from activities to outputs, outcomes and the goal. Our article on what a results framework is explains how to draw it.
- Indicator table. Each indicator with its definition, baseline, target, source, frequency and owner.
- Data collection methods. Surveys, attendance sheets, observation, interviews, group discussions.
- Evaluation plan. Any baseline, midterm or final evaluation, with its main questions and a rough budget.
- Accountability plan. How people can give feedback or complain, and how you respond.
- Learning plan. When the team will review evidence and who decides what changes.
- Roles and calendar. Who collects, who checks, who reports, and on which dates.
- Budget. The cost of staff time, travel, tools and evaluations.
What should the indicator table show?
The indicator table is the heart of the plan. For each indicator, write down:
| Column | What to write |
|---|---|
| Indicator | The exact wording, with the unit counted |
| Definition | What counts and what does not |
| Baseline | The starting value, or “to be collected” with a date |
| Target | The value you expect by a set date |
| Disaggregation | Splits such as sex, age group or disability |
| Source | The tool or record the number comes from |
| Frequency | Monthly, quarterly, once per year |
| Owner | A role, not only a name |
If two staff members would count the same activity differently, the definition is not yet clear enough. See our guide to the indicator reference sheet for a fuller template.
How do you plan data collection?
For each indicator, pick the simplest method that gives a reliable number. Counting people at a training needs an attendance sheet. Measuring a change in knowledge needs a short test before and after. Asking about satisfaction needs a small survey or group discussion.
Then decide four things:
- Who collects. Field staff, partners or community volunteers.
- How often. Match the pace of the work. Do not collect monthly what only changes once a year.
- Who checks. A second person should review data before it goes into a report.
- Where it is stored. One agreed place, not personal files.
Keep a note of risks to data quality, such as staff turnover or hard-to-reach sites, and say how you will reduce them.
How do accountability and learning fit in?
These are the two parts teams skip most often.
Accountability. Name at least one way for affected people to give feedback or raise a concern. State who receives it, how fast you reply, and how you tell the community what changed. Make sure sensitive reports, such as safeguarding concerns, go to the right person.
Learning. Put review meetings on the calendar. A common rhythm is a short monthly check, a deeper quarterly review and an annual reflection. For each meeting, say who attends, which data they look at and where decisions are recorded. A learning plan with no dates is only a wish.
What makes a MEAL plan easy to use?
- Keep one page that shows the whole plan: the framework, the indicators and the calendar.
- Use the same terms everywhere. If you say “participants” in one table and “beneficiaries” in another, readers will wonder whether they are different groups.
- Match each donor’s required indicators to your own, so you collect once and report many times.
- Share the plan with the field team in a short session, not only by email.
- Treat it as a working tool. Mark changes and keep older versions.
Where EMPOBase fits
In EMPOBase, the MEAL module holds results frameworks tied to Programs, a library of 235 indicators in eight sectors, Monitoring, 3W Coverage and Complaints & Feedback (CFM). You can start from a library definition and adapt it. Library text does not create a live link to results, so you still enter and review actuals in Monitoring. Reach totals are counts of records, not unique people. You can see how the pieces connect on the indicator library page.