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.
Case management is the coordinated process of moving a person from intake to outcome — its stages, models, and best practices, and the shift to reading case notes on arrival.
Case management is the coordinated process of helping a person move from intake to outcome — assessing their needs, planning the services that address them, connecting them to those services, and following up to see whether their situation actually improved. In social services, human services, and nonprofits the person — the client or participant — is the unit of work, and a case manager carries that person across every interaction so nothing is dropped between one contact and the next.
The same phrase names two things at once: the practice (what a case manager does) and, increasingly, the software that holds the record — a case management system, one persistent file per person from first contact through follow-up. Related searches — case management meaning, case management definition, case management services, case management in social work — all point to the same lifecycle.
A note on scope. This is case management in social and human services and nonprofits — not legal case management (court matters and litigation), not clinical nursing case management inside a hospital, and not IT or HR ticketing, all of which borrow the same words for different work.
Frameworks differ in wording, but nearly every one describes the same arc from first contact to closure — six stages. It is a loop, not a line: monitoring routinely sends a case back into reassessment until the goals are met.
1. Screening and intake. Confirm eligibility, open the case, and assign the client a persistent ID that every later stage attaches to. 2. Assessment. Capture the baseline — needs, strengths, risks, and goals — the reference point every later wave is measured against. 3. Planning. Agree a service plan with measurable goals and real timelines, so monitoring later has something concrete to check. 4. Implementation. Deliver or coordinate the services in the plan, directly or by brokering to partners; case notes capture what happened at each contact. 5. Monitoring. Track progress against the plan and adjust — only real if the caseload is sized so the case manager has time to do it. 6. Evaluation and closure. Measure the outcome against the baseline, then close or transition the case.
For the six stages in depth — what each one produces and where each one fails — see the case management process guide, and the case management workflow for how the stages connect into one continuous record.
"Types of case management" usually means one of five models. They differ mostly in how much direct service the case manager provides and how large the caseload runs; most real programs blend two or three.
Brokerage model. The case manager assesses needs and links the client to external services with light ongoing contact — large caseloads, connection over direct service, common in resource-referral and benefits programs. Clinical model. The case manager also provides direct therapeutic support alongside coordination, used where the relationship itself is part of the intervention — behavioral health, family services. Strengths-based model. Planning starts from the client's own assets and goals rather than their deficits; the dominant frame in modern social work, pairing naturally with narrative case notes. Intensive case management (ICM). Small caseloads and frequent contact for high-need clients — homelessness, severe mental illness, reentry — the most resource-intensive and the most dependent on continuity of record. Standard or generalist model. The general-purpose model across most human-services programs: assess, plan, coordinate, monitor, evaluate at a moderate caseload. When people say "case management" with no qualifier, this is usually what they mean.
The model decides the cadence and the caseload. It does not change the one thing every model needs: a continuous record per client, so the work in one stage is visible in the next.
A handful of principles decide whether the work produces funder-renewable evidence year over year. None require new tooling; all require deciding before the case opens, not at year-end. Assign one persistent client ID at first contact and reuse it everywhere. Capture a baseline at intake, before the program changes anyone. Pair every quantitative score with a short narrative — the number says what changed, the case note says why. Size the caseload to the model, so monitoring is real rather than nominal. Plan follow-up at intake, not at exit — the longitudinal horizon is what separates an exit survey from an outcome. And protect client data with role-based access and clear, appropriate consent.
The single highest-leverage practice is the persistent ID — without it, every later comparison becomes a manual matching project. For the full set with the practice behind each, see case management best practices.
For two decades the software that supported this work was built to collect: log the intake, record the service, file the year-end report. Collection is now solved — every system runs a basic intake, service, and outcome flow. The work moved. The hard part is no longer logging the service; it is reading the case note, the assessment, and the follow-up survey as they arrive, and carrying one client across every program so the outcome story is one query rather than a year-end reconstruction.
The richest evidence a program holds — the case notes — historically sat unread, piling up in a system nobody read across, sampled once a month by a supervisor if at all. Case intelligence reads them on arrival: every case note scored against the service plan with a citation trail, risk and drift surfaced the week they appear, and the baseline and follow-up on the same record so change is scored, not reconstructed. The client is still the unit of work — but now the client record is intelligent.
The part that changes daily work is the Assistant: caseload analysis, screen scoring, and open-text case-note reading unified into one chat-based function. Ask a question, get a defensible answer with citations to the underlying records — 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, and funders each need a different view of the same record, and a chat interface serves each of them directly. When the analysis is done, it becomes shareable reports tailored to each audience, every number traceable to the source case note. The lifecycle below shows what the software does underneath the six-stage process.
The prompts below are the same ones buyers paste into the Assistant to run the lifecycle on their own data. Placeholders in brackets are yours to fill.
Intake is where clean-at-source pays or fails. Instead of free text a caseworker decodes later, the form is designed so every narrative field maps to your framework, and every client gets a persistent ID that follows them across programs and years.
Build a client intake form from this program description: [PROGRAM URL OR DOCUMENT]. Map narrative fields to our theory of change, add eligibility screening with clear pass/fail criteria, and assign a persistent client ID at first contact. Flag any question that collects information we already hold on returning clients.
This is the stage record-keeping software cannot do. Every note is read as it lands, coded against the service plan, with risk signals surfaced the week they appear instead of at a month-end sample.
Read this batch of case notes: [NOTE BATCH]. For each client, 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 stay comparable.
Reports are questions, not formats. From the same accumulating client record, the caseload view, the supervisor dashboard, and the funder outcome report are each one query — with the supporting case note two clicks away.
Aggregate this program's client records into a [funder] 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.
The sections above are the argument; the Academy article is the practice — a hands-on companion written to run on your own data.
Case management is the coordinated process of helping a person move from intake to outcome — assessing their needs, planning the services that address them, connecting them to those services, and following up to see whether their situation actually improved. The person — the client or participant — is the unit of work, and a case manager carries that person across every interaction. The same word also names the software that holds the record: one persistent file per person, from first contact through follow-up.
Most frameworks describe six stages: screening and intake (confirm eligibility, open the case), assessment (capture the baseline needs and goals), planning (agree a service plan with measurable goals), implementation (deliver or coordinate services), monitoring (track progress and adjust), and evaluation and closure (measure the outcome and close or transition). The stages loop — monitoring often sends a case back into reassessment until the goals are met. See the case management process guide for depth.
The common models are the brokerage model (link the client to external services, light contact), the clinical model (the case manager also provides direct therapeutic support), the strengths-based model (planning starts from the client's own assets), intensive case management or ICM (small caseloads, frequent contact, high-need clients), and the standard or generalist model used across general social services. Most programs blend two or three depending on caseload size and client need.
In social work, case management is the practice of assessing a client's situation, building a plan that addresses their needs and goals, connecting them to resources, and following up to see whether their circumstances improved. It is client-centered and strengths-based: the plan starts from the client's own goals, and the social worker carries the case across every interaction. The narrative case note — what changed and why — is as important as the structured data. For the discipline-specific tooling, see social work case management software.
A case management system is the software that holds one record per client across the whole lifecycle — intake, assessment, service plan, case notes, services delivered, and outcome follow-up — so a team can answer questions without a spreadsheet merge. It differs from a CRM, which tracks donors and relationships, and from an EHR, which tracks clinical encounters and billing. A case management system is organized around the client's service-and-outcome journey, with case-note narrative and outcome evidence at the center. For the buyer's overview and vendor comparison, see case management software.
Care coordination is one activity inside case management: making sure the services a person receives from different providers fit together. Case management is the broader lifecycle that surrounds it — assessing needs, building a plan, delivering or brokering services, monitoring progress, and evaluating the outcome. Care coordination keeps today's services aligned; case management owns the whole arc from intake to outcome.
Case intelligence is the next step after collection: the software reads every case note, assessment, and follow-up survey as it arrives, scores it against the program's framework with a citation trail, and carries one client across every program so the outcome is a single query rather than a year-end reconstruction. Traditional case management software was built to log the intake and file the report; case intelligence reads what those records actually say. The client is still the unit of work — but now the client record is intelligent. For how this looks by program type, see nonprofit case management software and human services case management software.
No demo theater, no discovery phase. Tell us what you run and which funder reports you owe, and we will show you what the first 30 days look like on Sopact — one client record, the case note read on arrival, the outcome as one query. Book a 20-min walkthrough →