Results Framework: Organizing Indicators by Results Level

When Is a Results Framework the Right Tool?

A results framework helps articulate intended results and expected causal links for a project, program, or portfolio, and connects them to monitoring evidence. It can include outputs as well as outcomes and impact. Use it when:

• Managing a portfolio of programs: to aggregate results data across multiple projects and identify patterns in what works
• Agreed reporting needs: adapt the structure to the project's reporting needs and the applicable funding agreement
• Designing monitoring systems: to ensure your indicator selection focuses on outcomes and impacts, not just activities and outputs
• Conducting portfolio evaluations: to assess whether a collection of interventions collectively achieved intended results
• Communicating with non-technical stakeholders: a results framework is more accessible than individual logframes because it focuses on results, not activities

A results framework can support a single project. Pair it with a detailed logframe for operational planning or a theory of change to elaborate mechanisms and alternatives. The framework can support design and causal explanation as well as tracking. A more detailed theory of change may unpack mechanisms, assumptions, and alternatives.

How Does a Results Framework Work?

A results framework organizes indicators by results level to create a structured view of performance. The development process follows these steps:

1. Start with the strategic context. Identify the high-level development goal or outcome that your portfolio seeks to contribute to. This is typically drawn from a donor country strategy, national development plan, or organizational strategic plan. The results framework answers: "What strategic outcome are we tracking?"

2. Define the results hierarchy. Map the expected sequence of change from immediate results through to long-term impact. This typically includes: immediate results (short-term changes), intermediate results (medium-term changes), and development outcome (long-term impact). Each level represents a different time horizon and different level of program influence.

3. Select indicators for each level. Choose the smallest feasible set that captures decision-critical results and important causal links. Prioritize outcome-level indicators over output-level indicators. Ensure indicators are SMART (specific, measurable, achievable, relevant, time-bound) and include disaggregation requirements where appropriate.

4. Establish baselines and targets. For change indicators, document the needed starting reference with its source and date. Record a target at the relevant time and mark missing baselines explicitly; other measures may have different reference needs. Targets should be ambitious but achievable, based on evidence from similar contexts or historical performance.

5. Document data sources and collection methods. Specify where each indicator's data will come from (surveys, routine monitoring systems, administrative data, evaluations) and how it will be collected. This ensures data collection is feasible and sustainable throughout the program lifecycle.

6. Assign responsibility and timing. For each indicator, identify who is responsible for data collection, who analyses the data, and when reporting occurs. This creates accountability and ensures data flows into decision-making processes.

7. Build in review mechanisms. Schedule regular reviews of the results framework (typically quarterly or semi-annually) to assess whether indicators remain relevant, whether targets are being met, and whether the framework needs revision based on implementation experience.

Key Components

A well-constructed results framework includes these essential elements:

• Strategic outcome statement: a clear description of the high-level development goal the portfolio seeks to contribute to, typically aligned with donor or national strategies
• Results hierarchy: the structured sequence of expected change from immediate through intermediate to long-term outcomes, showing the logical progression of results
• Indicator matrix: a structured table listing each indicator by results level, including the indicator definition, disaggregation requirements, and measurement frequency
• Reference values: initial conditions where needed for change measurement, with source, date, exposure, and limitations
• Target values: the expected achievement levels at specific points in time, typically mid-term and end-of-program
• Data sources: the origin of each indicator's data (surveys, routine monitoring, administrative records, evaluations)
• Collection methods: the approach for gathering each indicator's data (household surveys, facility assessments, key informant interviews, routine data review)
• Reporting responsibilities: clear assignment of who collects, analyses, and reports each indicator's data
• Assumptions and risks: external conditions that could influence achievement of results, documented alongside relevant results levels

Best Practices

Balance delivery and change measures. Include the outputs and outcomes needed to test expected links and inform decisions. There is no universal minimum outcome-indicator percentage. A focused project framework with outputs and causal links is valid.

Align with donor strategies. Your results framework should directly map to donor strategic priorities. When designing indicators, ask: "Does this indicator help us demonstrate contribution to the donor's country strategy?" This alignment makes reporting more efficient and demonstrates strategic coherence.

Ensure feasibility of data collection. Before finalizing indicators, assess whether data can realistically be collected at the required frequency. An indicator with perfect theoretical value is useless if no one can collect the data. Consider existing data systems, resource constraints, and beneficiary burden.

Build in disaggregation from the start. Specify which indicators should be disaggregated (by gender, age, location, disability, etc.) and ensure your data collection systems can capture these breakdowns. Retrofitting disaggregation requirements is costly and often results in data gaps.

Review and revise regularly. A results framework is not a static document. Schedule formal reviews at least twice per year to assess whether indicators remain relevant, whether targets are achievable, and whether new evidence suggests the framework needs adjustment.

Common Mistakes

Confusing results frameworks with logframes. A logframe is project-specific and includes activities, outputs, outcomes, and impact with detailed indicators and targets. A results framework can represent a single project or a portfolio and can include outputs, outcomes, causal links, and assumptions. Terminology overlaps; choose the structure required by the decision.

Including measures without a clear use. Assess burden and decision value rather than applying a fixed numerical cap. Preserve measures required by the applicable agreement and explain any proposed changes.

Leaving reference needs unspecified. Define baselines where change measures need them and preserve dates, sources, and exposure information. Counts or valid post-test causal designs have different needs. A framework alone does not establish whether the intervention caused observed results.

Treating it as a reporting artefact only. Many organizations design results frameworks solely for donor reporting, then ignore them during implementation. A results framework should drive management decisions, not just satisfy compliance requirements. Use it to identify problems early and adapt programs accordingly.

Failing to account for attribution. A results framework tracks results, but doesn't prove your program caused them. Be clear that results framework data documents observations; even a contribution claim needs an explicit evidence-based causal argument. Use complementary approaches like contribution analysis or impact evaluation when attribution is required.

Examples

These scenarios and results are illustrative. A framework tracks observations; a causal contribution claim needs an additional justified design and evidence.

Bilateral Donor Country Strategy, Kenya, 2018-2023

A five-year bilateral donor country strategy developed a results framework tracking progress across four strategic objectives: democratic governance, economic growth, health outcomes, and humanitarian assistance. Each objective had 3-5 outcome-level indicators with baselines established during design. The framework enabled portfolio-level analysis showing a 15% reduction in child mortality alongside intervention delivery; this pattern alone did not identify a causal contribution, while governance programs showed mixed results. The results framework identified which strategic objectives were on track and which needed adaptive management, informing mid-course corrections that improved overall portfolio performance.

Water Security Program - East Africa

A regional water security program spanning three countries developed a results framework with three levels: immediate results (access to water infrastructure), intermediate results (sustainable water use practices), and development outcome (improved household water security). The framework included 12 indicators, 8 of which measured outcomes rather than outputs. Baselines were established through a regional household survey before program implementation. Semi-annual reviews identified that intermediate results were lagging in one country due to community engagement gaps, prompting program adaptation. The results framework functioned as a management tool, not just a reporting requirement.

Education Portfolio - South Asia

A multi-project education portfolio developed a results framework aligned with national education strategy indicators. The framework tracked literacy rates, secondary completion rates, and learning outcomes across three projects in two countries. By aggregating data across projects, the portfolio identified that literacy improvements were concentrated in urban areas while rural areas showed stagnation. This pattern analysis informed reallocation of resources to rural interventions. The results framework enabled cross-project learning that individual project logframes could not have revealed.

Compared To

A results framework is one of several frameworks used in program design and monitoring. The key differences:

Relevant Indicators

38 indicators across 5 major donor frameworks (USAID, FCDO, World Bank, EU, Global Fund) relate to results framework design and use:

• Portfolio alignment: "Proportion of portfolio programs with results frameworks aligned to donor strategic objectives" (USAID)
• Outcome focus: "Percentage of results framework indicators measuring outcomes rather than outputs" (FCDO)
• Baseline establishment: "Percentage of results framework indicators with baselines established before implementation" (World Bank)
• Framework revision: "Frequency of results framework review and update during program implementation" (EU)

Proposal Context

A results framework can express program logic at project, program, or strategy level. Match its terminology and format to the actual proposal instructions. Check that results, causal links, assumptions, and indicators agree with the theory of change and logframe. Do not infer quality from a fixed number of objectives or a universal output/outcome quota.

A useful proposal framework makes results and expected relationships clear, with feasible measurement and explicit assumptions. Document operational details through the performance management plan or an equivalent MEL plan.

Method Source

World Bank IEG, Designing a Results Framework for Achieving Results (2012), pp. 7-8 and steps 4-5. This is methodological guidance, not a funding requirement.