Definition

A results framework is a hierarchical diagram of the objectives an organisation or programme intends to achieve, showing how lower-level results contribute to higher-level ones. In its classic USAID form the hierarchy runs:

• Goal — the high-level development condition the strategy contributes to.
• Development Objectives (DOs) — the significant changes the mission or programme is accountable for delivering within the strategy period.
• Intermediate Results (IRs) — the results that must be achieved for a Development Objective to be reached, with sub-IRs beneath them where the logic needs another level.

Each element carries indicators, and the whole thing is presented as a single diagram: one goal at the top, a small number of Development Objectives beneath it, and the intermediate results that feed each one.

The distinction that actually matters

A results framework and a logframe are frequently described as the same thing in different shapes. They are not, and conflating them causes real problems in practice.

	Results framework	Logframe
Unit	A strategy, portfolio or country programme	A single project or contract
Time horizon	The strategy period, typically five years	The project period
Purpose	Organise and align objectives across many interventions	Specify and make accountable one intervention
Form	Hierarchical diagram	Four-column matrix
Contains activities?	No — it stops at results	Yes — the activities row is part of it
Contains assumptions?	Usually not as a formal column	Yes, as a dedicated column
Answers	“What are we trying to achieve, and how does it fit together?”	“What will this project deliver, how will we know, and what must hold?”

A results framework is a strategy artefact. It exists so that a mission with fifteen projects can see whether they collectively add up to the Development Objective, and so that a new project can be assessed on whether it contributes to something the strategy already wants. It deliberately excludes activities, because activities belong to projects and the framework outlives any one of them.

A logframe is a project artefact. It exists so that one implementer can be held to one set of deliverables.

The correct relationship: individual project logframes should map upward into the results framework’s intermediate results. When they do, the portfolio is coherent. When several projects claim to contribute to the same IR and none of their outcome indicators can be aggregated, the framework has revealed a real problem, which is one of the things it is for.

The supporting stack

A results framework on its own is a diagram. What makes it operational in USAID practice is the documentation stack beneath it:

• PMP — Performance Management Plan. The mission-level plan for how the framework will be monitored: which indicators, who collects them, at what frequency, how data quality is assured, when the framework will be reviewed.
• PIRS — Performance Indicator Reference Sheet. One per indicator. It fixes the precise definition, the unit of measure, the disaggregation required, the data source, the collection method and frequency, known data limitations, and the baseline and targets. The PIRS is the discipline that stops “number of people reached” meaning four different things in four reports.
• ITT — Indicator Tracking Table. The running record of targets against actuals by period, which is what gets reviewed and what feeds reporting.

The stack, not the diagram, is where the value sits. A results framework without PIRS-equivalent definitions produces numbers that cannot be compared across projects — which defeats the purpose of having a portfolio-level framework at all.

Who uses it

USAID is the originator and the heaviest user; the results framework is the standard structure of a Country Development Cooperation Strategy. The form has been adopted well beyond it: the World Bank uses results frameworks for programme and country partnership strategies, multilateral funds use them for portfolio-level reporting, and many INGOs use one for their own organisational strategy while running logframes at project level.

Note that the 2025 contraction in US development funding changed the market for this framework, not its logic. Organisations that inherited a results framework from a USAID-funded programme and now report to different funders generally find the structure still works — it is the indicator definitions that need renegotiating.

Artefacts it produces

• The framework diagram itself.
• A Performance Management Plan or equivalent monitoring plan.
• An indicator reference sheet per indicator — the PIRS discipline, whatever it is called locally.
• An indicator tracking table of targets against actuals by period.
• A portfolio map showing which projects contribute to which intermediate result.

How it relates to the other frameworks

• The logframe sits underneath it, one per project, and maps upward into the intermediate results.
• A theory of change should sit behind it. The results framework shows that IRs contribute to a DO; it does not explain why, and it has no assumptions column in which to say. Strategies that have both are markedly more defensible at mid-term review.
• The OECD-DAC criteria are how the strategy is judged at evaluation — particularly coherence, which is close to being the results framework’s own internal question asked from outside.
• Value for money is usually assessed at this level rather than at project level, because the trade-offs between the 4Es only become visible across a portfolio.

Common mistakes

1. Using it as a logframe. Adding an activities row and an assumptions column to a results framework produces a large, unwieldy logframe for a strategy nobody implements directly.
2. Skipping the indicator reference sheets. Without them the framework aggregates numbers that mean different things. This is the single most common cause of portfolio reporting that quietly stops being trusted.
3. Too many Development Objectives. Three or four is a strategy. Nine is a list of everything the organisation does, arranged vertically.
4. Intermediate results that are outputs. An IR is a result — a change in condition, behaviour or capability. “Training curriculum developed” is an output belonging in a project logframe.
5. No portfolio map. If nobody can say which projects contribute to IR 2.3, the framework is decorative.
6. Never revisiting it. The framework is set for the strategy period, but the indicator targets within it should be reviewed annually against actuals, which is what the ITT exists to enable.

How Monival supports this

Honestly stated: Monival’s shipped framework view is the grouped logframe matrix, not a results framework diagram. The results framework view exists as an option in the framework switcher but is not yet enabled, and the product does not currently render a goal-to-DO-to-IR hierarchy as a diagram.

What is genuinely usable today is the layer underneath. Monival holds organisation-level indicators that are defined once and reused — each with a baseline, a target, a collection frequency, a data source and a means of verification — which is the PIRS discipline expressed as a data model rather than a Word template. Actuals are recorded by period against each indicator, giving you the substance of an indicator tracking table. Indicators can be fed directly from field data by linking them to form questions, aggregating submissions as a count, a sum or a distinct count, with disaggregation by other questions on the same form.

Result nodes are organised by programme, so a multi-project organisation can keep separate frameworks side by side. Rolling those programmes up into a single portfolio diagram is not something the SaaS does.

For organisations that need genuine portfolio-level results management — cross-programme aggregation, alignment reporting, and reconciliation against finance — Sibasi delivers it as an implemented solution on Microsoft Power Platform and Dynamics 365 Business Central. That is a consulting engagement with live client references behind it, not a plan tier.