Quick Guide To The MEAL DPro
Quick Guide To The MEAL DPro
ISBN: 978-1-7345721-9-3
This work is licensed under the Creative Commons Attribution-NonCommercial 4.0 International
License. To view a copy of this license, visit http://creativecommons.org/licenses/by-nc/4.0/.
Version Information
This is “A Quick Guide to the MEAL DPro” compiled by PM4NGOs Board Member, Peter Marlow, and
based on “A Guide to the MEAL DPro – Monitoring, Evaluation, Accountability and Learning for
Humanitarian and Development Professionals”, Version 1.0 dated April 2019
Preface
All people working in the international relief and development sectors need to understand MEAL -
Monitoring, Evaluation, Accountability and Learning. The Guide to MEAL DPro provides a
certification-based and sector-wide standard which helps teams to design, plan and implement
MEAL in their projects by providing clear, practical guidance and tools that can immediately be
applied. This quick guide is a brief overview of the MEAL DPro guide. The full guide is downloadable
for free at https://mealdpro.org/ and contains many useful examples and case studies to illustrate
good practise. You will need to study the full guide if you are planning to take the certification
exam. Also, take a look at MEAL DPro Starter at https://mealdprostarter.org/ which gives on-
demand access to MEAL DPro tools for use in projects, which are also downloadable for free.
1. MEAL IN PROJECTS
By the end of this chapter, you will be able to:
✓ define the components, structure and purpose of MEAL;
✓ explain the benefits of a strong MEAL system;
✓ describe the relationship between MEAL and project management;
✓ identify the five phases of MEAL;
✓ describe the ethical standards and principles relevant to MEAL;
✓ understand the importance of participation and critical thinking in MEAL processes.
What is MEAL?
MEAL can be imagined as a puzzle made up of four unique pieces - monitoring, evaluation,
accountability and learning – only effective when the pieces are aligned, connected and working
together. We’ll look at each piece in turn to understand what they are - and what they are not.
M - Monitoring: The continual and systematic collection of data to provide information about
project progress.
E - Evaluation: The user-focused, systematic assessment of the design, implementation and results
of an ongoing or completed project.
Monitoring Evaluation
Purpose Tracking inputs, activities and progress A systematic and objective assessment of the merit,
toward achievement of agreed outcomes value or worth of an ongoing or completed project
and impacts
Frequency Regular and ongoing during project Periodic, one-off events during and, if funding
implementation permits, after project implementation
Responsibility Activities are conducted by members of Activities are often externally led, although they
the project team should involve the active participation of project staff
Use of Data Informs timely decision-making and short- Identifies potential course corrections
term corrective action in support of Contributes to longer-term organizational learning
adaptive management
Monitoring and evaluation data should always be used to inform management decisions, which, in
turn, promote Accountability and Learning.
A – Accountability: A commitment to balance and respond to the needs of all stakeholders
(including project participants, donors, partners and the organization itself) in the activities of the
project.
Projects embrace accountability by promoting transparent communications, aligning with standards
and best practises, by being responsive and encouraging participation.
L – Learning: Having a culture and processes in place that enable intentional reflection. The aim of
learning is to make smarter decisions.
Projects learn by incentivizing learning, encouraging a spirit of curiosity, embedding the learning
experience, promoting adaptive management and sharing information.
Together, the five phases of MEAL form a loop that promotes continual, intentional accountability
and learning. Your project should use MEAL data to periodically revisit the logic, design and
implementation of the project and its MEAL system. Furthermore, based on your learning, you
should update the original project design and adjust the MEAL system accordingly, if needed.
Introduction
The first phase of the MEAL cycle involves designing logic models. A logic model is a systematic,
visual way to present a summarized understanding of a project and how it works. It helps project
teams articulate the desired long-term change and how it will be achieved. The information
contained in logic models is the principal input to MEAL system design and is used by many
stakeholders such as project proposal writers, project managers and their teams.
This chapter explores three commonly used project logic models: the Theory of Change (ToC), the
Results Framework (RF) and the Logical Framework (Logframe). It’s best to create them in sequence
as each logic model draws and builds on the information found in the previous models.
Theory of change
The Theory of Change (ToC) is a comprehensive and visual description of how and why a desired
change is expected to happen. It defines the long-term goal of a project and the broad strategic
areas of intervention. It then maps the building blocks or preconditions which need to be in place
for the long-term change to occur. It also identifies the assumptions that need to hold true for the
project to succeed, and the evidence that is available to support them. It is recommended that ToCs
Results Framework
Now that the ToC is complete, the next step is to translate its contents into a Results Framework
(RF). The RF maps out the logic of the project strategy like the ToC but only includes interventions
that are the direct responsibility of the project team. It is important that the project team clearly
identify and prioritize the criteria it will use to decide what will be included in the RF, and what will
not be included. These criteria can be summarized as: needs prioritization; external program
considerations; appropriateness; institutional capacity; resources availability; financial and economic
feasibility; technical feasibility and sustainability; strategic considerations; and portfolio
considerations. Once these strategic decisions have been made, you will be able to identify what is
inside - and outside - of the scope of the results framework, and you can begin mapping content
from the ToC to your results framework.
The Guide to the MEAL DPro uses a four-level RF model that includes a hierarchy of objectives:
• Goal describes the longer-term, wider development to which the project contributes.
• Strategic objectives (SOs) express the central purpose of the project and significant benefits,
often addressing the immediate causes of the core problem.
• Intermediate results (IRs) express the expected change(s) in behaviors, systems, policies or
institutions as a result of project outputs and activities. There may be more than one IR for
each SO.
• Outputs are the deliverables resulting from project activities. There may be more than one
output for each IR.
In translating the contents of the ToC into an RF:
• The goal level in the RF is consistent with the long-term change identified in the ToC.
The full Guide contains an example of how to translate ToC content into Results Framework
objective statements.
Logical Framework
Once the Results Framework is complete, the next step is to develop the project’s Logical
Framework or Logframe. The Logframe is a logic model that describes the key features of the project
(objectives, indicators, measurement methods and assumptions) and highlights the logical linkages
between them. With the inclusion of these additional items, the Logframe provides the basis for
later developing the MEAL plan.
Like the Theory of Change (ToC) and the Results Framework (RF), the Logframe is intended to
communicate the purpose and main components of a project as clearly and simply as possible.
However, the Logframe includes information that is missing in the ToC and the RF, specifically:
• Indicators are measures used to track progress, reflect change or assess project performance.
• Measurement methods identify how the project will gather the data to track indicator progress.
There are many variations of Logframes. This guide uses a five-level matrix structure:
Objectives statements Indicators Measurement Methods Assumptions
Goal
Strategic Objectives
Intermediate results
Outputs
Activities
Assumptions (Column 4)
Before completing columns 2 and 3 of the Logframe (indicators and measurement methods), it is
helpful to complete column 4, the assumptions. They complement the “vertical logic” of objective
hierarchy by introducing the “horizontal logic” of the project. The vertical logic only succeeds if and
only if the assumptions at each level of the Logframe are true.
In principle, you can copy the ToC assumptions into your Logframe. The Guide contains a Decision
Tree for selecting Logframe assumptions
Indicators (Column 2)
An Indicator is a measure used to track progress, reflect change or assess project performance. Each
Objectives Statement will require at least one indicator, and sometimes more depending on the
information you need. Also, the type of information will depend on which objectives statement the
indicator is intended to track. The key to a good set of indicators is their quality and usefulness.
Also, they should be SMART - Specific, Measurable, Achievable, Relevant, Time-bound. To save you
time and effort, explore whether there are standard, validated indicators that can be reused or
repurposed for your needs.
There are two types of indicators:
• Direct indicators track change by directly examining what you are trying to measure.
• Indirect or proxy indicators track change by examining markers that are generally accepted as
being proxies for what you are trying to measure. These are helpful when the result you are
attempting to monitor is difficult or too expensive to measure.
Lastly, you will need to decide whether your indicator will be quantitative or a qualitative:
• Quantitative indicators are measures of quantities or amounts. They help you measure project
progress in the form of numerical information, such as numbers, percentages, rates (such as
birth rate) and ratios (such as number of men to number of women).
Data quality
The data you collect will never be free of bias. Thus, you need to determine, with the help of your
stakeholders, what quality and quantity of data is “good enough” for your decision-making, learning
and accountability needs. It is useful to consider the following five data quality standards.
• Validity. Data are valid when they accurately represent what you intend to measure i.e., the data
you collect helps you measure the indicators outlined in your Performance Management Plan
(PMP).
• Reliability. Data are reliable when the collection methods used are stable and consistent.
Reliable data are collected by using tools such as questionnaires that can be implemented in the
same way multiple times.
• Precision. Data are precise when they have a level of detail that gives you an accurate picture of
what is happening and enables you to make good decisions. For example, precise data allow
you to compare results between men and women (if this important for your project).
• Integrity. Data have integrity when they are accurate. Data should be free of the kinds of errors
that occur, consciously or unconsciously, when people collect and manage data.
• Timeliness. Timely data should be available when you need it for learning that informs decisions
and for communication purposes. Data are not useful to you when they arrive too late to inform
these processes.
Creating samples
Gathering data is expensive and time-consuming, making it difficult to speak to everyone. This is
why you need to identify a sample group (or subset) of respondents who will give you valid, reliable
and generalizable information to meet your needs. Sampling can be divided into two basic types:
Random sampling is used when you plan to use quantitative methods and analysis. This
sampling approach is used when you need confidence that what is true for your sample is likely
true for the entire population (or a subgroup of the larger population).
Take steps to avoid a sampling bias. This occurs when you are not taking into consideration all
the available perspectives, ideas and opinions and means that your data will not be as valid
(accurate), and cannot be easily generalized to the population you want to address. Two specific
types of bias can be especially problematic:
• Convenience sampling bias occurs when data are collected from respondents who are
easy to reach, or who are easy to work with. This runs the risk of over-representing
people located closer to main roads, or groups that are fluent in the predominant
language.
• Voluntary response bias occurs when data are collected disproportionately from self-
selected volunteers. This runs the risk of under-representing people with busy
schedules or people who travel frequently, and over-representing people with strong
opinions or specific agendas related to the project.
Managing data
Creating an effective data management system enables you to effectively analyze, interpret and use
the data you collect. There are four primary components:
Data entry. Use digital devices to collect data if possible. If manual entry is used, ensure your
data entry staff are trained.
Data cleaning is about detecting and removing errors and inconsistencies from data to improve
its quality. Conduct random quality checks, look for unexpected entries in the data, and remove
duplicate entries.
Data storage and security. It is important to ensure that data are secure and protected against
unauthorized changes, copying, tampering, unlawful destruction, accidental loss (have a backup
policy), improper disclosure or unauthorized transfer.
Data retention, disposal and de-identification. When it has been decided that data are no longer
needed - either following the end of the project, or during the implementation of the project -
all records and backups should be disposed of or adjusted so that it is impossible to identify the
data respondents. If you choose to retain data, de-identification can be done by anonymization
or pseudonymization.
Data visualization
Data visualization is the process of showing your data in a graph, picture or chart. This is easier than
poring over spreadsheets or reports, and helps to share detailed insights into data in the quickest
and most efficient way. It assists with:
• Analysis: Discovering relationships between, and patterns in, the data.
• Interpretation: Understanding and reflecting on patterns in the data set and then inferring new
information based on that interpretation.
• Communication: Making technical, statistical analysis understandable to people with limited
technical knowledge, and sharing your information in ways appropriate to your stakeholders.
Consider following these steps to ensure that your products are effective, especially if you intend to
use data visualization to aid communication to stakeholders:
✓ Step 1: Define the stakeholder(s) and your audience before designing a visualization. Keep in
mind that different people have different learning styles.
✓ Step 2: Define the data visualization content. Check your communications plan to determine the
“need-to-know” content for each of the stakeholders identified. Then, determine where a visual
will be most useful based on your findings, your information needs and the data available.
✓ Step 3: Design and test your visualization. Remember to keep it simple. Less is more with data
visualization. Do not crowd your visuals with too much data. Get started on paper, with the
audience-specific content that was identified. For each key audience identified, different visuals
or dashboards may need to be designed. The most common data visualization tools are:
o Bar chart: Shows multiple responses across different subgroups or points in time;
o Stacked column chart: Shows the variation in multiple variables or options across different
subgroups on different questions or different points in time;
o Pie chart: Shows composition of data set when component parts add up to 100 percent;
o Line chart: Shows the trends across different points in time;
o Scatter chart: Shows the relationship between two continuous variables or distribution
within a data set;
o Heat map: Shows the distribution of results across a geographic area, with greater
distributions represented by greater (“hotter”) color intensity;
Adaptive management
In order to contribute to project improvements, MEAL information should be used as part of
ongoing project decision-making. Adaptive management encourages and supports this process.
Effective adaptive management collects and analyzes project monitoring and feedback data to help
Progress Reporting
Reporting and communication can be seen as the culmination of your data analysis process,
recognizing that the ways you choose to include information in your reports is the final stage of
interpretation. High-quality, transparent reports in line with your donor or other internal and
external stakeholder requirements are vital. Good reporting captures and explains both the
successes and the challenges facing the project, and offers evidence of robust evaluative thinking in
the search for solutions. The guidance below is critical to creating reports that resonate with your
stakeholders and are useful.
Consult your project communications plan and data flow map to remind you of your
communications audience, purpose and timing.
Identify or develop report templates. Don’t make unnecessary effort when it comes to reporting.
Check whether your donor, organization or project already has a report template that you can (or
must) use. If you need to create a new one, ask your colleagues and stakeholders for examples they
find useful that you can adapt for your purposes.
Identify donor reporting requirements. Donors frequently specify their required reporting template
and schedule. Ensure that any templates you adapt or create also comply with these requirements.
Given the importance of reports, many donors and organizations have created detailed guidance on
how to create them. Check with your donor for their guidance on evaluation reporting. For example,
USAID gives extensive guidance on how to prepare an evaluation report.
FINALLY….
The Guide to MEAL DPro provides a certification-based and sector-wide standard which helps teams
to design, plan and implement MEAL in their projects by providing clear, practical guidance and tools
that can immediately be applied. We hope you now have a good understanding of the basics, but
remember this quick guide is only a brief overview of the MEAL DPro guide. If you want to learn
more and get a certification you should now study the full Guide to the MEAL DPro. It provides
important detail with lots of examples and practical advice for MEAL in projects in the real world.
It’s downloadable for free from https://mealdpro.org. Also, take a look at MEAL DPro Starter at
https://mealdprostarter.org/ which gives on-demand access to MEAL DPro tools for use in projects,
which are also downloadable for free.