A plain-language guide to case management: the definition, the process and its stages, the main models, best practices, and how a case management system turns record-keeping into case intelligence.
Case management is how a program carries one person from intake to outcome — assess the need, plan the services, deliver them, follow up to see what changed. For two decades the software that supported it was built to collect: log the intake, record the service, file the year-end report. Collection is solved.
The client is the unit of work, and the client record has to be intelligent. This guide explains what case management is — the process, the models, the best practices, the systems — and how the field is moving from record-keeping to case intelligence: software that reads every case note on arrival and surfaces the outcome on Tuesday, not at year-end.
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, nonprofits, and human services the person (the client or participant) is the unit of work, and a case manager carries that person across every interaction.
The same phrase names the software that holds the record — a case management system — one persistent file per person from first contact through follow-up. Related searches include case management meaning, case management services, and case management in social work; all point to the same lifecycle.
This guide covers:
A note on scope: this guide is about case management in social services, human services, and nonprofits — not legal case management (court matters), clinical nursing case management, or IT/HR ticketing, which use the same words for different work.
For two decades the category was defined by the record: open the case, log what was delivered, file the report. That was the right tool for getting the case file out of the filing cabinet. Collection is now solved — every system runs a basic intake → service → 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.
| Case management as record-keeping | Case management as case intelligence |
|---|---|
| Open the case, log the service, file the year-end report | Read what changed and surface risk as data lands |
| A separate case per program, reconciled by name at year-end | One client ID across every program, full history two clicks away |
| Case notes filed as documents, sampled monthly by a supervisor | Every note read on arrival; risk and drift surfaced before Monday |
| Outcome surveys land in a spreadsheet nobody links to intake | Baseline and follow-up on the same record, scored together |
| The funder report is a multi-week reconstruction | The report is one query off the same records, note attached |
Frameworks differ in their wording, but almost every one describes the same arc from first contact to closure. The stages are a loop, not a line — monitoring routinely sends a case back into reassessment until the goals are met.
Confirm eligibility, open the case, and assign the client a persistent ID. This is the load-bearing step — the ID assigned here is what every later stage attaches to.
Capture the baseline: needs, strengths, risks, and goals. The assessment is the reference point every later wave is compared against, so it has to be structured and consistent.
Agree a service plan with measurable goals and timelines. A good plan names what success looks like, so monitoring later has something concrete to measure against.
Deliver or coordinate the services in the plan — directly, or by brokering to partner providers. Case notes capture what happened at each contact.
Track progress against the plan and adjust. This is where caseload size matters: monitoring is only real if the case manager has the time to actually do it.
Measure the outcome against the baseline, then close or transition the case. This is the stage record-keeping software skips — and the one a funder cares about most.
The four levels of case management intensity — from light-touch monitoring to intensive case management (ICM) — change how often Stages 4 and 5 repeat, not the shape of the process.
“Types of case management” usually means one of these 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.
The case manager assesses needs and links the client to external services, with light ongoing contact. Caseloads are large; the work is connection, not direct service. Common in resource-referral and benefits programs.
The case manager also provides direct therapeutic support alongside coordination. Used where the relationship itself is part of the intervention — behavioral health, family services.
Planning starts from the client’s own assets and goals rather than their deficits. The dominant frame in modern social work; pairs naturally with narrative case notes.
Small caseloads, frequent contact, for high-need clients — homelessness, severe mental illness, reentry. The most resource-intensive, and the most dependent on continuity of record.
The general-purpose model used across most human-services programs: assess, plan, coordinate, monitor, evaluate, at a moderate caseload. When people say “case management” without a qualifier, this is usually what they mean — and it is the model the rest of this guide assumes.
The model decides the cadence and the caseload. It does not change the one thing every model needs: a continuous record per client, so that the work in one stage is visible in the next.
These are the recurring patterns across case management systems that produce funder-renewable evidence year over year. None require new tooling. All require deciding before the case opens, not at year-end.
Assign a unique ID at first contact and reuse it on every form, note, and follow-up. The single highest-leverage practice — without it, every later comparison is a manual match.
Capture the baseline at intake, before the program changes anyone. No baseline, no change to evidence later — the most common reason a program fails funder scrutiny.
A number tells you what changed; the case note tells you why. Collect both at the same moment, on the same record, so the narrative explains the score.
Monitoring is only real if the case manager has time to do it. An ICM caseload run at brokerage size produces nominal monitoring and biased data.
Capture contact channels and set follow-up expectations at the start, not at exit. The longitudinal horizon is what separates an exit survey from an outcome.
Get clear, appropriate consent; limit who sees identifiable data; be specific about how data is used. The trust that makes follow-up possible is built here.
Effective case management is mostly these six, decided early. The software’s job is to make the right practice the easy one — the ID automatic, the baseline structured, the note read on arrival.
The six-stage process above is what a case manager does. The five-stage spine below is what the software does underneath it — built once, so every program plugs into one continuous client record instead of re-collecting at each stage.
Structured fields, open-ended answers, documents, and assessments arrive on one form — and one persistent client ID, not a folder.
Your theory of change or outcome rubric, encoded as the framework every client record is evaluated against. The funder’s questions, built in.
Every field and code list in one dictionary, configured in plain English — what keeps the record readable after the case manager leaves.
Built-in skills read each case note on arrival and code it against the rubric with attribution — not a black box.
The funder report as one query, each number citing its case note. Clean exports drop into Looker Studio, Power BI, or Tableau.
Open Play Foundation had been running programs for years. The case notes, attendance logs, and outcome surveys lived in different systems, the way they do at almost every organization. The structured system recorded what was delivered. It was never built to read what changed. Until those records lived on one client, the team couldn’t see what was happening across the caseload — only what each spreadsheet told them.
That is the whole difference between case management and case intelligence. The process didn’t change — intake, assessment, plan, service, follow-up. What changed is that the record could finally be read: the pattern buried across files became a single query, and the answer showed up on Tuesday, not at year-end.
A case management system is the software that holds one record per client across the whole lifecycle. It is routinely confused with three other tools that share some of its features. The difference is what each was built around — and which one owns the outcome.
| What it’s built around | Case management system | CRM | EHR | Spreadsheet |
|---|---|---|---|---|
| One persistent client record, intake→outcome | Yes · core | Partial | Yes (clinical) | No |
| Service plan & case-note narrative at the center | Yes · core | No | Partial | No |
| Outcome / change measurement over time | Yes | No | Limited | Manual |
| Primary job it was designed for | Service & outcome lifecycle | Donors & relationships | Clinical encounters & billing | Ad-hoc lists |
| One client across multiple programs | Yes | Partial | No | No |
| Reads the narrative on arrival (case intelligence) | Yes · Sopact | No | No | No |
A case management CRM is a CRM stretched to do casework — it tracks the relationship well but rarely owns the service plan or the outcome. The cleanest stack keeps the CRM for fundraising and a purpose-built case management system for the client lifecycle, sharing one ID. See the case management system and case management platform guides for how to choose one.
This guide is the hub. The concept guides go deeper on each piece; the software guides show what it looks like for a specific kind of program. Read in any order.
The six stages in depth — screening, assessment, planning, implementation, monitoring, evaluation.
Brokerage, clinical, strengths-based, intensive, and standard — with the caseload each one implies.
The six principles that decide whether the measurement holds, with the practice behind each.
The platform layer — intake, AI reading, and reporting on one record.
Plain answers to the questions people ask when case management comes up — the definition, the process, the models, and the systems behind it.
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 / 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 / closure (measure the outcome and close or transition). The stages loop — monitoring often sends a case back into reassessment until the goals are met.
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.
Assign one persistent client ID at first contact and reuse it everywhere; capture a baseline at intake so change can be measured; pair every quantitative score with a short narrative; size caseloads so monitoring is real; plan follow-up at intake rather than at exit; and protect client data with role-based access and clear consent. The single highest-leverage practice is the persistent ID — without it, every later comparison becomes a manual matching project.
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.
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.
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.
Traditional case management software was built to collect — log the intake, record the service, file the year-end report. Collection is now solved. Case intelligence is the next step: 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. The client is still the unit of work — but now the client record is intelligent.
Programs use purpose-built case management systems and platforms — some general (Bonterra Apricot and ETO, CaseWorthy, Casebook), some built on a CRM (Salesforce, Microsoft Dynamics), and some, like Sopact, built around reading the case note and proving the outcome. The right choice depends on whether you need a record of services delivered or evidence of change over time. The case management system and case management platform guides walk through how to choose.
Case management is used wherever an organization helps the same people over time: human-services and community-action agencies, social work and child welfare, housing and homelessness programs, workforce and reentry, youth and after-school programs, and behavioral health. The vocabulary shifts by field — client, participant, member, household — but the lifecycle is the same: assess, plan, serve, monitor, evaluate.
No demo theater. No discovery phase. Tell us what you run and which funder reports you owe. We’ll 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.
