The Loop is Sopact's method for building a workflow that never stops improving — collect clean at the source, analyze the moment data arrives, improve in time to act. A case, an application, a grant round, a portfolio — or a workflow no one has named yet
Most workflows are built to run, not to learn. You collect data all year, then spend the last two months assembling it into a report — and by the time it's done, the people it describes have moved on, and the mistakes you could have caught are already set.
The tools make it worse. One person's intake sits in one tool, their survey in another, their case notes in a third, and nothing connects them. When the tangle finally gets too heavy, teams retreat to what feels safe — a clean spreadsheet and one more email survey. It's the most backward move of all: the further you get from the source, the longer it takes to see anything, and the less you can still change.
That distance — between the moment someone tells you something and the moment you can act on it — is the real problem. The Loop closes it.
The Loop is a cycle with three moves that never stop. Collect clean at the source — every form, survey, interview, and document enters as structured, connected data, not a pile to clean later. Analyze on arrival — the moment a response lands it is read: open text classified, risks flagged, scores applied, each conclusion tied to the respondent's own words. Improve while you can still act — because the reading happens now, you change a question, catch a drop-off, or fix a barrier this week, not next year. Then the cycle runs again, a little sharper each time.
Most teams have spent years bending the tools they already own — Excel, a survey platform, a CRM, a case-management system — to fit a program that keeps changing. Every new question becomes another column, another custom field, another standalone form. Six years of configuration later, the parts still don't line up: one person's intake sits in one tool, their survey in another, their case notes in a third, and nothing connects them into a single story. When the tangle finally gets too heavy, teams retreat to what feels safe — a clean spreadsheet and one more email survey. That retreat feels like a fresh start, but it is the most backward move of all, because it throws away the one thing that matters: the connection between what a person said at the beginning and what happened to them by the end.
The deeper problem is posture. Traditional tools assume you can design the perfect system up front and then just run it. Real programs don't work that way — you learn what to measure by measuring. The Loop assumes the opposite.
The Loop asks for an experimentation culture, not a rebuild. You do not design the perfect system on day one. You start where you already get immediate value — usually application or intake, the step every program already runs — and customize that one workflow until it clearly earns its keep. Then you apply the same pattern to the next data-collection step, and the next. Each one is live, useful, and connected before you add another. Nothing is thrown away; the system compounds.
This is not theory. A leader at the Open Play Foundation didn't roll out a platform — he started with one workflow, ran it himself, and added the next data step only once the first was paying off. Within weeks he was surfacing insights daily and catching drop-off signals his team had been missing, instead of waiting months for an evaluation cycle to tell him what had already gone wrong.
The method is the cycle itself. Instead of collecting for a year and analyzing at the end, the Loop reads every wave as it arrives and feeds what it learns straight back into how you collect the next one. Measurement stops being a season and becomes a habit — the same way a good product team ships, learns, and ships again rather than saving every fix for an annual release.
Generic AI tools are fluent but inconsistent: ask the same question of ChatGPT or Copilot twice and the numbers move. The Loop is engineered the other way — the same question over the same data returns the same answer, run after run. After moving from a spreadsheet-and-copilot workflow to Sopact Sense, a leader at the Open Play Foundation described the reports as much more consistent and accurate, adding that he could finally gauge where each number came from. That is not a nicety; it is the difference between a number you can defend to a funder and one you cannot.
A number you cannot trace is a number you cannot trust. In the Loop, every figure in a report links back to the exact response, note, or document it came from — a full audit trail from the headline result down to the raw evidence. That is increasingly not optional: the funders and standards bodies now scrutinizing impact claims expect cited benchmark sources, a proxy ledger, documented adjustments, and a step-by-step calculation trail. When a board asks “where did this come from?”, the answer is on the page.
Read: traceability & transparency →
The Loop is one method, but the work it supports is not one-size-fits-all. The same collect–analyze–improve cycle bends into four distinct workflows, each with its own course in this series — and none of them require you to abandon the system you already use; the Loop adds the reading layer on top.
Read: one method, four workflows →
A method is only worth adopting if you can put it to work — so the Loop comes with a guarantee. The Loop Guarantee is a paid two-month pilot: your first workflow — usually the intake or application step you already run — live, useful, and run by your own team within two months. Miss the two-month mark and we keep working at no charge until it is live. All-inclusive, never per-seat, and built to make your team independent — of the IT backlog, of consultants, and of Sopact.
Sopact Sense is a data-collection platform, not a data warehouse. Its innovation lives at the point of collection: clean, connected data captured at the source and read on arrival through a shared data dictionary and a Gen-AI layer. It deliberately does not try to be the place all of your data lives.
That makes it an AND, not a rip-and-replace. Keep your system of record — a CRM, a case-management tool, a grants system — and let Sense be the reading layer on top. Pipe its structured output onward through an API into a warehouse or BI stack such as Power BI or Microsoft Dynamics, and expose the same data to agentic AI assistants like Claude or ChatGPT so your team can ask questions from wherever they already work. The Loop runs the collection and the analysis; your warehouse and your agents keep doing what they do best.
Because free, general tools give you an answer — the Loop gives you the same answer twice, traced to its source. Generic models drift across long datasets, invent structure, and cannot show their work; teams that lean on them for real reporting end up re-checking everything by hand. The Loop keeps the conversational ease those tools made everyone love and adds the reliability and traceability that impact work actually requires. Fair to say: for a first draft or a brainstorm, reach for ChatGPT. For a number a funder will scrutinize, you want the Loop.
Pick one report you dread assembling and ask a different question of it: if every answer that fed this had been read the day it arrived, what would I have caught in time? That gap — between what you learned and when you learned it — is exactly what the Loop closes.
Program teams who can report activity but not change. Funders and funds who want a live view of a portfolio instead of a year-end PDF. Anyone measuring drop-off who needs the reason, not just the rate. If you collect data from people over time and someone is owed proof it mattered, the Loop was written for you.
Next: Principle 1 · The Loop methodology → · Try Sopact Sense →
ChatGPT, Claude, and Gemini are fine for a quick test — but not for an answer you'll put in front of a funder or board. When it has to hold up, run it in Sopact Sense.
Try it in Sopact →
