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.
The six stages of the case management process — intake, assessment, planning, implementation, monitoring, evaluation — as a loop, plus intensity levels.
The case management process is the coordinated sequence a case manager follows to move a client from first contact to outcome. Most frameworks describe six stages — screening & intake, assessment, planning, implementation, monitoring, and evaluation & closure — and it is a loop, not a line: monitoring routinely sends a case back into reassessment until the goals are met. The terms vary by field — some models add an engagement step before assessment, and many treat advocacy as a thread running through every stage rather than a separate step — but the arc is consistent: assess the need, plan the response, deliver it, check whether it worked, and loop until it does.
People also search this as the case management steps, the stages of case management, or the "7 steps of case management" — the seven-step version simply splits intake from engagement, or planning from goal-setting. The underlying spine is the same. Below is each stage in depth: what it captures, where it tends to break, and who does it. Then the four intensity levels, and finally how a case management system carries the client across all six so the loop actually closes.
This is one guide in the case management library. For the definition and the wider field, start with what is case management; for the styles of practice that run this process, see case management best practices.
The process is simple to name and hard to hold together. The failure is rarely in any single stage — it is in the handoff between them, when the record does not carry forward. Read each stage for what it produces, where it breaks, and who owns it.
What it captures. First contact, eligibility, consent, and the presenting need. This is where the case is opened and — in any system that will later evaluate outcomes — a persistent client ID is assigned. Where it breaks. If the ID is not assigned here and reused everywhere downstream, every later comparison between baseline and outcome becomes a manual match; this is the load-bearing stage. Who does it. Intake workers, navigators, or the first available caseworker at the front door.
What it captures. A structured baseline of needs, strengths, risks, and goals — often through validated screens (PHQ-9, GAD-7, VI-SPDAT, or a program's own indicators) plus a narrative intake. Where it breaks. No baseline at intake means no reference point to evaluate change against later — the single most common reason a program fails funder scrutiny. An assessment that sits unread in a folder until something goes wrong is nearly as costly. Who does it. The assigned caseworker or clinician, sometimes with a specialist assessor for high-need cases.
What it captures. A service or treatment plan built from the assessment — goals that are observable, timelines that are real, owners named, and the outcome each service is meant to move. The plan becomes the thing case notes are later read against. Where it breaks. A plan with vague goals gives monitoring nothing concrete to measure, so "progress" becomes a matter of opinion instead of evidence. Who does it. The caseworker with the client — planning is collaborative or it does not hold.
What it captures. Services delivered directly or brokered to partners, and a case note at each contact. The case notes are the richest evidence the process ever produces. Where it breaks. Notes filed as loose documents nobody reads across — the record of what actually happened, lost to the archive the week it is written. This is the stage record-keeping software captures but cannot read. Who does it. The caseworker, plus every partner agency the plan touches.
What it captures. Progress checks against the plan and the adjustments they trigger — the point where monitoring loops the case back into reassessment. Where it breaks. Caseloads sized so monitoring is nominal — checked off, not actually done — which quietly biases every later number. Risk signals that surface only at a supervisor's month-end sample surface too late. Who does it. The caseworker day to day; the supervisor at review.
What it captures. The outcome measured against the baseline captured in Stage 2, and a clean closure or transition — plus, where the program can support it, longitudinal follow-up at 90 days, one year, and beyond on the same client ID. Where it breaks. This is the stage record-keeping systems skip and the one a funder cares about most; without a baseline and a persistent ID, evaluation becomes a year-end reconstruction instead of a reproducible answer. Who does it. The caseworker and supervisor, with the program director owning the aggregate outcome.
Read down the list and the pattern is clear: every "where it breaks" is a handoff problem, not a stage problem. The fix is a record that carries the client across all six — which is what the second half of this guide is about.
The six stages stay the same; what changes across intensity levels is how often Stages 4 and 5 repeat and how large the caseload runs. People often search for the "levels" or "types" of case management — these are them, from lightest to most intensive.
Light-touch information, referral, and eligibility. Large caseloads, brief contact. The process runs once and mostly closes at Stage 4. Common at benefits access points and 211-style navigation.
Ongoing brokerage to external services with periodic check-ins. Stages 4–5 repeat on a slow cadence. The caseworker connects the client to partners and tracks whether the referral held.
Active management of a full service plan with regular monitoring. The full six-stage loop, run at a moderate caseload. This is the standard model most funded human-services programs operate.
Small caseloads, frequent contact, high-need clients. Stages 4–5 repeat constantly, and continuity of record matters most here — the client with the most touchpoints is the one whose history is hardest to hold together by hand.
The level is set by client need and resourcing, not by the process itself. For a fuller treatment of the disciplines that run at these levels — social work, human services, workforce, housing — see social work case management software and nonprofit case management software.
The six stages are what the case manager does. A case management system is what holds them together. Historically the case notes captured during implementation and monitoring — Stages 4 and 5, the richest evidence the process produces — sat unread until a supervisor's month-end sample or a year-end reconstruction. By then the signal was old and the outcome was a guess.
Case intelligence changes the reading, not the process. The persistent client ID assigned at intake threads through assessment, plan, services, and follow-up, so each stage can see the work of the one before it. Every case note and assessment is read on arrival — scored against the service plan with a citation trail — so monitoring is continuous instead of sampled, and evaluation writes itself off the same record. The part that changes daily work is the Assistant: ask a question in plain language, get a defensible answer with citations to the underlying case notes. No dashboard hunting, no waiting for the one analyst who knows where the export lives — caseworkers, supervisors, and program directors each query the same record directly.
The prompts below are copy-paste. Each mirrors a moment in the process — reading the assessment, checking case notes against the plan, comparing baseline to follow-up — and runs on your own data. The placeholders in brackets are yours to fill.
From this intake 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.
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 each month so results stay comparable.
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.
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 board summary — from the same underlying answer, every number traceable to its source case note. See how Sopact builds this spine on the case management platform guide, how the note layer works on case notes software, or how to choose a system on the case management software buyer's guide. For the day-to-day view of the workflow, see case management workflow.
The stages above are the map; the Academy articles are the practice — each a hands-on companion for one part of the process, written to run on your own data.
The case management process is the coordinated sequence a case manager follows to move a client from first contact to outcome. Most frameworks describe six stages: screening and intake, assessment, planning, implementation, monitoring, and evaluation or closure. The stages form a loop rather than a straight line — monitoring routinely sends a case back into reassessment until the goals are met.
Six stages, in order: (1) screening and intake — confirm eligibility, open the case, assign a persistent client ID; (2) assessment — capture the baseline needs, strengths, risks, and goals; (3) planning — agree a service plan with measurable goals; (4) implementation — deliver or coordinate the services; (5) monitoring — track progress against the plan and adjust; (6) evaluation and closure — measure the outcome against the baseline, then close or transition the case.
The seven-step version splits one of the six stages into two — usually adding a distinct engagement step before assessment, or separating goal-setting from planning. A common seven-step ordering is: screening, engagement, assessment, planning, implementation, monitoring, and evaluation. Whether it is drawn as six or seven, the arc is identical: assess the need, plan the response, deliver it, check whether it worked, and loop until it does.
In social work the same six stages apply, with two emphases: assessment is typically clinical and strengths-based, and advocacy runs as a thread through every stage rather than as a separate step. Social work case management also leans harder on safeguarding — reading each contact for risk the week it appears — and on licensure-aware documentation. The process shape does not change; the depth of assessment and the duty of care do.
A loop. Although the six stages are usually drawn in a line, monitoring (Stage 5) routinely loops back into reassessment (Stage 2) whenever a client's situation changes or a goal is met. A case typically runs the loop several times before it reaches evaluation and closure. Treating the process as a one-pass line is a common reason follow-up gets skipped.
A case management system carries one client record across all six stages, so the work in one stage is visible in the next: the ID assigned at intake threads through assessment, plan, services, and follow-up. A modern system also reads the case note and assessment on arrival, scoring against the plan with a citation trail, so monitoring and evaluation are continuous rather than a year-end reconstruction.
No demo theater. Tell us what you run and which funder reports you owe, and we will show you what the six stages look like on Sopact — intake to outcome, the case note read on arrival, the evaluation as one query. Scope a 2-month pilot →