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 number you cannot trace is a number you cannot trust. In the Loop, every figure links back to the exact response, note, or document it came from — the audit trail funders and standards now expect.
Reliability answers is the number stable? Traceability answers the next, harder question: where did it come from? In the Loop, every figure in a report links back to the exact response, note, or document that produced it — a continuous chain from the headline result down to the raw evidence. When a board member asks “where did this come from?”, the answer is already on the page.
Key takeaways
Most reporting hides its seams. A polished PDF shows a confident number, and the path from raw survey answers to that number lives in someone's head or a tangle of spreadsheets no one wants to reopen. Traceability inverts that. Because the Loop reads data on arrival through defined fields, every conclusion keeps a link to the evidence underneath it — the specific open-text answer that was classified, the note that flagged a risk, the row that fed a total. You can click from the claim to the proof. Nothing is asserted that cannot be shown.
This is no longer optional at the top of the market. Funders and standards bodies reviewing serious impact claims increasingly ask not just for a result but for the trail behind it. We heard this most sharply from a corporate foundation evaluating monetized impact, whose requirements for a defensible SROI report map almost exactly onto what traceability provides:
| Requirement | What it means |
|---|---|
| Benchmark provenance | Every benchmark cites the specific study or evidence base behind it — not a vague repository. |
| Proxy ledger | Each outcome maps to its financial proxy, the proxy's source, and why it was chosen. |
| Adjustment logic | Deadweight, attribution, displacement, and drop-off each documented with a rationale. |
| Calculation audit trail | Gross value → adjustments → net value → present value → final ratio, shown step by step. |
| Sensitivity analysis | Conservative, base, and optimistic scenarios, so the confidence range is explicit. |
You do not need to be doing SROI to feel the shift. The same expectation — show me the evidence, not just the answer — now reaches ordinary outcome reporting. Traceability is how you meet it without assembling a binder by hand.
Traceability is not a feature bolted on at the end; it falls out of how the Loop reads data. A shared data dictionary defines what each field means, how each open-ended answer is classified, and how each indicator is built. Because every value is computed against that dictionary rather than guessed, each one keeps a pointer to the exact input it came from. The same structure that makes the answer reliable makes it traceable — consistency and provenance are two views of one mechanism.
A number offered without its source asks for faith. A number you can trace offers proof, and proof is what survives scrutiny. When a funder can follow a claim to the response behind it, the conversation changes from “do I believe you?” to “what does this tell us?” That shift — from defending numbers to using them — is the practical payoff of transparency, and it is available on every report the Loop produces, not just the ones that get audited.
Frequently asked questions
Click from any figure in a report back to the exact response, note, or document it came from — a full chain from headline number to raw evidence.
A growing number of funder and impact standards now ask for benchmark provenance, a proxy ledger, documented adjustments, and a step-by-step calculation trail — especially for monetized metrics like SROI.
Keeping data means you could reconstruct the trail by hand; traceability means the link from claim to evidence is maintained automatically as data arrives.
Every value is computed against defined fields and categories, so each one keeps a pointer to the input it came from — the same structure that makes results reliable.
Next: Principle 4 · Flexibility: one method, four workflows → · Back to The Loop →
Open Sopact Sense, paste your program description, and put it to work.
Try in Sopact