Three worked logframe examples - education, public health, and environment - each a complete 4x4 logical framework matrix with every cell filled in.
A logframe example is a worked version of the logframe grid — goal, outcomes, outputs, and activities, each with an indicator, a means of verification, and an assumption — shown filled in so the structure is concrete. A useful example shows more than tidy columns: it shows each indicator tied to evidence on the participant record. Sopact makes that tie real on the Evidence Thread, so every row in the example resolves to the responses that would confirm it.
Most logframe examples online stop at the shape. They show plausible-looking rows, but the indicators are decorative, with no source named and no baseline, so anyone copying the example inherits a grid that cannot actually be checked against data. A worked example is only worth studying if it shows how each row gets wired to something real.
Key takeaways
The difference between a logframe example that teaches and one that misleads is whether the indicators can be checked. An example that lists an outcome and an aspirational target but names no source is showing you a shape, not a method. Copying it gives you a grid that looks finished and collapses at reporting time, when the rows turn out to have no data behind them.
A measurable example names, for each row, the indicator wording, the baseline, the schedule, and the means of verification, so the grid is testable from the start. Sopact keeps that testability on the Evidence Thread, where each indicator resolves to the participant responses that feed it. The blank grid to fill is on logframe template, and the pathway it operationalizes is on theory of change.
In a worked logframe, the means-of-verification column is where the example proves itself. An output row should verify against a delivery record; an outcome row should verify against a change measured on the same participant over time. If the example cannot say where each number comes from, it is teaching the wrong habit — a grid of assertions dressed as measurement.
Sopact is evidence-centric: in a real logframe built from an example, each indicator value is a query that resolves to the responses on a persistent record, so any figure can be followed back to the participant who gave it. That is what connects a worked example to the practice on impact measurement and the tracking on outcome tracking software.
Teams usually copy a logframe example into Excel, sketch the underlying logic in a diagramming or ToC tool, and plan to fill the indicator data in a separate tracker later. Each step is reasonable, but at the category level the worked grid and the participant evidence live in different systems, so the example never becomes an instrument that reads its own data.
The one test that separates a copied example from a working logframe: pick any outcome row and ask the system to show the participant responses behind its indicator. A spreadsheet returns the target you typed; a diagram returns a shape. Sopact answers from the Evidence Thread, because the indicator resolves to the responses on the record.
Read each row for its indicator, its source, and its baseline, and treat any row with no means of verification as unfinished. The illustrative example below is generic — no real organization, result, or statistic — and shows the kind of source each level needs.
| Level | Indicator (illustrative) | Means of verification |
|---|---|---|
| Goal | A long-term change in the population | Follow-up survey on the record |
| Outcome | A change in participant behavior or status | Repeat measure, same Contact ID |
| Output | A count of what the program delivered | Attendance and delivery records |
| Activity | The work carried out to produce outputs | Program logs and intake forms |
Fill your own grid from the blank logframe template and see the model version on logic model template.
An annual impact report is a lagging artifact: it summarizes a year that is already over, and its figures are assembled from data nobody read while there was still time to change anything. The value of impact evidence is highest while a program is running, when a weak result can still be improved. That is the premise of the Loop, Sopact’s method for continuous intelligence: collect clean at the source, analyze the moment data arrives, improve while there is still time to act.
The Loop is also what makes an impact claim defensible: every figure in a report traces back to the participant response it came from, the standard detailed in Loop traceability, so a funder or an investor can follow any number to its source rather than taking it on trust.
One method, three moves that never stop
Then the cycle runs again, a little sharper each time. Read the method: the Loop methodology →
The fastest way to learn from an example is to build your own grid and wire each row to data. Sketch your logframe and export the responses that would feed its indicators, then paste the prompts below into Sopact Sense’s Assistant, or reason through them with your team. The arrow above each links the Academy walkthrough with the expected output and tips.
Academy walkthrough → How to build a logframe
Here is our program and the change we expect it to produce: [DESCRIBE + ATTACH]. Using a standard logframe example as the structure, draft our logframe with goal, outcomes, outputs, and activities, and for every indicator name the wording, the baseline, the wave schedule, and the source on the participant record, so each row traces to evidence rather than to an assertion.
Academy walkthrough → How to review a logframe
Here is a logframe we built from an example, plus the indicator data behind it: [ATTACH]. For each row, tell me whether the evidence supports the target, falls short of it, or has no data at all, and quote the participant responses behind each verdict, so the review traces to the record rather than to the example we copied.
Academy walkthrough → Extract outcomes from a report
Here are our narrative reports and program data: [ATTACH]. For each outcome indicator in our logframe, extract the result, quote the sentence or figure that supports it, and flag any indicator with no traceable evidence, so every number in the grid has a source on the Evidence Thread rather than an inherited placeholder.
Academy walkthrough → Write a cited funder narrative
Here is our program data and open-ended responses on the same participant IDs: [ATTACH]. Draft a short funder narrative that walks our logframe row by row, and after each claim quote the participant evidence behind it, marking any indicator where the evidence is thin so the report does not overstate the result.
Each walkthrough is short and practical: what to do, the prompt to run, the output to expect, and the tips that keep it reliable.
Watch: impact as continuous, traceable evidence on one record, not an annual report figure.
A logframe example is a worked version of the logframe grid, with goal, outcomes, outputs, and activities filled in alongside an indicator and a means of verification for each. Sopact ties every row in a real logframe to evidence on the Evidence Thread, so the example becomes an instrument rather than a picture of columns.
No. The illustrative example is generic and contains no real organization, result, or statistic; it shows only the structure and the kind of source each level needs. Sopact then wires a real logframe to the participant responses on the Evidence Thread.
A useful example names a source and a baseline for every indicator, so each row can be tested. Sopact keeps that testability on the Evidence Thread, where each indicator resolves to the responses behind it, so a copied example becomes a measurable grid.
A template is the blank grid; an example is a filled version showing the kind of content each cell holds. Sopact works with either, tying every indicator to evidence on the Evidence Thread so the grid, blank or filled, becomes a working instrument.
The source that would confirm each indicator, such as a follow-up survey or a delivery record. Sopact makes that source real by resolving every indicator to the responses on a persistent record, so verification is a query against evidence rather than a named intention.
Yes. Because each outcome indicator resolves to the responses on the Evidence Thread, Sopact can show whether the data meets, falls short of, or leaves untested each row, and quote the participants behind the verdict.
Either works, as long as every indicator ends up with a traceable source. Sopact wires each row to evidence on the Evidence Thread, so the starting point matters less than whether the finished grid can be checked against data.
Continuously, not once a year. Sopact reads each response as it arrives through the Loop methodology, so a logframe built from a good example is checked against evidence mid-program while there is still time to act.
Next: fill your own from the logframe template, see the pathway on theory of change and logic model, and the tracking on outcome tracking software within the practice on impact measurement.
