What goes into a MEAL plan, section by section
A section-by-section guide to a project MEAL plan: theory of change, indicators, learning questions, data collection, data quality, use of results and budget.
Short answer
A MEAL plan is the document that shows how a project will monitor progress, evaluate results, stay accountable to communities and learn. It usually has a project description and theory of change, a measurement framework of indicators and targets, evaluation and learning questions, data collection and quality steps, a plan for using results, and the people and budget needed. Keep it short and update it.
Key points
- A MEAL plan turns your logframe into a practical system for collecting and using data.
- Cover the major results in your theory of change, but not every detail.
- For each indicator, say what method, who collects, and how often.
- Plan how results will be used, with meetings and decisions, not only reports.
- Treat the plan as a living document and update it as you learn.
What is a MEAL plan?
MEAL stands for monitoring, evaluation, accountability and learning. A MEAL plan is the project document that explains how the team will do all four. Catholic Relief Services (CRS) describes it as documenting the structures and processes used for monitoring, analysis, evaluation and reporting of progress, adding indicator definitions, data sources and the people responsible for collecting data.
A plan helps in three ways. It tells staff and partners what to collect and when. It helps you avoid collecting data nobody uses. It also shows donors that you can track results. If you are new to the field, start with our introduction to what MEAL is.
What sections should a MEAL plan have?
Donors and agencies use different formats. The LIFT fund, which supported projects in Myanmar, listed seven main components for its MEAL plans. The CRS guide adds a learning plan, feedback and complaints planning, and a data management plan. A practical outline for a small NGO is:
| Section | What it contains |
|---|---|
| 1. Project description | Summary of the project, goals and objectives |
| 2. Theory of change or results framework | The logic of how activities lead to change |
| 3. Measurement framework | Indicators, baselines, targets, methods, frequency, responsible people |
| 4. Evaluation and learning questions | The main questions you want answered, and how |
| 5. Data collection, quality and analysis | Tools, training, checks, storage, analysis |
| 6. Accountability | Feedback and complaints, and how you share results with communities |
| 7. Use of results | Reporting, review meetings, decisions, influencing |
| 8. Resources | Staff, partners, budget, timeline |
How do you write each section?
- Project description. Give a brief summary of the project, its background and goals. One page is enough.
- Theory of change. Describe, in words or a diagram, how your activities are expected to lead to results. Our guide on writing a theory of change shows how.
- Measurement framework. LIFT's guidance describes this as a data collection plan. Pick indicators for the major pieces of the theory of change. LIFT noted that it is important to measure the major parts, but not necessary to track everything. For each indicator, state the baseline, the annual targets, the method and tools, who collects the data and how often. Define each indicator in an indicator reference sheet and make sure indicators are SMART.
- Evaluation and learning questions. Write a small number of questions about how and why the project works, not only whether targets were met. LIFT advised not to propose more questions than the project can manage and report properly. CRS suggests that learning questions evolve during the project as early questions are answered and new needs arise.
- Data collection, quality and analysis. Describe baseline and endline surveys, interviews, field visits and activity tracking. Add steps to keep data accurate, reliable, precise, complete and timely. Say when and how data will be analysed, and who will interpret the results with programme staff and communities. See our guide on data quality checks.
- Accountability. Describe how people can give feedback and complaints, how you will respond, and how you will tell communities what you found. CRS builds feedback, complaints and response mechanisms into MEAL planning, and links them to safeguarding policies.
- Use of results. LIFT lists several ways to use MEAL results: reporting, improving project design and implementation, and influencing policy. Plan real events, such as monthly team meetings and quarterly reviews, because they only happen if planned and budgeted.
- Resources. List MEAL staff, partner roles, tools, training and the budget. CRS asks teams to ensure MEAL is supported by an appropriate budget and staffing before the plan is built. Our guide on how much of a project budget should go to MEAL can help.
What does a measurement framework look like?
A simple table works. Here is one row as an example:
| Indicator | Baseline | Target (year 1) | Method | Who collects | Frequency |
|---|---|---|---|---|---|
| Percent of trained farmers using at least two new practices | To be set at baseline survey | To be agreed with partners | Household survey and field observation | MEAL officer and partner staff | Baseline, midline, endline |
Keep the table to what you need. A long table of unused indicators wastes staff time.
How do you keep the plan useful?
- Build it with the team. CRS recommends designing MEAL systems in participatory workshops with MEAL, programme and partner staff. People use plans they helped to make.
- Link everything to decisions. For each data item, write the decision it supports.
- Set a review date. Review the plan after the first quarter and at least once a year.
- Test tools. Pilot data collection forms before the full roll-out.
- Train. Train staff and partners on the tools, consent and data protection.
Common mistakes to avoid
- Copying the logframe and calling it a MEAL plan. A plan needs methods, roles and timing.
- Too many indicators. More data does not mean more learning.
- No learning plan. Without questions, reports only repeat numbers.
- Ignoring partners. If partners do the data collection, include their capacity and their reporting load.
- Forgetting the budget. MEAL needs staff time, transport, training and tools.
How EMPO can help
EMPO is a reliable, Yangon-based training and consultancy provider and one of Myanmar's leading names in practical NGO training, with 1,200+ people trained and 15 partner organisations. We offer MEAL training and intensive support, including organisational systems support, in English and Burmese, online and in person across Myanmar. See our services or contact us to plan MEAL support for your project.
Sources
- Developing project monitoring and evaluation for learning and accountability (MEAL) plans: guidelines for implementing partners — LIFT Fund, Yangon, 2016
- SMILER+ Guide: MEAL system development — Catholic Relief Services, 2020
Questions people ask
What is the difference between a MEAL plan and a logframe?
A logframe sets out the objectives, results and indicators. A MEAL plan explains how you will collect and use the data for those indicators: methods, responsibilities, timing, data quality, learning and reporting. The logframe is an input to the MEAL plan.
When should the MEAL plan be written?
Draft the main elements during proposal design, then complete the plan in the inception period after the contract is signed, when the team and partners can shape it together. Update it when the context or the project changes.
How long should a MEAL plan be?
For a small project, 8 to 15 pages plus annexes is usually enough. Use tables so people can find what they need. If nobody reads it, it is too long.
