Results Chain

Definition

A results chain is the sequential hierarchy of change that shows how a programme is expected to create impact. It maps the logical connection from activities (what you do) through outputs (direct products) and outcomes (short and medium-term changes) to impact (long-term effects). The results chain is the backbone of any theory of change — it answers the question "how does doing X lead to Y?"

Each level of the chain represents a different type of result, with increasing distance from programme control but increasing significance for the target population. A well-constructed results chain makes explicit the causal assumptions that connect your programme actions to the change you seek.

Why It Matters

The results chain serves three critical functions in M&E practice:

Design validation. It forces you to test whether your activities logically connect to your intended impact. If you cannot articulate a plausible pathway from what you do to the change you seek, your programme design needs revision before implementation begins.

Measurement guidance. Each level of the results chain tells you what to measure. Activities (are you doing what you planned?), outputs (what did you produce?), outcomes (what changed?), and impact (what long-term difference?). Without a clear results chain, indicator selection becomes arbitrary.

Communication clarity. A simple results chain diagram can explain your programme logic to donors, communities, and staff in a way that narrative descriptions cannot. It shows not just what you're doing, but why you expect it to matter.

In Practice

A results chain typically appears as a horizontal or vertical flow diagram with four to five levels:

Inputs → Activities → Outputs → Outcomes → Impact

For example, a maternal health programme might map:

Activities: Train midwives, distribute delivery kits, conduct community awareness sessions
Outputs: 200 midwives trained, 5,000 delivery kits distributed, 50 community sessions held
Outcomes: Increased skilled birth attendance, higher facility delivery rates, improved recognition of danger signs
Impact: Reduced maternal mortality rates

At each link in the chain, you should document assumptions — the conditions that must hold true for the causal connection to work. "Training midwives leads to increased skilled attendance" assumes midwives remain in the health system, communities trust them, and facilities have the equipment to support their work.

The results chain is often visualized alongside a logframe, which adds the operational details (targets, indicators, verification sources) to each level. But the results chain itself focuses on the causal logic, not the management specifications.

Best Practices

Start with the impact. Work backwards from the long-term change you seek. Define impact precisely enough to be measurable, then ask "what outcomes must occur for this impact to happen?" Keep asking until you reach the level of activities you can directly control. This backward design prevents the common mistake of starting with activities and hoping they lead somewhere meaningful.

Make assumptions explicit. At each link in the chain, document what must be true for the causal connection to hold. These assumptions become the most important things to monitor — they are your programme's risk factors and learning opportunities.

Keep it testable. Every causal link should be something you can investigate through monitoring or evaluation. If you cannot conceive of evidence that would support or refute a connection, the link is too vague to be useful.

Distinguish outcomes from impact. Outcomes are changes your programme can reasonably contribute to within its timeframe. Impact is the broader, longer-term change that may require multiple programmes working together. Don't claim impact your programme cannot influence.

Use the chain to select indicators. Each level should have at least one indicator that tells you whether expected results are occurring. If a level has no indicator, you're not monitoring that part of your theory.

Common Mistakes

Skipping levels. A results chain that jumps from activities to impact without intermediate outcomes is not a causal explanation — it's a wish. Each level represents a necessary step in the change process, and skipping levels means you haven't thought through how change actually happens.

Confusing outputs with outcomes. Outputs are what you produce; outcomes are what change as a result. "500 farmers trained" is an output. "Farmers adopt improved practices" is an outcome. Many programmes measure only outputs because they're easier to count, but outputs alone tell you nothing about whether your programme matters.

Linear thinking in complex systems. A results chain implies causality, but real-world change is rarely linear. Use the chain as a working hypothesis, not a definitive map. Be prepared to revise it as implementation reveals unexpected pathways and feedback loops.

No assumptions documented. A results chain without assumptions is incomplete. The causal connections only hold if certain conditions are met, and those conditions are often where programmes fail. If you haven't documented your assumptions, you haven't finished the chain.

Examples

Education Programme — Sub-Saharan Africa

A secondary education quality programme mapped its results chain as: teacher training → improved teaching practices → student engagement → learning outcomes → educational attainment. The key insight was documenting the assumption "trained teachers remain in schools" — when mid-term data showed high turnover among trained teachers, the programme added retention activities (career progression pathways, recognition systems) to strengthen the chain. The results chain functioned as a diagnostic tool.

WASH Initiative — South Asia

A water and sanitation programme initially mapped a simple chain: infrastructure construction → water access → health improvements. Outcome harvesting revealed an important missing link: behaviour change was required between access and health. The revised chain added a hygiene behaviour outcomes level, which then required new indicators and monitoring activities. The results chain evolved to reflect implementation reality.

Governance Reform — Latin America

A legislative capacity programme mapped: training legislators → improved legislative scrutiny → better policy outcomes → reduced corruption. The results chain made explicit the assumption "political will exists to act on legislative recommendations" — a condition that varied significantly across the programme's jurisdictions. This awareness shaped adaptive management decisions about where to focus efforts.

Compared To

| Feature | Results Chain | Theory of Change | Logframe | |---------|--------------|---------|----:--| | Primary purpose | Map the hierarchy of change | Explain causal logic and assumptions | Manage implementation with targets | | Level of detail | Sequential levels only | Pathways, assumptions, evidence ratings | Activities, outputs, outcomes, impact with indicators and targets | | Assumptions | Should be documented | Central feature | Listed but often treated as secondary | | Best for | Design validation, communication | Design, evaluation, learning | Operational planning, donor reporting |

A results chain is a component of a theory of change — it shows the "what" of the causal pathway. A theory of change adds the "why" (evidence base) and the "what if" (assumptions and risks). A logframe takes the results chain and adds operational specifications (targets, indicators, verification).

Relevant Indicators

Approximately 12 indicators across major donor frameworks relate to results chain design and use:

Causal pathway documentation — "Proportion of programme results with documented causal pathways linking activities to outcomes" (USAID)
Results chain completeness — "Number of results chain levels with defined indicators and targets" (DFID)
Assumption monitoring — "Frequency of assumption testing through routine monitoring data" (World Bank)

Related Tools

Logic Model Builder — Interactive tool for constructing visual results chains and theories of change
ToC Template — Guided template for developing narrative theories of change with assumption documentation