Full Library

Internal and external stakeholders have different information needs over a project’s life, for purposes that include adaptive management, accountability, compliance, reporting and learning. A project’s monitoring, evaluation, accountability and learning, or MEAL, system should provide the information needed by these stakeholders at the level of statistical reliability, detail and timing appropriate to inform data use. In emergency contexts where the situation is still fluid, ‘informal monitoring’ has proved helpful to staff’s ongoing assessment of the broader environment in order to identify changes in the situation, in other actors’ responses, and in priority unmet needs that would require corresponding changes in the response.2 The same distinction between informal monitoring of possible changes in the project’s operating context—whether identified as project assumptions and risk factors or not—and formal monitoring of the activities included in the response and project indicators, is relevant for development contexts too. Informal monitoring: Ongoing assessment of changes in operating context Formal monitoring: Tracking progress against project activities and indicators Within formal monitoring, it is useful to further differentiate between light monitoring and rigorous monitoring: - Light monitoring aims to provide timely feedback on new activities (or new locations or target groups) or aspects of the project’s theory of change (activity-to-output or output-to-IR change) logic that staff are less confident about, to check for early signs that progress is being made and that assumptions are holding true while there is still ample time to make adjustments if necessary.3 - Rigorous monitoring aims to collect representative data for evidence-based project management, reporting and learning, not just at midterm but throughout project implementation.