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.
Reads every case note on arrival — safeguarding signals, not month-end samples.
Social work case management software is a platform that holds one persistent record per client across the whole casework lifecycle — referral, intake, biopsychosocial assessment, service or treatment plan, progress notes, services delivered, and outcome follow-up — so social workers, supervisors, and program directors get answers without stitching spreadsheets and Word documents together. It is also called case management software for social workers, a social work client database, or social services case management software. The newest generation adds intelligence to the record itself: AI reads each case note on arrival, scores it against the service plan with citations, flags safeguarding language the week it appears, and turns follow-up screens into outcome evidence — so the software answers whether the client's situation actually improved, not just what was documented.
Used by: child welfare and child protective services · behavioral health and substance-use programs · adult protective services (APS) and aging services · family services and family preservation · school social work · medical and hospital social work · multi-program agencies coordinating one client across teams.
Not because the software stopped working — because storing the client and logging the service became table stakes. Penelope (Athena), Bonterra (Apricot, ETO), Casebook, ClientTrack, and CaseWorthy earned their positions honestly: they got casework out of the paper file, standardized the intake, and gave agencies a real system of record. If your problem was collection — hundreds of clients, a dozen caseworkers, one county audit deadline — that generation solved it.
But the strengths hardened into weaknesses. Implementations run three months to a year; agencies describe legacy builds where every new program, funder, or validated screen is another integrator engagement. 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."
The cost of not reading is concrete, and in social work it is measured in people. 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 casework is safe and effective has moved to the two ends the record-keeping tools never owned: reading every case note and assessment on arrival — surfacing safeguarding and risk language before the next supervision — and proving the outcome months and years later on the same client.
Permissions are where this gets real for social work. As one foundation put it, "therapists need to be able to create quite sensitive case notes… but the bus driver only needs to see names, addresses." Field-level role-based access is not a nice-to-have when the record holds a child-at-risk flag — it is the difference between a defensible deployment and a breach. Legacy stacks bolt this on; an intelligent record treats it as structure.
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. The stake, stated honestly: county auditors, boards, and funders have already changed the question from "how many did you serve" to "did their situation improve, and can you show it." If you are signing a multi-year configuration build today, ask which question it will be able to answer when it finally goes live.
Social work case intelligence is reliable answers from your case data — in minutes, not months. Everything a client touches is treated as data: the referral, the biopsychosocial assessment, the validated screen (PHQ-9, GAD-7, VI-SPDAT, or your own indicator), the treatment plan, every progress note, the 90-day and year-three follow-up. All of it lands on one persistent client record, aligned to your framework and data dictionary, so the same person looks like the same person across three programs and five years.
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 analyst who knows where the export lives. A program is never one user — caseworkers, supervisors, finance, the board, funders, and clients themselves all need different views of the same record — and a chat interface empowers each of them directly, with sensitive fields excludable from AI processing entirely.
When the analysis is done, it does not die in the chat: create shareable reports tailored to each audience — the supervisor's caseload view, the funder outcome report, the county behavioral-health submission — 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 organizations 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.
The honest way to evaluate social work case management software is against the casework lifecycle, not the feature list. Nearly every framework describes the same arc — and it is a loop, not a line: monitoring routinely sends a case back into reassessment until the goals are met or the case safely closes. 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 caseworker to decode later, the form is designed so every narrative field maps to your framework, and every client gets a persistent unique ID that follows them across programs and years. Eligibility screening, consent and confidentiality notice, save-and-return — and AI drafts the intake form from the program documents you already have.
Build a social work intake form from this program description: [PROGRAM URL OR DOCUMENT]. Create structured fields for demographics, eligibility, and consent; narrative fields for presenting needs and safety concerns 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 returning clients.
Expected output. A ready-to-edit intake form: structured fields, mapped narrative prompts, eligibility gates, and a persistent client ID assigned at first contact.
Tips for reliable output. Give the AI your theory of change and data dictionary before form design. Assign the client ID at referral, not at enrollment — everything downstream attaches to the ID created here.
The baseline is the reference every later wave is compared against. Validated screens (PHQ-9, GAD-7, VI-SPDAT, AAPI-2, or your own indicator) and the biopsychosocial 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 biopsychosocial assessment, extract the client'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 clients, proves the loop works before anything scales.
Every client gets a service or treatment plan built from the assessment and mapped to your framework — goals that are observable, timelines that are real, and the outcome each service is meant to move. The plan becomes the thing progress notes are later read against.
Draft a service and treatment 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. Write goals as observable statements a caseworker can evidence, and flag any need with no service currently available.
Expected output. A treatment or service plan with measurable goals, mapped services, outcome indicators, 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.
This is the stage record-keeping software cannot do. Every progress note is read as it lands, coded against the treatment plan, with risk signals — missed appointments, disengagement, safeguarding language, escalation — surfaced the week they appear instead of at the supervisor's month-end sample. The narrative stays with the caseworker; the structure is generated and tied back to the source sentence, so a safeguarding flag arrives with the exact words that triggered it and goes to a human.
Read this batch of progress notes: [NOTE BATCH]. For each client, summarize progress against the treatment plan with citations, code the note against our outcome indicators, and flag risk and safeguarding signals — missed appointments, disengagement, child-at-risk or self-harm language, escalation — with the exact source sentence, routed for human review. Use the same method as last month so results are comparable.
Expected output. Per-client progress summaries with citations, coded outcome evidence, and a safeguarding-flag list with source sentences and a named human reviewer — the day notes are written, not six weeks later.
Tips for reliable output. Route every safeguarding flag to a named owner with a deadline. A flag nobody owns is a finding that sat there while a child waited.
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 and county asks — did the situation actually improve — has a reproducible answer instead of a year-end reconstruction. Re-engaging clients arrive with their full case history attached.
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.
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.
Tips for reliable output. Capture contact channels and follow-up expectations at intake, not at exit. The longitudinal horizon is what separates a closure summary from an outcome.
Reports are questions, not formats. From the same accumulating client record, the caseload report, the supervisor dashboard, the funder outcome report, and the HMIS or county behavioral-health submission 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.
Aggregate this program's client records into a [funder / county] outcome report: outcomes achieved against targets, coded case-note themes ranked by frequency with representative quotes, demographic distribution, and clients flagged as missing a required follow-up. Cite the source client record for every number and quote. Format one version for the board and one for the funder.
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.
Tips for reliable output. Lock the data dictionary before the first reporting cycle and version every change — comparability across years is the entire value. If your outcome framework needs an external anchor, align it to the practice standards published by the National Association of Social Workers (NASW) so your indicators are legible beyond your own agency.
Beyond table stakes — intake, caseload views, services logging, security — four criteria actually separate tools: time to first live cycle (days vs. a quarter), whether AI reads case notes on arrival or a supervisor still samples them by hand, whether configuration is plain-English or a consultant engagement, and whether the platform can prove client outcomes and surface safeguarding signals rather than just count services. Ask every vendor to show the outcome report on real case data, not a slide.
The evaluation itself is work you can delegate to AI. These prompts mirror what buyers are already asking answer engines — use them as they are:
Build an evaluation matrix for social work case management software with technical and program criteria weighted 50/50. Technical: security and field-level access control (therapist vs. non-clinical roles), integrations with our HMIS or billing system, configuration model, data export and exit rights, offline/field support. Program: AI case-note reading with citations, safeguarding-signal detection, one client ID across programs, longitudinal outcome tracking, funder report generation. Score vendors [VENDOR LIST] on each criterion with evidence required, not vendor claims.
Propose a 30-day pilot plan to evaluate social work case management software: one program, one cohort of roughly 50 current clients, tested end to end (intake → assessment → treatment plan → progress-note reading → 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 vertical with a different intake and funder report — the parent case management software hub, nonprofit case management software, and human services case management software each cover their fit directly. For the note layer itself, see case notes software; for caseworker capacity and drop-off signals, caseload management software. To carry one client across every program a family touches, see stakeholder intelligence.
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 case data.
Honest boundaries, because the fastest way to a failed implementation is buying the wrong category.
Not a CRM, and not an EHR. A CRM (Salesforce, Blackbaud) tracks donors and relationships; an EHR (Epic, Cerner) tracks clinical encounters and billing in a hospital system. Social work case management software tracks clients through a service-delivery lifecycle, with case-note narrative and outcome evidence at the center. The CRM keeps the relationship history; the EHR keeps the clinical visit; social work casework keeps the service record, the narrative, and the outcome.
Not your billing or HMIS system. The Medicaid or insurance billing engine and the HMIS submission stay in the systems built for them; case intelligence integrates on one shared record rather than replacing them.
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 agency is subject to HIPAA, FERPA, 42 CFR Part 2, state child-welfare confidentiality rules, or county behavioral-health requirements, evaluate these controls against your compliance program and confirm scope in writing with your counsel before storing protected information. And if your use case is purely a data warehouse, Sopact is not the ideal system for that.
Social work case management software is a platform that holds one persistent record per client across the casework lifecycle — referral, intake, biopsychosocial assessment, service or treatment plan, progress notes, services delivered, and outcome follow-up — so social workers, supervisors, and directors get answers without a spreadsheet merge. Also called case management software for social workers or a social work client database. The newest generation adds AI that reads each case note on arrival, flags safeguarding language, and turns follow-up into cited outcome evidence.
The best social work case management software is one that reads every case note on arrival rather than waiting for a supervisor's monthly review, surfaces safeguarding signals the week they appear, keeps one persistent client record across every program a client touches, generates caseload and funder reports as queries instead of CSV merges, and supports longitudinal follow-up at 90 days, one year, and three years on the same client ID. Legacy choices like Penelope, Bonterra Apricot, Bonterra ETO, Casebook, and CaseWorthy were built for a configure-heavy era; AI-native platforms like Sopact treat configuration as conversation and generate outcome reports as queries.
Yes — free tiers, spreadsheet workflows, and open-source social work case management tools exist, and they cover basic service logging honestly. But the cost moves elsewhere: lost case continuity when staff turn over, safeguarding signals that sit unread, manual outcome reporting, and the staff hours spent reconciling intake, services, and follow-up at year-end. Outcome and safeguarding work tends to outgrow the free options within the first reporting cycle — a small agency that values its social workers' time usually finds a low-cost paid platform pays back quickly.
Most social work agencies run some combination of an intake form, a case-note or progress-note store, a validated-screen scoring tool, a caseload tracker, and a year-end outcome or funder report — often across separate systems. Case intelligence collapses those into one persistent client record: the intake, the biopsychosocial assessment, the treatment plan, every progress note, and the follow-up screen all attach to the same client ID, read on arrival and reportable as a query.
Look for AES-256 encryption at rest, TLS 1.3 in transit, role-based access to the field level (therapist vs. non-clinical roles), 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 with your counsel. Sensitive fields can be excluded from AI processing entirely, and analysis can run on anonymized IDs.
Field social work — home visits, shelters, rural casework — often happens where connectivity does not. Look for save-and-return intake, mobile-friendly note capture, and a record that reconciles cleanly when the worker is back online, so a case note written at a kitchen table lands on the same client ID as everything else. Ask every vendor to demonstrate the offline-to-synced path on a real note, not a slide.
Yes — when it is built around one persistent client record. A family receiving child welfare services, behavioral health counseling, and housing support appears as one record with three service streams, not three separate cases. Multi-program agencies use this to coordinate across teams, recognize re-engaging clients automatically, and report at the agency level instead of reconstructing the picture per program at year-end — with field-level permissions so the therapist and the non-clinical role each see only what their job requires.
AI reads every progress note on arrival and codes it against the treatment plan and the validated screens the client completed at intake. Safeguarding and risk signals — child-at-risk language, self-harm mentions, missed appointments, disengagement, treatment-plan deviations — surface the week they appear instead of at the supervisor's monthly review, each flag carrying the exact source sentence and routed to a named human reviewer. The narrative stays with the social worker; the structure is generated automatically and tied back to the source. For the note layer specifically, see case notes software.
Two months, one contained use case — one program, one intake form, one cohort of clients you already serve. You bring last year's case notes; the pilot shows you the coded, cited, safeguarding-aware version of your own caseload, ending with a demonstrated export. If the outcome answers aren't defensible in front of your board, funder, or county auditor, don't continue. Scope a 2-month pilot →