In short: A results framework arranges a program as a hierarchy — one Strategic Objective at the top, a handful of Intermediate Results beneath it, and Sub-IRs under those — each with a baseline-and-target indicator. To build one fast, describe your program to Sopact Sense; it maps the hierarchy and grades each element by evidence — green where the result ladders up and has a baseline, amber where an indicator is unmeasured, red where a result doesn't link to the objective or has no baseline. The steps below show how, with copy-paste prompts.
1 · Describe the program
A results framework is only as sound as the program you feed it. Start from what your program actually states and let Sense work from that — set up the Assistant so it sticks to your words:
You are the Sopact Sense Assistant. Here is my program description: [PASTE PROGRAM DESCRIPTION]. Use only what it states; mark anything you infer as [INFERRED]. Wait for my task.
2 · Write the prompt, not the hierarchy
You don't draw the ladder — you write the prompt that builds it and grades it. This is the one that maps the framework and flags results that don't connect:
Map a Results Framework for [PROGRAM]: one Strategic Objective, 3–5 Intermediate Results, and Sub-IRs, each with a baseline / target indicator. Flag any result that doesn't ladder up and any missing baseline. Use only what the program states; mark anything inferred [INFERRED]. Grade every element green / amber / red.
Five elements make it work: the input ([PROGRAM] or its page); the SO → IR → Sub-IR hierarchy; unlinked results and missing baselines (the two ways results frameworks fail); no hallucination (mark anything inferred); and the grade (green / amber / red at a glance).
3 · What Sense builds
Sense returns the hierarchy with every result graded — the ones carried by a baselined indicator, the ones running on an untested assumption, and the ones that don't ladder up to the objective. The demo runs on Vista Workforce Collaborative, engineered to grade one green, one amber, one red:
Vista Workforce Collaborative runs a 12-week coding bootcamp for ~60 low-income adults per cohort. Activities: 200 hours of instruction, weekly 1:1 mentoring, and an employer demo day. In the latest cohort, 41 of 58 graduates (71%) were placed in a tech job within 6 months, verified by employer letters. We believe the 1:1 mentoring builds the confidence that keeps participants engaged. We do not yet track whether participants stay employed beyond the first placement or whether wages grow over time.
GRADE: green | employment IR | 71% placed, verified — ladders to the objective; amber | mentoring sub-IR | rests on an unmeasured confidence assumption; red | sustained-employment IR | no baseline, and an orphan sub-IR that doesn't link up
The green result is an intermediate result carried by a verified indicator, the amber result rests on an unmeasured assumption, and the red result is a sustained-employment IR with no baseline — plus a sub-IR that doesn't ladder up to any objective.
4 · Turn a weak link green
The framework is worth most when you fix the result holding it back. Take the lowest-graded element and make it measurable with one realistic change:
Take the lowest-graded element above and fix it using only what the program could realistically measure. Show the before → after grade and the single indicator/edit that moves it to green.
For Vista, that's stating a baseline for sustained employment and re-linking the orphan sub-IR to the employment objective — turning a red result green.
5 · Make the report and share it
Generate a decision-first report in your own brand, then a shareable link:
Create a 'missing & incomplete' report from this analysis in Sopact branding [or paste your website URL / brand guideline to apply your own]. List every element graded amber or red, what is missing, and the one input that fixes each. Lead with the decision this report informs.
Create a shareable link for this report and open it in a new tab.
Tricks, tips, and troubleshooting
Every result must ladder up. The defining test of a results framework is that each sub-IR rolls into an IR, and each IR into the objective. Ask Sense to flag any result that doesn't connect — an orphan result is the most common reason a framework reads as incoherent.
No baseline, no IR. An intermediate result with a target but no baseline can't be judged. Ask Sense which results are missing a baseline and to suggest one the program could realistically collect.
Turn one result green per cycle. Fix the reddest result with the one indicator Sense suggests, collect it next cycle, and re-run the framework.
Tighten your program page while you're here. Once Sense has graded the framework, ask it to fix your program page so the claims match the evidence:
Based on the grades above, suggest edits to my program page so its claims match the evidence. Flag every sentence that overstates what we can show, and rewrite it to be accurate and specific.
Frequently asked questions
What is a results framework in M&E?
A results framework is a hierarchy used in monitoring and evaluation that shows how a program's lower-level results add up to its top-level aim: one Strategic Objective, several Intermediate Results that must each occur to achieve it, and Sub-IRs beneath those — every level carrying a baseline-and-target indicator. It's favored by USAID and similar funders for showing the logic of “what leads to what.”
What's the difference between a results framework and a logframe?
A results framework shows the hierarchy of results — how sub-results ladder up to intermediate results and to the strategic objective. A logframe is a 4×4 matrix that adds indicators, means of verification, and assumptions for each level. The results framework answers “what leads to what”; the logframe adds “how we'll measure and what must hold true.” Many funders ask for both.
How do you build a results framework with AI?
Describe your program and ask the AI to map one strategic objective, three to five intermediate results, and their sub-IRs, each with a baseline-and-target indicator, then flag any result that doesn't ladder up and any missing baseline. In Sopact Sense this takes minutes and stays grounded only in what your program states, grading each element so the unlinked results and gaps are obvious.