Monitoring, Evaluation and Learning

Systems and studies that measure program implementation and outcomes and explain what happened, why, and how performance can improve.

• Develop a results framework or theory of change.
• Establish baselines, indicators, and instruments.
• Monitor implementation, quality, and reach.
• Conduct midterm, final, or impact evaluation where feasible.
• Translate findings into learning and adaptation.

• Review program logic and evaluation questions.
• Develop indicators and verification sources.
• Use surveys, interviews, observation, and record review.
• Analyze implementation quality and unintended outcomes.
• Facilitate learning and interpretation workshops.
• Design monitoring systems and indicator dashboards.

• Before-and-after designs, comparisons, or time series.
• Theory-based or contribution evaluation.
• Experimental or quasi-experimental designs where appropriate and ethical.
• Multiple case studies or process tracing.
• Mixed methods and source triangulation.

The study population, unit of analysis, and access frame are defined before implementation. Sampling is selected according to purpose, inference needs, resources, and risk. “Representative” is used only where the design supports it, and exclusions, nonresponse, and adjustments are documented.

• Review the question and instrument before fieldwork.
• Pilot or pretest where the assignment permits.
• Train researchers and standardize instructions.
• Monitor completion and apply consistency, duration, and location checks where appropriate.
• Use clear consent, voluntary participation, and harm minimization.
• Separate identifying information and restrict access.
• Document deviations, problems, and corrective action.

• Monitoring framework and indicator matrix.
• Baseline or evaluation report.
• Performance dashboard and quality alerts.
• Learning record and actionable recommendations.
• Presentation to teams, management, and partners.

• Impact is not attributed without a design supporting attribution.
• Indicators do not replace evaluation questions or explanation.
• Program records may reflect reporting incentives and require validation.
• Learning should be separated from punitive accountability where possible.

Work begins with the question, intended audience, decision to be supported, relevant areas and groups, schedule, and budget. The Center then proposes a feasible scope, methodology, and deliverables.

Submit a Research Request

• Were activities implemented as planned?
• Who was and was not reached?
• What outcomes and changes are associated with the program?
• Why did some components work or struggle?
• What lessons and decisions should follow?

An inception discussion confirms purpose, questions, population, geography, users, deliverables, and constraints. An inception note or protocol may define design, roles, schedule, quality plan, risk, and change rules before implementation.

• Reconstruct the theory of change and evaluation questions.
• Define indicators, sources, and calculation rules.
• Distinguish monitoring, evaluation, and audit.
• Select a design appropriate to contribution or impact claims.
• Protect evaluation independence when program management reviews findings.

• Review concepts and definitions before item wording.
• Use language appropriate to context and collection mode.
• Review translation for meaning rather than literal equivalence alone.
• Conduct logical and technical testing and, where needed, a pilot or cognitive interviews.
• Freeze the approved version and document subsequent changes.

Tables, indicators, comparisons, quotations, and qualitative themes are defined before collection closes where possible. Descriptive, exploratory, and explanatory analysis are distinguished, and small cells, missing values, weights, multiple tests, and uncertainty are reviewed.

The commissioner may review factual accuracy, contextual understanding, and compliance with scope. It may not select which valid findings appear or require a correct figure or material limitation to be removed. Comments and changes affecting method or meaning are recorded.

The agreement defines ownership of instruments, data, code, reports, and publication rights. Identifiable or restricted data are shared only for a defined purpose under clear authority and safeguards. Delivery of a report does not by itself authorize redistribution of the original dataset.

Data Collection and Fieldwork Management · Data Analysis and Reporting · Methodological Advisory