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.
Impact measurement that rides the workflow you already run — case, training, grant, application, or portfolio. Deeper than legacy measurement, captured as a byproduct of the work, with a reliability layer no ChatGPT paste can match.
Impact measurement is the practice of establishing what changed for the people a program serves. It compares participants’ situations before, during, and after a program on the outcomes the program promised, using numbers and first-person evidence together, so that a claim like “confidence improved” can be traced to specific people and specific records.
Most teams searching this term already measure something. They run intake forms, pre and post surveys, case notes, grantee reports. The frustration is what happens next, and practitioners describe it the same way: “we collect data all year and only look at it when the report is due.” The survey goes out in January, the export gets cleaned in September, and the dashboard arrives after the cohort it describes has already left. The data was real. The reading came too late to help anyone in it.
Key takeaways
For twenty years the sector has used “impact measurement” to describe a reporting exercise. Data is collected across the year, assembled in the weeks before a funder deadline, and published as metrics in an annual report or a dashboard. On that definition, measurement is something a program does about its work, after the work, for someone else. The typical gap between a participant answering a question and anyone acting on the answer runs nine to twelve months.
Sopact rejects that definition. Sopact defines impact measurement as a continuous loop: collect clean data at the source, read every response the day it arrives, and ask and act while the people in the data can still benefit. Sopact calls the cycle the Loop, and documents it end to end in the Loop and the Loop methodology. A report still gets produced; it stops being the definition of the work.
The disagreement is architectural before it is philosophical. Annual measurement is report-centric: every instrument exists to feed a document, so responses pool in exports until the document is due. The Loop is record-centric: every instrument lands on one persistent record per participant, the record stays current, and a report is a view of the record at a moment in time. Report-centric systems make the year-end scramble inevitable. Record-centric systems make it unnecessary.
The old definition also produced the funding stalemate this page has long described: the funder asks for outcomes, the grantee or investee carries the cost, and almost nobody funds a separate measurement project. When the reading happens inside the workflow a team already runs, such as intake, training delivery, or grantee reporting, there is no separate measurement project left to fund. Measurement becomes a byproduct of the work instead of a tax on it.
The survey era made collection cheap and reading expensive. SurveyMonkey, Google Forms, and Qualtrics let any program field a questionnaire in an afternoon, but every wave produced a fresh pool of disconnected rows. Matching one person’s pre and post answers meant a spreadsheet join on names and emails, and teams that tried routinely lost 20 to 30 percent of their matches. Survey-era stacks count activity well and follow people badly.
The dashboard era promised visibility and delivered lag. Case systems such as Salesforce and Apricot held the client record; Power BI, Tableau, and Looker Studio charted whatever was structured enough to chart. Two limits defined the era. The dashboard refreshed on a reporting calendar rather than an arrival calendar, so it answered last quarter’s question. And the open-ended material that explains the numbers, roughly 95 percent of the evidence by Sopact’s long-running estimate, sat unread in narrative fields while the numeric 5 percent got charted.
The continuous-reading era changes what happens on arrival. Each response is coded the day it lands, joined to the participant’s existing record, and compared against that participant’s earlier answers. Qualitative material is read as evidence rather than stored as attachment. Sopact Sense was built for this era.
One evaluation test separates the eras: ask when you would learn that a cohort is drifting — this quarter’s dashboard or this week’s read. A loop learns the week the drift starts, which is the only moment the knowledge is cheap to act on.
Each card below is one common program type. It shows how that program measures today, the point where the traditional approach breaks, and the same program running the full Loop: collect clean at the source, read on arrival, ask and act.
Impact measurement establishes what changed for the people a program serves; impact reporting communicates that evidence to an audience such as a funder, board, or the public. Measurement is upstream and continuous; reporting is downstream and periodic. A program can report without having measured, which is where “1,500 served” slides come from. In the Loop, a report is generated on demand from an always-current record. Sopact’s reporting-side pages, social impact report and impact reporting software, cover that downstream half.
Impact measurement and management (IMM) is the fund and investor version of the same discipline: measurement plus the portfolio decisions that follow from it — diligence, capital allocation, investee support, LP reporting. If you searched for IMM or its full form, that material lives on Sopact’s dedicated impact measurement and management page; this page covers the practice itself.
And if your question is which platform to buy, that comparison has its own page too: impact measurement software evaluates the major platforms criterion by criterion.
You measure the impact of a program by capturing a baseline at intake, holding question wording constant across waves, keeping every response on one persistent record per participant, reading each response on arrival, and treating reports as views of the record rather than annual assemblies. Five practices, and only the last two distinguish continuous measurement from good annual measurement.
The first three are discipline: a stable ID assigned at first contact, so the exit answer joins the intake answer without a spreadsheet match; a baseline captured before the program starts; and wording locked in a shared data dictionary, because a question that drifts between waves measures the drift, not the participant. The outcomes themselves come from the program’s own promise — a theory of change names them, and the Academy walkthrough shows how to build one that binds to real data.
The last two are the loop. Reading on arrival means open text is coded and joined the day it lands, so the mid-program read can change the program. Reports as views means the six-week assembly disappears: the funder report, the board view, and the Tuesday question a program officer asks mid-quarter all draw on the same current record.
Continuous impact measurement earns its keep where cohorts are large enough for drift to hide in, where open-ended evidence explains the numbers, and where a mid-program correction is worth money. It is not a universal upgrade.
| Your situation | Fit | Why |
|---|---|---|
| Cohort program with pre, mid, and post waves and open-ended responses (25+ per cohort) | Strong | Drift becomes visible mid-cohort, when acting on it is cheap and the participants are still reachable. |
| Multi-site nonprofit where caseworkers write notes | Strong | Notes become readable evidence the week they are written instead of sitting unread in narrative fields. |
| Funder, fund, or accelerator tracking a portfolio | Strong — different page | The same loop runs at portfolio grain; see the impact measurement and management page for the fund version. |
| One-time event or workshop feedback | Not yet | There is no second wave to join to the first. A survey tool answers this well on its own. |
| Under roughly 50 participants, no wave after exit | Not yet | A spreadsheet is still honest at this scale. The Loop pays off where the qual + quant join is unmanageable by hand. |
| Funder requires only activity counts | Not yet | Counts come from operational records already. Adopt the Loop when an outcome question arrives, not before. |
The two “not yet” rows in the middle convert on the same trigger: the moment someone asks what changed rather than what was delivered. When that question arrives, the cheapest time to have started a persistent record was intake.
Nothing is wrong with the annual report as an artifact. It is wrong as a definition. When the report defines the work, every instrument is aimed at a deadline, and the year’s most useful information — the trainee who named a barrier in week two — waits in an export for a reading that comes after it could have mattered. Sopact’s Loop aims the same instruments at the program instead.
The Loop also changes what a report is worth once it exists. Because every figure descends from a specific response, note, or document on a specific record, every figure can cite its source, and a board question about where a number came from is answered in one click. The Loop methodology covers the operating detail: the cadence, the reads, and what each role does with them.
One method, three moves that never stop
Then the cycle runs again, a little sharper each wave. Read the method: the Loop methodology →
The fastest way to test the definition is to run it against your current setup. Each prompt below is written to paste into Sopact Sense’s Assistant; the arrow above each one links the Academy walkthrough with the expected output and tips.
Academy walkthrough → The Loop
Here is how my program measures impact today: [DESCRIBE INSTRUMENTS AND CADENCE, e.g. intake form, post survey, annual report]. Map this against a continuous loop — collect clean at the source, read on arrival, ask and act. Identify exactly where my loop breaks: where responses wait unread, where identity breaks across waves. Recommend the smallest change that closes each break.
Academy walkthrough → The Loop methodology
My team currently reviews program data [CADENCE, e.g. quarterly]. Using this cohort’s responses: [PASTE OR ATTACH], show what a weekly read would have caught earlier: participants whose outcome trajectory dropped between waves, themes that are new this month in the open-ended answers, and the one follow-up question you would send this week.
Academy walkthrough → Analyze pre, mid, and post survey data
Analyze this pre, mid, and post survey data collected on the same participants: [PASTE OR ATTACH]. Report movement on each outcome from baseline, the open-ended themes that explain the movement, and the participants whose mid-program read predicts a poor outcome if nothing changes. Cite the source response for every claim.
Academy walkthrough → How to build a data dictionary
Build a data dictionary for continuous impact measurement of this program: [PROGRAM DESCRIPTION]. For each outcome, define the exact question wording to hold constant across waves, the scale, the wave schedule, who answers, and the arrival-time checks that keep each response clean enough to read the day it lands.
Each walkthrough is practical and short: what to do, the prompt to run, the output to expect, and the tips that make it reliable.
Watch: the Loop on a real cohort, from clean collection to a cited answer.
Impact measurement is the practice of establishing what changed for the people a program serves, using numbers and first-person evidence on the same participant record. Sopact defines it as a continuous loop, the Loop, rather than an annual reporting exercise: collect clean at the source, read every response on arrival, and ask and act while the cohort is still in the program.
Impact measurement establishes what changed; impact reporting communicates that evidence to an audience such as a funder or board. In Sopact’s Loop the two decouple cleanly: the participant record is always current, so a report is a view generated from it on demand.
Impact measurement and management (IMM) adds the decisions that follow measurement: capital allocation, program redesign, investee support, and LP reporting. The term is most common among impact investors and funds. Sopact runs both on the same continuous loop; the portfolio version, from diligence to LP report, is covered on Sopact’s impact measurement and management page.
Collect on the cadence the program design needs, typically intake, mid-program, exit, and one or two follow-ups, but read continuously. Sopact’s Loop separates the two clocks: collection waves stay disciplined and comparable, while reading happens the day each response arrives, so drift shows up the week it starts rather than at report time.
The Loop is Sopact’s name for impact measurement run as a continuous cycle: collect clean data at the source on one persistent participant ID, read every response the day it arrives, and ask and act while the people in the data can still benefit. The cycle then repeats.
Capture a baseline at intake, hold question wording constant across waves, keep every response on one persistent record per participant, read each response on arrival, and generate reports as views of the record. Sopact’s Loop adds the last two practices to the discipline most programs already have.
No. The Loop runs on the instruments most programs already use: intake forms, pre and post surveys, case notes, reflections, and reports. What changes is the clock, not the burden. Responses are read on arrival instead of pooled for a year-end analysis, so participants answer the same number of questions while each answer becomes worth more.
Platforms commonly evaluated include Sopact Sense, UpMetrics, Bonterra Impact Management, Amp Impact, SureImpact, and ActivityInfo. Sopact’s impact measurement software page compares them criterion by criterion. The question that separates the field: does the platform read responses on arrival, or store them for a later report?
Below roughly 50 participants, a survey tool plus a careful spreadsheet is often still the right answer, and Sopact says so plainly. Continuous measurement earns its keep where cohorts are large enough for drift to hide in and where qualitative evidence is too voluminous to read by hand. The practices that transfer at any size: persistent IDs, baselines, and constant wording.
An impact measurement framework is the named structure that connects what a program does to what changes for the people it serves: a theory of change, logic model, IRIS+, or SROI. The framework decides what to measure; the cadence decides when you learn. Sopact binds frameworks to live participant records so indicators fill continuously instead of once a year.
Next: if you run a fund or portfolio, the same loop at portfolio grain is on impact measurement and management; if you are comparing platforms, start with impact measurement software.