What is Monitoring, Evaluation & Learning (MEL)?

Monitoring is the continuous, routine tracking of a programme while it runs — collecting data on what was planned versus what actually happened, on a regular schedule, so problems surface while there is still time to act on them. Monitoring answers questions like "are we on track?" and "how many people have we reached so far this quarter?"

Evaluation is a periodic, more structured assessment of a programme, usually at a milestone or at the end, that asks harder questions monitoring data alone cannot answer: did the programme cause the change we see, was it worth what it cost, would a different approach have worked better? Evaluation often draws on monitoring data as one of its inputs, but goes further — comparing against a baseline or a counterfactual, and often involving people outside the immediate delivery team to reduce bias.

Learning is what an organization deliberately does with monitoring and evaluation findings — adjusting an activity mid-course, changing a target that turned out to be unrealistic, or carrying a lesson into the next phase or the next programme entirely. Learning is easy to skip under delivery pressure, which is precisely why it is usually named explicitly (MEL, or MEAL when "accountability" is added) rather than assumed to happen automatically.

Programmes monitor results for three overlapping reasons: to manage delivery in real time, to be accountable to the people the programme serves and the funders paying for it, and to build an honest record of what worked, so the next programme does not have to relearn the same lessons from scratch. None of these three purposes is optional in a well-run programme — they simply operate on different clocks: monitoring is continuous, evaluation is periodic, and learning is ongoing but easy to neglect without a deliberate process for it.

METRA GET is built around the monitoring layer of MEL — indicators, targets, actuals, workplans and Data Quality checks are all live, continuous tracking, not a periodic evaluation exercise. Its reporting history and evidence trail (see "Governance & review workflows") exist so that a later evaluation, run by whoever the organization chooses to run it, has a real, traceable record to draw on rather than reconstructed memory.