Plan impact measurement with suitable methods, clear outcomes, a worked example, shared data definitions and evidence your team can use during delivery.
Impact measurement is the practice of understanding whether and how an organisation contributes to meaningful change. It starts with a decision: what needs to improve, for whom, and what evidence would be useful enough to act on. The result should be a connected evidence trail—not a pile of indicators detached from the people and activities that produced them.
That distinction separates it from monitoring alone. Monitoring tracks implementation: attendance, services delivered, applications processed, training completed. Impact measurement connects those operational facts to outcomes, assumptions, experience and decisions. It asks not merely what happened? but what changed, how confident are we, and what should we do next?
Scroll horizontally to see all columns →
| Term | What it answers | Practical example |
|---|---|---|
| Activity data | What did we do? | A coach logged a session; a grant officer reviewed an application. |
| Outcome evidence | What changed for a person, group or place? | A participant reports confidence, access or progress over time. |
| Impact measurement | What can we reasonably learn about our contribution, and what must change next? | A team connects delivery, participant experience and outcome patterns to redesign a programme. |
There is no single “best” impact measurement method. The appropriate approach depends on the decision, the maturity of the programme, the risk of getting the answer wrong and the evidence that can be collected ethically. The OECD’s evaluation criteria treat impact as one lens alongside relevance, coherence, effectiveness, efficiency and sustainability—not a universal score for every intervention.
Scroll horizontally to see all columns →
| Method | Best used when | What it cannot establish alone |
|---|---|---|
| Theory of Change | You need to make the pathway, assumptions, stakeholders and intended change explicit before collecting data. | Whether the pathway actually held in practice. |
| Monitoring and outcome tracking | Teams need timely visibility of delivery, experience and progress for individuals or cohorts. | That the programme caused every observed outcome. |
| Contribution analysis | Several factors may influence a result and you need a transparent account of the programme’s plausible contribution. | Experimental proof of causality. |
| Experimental or quasi-experimental evaluation | The stakes justify a causal design and a credible comparison is ethical and feasible. | The lived experience or operational reasons behind the result. |
| Qualitative and participatory inquiry | You need stakeholder interpretation, mechanisms, unintended effects and equity perspectives. | Population-level prevalence without complementary quantitative evidence. |
Combine methods when the decision needs complementary evidence; do not add another method without a clear purpose. It makes the claim proportionate to the evidence: track what is delivered, understand what changes, test alternative explanations, and make uncertainty visible.
Sources: OECD DAC, Applying Evaluation Criteria Thoughtfully · BetterEvaluation, Contribution Analysis.
Measurement can become organized around reporting deadlines rather than the decisions made during delivery. A funder requests a framework and a set of comparable outcomes. The mission-driven organisation then adds forms, spreadsheets and reporting work around delivery. Evidence is collected late, re-keyed across systems and turned into a polished narrative after the decisions that mattered have already been made.
This is not simply a technical failure. It is a value and incentive mismatch. Funders understandably need assurance, stewardship and a view across a portfolio. Mission-driven organisations need evidence that helps them serve people better, manage teams and adapt in real time. When the same data system does not create value for both parties, reporting becomes an administrative cost borne by the delivery team.
Scroll horizontally to see all columns →
| What the funder needs | What the delivery team experiences | What a connected design changes |
|---|---|---|
| Comparable outcomes, confidence and accountability | Many different templates, late requests and evidence reconstructed at report time | Common definitions and a reusable evidence model, without forcing every programme into one rigid workflow |
| Clear progress across grants or partners | Data that cannot be used during delivery because it lives in a separate reporting process | One operational record from activity to decision, with the reporting view generated from it |
| Trustworthy narrative and learning | Pressure to present certainty when context is incomplete or outcomes take time | Traceable evidence, explicit assumptions and an honest view of what is known, unknown and next |
The aim is not to make frontline work look measurable. It is to make evidence useful enough that frontline teams choose to use it.
A connected impact system begins with the work that already happens. A case may begin with an application and end with an exit or referral. A grant may move from prospecting to due diligence, payment, activity logging, outcome review and renewal. A training programme may connect enrolment, attendance, practice, feedback and follow-up. These are not separate “data projects”; they are one evolving context.
Where the work requires matching over time, use an appropriate stable identifier for the person, household, partner, case or organization. Anonymous or place-level measurement may instead require group context and a clear reporting period. Teams need flexible forms for the data appropriate to their workflow. Leaders need a shared evidence model so “retention”, “completion” or “wellbeing” means the same thing wherever it is used. And the record needs to retain who collected a fact, when, for what purpose and how it relates to the next decision.
Sopact Sense is designed for this connected approach. It can centralise the evidence required for a use case while fitting alongside the systems a team already uses. The goal is not a rip-and-replace data warehouse. It is a governed, usable operational record that makes learning and reporting easier because it is built into the flow of work.
AI is useful when it can retrieve the right evidence, compare patterns, surface gaps, group themes and prepare source-linked drafts. It cannot decide what an outcome means, resolve attribution, approve a sensitive conclusion or make data trustworthy simply by sounding confident. Those are governance responsibilities.
Before applying AI, an organisation needs defined ownership, appropriate access, valid record relationships, clear data definitions, evidence provenance and a review step for consequential decisions. Centralising the relevant evidence in a governed system gives AI context; it does not remove human accountability. This aligns with the NIST AI Risk Management Framework’s cross-cutting governance approach: Govern, Map, Measure and Manage.
Source: NIST AI RMF Playbook.
These principles turn a one-off measurement exercise into an embedded operating practice. They are not an extra checklist after implementation. In a connected Sopact design, they become part of how a team configures a use case, collects evidence and acts on it.
Use the Impact Measurement & Reporting course to work through outcome definitions, evidence design and reporting. Then choose the workflow course that fits the work you manage, such as participant support, training or a portfolio.
The practical output is a plan your team can operate: what to collect, from whom, when, under which definition, who reviews it and how it informs a decision. Keep the learning path focused on that goal rather than adding another competing checklist.
Open Play Foundation illustrates what becomes possible when measurement belongs to the organisation, not a reporting deadline. Its team uses Sopact Sense across its business: to log activities, manage water-resource information and organise individual outputs through bespoke survey forms. The platform supports a growing portfolio because the same connected foundation can adapt to the work rather than forcing the work into a fixed template.
The lesson is to make collected information useful during delivery as well as reporting. This example describes an evidence practice; it does not establish that the approach caused particular social outcomes.
Do not begin by trying to standardise every system or prove every long-term outcome. Start with one high-value workflow: a case journey, a grant lifecycle, a training programme or a partner-support process. Define the decision, choose the appropriate unit and record relationship, connect the evidence already available and design the smallest reliable collection step at the source.
Once the team uses that evidence to make a real decision, the system has earned the right to grow. That is how impact measurement becomes self-driven: the organisation sees its own value in the record before it is asked to report from it.
A fictional business runs a skills program for 80 employees. Sixty complete the sessions. At a three-month follow-up, 50 respond and 35 report using the technique at work.
Scroll horizontally to see all columns →
| Evidence | Reasonable statement | Statement it does not justify |
|---|---|---|
| 60 completions from 80 enrolled | 75% completed the sessions | 75% improved their performance |
| 35 of 50 follow-up respondents report use | 70% of follow-up respondents reported applying the technique | 70% of all enrolled employees applied it |
| Comments describe a useful practice task | Some respondents described how the task helped them | The practice task caused all reported improvement |
The 35 reported users are also 43.75% of the original 80 enrolled. That is the observed number relative to enrollment, not an estimate that the remaining 45 did not use the technique. Thirty did not provide follow-up evidence. Show that gap rather than assigning them an assumed outcome.
To improve the evidence, the team might define what “use” means, collect an example of application and review a relevant work artifact with permission. A stronger claim about effects would require a design that addresses alternative explanations. More connected records improve traceability; they do not automatically establish causality.
Organizations with multiple locations or partner programs often need different collection instruments. Agree the few fields needed for a common decision, then allow local questions around them. Define each shared field in a data dictionary: meaning, unit, population, period, response options, calculation and change rules.
One location may report people registered while another reports attendance entries. Both can be useful, but they cannot be added as though they were the same unit. Similarly, a six-month outcome and a one-month outcome should not become one unlabeled rate.
Collect stable context once where practical and update information that changes. Keep new observations dated and connected to the right unit. If an outcome definition changes, decide whether historical results can be restated consistently or need to remain a separate series.
A useful report connects the outcome definition, coverage, observed result, stakeholder accounts and limitations. Different audiences may need different detail, but they should receive the same underlying calculation and evidence.
Use the How to Write an Impact Report guide and report examples to develop the presentation. For the step from finding to action, continue with social impact management. For an investment portfolio, use the IMM portfolio workflow.
Monitoring tracks delivery, such as services provided or people reached. Impact measurement connects delivery to intended outcomes, stakeholder experience, context and decisions so a team can understand its contribution and improve its work.
Common methods include Theory of Change, outcome monitoring, contribution analysis, experimental or quasi-experimental evaluation, and qualitative or participatory inquiry. The right method depends on the decision, the claim being made and what evidence can be collected credibly and ethically.
Traditional reporting is often separate from operational work. It creates a mismatch: funders need assurance and comparability while delivery teams absorb the cost of collecting data that arrives too late to improve programmes.
AI can help retrieve evidence, identify patterns and prepare source-linked analysis. It cannot set outcome definitions, judge causality or take accountability for decisions. AI is useful only when the underlying evidence is connected, governed and reviewed by people.
A persistent ID connects evidence collected across time, teams and workflows to the same person, case, partner or programme. It is useful when the same unit must be followed over time. Anonymous or group-level evidence can still support valid questions when its scope and limitations are clear.
No. A connected measurement design can work alongside existing systems. The priority is a governed evidence model that links the operational data needed for a use case, while preserving clear ownership, definitions and traceability.
Start with one decision and one end-to-end workflow. Define the intended change, map the evidence already available, add the smallest useful collection step and use the resulting record to improve a real decision.
Explore how participant feedback supports program review and learning. The worked employee-training figures in this guide are fictional.
Read the customer story →
