Outcome tracking software that joins baseline, services delivered, and year-1/3/5 follow-up on one persistent client ID — mixed-method qual + quant on one row.
The outcome tracking software your team uses was designed when the bottleneck was year-end reconstruction — pull the intake table from one system, the services log from another, the follow-up survey from a third, and join them by name match. That bottleneck moved.
Reconstruction is no longer the answer. The new bottleneck is the workflow that holds one persistent client ID from baseline assessment through year-three follow-up — with intake, services delivered, case notes, and every follow-up survey on the same row. The outcome at year three is connected back to what the client said at year zero, with a citation trail.
That is the difference between outcome reports — the year-end CSV merge across separate systems — and outcome intelligence: one persistent client record, mixed-method qual + quant on the same row, with every conclusion reproducible because the data dictionary keeps the math reproducible.
AI without a workflow is a clever intern with no desk. The teams winning at outcome tracking are the ones whose client data has a place to land — one record, one ID, one story.
Outcome tracking software is a platform that joins baseline assessment, services delivered, and follow-up surveys on the same persistent client ID — so the outcome at year 1, year 3, or year 5 is connected back to what the client said at intake, what services they received, and what the case worker observed along the way. The older generation produced year-end outcome reports as CSV merges across separate systems. The new generation runs them as queries against one persistent record.
Used by:
Client outcome tracking, outcomes management software, outcome measurement software, outcome reporting software, longitudinal outcome software, impact measurement software — different terms point to the same software category. What varies is who’s asking and at what time horizon.
Survey software (SurveyMonkey, Qualtrics) collects responses but doesn’t join them to a baseline. BI tools (Tableau, Power BI) visualize joined data but don’t do the joining. Outcome tracking software is the layer where one persistent client ID makes the join possible.
The outcome tracking your team does was designed when the bottleneck was year-end reconstruction. Pull intake from one system, services from another, follow-up from a third, join by name and birthdate, hope nothing dropped, send the report.
Reconstruction is solved. The new bottleneck is the workflow that holds one persistent client ID from baseline through year-3 follow-up, joins qualitative case notes to quantitative validated screens on the same row, and reports outcomes as queries against the persistent record. The outcome is no longer something you reconstruct; it is something you query.
The outcome that takes four weeks to reconstruct is not the same outcome the next analyst will produce. Reproducibility is the foundation of evidence.
For years, Open Play’s program and facility data sat in paper logs and spreadsheets — including a water log Marco Botha had kept by hand for nearly three years. The foundation needed comparable, real-time evidence to put in front of investors and partners, not a quarter-end export — and nothing in the old setup could flag an operational problem while it was still fixable.
After heavy rain, Open Play’s water purification system reported it had run out of rainwater — which Marco knew was impossible. Because the figures were live on the record, he cross-checked in minutes and surfaced a probable reservoir leak. Same logic for client outcome tracking: when baseline, services, and follow-up live on one persistent record, the impossible outcome reading (e.g. a year-3 outcome that doesn’t match baseline trajectory) shows up immediately, not at year-end.
“Those statistics that we’re now running on Sopact immediately showed me there’s something significantly wrong … things like that, we would never have been able to do in the past.”
Every effective outcome tracking workflow moves through the same five stages — from baseline assessment to year-3 follow-up. Each stage writes back to the same persistent client record.
Validated screens, intake demographics, initial service plan.
Theory of Change, Logic Model, outcome rubric.
Indicator definitions, attribution rules, cohort schema.
Follow-up read on arrival, joined to baseline by client ID.
Cohort comparisons, longitudinal trends, funder evidence.
Assign a persistent client ID at baseline. Every later stage writes back to the same row. Year-3 outcome is one query, not a four-spreadsheet reconstruction.
The validated screen changes, the follow-up window changes, the funder report changes. The architecture — one persistent client ID across baseline, services, and follow-up — does not.
In legacy outcome tracking, each follow-up survey is a separate file matched by name at year-end. In outcome intelligence, the record continues on the same persistent client ID.
One persistent client ID carries every screen, service, case note, and follow-up from baseline through year five. The year-5 outcome is a query against the same record where the year-0 baseline lives.
Most outcome-tracking evaluations include four to five recognizable names. Each was built for a different funder ask.
All five can produce a year-end outcome report. The differences show up at the funder’s next question: can you compare this cohort to year-1 of cohort 2022, on the same indicator definitions?
No per-seat tax. No per-client meter. The line items are the things that actually drive work — how deep the longitudinal follow-up runs, how custom the outcome rubric needs to be, and how branded the funder-facing reports have to look.
Your outcome indicators, your validated screen scoring, your demographic categories, your attribution rules — drafted in one working session.
Outcome Rubric, Cohort Roll-up, Comparative Analysis, Theory of Change, Logic Model — turned on by default. Add domain skills (SROI, ROMA, HMIS exit codes) when needed.
Logo, color palette, follow-up survey styled to your brand. Funder-facing pages match your identity.
Closed-ended validated screens and open-text reflections scored together. Indicators populate automatically with citation trails to the source paragraph.
Cohort comparison · year-1 vs year-3 · outcome attribution · funder dashboards — each generated from one place with citation trails preserved across years.
One program with one outcome rubric is simplest. Multiple programs sharing one client ID adds cross-program attribution.
90-day follow-up is light. Year-1, year-3, and year-5 cohorts attributed back to baseline adds depth.
One cohort is simplest. Comparing year-1 cohort 2022 to year-1 cohort 2026 across schema changes adds dictionary work.
Built-in skills cover common patterns. Your funder’s required indicators (CSBG ROMA, HMIS exit codes, custom outcome frameworks) compose with the built-ins.
One funder, one report is simplest. Multi-funder white-label (separate funder portals) adds configuration.
Reading reports in Sopact is included. Piping to Tableau, Power BI, Looker, Snowflake adds integration setup.
A small workforce program tracking 90-day placement pays less than a foundation portfolio tracking year-5 outcomes across 12 grantees on three indicator frameworks. Talk to us with your indicator list; we will quote against it directly.
Outcome tracking touches confidential client data — clinical screens, services received, household context, employment status. Here is what Sopact actually provides.
AES-256 at rest, TLS 1.3 in transit, encrypted backups, scheduled key rotation. The reading model returns structured output and does not retain the underlying text.
Role-based access at the field level (worker, supervisor, evaluator, auditor), single sign-on, multi-factor authentication, complete audit trail.
All AI calls run under enterprise-grade SLAs with no training-data retention. The model reads, returns structured output, and forgets.
Sopact is not currently HIPAA-certified or covered by a Business Associate Agreement (BAA). The controls above support a security-conscious deployment, but if your outcome data is subject to HIPAA, FERPA, 42 CFR Part 2, or state confidentiality rules, you should evaluate the specific controls against your compliance program and consult your counsel.
Outcome reports are not formats — they are questions. The same accumulating client record produces four distinct shapes.
The 90-day follow-up nobody returned, the year-1 cohort with a 40% response rate vs. expected 70%, the indicator with no data point this quarter.
A year-3 outcome that doesn’t match the baseline trajectory, a sub-cohort drifting from agency norms, an indicator with a value too far from expectation.
Baseline screen, services received, every case note, every follow-up survey — tied together by one persistent client ID. Funder asks “what happened to client #4471?” — two clicks.
Year-1 cohort 2022 vs year-1 cohort 2026 on the same indicators. Trend lines. Attribution to services. Reproducible across years because the dictionary is locked.
Strip away the marketing and four properties separate outcome intelligence from everything before it.
For outcome reports a funder will scrutinize, variance is disqualifying. Sopact runs the model to read, then locks the answer, so cohort comparisons across years are reproducible.
A validated screen tells you what changed. The open-text reflection tells you why. Sopact joins both on the same persistent client ID — so the score and the narrative reason live on the same row in the funder report.
Every theme, indicator, and attribution points back to the source. When the funder asks “why this conclusion?” the supporting paragraph is two clicks away.
Every indicator definition, attribution rule, and cohort schema is documented and versioned. Year-3 cohort 2026 can be compared to year-3 cohort 2023 on the same definitions.
The architecture is the same; the configuration scales with the work.
A 12-person agency tracking placement at 90 days. Validated screen at baseline, exit survey at closure, follow-up at 90 days. Live in a week.
30-person agency running 3–5 programs. Same client appears across them. Year-1 outcome cohorts joined to baseline by client ID. Funder reports per program plus the agency roll-up.
Foundation tracking 12 grantees across 5-year arcs. Same indicator schema across grantees. Year-3 cohort 2022 compared to year-3 cohort 2026. Reproducible.
Ten questions that come up in nearly every outcome-tracking evaluation.
Sopact treats outcome tracking as the natural continuation of case management. Same client ID, same persistent record, year-3 follow-up is one query away from the baseline.
One year’s baseline assessments, the services log, and the 90-day or year-1 follow-up survey. We’ll walk through how Sopact would join them on a persistent client ID, what the outcome cohort report would look like, and how cohort comparisons would run.
