Sopact is a technology based social enterprise committed to helping organizations measure impact by directly involving their stakeholders.
Copyright 2015-2026 © sopact. All rights reserved.
A results framework orders results into a hierarchy — goal, intermediate results, sub-results, indicators — with examples, a template, and how it differs from a theory of change and a logframe.
A results framework is a diagram that orders a program's intended results into a hierarchy — from a top-level goal, down through a strategic objective and intermediate results to sub-results — with an indicator attached to each level. It is the results-based management tool development funders use to show how day-to-day work ladders up to a long-term goal. It orders the what; it does not explain the why.
A results framework shows that improved skills sit under increased employment without saying why the link should hold — that explanation is a theory of change's job. This guide walks the results hierarchy, gives worked examples, compares the framework to a theory of change and a logframe, and shows how to keep the indicators live rather than reporting them by hand once a year.
Key takeaways
A results framework reads top to bottom: the goal is the long-term change the program contributes to, the strategic objective is the end result it is accountable for, intermediate results are the outcomes that must happen to reach it, sub-results build toward each intermediate result, and an indicator is attached to every level. Each level is a result — a change — not an activity.
The distinction that keeps a results framework honest is that every box is a result, phrased as a change achieved, not a task performed. “Deliver training” is an activity; “participants demonstrate the skill” is a result. Worked examples across sectors, and a prompt recipe to draft one, follow below. The causal layer the hierarchy sits on is on theory of change.
The classic results framework is drawn for a proposal and revisited at the annual review — a clean hierarchy that looks like management but functions like a diagram. Between reviews the program runs and the indicator values accumulate somewhere else, so the framework and the evidence never meet until reporting time, a year after the decisions the numbers should have informed.
Sopact calls the alternative The Live Results Hierarchy: every level of the hierarchy carries an indicator wired to arriving data, so a slipping intermediate result is visible mid-year and a goal-level number drills to the sub-result and the response behind it. The difference is a data-model one — a static chart orders intentions, while a live hierarchy tracks progress against them. Where this sits in the wider practice is on monitoring and evaluation and impact measurement and management.
The stage below runs one reporting cycle both ways.
The results framework is a results-based management tool from international development. USAID popularized the nested results-framework format, the World Bank and other agencies built results-based management around it, and the logical framework — the logframe — is its matrix sibling. These formats did real work: they forced programs to state results rather than activities and to attach an indicator to each.
What the format cannot do on its own is stay current. A results framework in a proposal document has no way to pull an indicator value, so the hierarchy is only as fresh as the last person who updated it by hand. A live results framework wires each level to the data that measures it.
The one test: pick any indicator on the framework and ask whether its current value is one query away, or a request someone fulfills manually at the annual review. If it cannot be pulled live, the framework is a plan, not a management tool. The matrix version is on logframe.
A results framework orders results into a hierarchy, a theory of change explains why each level produces the next, and a logframe adds indicators, means of verification, and assumptions in a matrix. They are three presentations of the same underlying logic, not three competing plans — which is why the cleanest workflow builds the logic once and switches the format. The structural comparison with a logic model is on theory of change vs logic model.
| Artifact | What it does | What it leaves out |
|---|---|---|
| Results framework | Orders results into a hierarchy to a goal | The causal 'why' between levels |
| Theory of change | Explains why each level produces the next | The tidy one-page hierarchy |
| Logframe | Adds indicators, verification, assumptions in a matrix | The nested results structure |
Read across the row: each artifact is strong at exactly what the others leave out. The results framework gives a funder the tidy hierarchy, the theory of change gives an evaluator the causal logic, and the logframe gives a grants officer the indicator matrix — and with one logic on one record, producing any of the three is a view rather than a rebuild.
A results framework revisited once a year discovers a slipping result a year late. Reading each indicator as its data lands surfaces the slip in weeks, while a correction to the program can still be made. That is the premise of the Loop, Sopact's method for continuous impact intelligence: collect clean at the source, analyze the moment data arrives, improve while you can still act.
The Loop is also what makes a results framework defensible. Every indicator value traces to the participants and responses behind it, so a goal-level number resolves to its source rather than to a spreadsheet. That standard has its own chapter in reliability and reproducibility. The evaluation practice that reads these results is on program evaluation.
One method, three moves that never stop
Then the cycle runs again, a little sharper each cycle. Read the method: the Loop methodology →
The fastest way to test a results framework is to draft the hierarchy from what you already have and check that every box is a result, not an activity. Each prompt below pastes into Sopact Sense's Assistant, or reasons through with your team; the arrow above each links the Academy walkthrough that shows the expected output and the tips.
Academy walkthrough → Draft the results hierarchy
Build a results framework from this program description: [PROGRAM URL OR DOC]. Order the results into a hierarchy — goal, strategic objective, intermediate results, sub-results — and attach an indicator to every level. Flag any box that is an activity rather than a result. Return the hierarchy as a nested outline with the indicator beside each line.
Academy walkthrough → Audit results vs activities
Audit this results framework: [PASTE OR LINK]. Flag every level that states an activity instead of a result, every result with no indicator, and every intermediate result that does not ladder up to the objective. Return a corrected hierarchy with a measurable indicator on each level.
Academy walkthrough → Convert to a logframe
From this results framework: [PASTE OR LINK], produce a logframe: goal, purpose, outputs, and activities, each row with its indicator, means of verification, and assumption. Keep it consistent with the results hierarchy rather than rebuilding from scratch.
Academy walkthrough → Add the causal layer
From this results framework: [PASTE OR LINK], derive the theory of change beneath it: name the mechanism between each level (why this sub-result produces that intermediate result) and the assumption each link depends on. Return the causal version the hierarchy summarizes.
Each walkthrough is a hands-on companion written to run on your own data: what to do, the prompt to run, the output to expect, and the tips that keep it reliable.
Watch: ordering results into a hierarchy and wiring an indicator to each level, so the framework tracks progress instead of ordering intentions.
A results framework is a diagram that orders a program's intended results into a hierarchy — goal, strategic objective, intermediate results, sub-results — with an indicator attached to each level. It is the results-based management tool development funders use to show how work ladders up to a long-term goal. In Sopact's framing it is kept as a Live Results Hierarchy, each level wired to arriving data, rather than a chart drawn for a proposal and reported against once a year.
From the top: the goal (the long-term change the program contributes to), the strategic objective (the end result the program is accountable for), intermediate results (the outcomes needed to reach the objective), sub-results (the lower-order results that build toward each intermediate result), and an indicator on every level. The rule that keeps it honest is that each level is a result — a change achieved — not an activity performed.
Yes — a results framework template is a pre-structured hierarchy with a row for the goal, the objective, intermediate results, sub-results, and an indicator column. A template gets a team to a draft quickly, which is the point. The template is not the finished tool, though: the team still supplies the indicators and the data sources that make each level measurable. Sopact drafts the hierarchy from a program page and attaches an indicator to each level, so it starts as a tool rather than a chart.
A workforce example: the goal is reduced regional youth unemployment; the strategic objective is that program graduates secure and keep living-wage jobs; intermediate results are that participants gain an in-demand skill and that employers recognize the credential; sub-results are module completion and internship placement; and indicators run from a job-placement rate at the objective down to a completion rate at the sub-result. Each level is a result with a measure, not a task.
In monitoring and evaluation, the results framework is the structure that connects a program's results hierarchy to the indicators an M&E system tracks. Each level of the hierarchy carries an indicator, each indicator a data source and a collection cadence, so monitoring rolls up from sub-result to goal. Without the framework, M&E produces indicator values with no structure to interpret them against; Sopact wires each level to its data so the M&E view is generated rather than assembled by hand.
A results framework is a nested hierarchy that shows how results ladder from sub-results up to a goal; a logframe (logical framework) is a matrix that lists goal, purpose, outputs, and activities against indicators, means of verification, and assumptions. The results framework is better for showing the structure of results; the logframe is better for the indicator-and-assumption detail. They derive from the same logic, so Sopact produces either as a view rather than a separate document.
A results framework orders results into a hierarchy but does not explain why one level produces the next; a theory of change adds exactly that causal explanation and the assumption behind each link. The results framework is the tidy management picture; the theory of change is the reasoning underneath it. The cleanest workflow builds the theory of change first and derives the results framework from it as the ordered hierarchy.
A results chain is the linear sequence of results — inputs to activities to outputs to outcomes to impact — that a results framework arranges into a hierarchy. The chain is the horizontal logic; the framework nests it under a goal. Both describe how lower-order results build to higher-order ones, and both need an indicator on each link to be measurable rather than merely plausible. Sopact keeps the chain's indicators live so progress along it is visible, not assumed.
Results-based management is a management approach that defines a program by the results it intends to achieve rather than the activities it performs, then tracks progress against those results. The results framework is its central planning tool. The approach only works if the results are measured, not just declared, which is where most implementations fall short — Sopact's contribution is keeping every level's indicator wired to arriving data so results-based management is actually based on results.
Next: add the causal layer on theory of change, or produce the matrix version on logframe.