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.
One client record across every program — outcomes as a query.
Nonprofit case management software is a platform that holds one persistent record per client across every program a mission-driven organization runs — intake, assessment, service plan, case notes, services delivered, and outcome follow-up — so program staff, directors, and boards can prove what changed without stitching spreadsheets together the week before a funder deadline. It is also called nonprofit case management, case management software for nonprofits, or client tracking software for nonprofits. The newest generation adds intelligence to the record itself: AI reads each case note on arrival, scores it against the service plan with citations, and turns follow-up surveys into outcome evidence — so the software answers whether the participant's situation actually improved, not just how many services were logged for the grant report.
Used by: human services nonprofits · youth development and mentoring programs · workforce and reentry nonprofits · housing and homelessness services · family services and community action agencies · multi-program nonprofits coordinating one client across teams and funding streams.
Not because the software stopped working — because storing the client and logging the service became table stakes. Bonterra (Apricot, ETO, Social Solutions), Salesforce Nonprofit Cloud, Casebook, ClientTrack, Penelope, Sumac, and Exponent earned their positions honestly: they got casework out of the filing cabinet, standardized the intake, and gave lean nonprofit teams a real system of record. If your problem was collection — hundreds of participants, a handful of case managers, one funder deadline — that generation solved it.
But the strengths hardened into weaknesses. Implementations run three months to a year, and small nonprofits with no IT department describe legacy builds where every new program or funder requirement becomes another integrator invoice. The logic is rigid by design, and the richest evidence those systems hold — the case notes — dies after collection: narrative piles up in a system nobody reads across, and the analytics describe what was delivered, not what changed. A program lead running services across sites put the pattern plainly: they could track "outputs and dollars and volunteer hours," but "the biggest pain point is that we can't tell a cohesive story across all of it. Each thing works fine in a silo."
For a nonprofit, the cost of not reading is not abstract — it is the difference between renewing a grant and losing it. As one practitioner described it, case notes end up "just sitting around in the systems… by the time they find out, you already failed a child." The work that decides whether a program keeps its funding has moved to the two ends the record-keeping tools never owned: reading every case note and assessment on arrival, and proving the outcome months and years later on the same participant.
None of this requires ripping out your incumbent. The sentence we hear on almost every call now: "We're not gonna leave our system, but we're open to an AND." Keep the system of record; add the layer that reads what it produces. (If you're comparing the broader category — the full lifecycle and how to evaluate it — start with case management software.)
The stake, stated honestly for a nonprofit board: funders have already changed the question from "how many did you serve" to "did their situation improve, and can you show it" — the same shift the IRS made when Form 990 Schedule I began asking for program accomplishments, not just dollars out the door. If you are signing a multi-year configuration build today, ask which question it will be able to answer when it finally goes live.
Case intelligence is reliable answers from your case data — in minutes, not months. Everything a participant touches is treated as data: the intake form, the assessment, the validated screen, the service plan, every case note, the 90-day and year-three follow-up. All of it lands on one persistent client record, aligned to your theory of change and data dictionary, so the same person looks like the same person across three programs and five years — and across the grants that each pay for a slice of that person's journey.
The part that changes daily work is the Assistant. Caseload analysis, screen scoring, and open-text case-note analysis are unified into one chat-based function: ask a question, get a defensible answer with citations to the underlying records. No prompt engineering, no dashboard hunting, no waiting for the one staffer who knows where the export lives. A nonprofit is never one user — case managers, the program director, the development team writing the grant report, the board, funders, and the participants themselves all need different views of the same record — and a chat interface empowers each of them directly.
When the analysis is done, it does not die in the chat: create shareable reports tailored to each audience — the case manager's caseload view, the funder outcome report, the board summary, the Form 990 Schedule I program detail — from the same underlying answer, each number traceable to the source case note.
One proof point from the field. Open Play Foundation ran programs the way most funded nonprofits do — intake forms, follow-up reflections, stacks of narrative that never made it past the spreadsheet. When that work moved onto Sopact, the record could finally read itself: "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." — Marco Botha, CEO, Open Play Foundation. A system of record tells you the service was delivered. An intelligent record tells you something is wrong in time to act — and in time to fix it before the funder reads about it.
The honest way to evaluate nonprofit case management software is against the lifecycle, not the feature list. Nearly every program describes the same arc — and it is a loop, not a line: follow-up routinely sends a case back into reassessment until the goals are met. Below is the full cycle — six stages, each with what the software should do, the exact prompt to use, and what to expect back. Every prompt is copy-paste; the placeholders in brackets are yours to fill.
Intake is where clean-at-source pays or fails. Instead of free-text answers you will pay a case manager to decode later, the form is designed so every narrative field maps to your theory of change, and every participant gets a persistent unique ID that follows them across programs, grants, and years. Eligibility screening, consent capture, save-and-return — and AI drafts the intake form from the program documents and grant agreement you already have.
Build a client intake form from this program description: [PROGRAM URL OR GRANT AGREEMENT]. Create structured fields for demographics, eligibility, and consent; narrative fields for presenting needs and goals mapped to our theory of change; and eligibility screening questions with clear pass/fail criteria. Flag any question that collects information we already hold on a participant enrolled in another one of our programs.
Expected output. A ready-to-edit intake form: structured fields, mapped narrative prompts, eligibility gates, and a persistent client ID assigned at first contact that ties this participant to any other program they touch.
Tips for reliable output. Give the AI your theory of change and data dictionary before form design. Assign the client ID at intake, not at enrollment — everything downstream, and every grant that later reports on this person, attaches to the ID created here.
The baseline is the reference every later wave is compared against — and the "before" number your funder outcome report will need. Validated screens (PHQ-9, GAD-7, a workforce self-sufficiency scale, or your own indicator) and the intake narrative land on the same record, and the assessment is read the moment it arrives — needs, risk factors, and protective factors extracted and cited, not left in a folder until something goes wrong.
From this intake assessment, extract the participant's baseline needs, risk factors, and protective factors, each with the exact source sentence. Score the validated screens included, flag any safeguarding or immediate-risk language for human review, and note where the assessment is incomplete. Do not infer a diagnosis — report only what the text supports.
Expected output. A structured baseline with per-item evidence, scored screens, and a flagged list of risk or safeguarding language routed to a human.
Tips for reliable output. Lock the baseline before services begin — a baseline captured on day one, even on a handful of participants, proves the loop works before you scale it across the whole program or write it into next year's grant proposal.
Every participant gets a service plan built from the assessment and mapped to your theory of change — goals that are observable, timelines that are real, and the outcome each service is meant to move. The plan becomes the thing case notes are later read against, and the thing your grant report measures progress toward.
Draft a service plan from this assessment: [ASSESSMENT]. Map each identified need to a measurable goal, a service or referral, and the outcome indicator it should move, aligned to our theory of change and the outcomes we committed to in the grant. Write goals as observable statements a case manager can evidence, and flag any need with no service currently available in our program.
Expected output. A service plan with measurable goals, mapped services, outcome indicators tied to your funded outcomes, and a gap list where needs have no matching service.
Tips for reliable output. Name the outcome for every goal. A plan that can't say what success looks like can't be evaluated later — and can't be defended in a funder report.
This is the stage record-keeping software cannot do. Every case note is read as it lands, coded against the service plan, with risk signals — missed appointments, disengagement, safeguarding language, escalation — surfaced the week they appear instead of at the director's month-end sample. The narrative stays with the case manager; the structure is generated and tied back to the source sentence.
Read this batch of case notes: [NOTE BATCH]. For each participant, summarize progress against the service plan with citations, code the note against our outcome indicators, and flag risk signals — missed appointments, disengagement, safeguarding or escalation language — with the exact source sentence. Use the same method as last month so results are comparable across the reporting period.
Expected output. Per-participant progress summaries with citations, coded outcome evidence, and a risk-flag list with sources — the day notes are written, not six weeks later. For the note layer on its own, see case notes software.
Tips for reliable output. Route every risk flag to a named owner with a deadline. A flag nobody owns is a finding that sat there — and in a youth or family program, a finding that sat there is exactly what a funder audit asks about.
Closure is not the end of the record. The 90-day, one-year, and three-year follow-ups land on the same client ID as the intake assessment, so the question every funder asks — did the situation actually improve — has a reproducible answer instead of a year-end reconstruction. Re-engaging participants arrive with their full history attached, across whichever program brought them back.
Compare the baseline assessment to the [90-day / 1-year] follow-up across [COHORT / PROGRAM]: which outcomes moved, by how much, and with what confidence? Show change per indicator, note where the sample is too small to conclude, and pair every number with a representative case-note quote. Treat this as change over time, not attribution, so the funder report stays defensible.
Expected output. A baseline-to-follow-up outcome analysis with honest confidence bounds and a narrative quote behind each number — the longitudinal view a persistent ID makes possible, and the one a board wants to see.
Tips for reliable output. Capture contact channels and follow-up expectations at intake, not at exit. The longitudinal horizon is what separates an exit survey from an outcome — and what lets you go back to a funder with a three-year story instead of a one-year snapshot.
Reports are questions, not formats. From the same accumulating client record, the caseload report, the director's dashboard, the funder outcome report, the board summary, and the Form 990 Schedule I program detail are each one query — with the supporting case note two clicks away — instead of a two-to-four-week reassembly across intake, services, and follow-up systems every reporting cycle.
Aggregate this program's participant records into a [funder] outcome report: outcomes achieved against the targets in our grant, coded case-note themes ranked by frequency with representative quotes, demographic distribution, and participants flagged as missing a required follow-up. Cite the source participant record for every number and quote. Format one version for the board and one for the funder, and a short program-accomplishments paragraph suitable for Form 990 Schedule I.
Expected output. A funder-ready outcome report generated as a query, every figure citing its source record — plus the "missing" list surfaced before the deadline asks, and a Schedule I paragraph you can hand to whoever files the 990.
Tips for reliable output. Lock the data dictionary before the first reporting cycle and version every change — comparability across years is the entire value when a multi-year funder wants a trend, not a one-off number. If your outcome framework needs an external anchor funders recognize, align it to IRIS+ so metrics are comparable beyond your own walls.
Beyond table stakes — intake, caseload views, services logging, security — four criteria actually separate tools for a nonprofit: time to first live cycle (days vs. a quarter your grant timeline can't afford), whether AI reads case notes on arrival or a director still samples them by hand, whether configuration is plain-English or a consultant engagement your budget can't sustain, and whether the platform can prove participant outcomes to a funder rather than just count services. Ask every vendor to show the funder outcome report on real data, not a slide.
The evaluation itself is work you can delegate to AI. These prompts mirror what nonprofit buyers are already asking answer engines — use them as they are:
Build an evaluation matrix for nonprofit case management software with technical and program criteria weighted 50/50. Technical: security and field-level access control, integrations with our donor/CRM or accounting system, configuration model, data export and exit rights. Program: AI case-note reading with citations, one client ID across programs, longitudinal outcome tracking, funder and board report generation. Score vendors [VENDOR LIST] on each criterion with evidence required, not vendor claims.
Propose a 30-day pilot plan to evaluate nonprofit case management software: one program, one cohort of roughly 50 current participants, tested end to end (intake → assessment → service plan → case-note reading → funder outcome report), with numeric success thresholds and rollback criteria if the pilot fails.
A note on scope while you evaluate: the same spine adapts by discipline with a different intake and funder report — social work case management software and human services case management software each cover their fit directly, and every participant's story ultimately rolls up into stakeholder intelligence across your whole organization. If a grant funds the work, keep the reporting tied to grant management software so outcomes and dollars tell one story.
The stages above are the argument; the Academy articles are the practice — each a hands-on companion for one workflow, written to run on your own data.
Honest boundaries, because the fastest way to a failed implementation on a nonprofit budget is buying the wrong category.
Not a donor CRM, and not an EHR. A donor CRM (Salesforce, Blackbaud, Bloomerang) tracks donors, gifts, and relationships; an EHR (Epic, Cerner) tracks clinical encounters and billing. Nonprofit case management software tracks participants through a service-delivery lifecycle, with case-note narrative and outcome evidence at the center. That said, the two worlds should meet: case intelligence connects program outcomes to donor and fundraising data on a shared record, so development can tell funders what their dollars changed — see stakeholder intelligence for where those layers join.
Not your accounting or grants-payment system. The general ledger and the grant-drawdown engine stay in the systems built for them; case intelligence integrates on one shared record rather than replacing them, and connects the outcome story back to grant management software so the funder report and the financials agree.
Not for every compliance regime. Sopact provides AES-256 encryption, TLS 1.3, field-level role-based access, SSO/MFA, and full audit logging, with AI under enterprise SLAs and no training-data retention — but Sopact is not currently HIPAA-certified or covered by a Business Associate Agreement. If your program is subject to HIPAA, FERPA, 42 CFR Part 2, or county behavioral-health rules, evaluate these controls against your compliance program and confirm scope in writing before storing protected information. And if your use case is purely a data warehouse, Sopact is not the ideal system for that.
Nonprofit case management software is a platform that holds one persistent record per participant across every program a nonprofit runs — intake, assessment, service plan, case notes, services delivered, and outcome follow-up — so program staff, directors, and boards get answers without a spreadsheet merge before each funder deadline. Also called case management software for nonprofits or client tracking software. The newest generation adds AI that reads each case note on arrival and turns follow-up into cited outcome evidence for funder and board reporting.
The best nonprofit case management software is one that reads every case note on arrival rather than waiting for a year-end review, keeps one persistent client record across every program a participant touches, generates funder and board outcome reports as queries instead of CSV merges, and supports longitudinal follow-up at 90 days, one year, and three years on the same participant ID. Legacy choices like Bonterra Apricot, Salesforce Nonprofit Cloud, Penelope, and Casebook were built for a configure-heavy era; AI-native platforms like Sopact treat configuration as conversation and generate the outcome report as a query. The right answer depends less on the feature list than on which tool can show your own outcome report on real data during evaluation.
Pricing varies widely — legacy platforms often quote per-seat or per-caseload licenses plus a separate implementation fee, which is what makes them expensive for a small nonprofit with no IT. Sopact is priced by use-case complexity, not by seats or caseload: how many programs share the client record, how custom the data dictionary is, which built-in skills are activated, longitudinal depth, and integration to your CRM or accounting system. A 12-person family services nonprofit running one program pays less than a 50-person multi-program agency. Because the model is all-inclusive rather than per-seat, adding a case manager or a board reviewer does not change the price.
Free and spreadsheet options exist and cover basic service logging, and some vendors offer discounted or grant-funded tiers for small nonprofits. But the cost does not disappear — it moves elsewhere: lost continuity when a case manager turns over, manual outcome reporting the week before every grant deadline, and the staff hours spent reconciling intake, services, and follow-up at year-end. For a program that has to prove outcomes to keep its funding, the question is not "is it free" but "what does it cost me at report time."
Six questions separate platforms that work from platforms that only demo well: How long until our first cycle is live, measured against our grant timeline? Will every case note get read, or just the ones a director samples? Does the same participant appear as one record across all our programs and grants? Is the funder report a query, or a CSV merge? When a funder or auditor asks why this outcome, can I show the supporting case note in two clicks? And does the system work offline for field work? Then run a contained pilot on your own data before you commit.
Both were built for the configure-heavy era. Bonterra Apricot is closer to community-services casework out of the box, with prebuilt intake and outcome templates familiar to human-services nonprofits; integrator work is still required for real outcome reporting. Salesforce Nonprofit Cloud is more flexible but requires significant integrator work — and budget — to become a real case management system, and Einstein AI is an add-on rather than native. Both produce numbers; neither reads case notes on arrival. AI-native case intelligence avoids both the configuration cost and the year-end reporting cost — and often runs alongside an incumbent as the reading layer rather than replacing it, which is exactly the "AND" most nonprofits ask for.
Yes, on a shared record. The point of connecting them is not to merge two systems but to let development tell funders what program dollars actually changed — the outcome story next to the gift. Case intelligence keeps the participant record as the spine and connects to donor/CRM and fundraising data so the board sees outcomes and revenue as one picture rather than two disconnected reports. For how those layers join across an organization, see stakeholder intelligence.
Look for AES-256 encryption at rest, TLS 1.3 in transit, role-based access to the field level, SSO with MFA, and full audit logging — all of which Sopact provides, with no training-data retention on AI calls. Sopact is not currently HIPAA-certified or covered by a Business Associate Agreement; if your casework touches protected health information under HIPAA, FERPA, or 42 CFR Part 2, treat that as gating and confirm scope in writing before storing protected data. Sensitive fields can be excluded from AI processing entirely, and analysis can run on anonymized IDs.
Yes — when it is built around one persistent client record. A family receiving family services, workforce navigation, and housing support from the same nonprofit appears as one record with three service streams, not three separate cases. Multi-program nonprofits use this to coordinate across teams, recognize re-engaging participants automatically, and report at the organization level — and to the whole 990 — instead of reconstructing the picture per program, and per grant, at year-end.
Two months, one contained use case — one program, one intake form, one cohort of participants you already serve. You bring last year's case notes; the pilot shows you the coded, cited version of your own caseload, ending with a demonstrated funder outcome report. If the outcome answers aren't defensible in front of your board or funder, don't continue. Scope a 2-month pilot →