📈Monitoring, Evaluation, Learning and Impact

The results chain: from activity to impact

You delivered a training to thirty people. That is what you did — not what you caused.

The results chain is the basic framework for thinking about what a project produces in stages. It consists of four consecutive links: Activity is what you do: run a workshop, plant trees, distribute booklets. Output is what the activity directly produces: the number trained, trees planted, booklets distributed. Outcome is the change in beneficiaries that emerges over time after delivery: a skill acquired, a behaviour changed, a capacity built. And impact is the broader change in people's lives or the community that is partly attributable to the intervention. Confusing these links is not merely a definitional error — it has practical costs. When outputs are called outcomes, projects look more effective than they are. When outcomes are called impact, we attribute to our project changes caused by many other factors.

Indicators and baseline

An indicator without a baseline is like a ruler with no numbers — you can measure something but you cannot know what.

An indicator is a measurement tool, not a goal in itself. "Number of volunteers trained" is an indicator. "80% of trained volunteers apply the skill within a month" is a target that uses this indicator. The difference is crucial: an indicator tells you direction, a target tells you how close you are to the desired change. A baseline is a measurement of the situation before the intervention. Without it, you cannot prove the intervention made a difference. If you begin a training workshop without measuring knowledge beforehand, you will finish the workshop without knowing whether anything changed. The one exception: if reliable historical data exists that can serve as the baseline.

Participatory evaluation differs from traditional evaluation at its core: rather than treating beneficiaries as a data source to fill into a form, they become partners in shaping the questions, interpreting the findings, and sometimes building recommendations. This shift is not merely a methodological choice — it is an ethical commitment to accountability toward those the organisation serves. Participatory evaluation tools vary to suit different contexts. Focus group discussions bring together beneficiaries with shared characteristics to discuss their experience with the service — they offer depth of understanding compared with a quantitative questionnaire. Community evaluation techniques such as stone-ranking and social mapping are particularly useful with groups who are not literate. And the participatory end-of-project review is a structured session where beneficiaries and the team together evaluate what happened and what could be improved, combining documentation and learning at once. The value of participatory evaluation is not limited to the data it produces — it extends to building the beneficiary's trust in the organisation and sense of belonging, making them feel that their voice genuinely reaches decisions that affect them. This effect remains present after the evaluation ends and contributes to accumulating social capital that cannot be purchased.

Data collection and quality

Bad data documented beautifully is still bad data — and spreadsheets do not correct for wrong questions.

Data quality has four main dimensions in humanitarian and community contexts: accuracy (does the data reflect reality?), completeness (has everyone who should be measured been measured?), timeliness (was it collected at the right time?), and ethics (was it collected with consent and safely?). The most common problem in project reports: biased data selection. What supports success is presented; what reveals failures is omitted. This is not an individual decision — it is an organisational culture that punishes the bearer of bad news. The solution: standardised reporting frameworks that explicitly ask for what was not delivered and what went differently from expected.

• Before collection: what is the specific question these data answer?
• During collection: are respondents interpreting questions the same way?
• After collection: are there missing values that weaken the full picture?
• Before use: were data collected with clear consent? Will they be stored securely?

Data quality in the volunteering context has specific challenges not faced by large organisations with specialist teams. Often the data collector is a volunteer doing this as a side task alongside their main role, in variable field conditions, with beneficiaries who are not always comfortable writing or expressing opinions freely to strangers. This creates a particular fragility that needs thoughtful handling, not merely hoping that "the numbers will add up." Four principles reinforce data quality in this context: first, simplify before collecting — a collection tool that takes more than ten minutes to fill will be filled hastily at best and lost at worst; the simpler and more focused the tool, the higher the data quality. Second, train the collectors — a good questionnaire does not replace a trained collector who understands why each specific question is being collected, asks it faithfully, and notices ambiguous answers that need clarification. Third, review immediately — checking forms at the end of each field day reveals errors while they are still correctable. Fourth, ethics as part of quality — data collected without clear consent or that exposes individuals' identities to risk may not be used regardless of its statistical accuracy.

The honest report

A report that hides what was not delivered does not persuade a funder to give again — it persuades them to fund an illusion.

An honest impact report differs from a promotional one in one crucial way: it states what was not delivered and not achieved, and explains why. This is not an admission of failure — it is a professional report that builds more trust with the funder and community than a fabricated perfect report. The honest report structure includes: what did we plan and what did we actually deliver? Which outcomes did we achieve and which did we not? What context affected performance? What did we learn and how will we adjust next time? A report that answers these questions does not need inflation — and it leaves the next beneficiary better positioned than before.

The gap between evaluation and improvement is the most common gap in volunteering organisations. Data is collected, a report is written, then it is placed on a shelf and the next cycle starts as if the evaluation never happened. This disconnect wastes time, resources, and the trust of beneficiaries who answered questions that led to nothing tangible affecting their lives. Translating evaluation findings into improvement requires three organised steps. First, identifying what can be changed: not every negative finding needs an immediate response — some are structural and require time and a higher decision, and some are outside the organisation's control. Distinguishing between these two types directs energy toward where real effect is possible. Second, forming specific traceable decisions: "we will improve communication with beneficiaries" is not a decision but an intention; a decision specifies the procedure, the responsible person, and the deadline precisely. Third, building the change into the next planning cycle: decisions drawn from the evaluation do not stay in the evaluation report — they are incorporated into the next project plan as clear items with defined follow-up and measurement timing. The real measure of evaluation success is not the beauty of the report — it is the organisation's ability to demonstrate that some decision in the next project differed because of what it learned from this evaluation.

Organisational learning and accumulated knowledge

An evaluation that ends with a report nobody reads has not evaluated anything — it has wasted time and resources.

Organisational learning means that experiences build on each other rather than being reinvented from scratch. A project that is not documented teaches nothing — and the next project often repeats the same mistakes with complete good intentions. The simple tool is the learning cycle: plan, implement, review, adjust. The "review" phase is not a standalone evaluation exercise — it is a structured moment where you ask: what exactly happened? What do we understand now that we did not at the start? What do we change next time? The measure of evaluation success is not the beauty of the report — it is whether the next project makes a different decision because of what we learned.

Communicating evaluation findings to the community differs fundamentally from the report submitted to the funder. The funder wants documented data, analysis, and methodology. The community wants to understand: what did you do? Did you make a real difference in people's lives? And are you genuinely listening to what is being said about you? These are different questions requiring a different approach. Good communication of findings to the community includes four elements. Clarity: using everyday language not technical terminology — "the proportion of children attending sessions rose from forty to seventy-five percent" is clearer than "we achieved a notable increase in the attendance indicator." Honesty: mentioning what was not accomplished alongside what was — the community that sees an organisation acknowledge its shortcomings constructively grants it deeper trust than one that hears successive success stories that never pause. Interactivity: findings are not a one-way statement delivered to the community but an invitation to dialogue — "this is what we found; what do you think? What explains these findings from your perspective?" Continuity: communicating about findings is not an annual event but a regular practice, and the organisation that keeps its community regularly informed builds a social capital that is difficult to erode.

Different data collection tools give you different pictures of the same reality — no single picture is complete. Individual interviews give you depth, context, and fine detail that appear in no survey, but they are time-intensive and their sample is limited. Surveys give you broader reach and comparable data, but they constrain answers to pre-set options that may not reflect what the beneficiary actually wants to say. Direct field observation tells you what actually happens, not what is said to happen — and this difference is fundamental in evaluating social programmes where people sometimes answer with what they think you want to hear. A mixed approach combines multiple methods for a more complete picture: a quantitative survey identifying patterns, then qualitative interviews interpreting those patterns and adding human context. The number tells you that seventy percent of participants reported improvement in their skills — the interview tells you why the remaining thirty did not, and what they were missing.

Translating evaluation findings into actionable decisions is the difference between an evaluation that changes things and one that gets stored. Before closing any evaluation report, ask: what specific decision must change in the next project based on this finding? Who is responsible for this change? And what is the timeline? These three questions transform an evaluation from an analytical document into an action plan. Recurring patterns in evaluation reports deserve structural treatment rather than repeated treatment. When the same weakness appears in three consecutive projects, that is not an operational problem — but a design problem requiring review of the system process itself.