Most monitoring, evaluation, accountability and learning (MEAL) frameworks are built the same way: a results framework drafted at headquarters, indicators selected for donor reporting, and a data collection plan handed to field teams to execute. In stable contexts, this sequence works well enough. In fragile and conflict-affected settings, it is one of the most common reasons MEAL systems quietly fail — producing data nobody trusts and learning nobody uses.

The gap between design and delivery

A framework designed without field input tends to assume a level of access, security and administrative continuity that fragile contexts rarely offer. Indicators that require monthly household surveys in an area with intermittent access become, in practice, indicators nobody can report on reliably. The result is not bad data — it is missing data, filled in with estimates that look precise but are not.

The second failure point is timing. Frameworks are often finalised before the programme’s operational model is settled, which means MEAL ends up measuring an idealised version of the programme rather than the one actually being delivered.

Three fixes that hold up in the field

What good MEAL looks like in practice

A MEAL system that survives contact with a fragile context is deliberately smaller than the one drafted on paper, built jointly with the teams who will run it, and revisited as access and security conditions change — not treated as fixed once a donor has signed off on it. The purpose of monitoring and evaluation is not the framework itself; it is the decisions it allows a programme to make in time to matter.