A Practical Guide for Program Managers, M&E Professionals and Development Partners

Publication Date: August 2026
Author: Insight Research & Analytics
Estimated Reading Time: 5 minutes

Key Takeaways

• A Theory of Change (ToC) is more than a flow diagram—it is a set of evidence-based hypotheses about how change is expected to happen.

• Every programme relies on assumptions that must hold true for activities to produce outcomes and long-term impact.

• Many programme failures result from untested or unrealistic assumptions rather than poor implementation.

• Monitoring assumptions alongside programme indicators strengthens adaptive management and improves programme performance.

• Regular Theory of Change reviews help organisations identify risks early and adjust implementation before outcomes are affected.

Introduction

Development programmes are designed to create positive and lasting change. Whether improving education, strengthening health systems, increasing agricultural productivity, or promoting climate resilience, every intervention is based on an underlying belief about how change will happen.

This belief is captured in the programme’s Theory of Change (ToC).

However, while many organisations invest considerable effort in developing a Theory of Change during project design, relatively few revisit it during implementation.

When expected results fail to materialise, implementation is often blamed. In reality, the problem may lie elsewhere.

The programme’s assumptions may simply have been incorrect.

Understanding and testing these assumptions is essential for effective Monitoring, Evaluation and Learning (MEL).

What is a Theory of Change?

A Theory of Change is a logical explanation of how programme activities are expected to produce desired outcomes and long-term impact.

It identifies:

• The problem being addressed.

• The sequence of expected changes.

• The assumptions linking each stage.

• The external factors that may influence success.

Unlike a Results Framework, which focuses on what will be achieved, a Theory of Change explains why and how those results are expected to occur.

Understanding Assumptions

Assumptions are conditions that must be true for one step in the results chain to lead to the next.

For example:

Training Teachers
        ↓
Teachers improve classroom practices
        ↓
Student learning improves

Several assumptions exist between these steps, including:

• Teachers understand the training.

• Teachers are motivated to apply new methods.

• Schools provide supportive learning environments.

• Teaching materials are available.

• Students attend school regularly.

If one or more assumptions fail, expected outcomes may not occur despite successful implementation.

Five Common Theory of Change Assumptions That Fail

1. Assuming Participation Equals Behaviour Change

Many programmes assume that once beneficiaries attend training, they will automatically apply what they have learned.

In practice, behaviour change is influenced by many factors including motivation, confidence, incentives, social norms, and available resources.

Example

Farmers receive climate-smart agriculture training but continue using traditional farming methods because improved inputs are unaffordable.

Key Lesson

Measure adoption—not attendance.

2. Assuming Resources Are Sufficient for Change

Providing equipment, seeds, textbooks, or assistive devices does not guarantee effective utilisation.

Beneficiaries often require ongoing technical support, supervision, maintenance, or complementary resources.

Example

Schools receive assistive learning devices, but teachers have not been trained to use them effectively.

Key Lesson

Resource availability must be accompanied by capacity development and continued support.

3. Assuming External Conditions Remain Favourable

Programmes rarely operate in stable environments.

Economic shocks, climate events, political instability, disease outbreaks, or market fluctuations can significantly influence results.

Example

Farmers adopt improved agricultural practices, but prolonged drought results in poor harvests.

Key Lesson

Monitor contextual indicators alongside programme indicators.

4. Assuming Improved Outcomes Automatically Lead to Impact

Improved knowledge or increased production does not always translate into improved wellbeing.

Several intermediate factors influence long-term impact.

Example

Crop production increases, but household income remains unchanged because market prices decline.

Similarly, increased school enrolment does not automatically improve learning outcomes.

Key Lesson

Do not assume outcomes automatically become impact.

5. Assuming Implementation Quality Is Consistent

A programme may report that activities were completed, but implementation quality can vary considerably.

Questions worth asking include:

• Was the training delivered effectively?

• Were extension visits meaningful?

• Did facilitators possess the necessary technical skills?

• Were beneficiaries actively engaged?

High activity completion does not necessarily indicate high-quality implementation.

Key Lesson

Monitor both implementation coverage and implementation quality.

How to Test Theory of Change Assumptions

Organisations should routinely ask:

• Are beneficiaries applying what they learned?

• Which assumptions remain valid?

• What contextual factors have changed?

• Which assumptions present the highest risk?

• What evidence supports or challenges our Theory of Change?

Regular reflection enables adaptive programme management rather than waiting until the final evaluation.

Practical Checklist

Before approving your next programme report, ask:

☐ Have we measured behavioural change?

☐ Have we tested our key assumptions?

☐ Have external factors changed since programme design?

☐ Are outcomes occurring as expected?

☐ Do beneficiaries report barriers we did not anticipate?

☐ Does our monitoring system explain why results occurred?

If the answer to several of these questions is “No,” your Theory of Change may require review.

Key Message

A Theory of Change should not be viewed as a document prepared solely for donor proposals.

It is a living management tool that helps organisations understand how change occurs, identify emerging risks, and adapt implementation based on evidence.

Programmes are most effective when they continuously test their assumptions, learn from implementation, and refine their strategies in response to changing contexts.

Strong monitoring and evaluation systems therefore measure not only what was achieved, but also why change did—or did not—occur.

Lessons for Programme Managers, Researchers and Development Partners

Publication Date: August 2026
Author: Insight Research & Analytics
Estimated Reading Time: 5 minutes

Key Takeaways

• Delivering project activities successfully does not guarantee meaningful development outcomes.

• Strong monitoring systems should measure behavioural change and results, not only implementation progress.

• Every Theory of Change depends on assumptions that should be monitored and tested throughout implementation.

• External factors such as climate, markets, policies, and economic conditions can significantly influence programme performance.

• High-quality data are essential for understanding why programmes succeed or fail and for informing future programme design.

Introduction

Development programmes are often evaluated based on impressive implementation statistics.

A project may report that all planned trainings were completed, most beneficiaries received project inputs, attendance rates were high, and implementation remained on schedule.

At first glance, these results suggest success.

However, many endline evaluations reveal a different picture. Crop yields may increase only slightly, household incomes remain unchanged, or intended improvements in health, education, or food security fail to materialise.

This raises an important question:

Why do programmes that successfully deliver activities sometimes fail to achieve their intended impact?

Understanding this distinction is fundamental to effective Monitoring, Evaluation and Learning (MEL). Organisations that focus only on outputs risk overlooking the factors that ultimately determine whether a programme improves people’s lives.

Understanding the Results Chain

Every development programme follows a logical pathway from resources to long-term change.

Inputs → Activities → Outputs → Outcomes → Impact

Each stage represents a different level of results.

• Inputs are the resources invested in the programme.

• Activities are the actions carried out using those resources.

• Outputs are the immediate products or services delivered.

• Outcomes describe changes in knowledge, behaviour, or practices among beneficiaries.

• Impact reflects the long-term changes in people’s wellbeing and development.

A common mistake in programme monitoring is assuming that successful outputs automatically lead to successful outcomes and impact.

They do not.

Five Reasons Strong Outputs May Not Lead to Impact

1. External Factors Influence Programme Results

Development programmes operate within complex environments.

Even when implementation is successful, external conditions such as drought, floods, pest outbreaks, inflation, market price fluctuations, or policy changes may prevent beneficiaries from achieving expected results.

For example, farmers may adopt improved agricultural practices, but prolonged drought may still result in poor harvests.

Monitoring contextual risks alongside programme indicators helps explain why results differ from expectations.

2. Participation Does Not Always Lead to Behaviour Change

Training beneficiaries does not guarantee that they will apply what they have learned.

Likewise, distributing improved seeds does not ensure that they will be planted correctly or managed using recommended practices.

Monitoring systems should therefore include indicators that measure adoption, utilisation, and sustained behavioural change rather than simply participation.

Understanding the gap between participation and practice is essential for interpreting programme performance.

3. Theory of Change Assumptions May Not Hold

Every Theory of Change is built upon assumptions.

Examples include:

• Farmers will adopt the knowledge gained through training.

• Improved seeds will perform well under local environmental conditions.

• Increased agricultural production will translate into higher household income.

If one or more assumptions prove incorrect, the pathway from outputs to impact weakens.

Regularly reviewing these assumptions enables programmes to adapt before implementation challenges become long-term failures.

4. Monitoring Systems May Focus Too Heavily on Outputs

Many projects carefully monitor:

• Number of people trained.

• Number of inputs distributed.

• Number of meetings conducted.

While these indicators are important, they provide limited information about whether meaningful change has occurred.

Effective Monitoring, Evaluation and Learning systems should also track behavioural change, intermediate outcomes, beneficiary experiences, and contextual influences to support evidence-based decision making.

5. Data Quality Determines the Quality of Decisions

Reliable decisions require reliable evidence.

Before interpreting programme results, organisations should verify:

• Training attendance records.

• Survey methodology.

• Sampling procedures.

• Data completeness and consistency.

• Measurement techniques.

• Indicator calculations.

Data Quality Assessments (DQAs) help ensure that reported findings accurately represent programme performance and provide a sound basis for decision making.

Practical Questions for Programme Managers

Before concluding whether a programme has succeeded or failed, consider the following questions:

• Are we measuring behavioural change or only implementation outputs?

• Which assumptions underpin our Theory of Change, and have they been tested?

• What contextual factors may have influenced programme performance?

• Are our indicators sufficient to explain why results occurred?

• Have we assessed the quality and reliability of our data?

These questions encourage reflective practice and strengthen organisational learning.

Key Message

Successful implementation is an important achievement, but implementation alone does not deliver impact.

Development programmes create lasting change when they combine effective implementation with strong evidence, continuous learning, adaptive management, and rigorous monitoring and evaluation.

Organisations that understand why results occur—not simply what was delivered—are better positioned to improve programme performance, strengthen accountability, and maximise development impact.

A Practical Guide for Strengthening Evidence Before Reporting Results

Publication Date: August 2026
Author: Insight Research & Analytics
Estimated Reading Time: 5 minutes

Key Takeaways

• The credibility of an endline evaluation depends on the quality of the data collected.

• Data quality should be assessed before interpreting programme results or making recommendations.

• Simple quality checks can identify errors that significantly affect conclusions and decision making.

• A Data Quality Assessment (DQA) is not only about finding mistakes—it is about building confidence in the evidence.

• Investing in data quality improves accountability, learning, and evidence-based programme management.

Introduction

Endline surveys are often used to answer one of the most important questions in development programmes:

Did the project achieve its intended results?

The findings from an endline evaluation may influence future funding decisions, programme redesign, policy development, or organisational learning.

However, these decisions are only as reliable as the data on which they are based.

Before interpreting indicators, comparing baseline and endline results, or writing conclusions, organisations should first ask a more fundamental question:

Can we trust the data?

Data Quality Assessments (DQAs) help answer this question by verifying whether data are accurate, complete, consistent, timely, and reliable.

This Knowledge Note outlines five essential data quality checks that every endline survey should pass before results are reported.

Why Data Quality Matters

Poor-quality data can lead to:

• Incorrect programme conclusions.

• Misallocation of resources.

• Poor policy decisions.

• Reduced donor confidence.

• Missed opportunities for organisational learning.

High-quality data, on the other hand, strengthens accountability and ensures that programme decisions are grounded in credible evidence.

Five Essential Data Quality Checks

1. Verify the Sampling Method

The first question should be:

Does the sample accurately represent the target population?

Review whether:

• The sampling method matches the evaluation design.

• Sample size requirements were achieved.

• All intended geographic areas were covered.

• Selection bias was minimised.

• Replacement procedures were appropriately documented.

Common Risk

Convenience sampling may produce misleading results that cannot be generalised to the wider beneficiary population.

Practice Tip

Always compare the achieved sample with the planned sample described in the evaluation protocol.

2. Check Data Completeness and Consistency

Missing or inconsistent information can distort findings and reduce confidence in reported indicators.

Review:

• Missing responses.

• Duplicate records.

• Logical inconsistencies.

• Outliers.

• Incorrect skip patterns.

Example

A respondent reports having no children but later answers questions about children’s school attendance.

Such inconsistencies should be identified and resolved before analysis.

3. Validate Indicator Calculations

Indicators should never be accepted simply because they appear in a dashboard or statistical output.

Verify:

• Indicator definitions.

• Numerators and denominators.

• Formula calculations.

• Unit of measurement.

• Alignment with the Monitoring and Evaluation Plan.

Example

An indicator reporting “percentage of trained farmers adopting climate-smart agriculture” should clearly define what constitutes adoption and how the percentage was calculated.

Practice Tip

Recalculate a sample of indicators independently to confirm reported results.

4. Assess the Reliability of Data Collection

Reliable data depend on consistent data collection procedures.

Review whether:

• Enumerators received adequate training.

• Survey tools were piloted.

• Field supervision was conducted.

• Interview protocols were followed consistently.

• Electronic data collection tools functioned correctly.

Poor field implementation may introduce interviewer bias, measurement error, or inconsistent interpretation of survey questions.

5. Compare Findings with Other Sources of Evidence

Survey findings should be interpreted alongside other available information.

Cross-check results using:

• Routine monitoring data.

• Administrative records.

• Baseline findings.

• Field observations.

• Key informant interviews.

• Focus group discussions.

This process, often referred to as triangulation, strengthens confidence in evaluation findings and helps explain unexpected results.

Example

If survey respondents report high adoption of agricultural practices but field observations indicate limited implementation, further investigation is required before drawing conclusions.

Practical Checklist Before Finalising an Endline Report

Before submitting your report, confirm the following:

☐ The sample accurately represents the target population.

☐ Data have been cleaned and verified.

☐ Indicators have been independently validated.

☐ Data collection procedures were implemented consistently.

☐ Survey findings have been triangulated with other evidence.

☐ Any data limitations have been clearly documented.

Common Mistakes to Avoid

Many organisations make avoidable errors when preparing endline reports.

Examples include:

• Reporting results without conducting data cleaning.

• Ignoring missing or inconsistent records.

• Comparing indicators that were measured differently at baseline and endline.

• Assuming statistical significance without appropriate analysis.

• Drawing conclusions without considering contextual factors.

Recognising these pitfalls strengthens the credibility of evaluation findings.

Key Message

High-quality decisions require high-quality data.

Conducting an endline survey is only the beginning of the evaluation process. Before interpreting results, organisations should systematically verify the quality, reliability, and consistency of their data.

A robust Data Quality Assessment helps ensure that programme conclusions are evidence-based, transparent, and suitable for informing future decisions.

Ultimately, data quality is not merely a technical requirement—it is the foundation of credible monitoring, evaluation, learning, and accountability.

A Practical Guide to Results-Based Management for Development Programmes

Publication Date: August 2026
Author: Insight Research & Analytics
Estimated Reading Time: 5 minutes

Key Takeaways

• The results chain provides a logical framework for planning, monitoring, and evaluating development programmes.

• Outputs, outcomes, and impact represent different levels of change and should never be used interchangeably.

• Measuring activities alone does not demonstrate programme success.

• Strong Monitoring, Evaluation and Learning (MEL) systems monitor progress across the entire results chain.

• Understanding the results chain helps organisations improve accountability, learning, and evidence-based decision making.

Introduction

One of the most common challenges in programme management is confusion between outputs, outcomes, and impact.

Many project reports celebrate achievements such as:

• 5,000 farmers trained.

• 10 schools rehabilitated.

• 2,000 textbooks distributed.

• 50 health workers trained.

While these are important accomplishments, they do not necessarily demonstrate that people’s lives have improved.

Development programmes exist to create change—not simply to deliver activities.

Understanding the results chain enables organisations to distinguish between implementation progress and real development outcomes.

It also helps programme managers answer one of the most important questions in Monitoring, Evaluation and Learning:

Did our activities create meaningful and lasting change?

What is the Results Chain?

The results chain is a logical sequence that explains how programme resources are expected to produce long-term development impact.

It links programme investments to measurable change.

The standard results chain is:

Inputs
  ↓
Activities
  ↓
Outputs
  ↓
Outcomes
  ↓
Impact

Each level answers a different management question.

Results Level

Key Question

Inputs - What resources are required?

Activities -What actions will be implemented?

Outputs - What products or services were delivered?

Outcomes - What changed because of the programme?

Impact - What long-term difference was achieved?

Understanding these distinctions is essential for designing effective monitoring systems.

Understanding Each Level

1. Inputs

Inputs are the financial, human, material, and technical resources invested in a programme.

Examples include:

• Funding

• Staff

• Equipment

• Vehicles

• Training materials

• Information systems

Inputs alone do not create change.

They simply make programme implementation possible.

2. Activities

Activities are the actions undertaken using programme resources.

Examples include:

• Conducting training workshops.

• Distributing agricultural inputs.

• Constructing classrooms.

• Providing extension services.

• Collecting survey data.

Activities describe what the programme does.

They do not describe the results achieved.

3. Outputs

Outputs are the immediate products or services generated by programme activities.

Examples include:

• Number of farmers trained.

• Number of schools rehabilitated.

• Number of teachers trained.

• Number of surveys completed.

• Number of extension visits conducted.

Outputs answer the question:

“What did the programme deliver?”

However, outputs do not indicate whether beneficiaries changed their behaviour or experienced improved wellbeing.

4. Outcomes

Outcomes represent changes in behaviour, knowledge, skills, attitudes, practices, or access to services that occur because of programme outputs.

Examples include:

• Farmers adopt climate-smart agricultural practices.

• Teachers apply learner-centred teaching methods.

• Households improve hygiene practices.

• Communities increase utilisation of health services.

Outcomes answer the question:

“What changed because of the programme?”

Outcomes often require time and continued support to achieve.

5. Impact

Impact refers to the long-term changes in people’s lives resulting from sustained programme outcomes.

Examples include:

• Reduced poverty.

• Improved food security.

• Higher household incomes.

• Improved learning outcomes.

• Reduced child mortality.

Impact answers the question:

“What lasting difference did the programme make?”

Because many external factors influence impact, attribution is often more challenging than measuring outputs.

Practical Example

Consider an agricultural development programme.

Results Level

Example

Input

Funding, agricultural experts, improved seed

Activity

Train farmers and distribute improved seed

Output

5,000 farmers trained and supplied with seed

Outcome

Farmers adopt improved farming practices

Impact

Increased agricultural productivity, higher household income and improved food security

This example demonstrates that each level builds upon the previous one, but success at one level does not guarantee success at the next.

Common Mistakes in Results-Based Management

Mistake 1: Confusing Activities with Outputs

Activity:

Conduct farmer training.

Output:

5,000 farmers trained.

The activity is the action.

The output is the result of completing that action.

Mistake 2: Assuming Outputs Equal Outcomes

Distributing textbooks does not automatically improve learning.

Training health workers does not automatically improve patient care.

Providing improved seed does not automatically increase crop yields.

Behaviour change must occur before outcomes can be achieved.

Mistake 3: Measuring Only What Is Easy

Many programmes monitor:

• Meetings conducted.

• Workshops completed.

• Participants trained.

While these indicators are useful, they provide limited insight into programme effectiveness.

Balanced monitoring systems measure outputs, outcomes, and impact.

Mistake 4: Ignoring External Factors

Economic conditions, climate, political changes, and social norms may influence programme outcomes regardless of implementation quality.

Results should always be interpreted within their broader context.

Why the Results Chain Matters

A well-defined results chain helps organisations:

• Design stronger programmes.

• Develop meaningful indicators.

• Monitor implementation effectively.

• Identify where progress is slowing.

• Improve accountability.

• Strengthen programme learning.

• Support evidence-based decision making.

It also provides a common language for programme teams, donors, government institutions, and evaluation partners.

Practical Checklist

Before finalising your programme design or evaluation report, ask:

☐ Have we clearly distinguished activities from outputs?

☐ Do our indicators measure outcomes rather than only implementation?

☐ Can we demonstrate behavioural change?

☐ Have we identified the assumptions linking each stage?

☐ Have we considered contextual factors affecting programme performance?

☐ Are we measuring long-term impact appropriately?

If several answers are “No,” your results framework may require strengthening.

Key Message

The success of a development programme cannot be judged solely by the number of activities completed or beneficiaries reached.

True programme success is measured by the positive and sustainable changes experienced by people and communities.

Results-Based Management encourages organisations to look beyond implementation and ask a more important question:

Did our work improve lives, and what evidence demonstrates that change?

Understanding the results chain enables programme managers, researchers, and development partners to answer this question with confidence and credibility.

A Practical Guide to Developing Meaningful Indicators for Research, Monitoring and Evaluation

Publication Date: August 2026
Author: Insight Research & Analytics
Estimated Reading Time: 5 minutes

Key Takeaways

• Indicators translate programme objectives into measurable evidence.

• Good indicators measure progress towards results rather than simply tracking activities.

• The SMART framework helps ensure indicators are practical, measurable, and useful for decision making.

• Every indicator should have a clear definition, data source, frequency of collection, and responsible person.

• Strong indicators improve accountability, learning, reporting, and programme performance.

Introduction

Every development programme seeks to answer a fundamental question:

How will we know whether we are making progress?

The answer lies in well-designed indicators.

Indicators are the foundation of effective Monitoring, Evaluation and Learning (MEL). They provide objective evidence of progress, help programme teams monitor implementation, and enable donors and stakeholders to assess whether intended results have been achieved.

However, many programmes rely on indicators that are vague, difficult to measure, or poorly aligned with programme objectives.

Examples include:

• Community empowerment improved.

• Farmers benefited from training.

• Schools became more inclusive.

While these statements describe desirable outcomes, they cannot be measured objectively.

Well-designed indicators convert broad objectives into measurable evidence that supports informed decision making.

What is an Indicator?

An indicator is a measurable variable used to assess progress toward achieving a specific objective, output, outcome, or impact.

Indicators answer questions such as:

• How much was achieved?

• How many people were reached?

• What changed?

• By how much did it change?

• Is the programme moving in the intended direction?

Indicators do not measure everything.

They measure the most important evidence needed to determine programme performance.

The SMART Framework

A good indicator should be SMART.

S – Specific

The indicator should measure one clearly defined result.

Poor Indicator

Farmers improved their livelihoods.

Better Indicator

Percentage of participating farmers reporting increased household agricultural income.

Specific indicators reduce ambiguity and improve consistency in reporting.

M – Measurable

The indicator must be quantifiable or objectively verifiable.

Ask yourself:

• Can this be counted?

• Can it be observed?

• Can it be measured consistently?

Example

Number of schools with functional disability-accessible toilets.

This indicator can be verified through observation.

A – Achievable

Indicators should be realistic given available resources, data systems, and implementation capacity.

Avoid indicators that require expensive or impractical data collection unless they are essential for programme decision making.

Good indicators balance usefulness with feasibility.

R – Relevant

Every indicator should directly measure progress toward the programme objective.

For example:

Objective:

Improve reading skills among primary school learners.

Relevant Indicator:

Percentage of Grade 4 learners achieving minimum reading proficiency.

Irrelevant Indicator:

Number of teacher meetings conducted.

Although teacher meetings may support implementation, they do not directly measure reading outcomes.

T – Time-bound

Indicators should specify the period over which change will be measured.

Examples:

• By the end of Year 1.

• Quarterly.

• Annually.

• At baseline and endline.

Timeframes enable organisations to monitor progress and compare performance over time.

Linking Indicators to the Results Chain

Different levels of the results chain require different indicators.

Results Level

Example Indicator

Input

Budget disbursed for teacher training

Activity

Number of teacher training sessions conducted

Output

Number of teachers successfully trained

Outcome

Percentage of trained teachers applying learner-centred teaching methods

Impact

Percentage improvement in learner reading proficiency

Measuring only outputs provides limited insight into programme effectiveness.

A balanced indicator framework should capture progress across the results chain.

Common Mistakes in Indicator Development

Mistake 1: Measuring Activities Instead of Results

Activity:

Conduct nutrition awareness sessions.

Indicator:

Number of awareness sessions conducted.

This measures implementation—not change.

A stronger outcome indicator would be:

Percentage of caregivers adopting recommended child feeding practices.

Mistake 2: Using Vague Language

Words such as:

• Improved

• Enhanced

• Better

• Increased awareness

should be supported by measurable definitions.

Instead of:

Improved community participation.

Use:

Percentage of community members attending at least three village development meetings during the reporting period.

Mistake 3: Ignoring Baseline Values

Without a baseline, it is difficult to determine whether change has occurred.

Every indicator should have:

• Baseline value.

• Target value.

• Actual value.

This allows progress to be monitored objectively.

Mistake 4: Too Many Indicators

More indicators do not necessarily produce better monitoring.

Focus on indicators that provide meaningful evidence for programme management and decision making.

Quality is more important than quantity.

Building an Indicator Reference Sheet

Every indicator should be documented using an Indicator Reference Sheet (IRS) that includes:

• Indicator title.

• Indicator definition.

• Purpose.

• Unit of measurement.

• Numerator.

• Denominator (where applicable).

• Data source.

• Data collection method.

• Frequency of collection.

• Responsible person.

• Data quality considerations.

An Indicator Reference Sheet promotes consistency and reduces errors during implementation and reporting.

Practical Checklist

Before approving an indicator, ask:

☐ Does it measure a programme result?

☐ Is it specific and clearly defined?

☐ Can it be measured objectively?

☐ Is the required data available?

☐ Does it align with the programme objective?

☐ Does it have a baseline and target?

☐ Is there an Indicator Reference Sheet?

If several answers are “No,” the indicator should be revised.

Key Message

Indicators are more than reporting requirements.

They are decision-making tools that help organisations understand whether programmes are delivering meaningful results.

Well-designed indicators provide credible evidence, strengthen accountability, improve programme learning, and support adaptive management.

The most effective monitoring systems do not measure everything.

They measure what matters.