Monitoring & Evaluation Fundamentals
Module 1: Introduction to M&E Foundations
Mediacrest College — Department of Health
Systems & Programme Management
Course Facilitator: M&E Training Unit
June 15, 2026
Course: M&E Fundamentals — Population, Health & Nutrition Programmes
Module: 1 of 4
Duration: 6 hours (4 × 90-minute sessions)
Level: Introductory
Prerequisites: None
1 Session 1: Introduction to M&E Foundations
1.1 Welcome & Course Overview
1.1.1 Trainer Introduction
Welcome to Module 1: M&E Fundamentals, delivered by Mediacrest College’s Department of Health Systems and Programme Management. This module is the gateway to understanding how data-driven management transforms health, nutrition, and population programmes from well-intentioned efforts into evidence-based interventions with measurable impact.
By the time you leave this room today, you will think differently about every statistic you read, every report you receive, and every decision you make in programme management.
1.1.2 Why Data-Driven Management Matters
Consider the following two statistics from a real-world national health survey:
- The low birth weight prevalence in a country is 20%
- Modern contraceptive use among married rural women rose from 52% to 73% over five years
Pause and reflect: How do we actually know these numbers? Who collected them? How were they verified? And what decisions do they drive?
These figures are the direct output of systematic Monitoring and Evaluation (M&E) efforts — the operational backbone of every programme that seeks to prove and improve its impact.
1.2 Learning Objectives
By the end of this module, participants will be able to:
| # | Learning Objective | Session | Domain |
|---|---|---|---|
| 1 | Identify the basic purposes and scope of M&E | S1 | Conceptual |
| 2 | Differentiate clearly between monitoring functions and evaluation functions | S2 | Conceptual |
| 3 | Describe the functions and main components of an M&E plan | S1 | Applied |
| 4 | Identify conceptual frameworks, results frameworks, and logic models | S1 | Applied |
| 5 | Describe how frameworks are utilised for systematic planning | S1 | Applied |
| 6 | Identify robust criteria for selecting programme indicators | S2 | Technical |
| 7 | Link indicators back to organisational frameworks | S2 | Technical |
| 8 | Identify primary types of data sources and use information for decision-making | S4 | Applied |
1.3 The Purpose of M&E
1.3.1 Defining M&E
Monitoring and Evaluation (M&E) is an essential, non-negotiable component of any intervention, project, or programme. This module approaches M&E specifically through the lens of population, health, and nutrition projects, establishing common terminology and a shared understanding of why M&E keeps programme management on track.
M&E serves three fundamental masters simultaneously:
The Three Purposes of M&E
1.4 Interactive Icebreaker
1.4.1 Brainstorm Exercise — Where Does the Data Come From?
Facilitator instruction: Allow 15 minutes. Ask participants to discuss in pairs before sharing with the group.
Prompt: When you read that “modern contraceptive use among married rural women rose from 52% to 73%,” pause and ask yourself:
- Who went out and collected that information?
- How frequently was it collected?
- How do we know the 73% figure is accurate?
- Who used that figure, and for what decision?
| Data Source | What it captures | Frequency | M&E Use |
|---|---|---|---|
| Demographic & Health Survey (DHS) | Population-level health indicators, behaviours, outcomes | Every 5 years | Evaluation baseline/endline |
| Health Management Information System (HMIS) | Aggregate facility-level service delivery data | Monthly | Monitoring |
| Routine Service Statistics | Monthly counts of services delivered | Monthly | Monitoring |
| Facility Registers & Client Records | Individual client-level data | Continuous | Monitoring & Eval |
| Community Health Worker Reports | Community-level coverage and outreach data | Weekly/Monthly | Monitoring |
| Special Studies / Surveys | In-depth programme-specific questions | As needed | Evaluation |
2 Session 2: Deep Dive into Monitoring
2.1 What is Monitoring?
2.1.1 Definition
Monitoring is the systematic, continuous collection of routine data to measure progress toward achieving specific programme objectives. It tracks changes in programme performance over time, empowering stakeholders to make informed decisions regarding programme effectiveness and efficient resource use.
2.1.2 Monitoring as Process Evaluation
Monitoring is frequently referred to as process evaluation because it focuses primarily on how a programme is being implemented, not just whether it achieved its goal.
Key questions monitoring is designed to answer:
| Core Question | Data Required | Decision it Enables |
|---|---|---|
| How well has the programme been implemented? | Fidelity checklists, supervision reports, activity logs | Course-correct implementation weaknesses |
| How much does implementation vary from site to site? | Facility-level comparative service statistics | Scale up best-performing sites; support lagging sites |
| Did the programme benefit the intended people? | Beneficiary reach counts disaggregated by target group | Adjust targeting strategy if gaps identified |
| At what cost were services delivered? | Financial expenditure records vs. output counts | Improve cost efficiency of service delivery |
2.2 What Can We Monitor?
2.2.1 Practical Elements of a Monitoring System
Real-world programme elements that are regularly monitored span the entire service delivery chain:
The Programme Monitoring Chain — from Inputs to Initial Outcomes
2.3 The Monitoring Trajectory
2.3.1 Visualising Monitoring Over Time
A key characteristic of monitoring is that it is continuous — data is collected at regular, repeated intervals throughout the entire programme lifecycle. This allows managers to see trends, spot problems early, and course-correct before they become crises.
Illustrative Monitoring Trajectory — Programme Indicator Over Time
Reading this chart: The Y-axis represents any programme indicator requiring tracking — percentage of clients satisfied, cost per commodity, or frequency of staff information-sharing. The X-axis maps the journey from programme start to end. Vertical amber lines mark key monitoring moments — baseline, mid-term review, corrective action, and end of programme.
2.4 Core Characteristics & Group Activity
2.4.1 Key Pillars of a Monitoring Routine
| Pillar | Description | Example Activity |
|---|---|---|
| Continuous | Monitoring is an ongoing process, not a one-off event. Data flows are maintained throughout the entire programme cycle. | Monthly facility reporting of client numbers |
| Multi-point | Data is collected at multiple time points — beginning (baseline), midpoint, and continuously thereafter. | Baseline survey before intervention; same survey repeated at midterm |
| Responsive | Findings are used in real time to determine if activities need adjustment during implementation. | If condom distribution drops 30%, investigate and restock within the same quarter |
| Practical | Common activities include counting clients, tracking health workers trained, and logging commodities distributed. | Clinic register review every 4 weeks |
2.4.2 👥 Group Activity — Indicator Mapping (30 Minutes)
Facilitator Instructions: Divide participants into teams of 4–5. Each team is assigned a mock health programme (e.g., a nutrition roll-out programme in a rural county).
Task: Identify 3 distinct routine process elements your team would monitor monthly and fill in the table below for each one.
| What are you monitoring? | Y-axis indicator | How often? | Who collects it? | Decision it informs | |
|---|---|---|---|---|---|
| Element 1 | ____________ | ____________ | ____________ | ____________ | ____________ |
| Element 2 | ____________ | ____________ | ____________ | ____________ | ____________ |
| Element 3 | ____________ | ____________ | ____________ | ____________ | ____________ |
3 Session 3: Understanding Evaluation & Attribution
3.1 What is Evaluation?
3.1.1 Defining Evaluation
While monitoring tells you what is happening, evaluation answers the harder question: why is it happening, and is the programme responsible?
Evaluation measures how well programme activities have met expected objectives and — critically — determines the extent to which changes in outcomes can be explicitly attributed to the programme or intervention.
Key concept: The difference in the outcome of interest between having the programme and not having it is known as its impact. Measuring this change is what we call impact evaluation.
3.1.2 The Counterfactual: With vs. Without Programme
Programme Impact: The Counterfactual Comparison
Reading this chart: The teal line shows outcomes with the programme. The dashed grey line shows the hypothetical trajectory without the programme (the counterfactual). The red bracket at the right shows the net programme impact — what the programme alone is responsible for, isolated from background trends.
3.2 Requirements for Robust Evaluation
3.2.1 What Does an Evaluation Require?
Unlike routine monitoring, a proper evaluation imposes strict methodological requirements:
| Requirement | Why it matters | Monitoring equivalent? |
|---|---|---|
| Baseline data collection | Establishes the starting point against which change will be measured. Without a baseline, you cannot prove improvement. | Yes (first data point) |
| End-line data collection | Measures the status of the same indicators at programme end to calculate change. | No — monitoring is continuous |
| Control or comparison group | Provides the counterfactual — what would have happened in the absence of the programme. Without this, you cannot attribute change to your intervention. | No — monitoring does not require this |
| Rigorous study design | Ensures findings are credible, replicable, and defensible to donors, government, and scientific audiences. | Partial — monitoring uses standard tools |
3.3 Monitoring vs. Evaluation — Comparison
| Dimension | Monitoring | Evaluation |
|---|---|---|
| Primary question | Is the programme being implemented as planned? | Did the programme achieve its intended impact? |
| Timing | Continuous throughout programme life | At start and end (or midterm) of programme |
| Data collection frequency | Repeated at short intervals (monthly/quarterly) | At two or more fixed points in time |
| Requires control group? | No | Yes — required for attribution |
| Key output | Progress reports, performance dashboards | Impact assessment reports, evidence briefs |
| Primary audience | Programme managers, implementers | Donors, policymakers, scientific community |
| Budget implication | Included in routine operational budget | 5–10% of total programme budget |
3.4 Interactive Scenario Sorting
3.4.1 Practice: Is it Monitoring or Evaluation?
Facilitator instructions: Read each scenario aloud. Ask participants to vote — raise hands for Monitoring, stay seated for Evaluation — before revealing the answer.
| Scenario | Description | M&E Function | Rationale |
|---|---|---|---|
| A | The National Council wants to know if the programmes being carried out in Province A are successfully reducing unintended pregnancy among adolescents in that province. | Evaluation | Concerned with long-term IMPACT and whether change can be attributed to programme activities. Requires comparison over time. |
| B | USAID wants to know how many sex workers have been successfully reached by your outreach programme this year. | Monitoring | Focused purely on COUNTING volume of people reached — a routine output tracking function with no attribution question. |
| C | A country director is interested in finding out if the post-abortion care provided in public clinics meets national standards of quality. | Monitoring | Requires tracking whether a CONTINUOUS PROCESS STANDARD is being maintained — a classic process monitoring function. |
4 Session 4: Strategic Alignment, Budgeting & Recap
4.1 The Value Proposition of M&E
4.1.1 Why is M&E Important?
M&E is not a bureaucratic box-ticking exercise. Done well, it is the most powerful management tool available to programme implementers. It enables:
What M&E Delivers for Programme Managers
4.2 The Four Burning Questions of M&E
4.2.1 Key Questions Your M&E System Must Answer
A well-designed M&E system is architected to answer exactly four programme management questions:
| # | Question | M&E Mechanism | Data Source |
|---|---|---|---|
| 1 | Was the programme successfully implemented exactly as planned? | Process monitoring — fidelity tracking, activity logs, supervision checklists | Programme registers, supervision reports |
| 2 | Did the target population benefit from the programme, and at what cost? | Output monitoring + cost analysis — beneficiary counts, cost per output calculations | Routine HMIS data, financial records |
| 3 | Can observed improvements in health outcomes be directly attributed to programme efforts? | Impact evaluation — baseline/endline comparison with control group | Population surveys (DHS, MICS, special studies) |
| 4 | Which programme activities were highly effective and which were less effective? | Outcome evaluation — disaggregated analysis of results by activity/site/strategy | Disaggregated programme data, qualitative methods |
4.3 Timing & the Project Lifecycle
4.3.1 When Should M&E Planning Take Place?
A common mistake is treating M&E as an afterthought — something you organise once the programme is already running. This fundamentally undermines the system’s value.
M&E Integration Across the Programme Lifecycle
Critical principle: Evaluations rely heavily on baseline data that must be collected before the programme begins. If you wait until the programme is running to plan your evaluation, it is already too late.
4.4 The 5–10% Budgeting Rule
4.4.1 Funding Your M&E System
The 5–10% Rule: How M&E Fits in a Programme Budget
⚠️ Warning: Skimping on this allocation means running a programme without visibility. Without M&E funding, you cannot prove your achievements to donors, identify failures early enough to fix them, or justify future investment.
5 Module 1 Summary & Assessment
5.1 Key Takeaways
5.1.1 What We Covered Today
| Session | Key Concept | One-line reminder |
|---|---|---|
| S1: Foundations | M&E defined | Systematic data collection and analysis to track and prove programme performance |
| S1: Foundations | Three purposes of M&E | Accountability + Learning + Decision-making |
| S2: Monitoring | Monitoring = process evaluation | Monitoring asks HOW the programme is being implemented |
| S2: Monitoring | Monitoring is continuous & responsive | Data at multiple points; used to course-correct in real time |
| S3: Evaluation | Evaluation measures attribution | Evaluation asks WHETHER the programme caused the change |
| S3: Evaluation | Counterfactual & impact definition | Impact = difference in outcome WITH vs. WITHOUT the programme |
| S4: Strategy | M&E must be planned at design stage | Baseline data cannot be collected retroactively — plan early |
| S4: Strategy | 5–10% budget rule | No M&E budget = no evidence of impact = no donor confidence |
5.2 Knowledge Check
5.2.1 Self-Assessment Quiz
Answer the following questions independently. Answers are provided below.
Question 1: A programme manager reviews monthly reports showing the number of antenatal care visits at 12 facilities. She notices one facility has a 40% drop and immediately sends a supervision team. Is this Monitoring or Evaluation? Why?
Question 2: A researcher compares HIV prevalence in a district where a prevention programme ran for 3 years with a matched district where no programme existed. Is this Monitoring or Evaluation? What specific component makes it an evaluation?
Question 3: Your programme has a total budget of KES 50,000,000. What is the minimum amount that should be ring-fenced for M&E? What is the recommended maximum?
Question 4: True or False — An evaluation can be designed and baseline data collected after the programme has already started, as long as it is done within the first 3 months.
5.2.2 Answers
| Q# | Answer | Score |
|---|---|---|
| Q1 | MONITORING. She is tracking a continuous routine output (ANC visit counts) at repeated short intervals and using findings responsively to adjust programme activities. | 1 mark |
| Q2 | EVALUATION. The comparison group (matched district without programme) is the key component — it provides the counterfactual needed to attribute the difference in HIV prevalence to the programme. | 2 marks |
| Q3 | Minimum: KES 2,500,000 (5%). Recommended: KES 5,000,000 (10%). | 2 marks |
| Q4 | FALSE. Baseline data must be collected BEFORE the programme begins. Once an intervention starts, the baseline status is altered. A baseline collected 3 months in already reflects programme effects. | 1 mark |
5.3 Pre-Work for Module 2
5.3.1 Before the Next Session
To prepare for Module 2: Indicators, Results Frameworks & Logic Models, please complete the following before the next class:
| Task | Description |
|---|---|
| Reading | Review the PEPFAR MER 2.0 Indicator Reference Sheet (available on the course portal). Focus on Section 1: HTS and Section 2: TX indicators. |
| Reflection exercise | Think of one programme you are currently working on or familiar with. Write 3 sentences describing: (1) its goal, (2) one thing you would monitor, and (3) one question an evaluation might answer. |
| Bring to class | Your organisation’s M&E plan or logical framework (if you have access to one). We will use real documents during the logic model session. |
| Optional | Kusek & Rist (2004) — Ten Steps to a Results-Based Monitoring and Evaluation System. Chapter 1 available free online. |
Appendix: R Session Info & Reproducibility
sessionInfo()
## R version 4.5.2 (2025-10-31 ucrt)
## Platform: x86_64-w64-mingw32/x64
## Running under: Windows 11 x64 (build 26200)
##
## Matrix products: default
## LAPACK version 3.12.1
##
## locale:
## [1] LC_COLLATE=English_United Kingdom.utf8
## [2] LC_CTYPE=English_United Kingdom.utf8
## [3] LC_MONETARY=English_United Kingdom.utf8
## [4] LC_NUMERIC=C
## [5] LC_TIME=English_United Kingdom.utf8
##
## time zone: Africa/Nairobi
## tzcode source: internal
##
## attached base packages:
## [1] stats graphics grDevices utils datasets methods base
##
## other attached packages:
## [1] tibble_3.3.1 scales_1.4.0 kableExtra_1.4.0 knitr_1.51
## [5] tidyr_1.3.2 dplyr_1.2.0 ggplot2_4.0.2
##
## loaded via a namespace (and not attached):
## [1] gtable_0.3.6 jsonlite_2.0.0 compiler_4.5.2 tidyselect_1.2.1
## [5] xml2_1.5.2 stringr_1.6.0 jquerylib_0.1.4 textshaping_1.0.5
## [9] systemfonts_1.3.2 yaml_2.3.12 fastmap_1.2.0 R6_2.6.1
## [13] labeling_0.4.3 generics_0.1.4 svglite_2.2.2 bslib_0.10.0
## [17] pillar_1.11.1 RColorBrewer_1.1-3 rlang_1.1.7 cachem_1.1.0
## [21] stringi_1.8.7 xfun_0.56 sass_0.4.10 S7_0.2.1
## [25] otel_0.2.0 viridisLite_0.4.3 cli_3.6.5 withr_3.0.2
## [29] magrittr_2.0.4 digest_0.6.39 grid_4.5.2 rstudioapi_0.18.0
## [33] lifecycle_1.0.5 vctrs_0.7.1 evaluate_1.0.5 glue_1.8.0
## [37] farver_2.1.2 rmarkdown_2.30 purrr_1.2.1 tools_4.5.2
## [41] pkgconfig_2.0.3 htmltools_0.5.9Document prepared by the M&E Training Unit, Mediacrest
College Department of Health Systems & Programme
Management.
This document is intended for educational purposes only. All data
and scenarios are illustrative.
© 2026 Mediacrest College. All rights reserved.