Case Management Process: The Stages, Made Readable

What is the case management process?

The case management process is the step-by-step way a caseworker helps one person over time, from first contact to a resolved outcome. It runs in six stages: intake opens the record and gathers the basics; assessment identifies needs, risks, and barriers; planning sets goals and the services to reach them; intervention delivers those services and records progress; monitoring and review checks progress and adjusts the plan; and closure records the outcome and the reason for ending. Each stage produces documentation, and the process only works if that documentation is read.

If case management is new to you: a “case” is one person or family a program is helping, and a “caseworker” is the person who guides them through it. This page describes the process as human services and social services agencies run it — not the court-scheduling or hospital-nursing senses of the same term. It is usually drawn as a cycle rather than a straight line, because closing one goal often loops back into a fresh assessment. Different frameworks number the same work differently — some call it four stages, some six, some nine — but the stages below are the version most social-services teams follow.

The short version

Six stages: intake, assessment, planning, intervention, review, and closure. Each one produces a document, and its value depends on that document being read.
It is a cycle, not a line. Closure on one goal often feeds a new assessment, which is why it is called a case management cycle or lifecycle.
The number of steps depends on the framework. Four, six, seven, or nine — the labels differ, the work is the same.
The process is usually followed but rarely read. The barriers, risks, and outcomes are written down at each stage and then sit in free text until someone opens the file.

The case management steps, stage by stage

Here is the whole process, one stage at a time: what happens, what it produces, and the one place each stage tends to leak. Read top to bottom and you have walked a case from the first meeting to closure.

The whole cycle at a glance

1Intake→2Assessment→3Planning→4Intervention→5Monitoring & review→6Closure↶ often loops back to a new assessment

Stage 1

Intake

opening the case

What happensThe caseworker meets the client for the first time, opens a record, and gathers the basics — who they are, what brought them in, and what they need right now.

Produces: an intake form and the first case notes

The gapThe real story is in the notes, not the form fields — and those notes are rarely opened again.

Stage 2

Assessment

understanding the need

What happensA structured look at the client’s situation against a framework — their strengths, their risks, and the barriers standing between them and their goals.

Produces: a completed assessment and risk notes

The gapAssessments get scored and filed; the narrative that explains the score usually goes unread.

Stage 3

Planning

setting the goals

What happensThe caseworker and client agree on goals and the services that will reach them, and write it down as a case plan.

Produces: a case plan

The gapA plan is only as good as the needs it was built from — and those needs sit in the assessment nobody re-reads.

Stage 4

Intervention

doing the work

What happensServices are delivered — referrals, sessions, support — and after each contact the caseworker records what happened in progress notes.

Produces: progress notes and service records

The gapNew progress and new risks are written here every week — and this is exactly where the signal goes missing at caseload scale.

Stage 5

Monitoring & review

checking progress

What happensAt set points the caseworker compares progress to the goals, decides what is working, and adjusts the plan.

Produces: a review record

The gapReview reads a sample from memory; the barrier recurring across the whole caseload stays invisible.

Stage 6

Closure

ending the case

What happensThe case ends — goal met, client moved on, or referred elsewhere — and the outcome and the reason for ending are recorded.

Produces: a closure summary and an outcome record

The gapThe outcome is real but hard to prove, because it is scattered across notes that were never read together.

Every stage produces a document, and teams often codify the whole thing in a written procedure, a workflow diagram, and a checklist so it is followed the same way each time. The operational version of these stages — who does what, and when — is the case management workflow; the practice behind them is what is case management.

Where the process leaks, and how to read it

The case management process leaks in the three stages that generate free-text notes — assessment, intervention, and review — because those notes carry the real intelligence (barriers, risk, progress) that a stage-based system stores but never reads across a caseload. Intake and closure are structured enough to be usable; the middle is where a client’s trajectory is actually written down, and it is exactly the text that goes unread until the next review.

The fix is not a new process — it is reading each stage’s documentation the moment it is written rather than saving the read for review time. Sopact does this: it analyzes every note, form, and assessment as it is created — for barriers, risk, and progress — so a signal surfaces at the stage it appears rather than a quarter later. It keeps this on one continuously read client record, which Sopact calls the Case Thread, and it runs alongside the head case management software and the deeper case notes software.

Here is what that reading looks like on one real note.

A caseworker writes

“Client missed two appointments because childcare fell through.”

Software that reads the note automatically

→Tags childcare as a barrier for this family, and counts how many other families report the same thing.
→Updates the client’s risk profile and flags them as at risk of disengaging.
→Alerts a supervisor if the same barrier is rising across the caseload — the day it is written, not at the next review.

The six stages and what each records

Stage	What it records	What to read it for
Intake + assessment	Baseline needs and identified barriers	Barriers and early risk signals
Planning	Goals and the services to reach them	Whether the goals match the needs recorded
Intervention	Progress notes and observations	Progress against goals, safeguarding signals
Review + closure	What changed, outcomes, reason for ending	Outcomes, read from the notes

A case file tells you what was recorded. The Loop tells you in time to act.

A case note written today and read at a quarterly review is a safeguarding signal that waited three months. The value of reading a case note is highest the moment it is written, while the client’s situation can still be responded to. That is the idea behind the Loop, Sopact’s method for reading a process as it runs: collect clean at the source, analyze the moment a note arrives, and improve while there is still time to act — so the case management process becomes something you can see through rather than a filing exercise you reconstruct at the end.

Frequently asked questions

What are the stages of the case management process?

Intake, assessment, planning, intervention, monitoring and review, and closure. Each stage produces documentation whose value depends on being read. Sopact reads each stage’s notes the moment they are written, so barriers and risk surface at the stage they appear rather than at review.

What are the 4 stages of case management?

The four-stage version compresses the process to assessment, planning, implementation, and evaluation, with intake folded into assessment and closure into evaluation. It is the same work as the six-stage model, grouped more broadly. Sopact reads each stage’s notes the moment they are written whichever way a framework counts the stages.

What are the 5 stages of case management?

A common five-stage version is assessment, planning, implementation, monitoring, and evaluation — it separates monitoring from evaluation and folds intake into assessment. The labels differ but the work is the same, and the free-text stages still carry the intelligence that has to be read.

What are the 7 steps of the case management process?

A seven-step version adds screening at the front and separates closure or transition at the end: screening, assessment, planning, implementation, monitoring, review, and closure. Sopact reads the free-text steps — assessment, implementation, and review — as it is written, so the signal surfaces at the step it appears.

What are the 9 phases of case management in human services?

A nine-phase version breaks the same process finer: screening, assessment, stratifying risk, planning, implementation, coordination, monitoring, transition or closure, and evaluation. More phases do not change the gap — the notes each phase produces still go unread until someone opens the file, which is what Sopact reads the moment they are written.

What are the 4 levels of case management?

Levels are not stages: they describe the intensity of support a client needs, from light-touch coordination through moderate and intensive to full wraparound. A client can move between levels while the same process stages apply. Levels set how often you touch a case; reading the notes sets whether you catch what the case is telling you.

Is the case management process a cycle or a line?

A cycle. Closure on one goal often loops back into a new assessment, which is why it is also called the case management cycle or lifecycle. Reading each stage as it completes is what keeps the cycle moving on evidence rather than on memory, so the next loop starts from what the last one actually recorded.

What documents does the case management process produce?

Each stage produces an artefact: an intake form, an assessment, a case plan, progress notes, a review record, and a closure summary — often codified in a written procedure, a workflow diagram, and a checklist. Those documents are where the process’s intelligence lives, and Sopact reads them as it is written so a procedure that is followed is also read.

Where does the case management process most often fail?

In assessment, intervention, and review, where free-text notes accumulate and carry the real intelligence — barriers, risk, progress — that a stage-based system stores without reading. Sopact reads those stages as their notes are written, so the signal is not lost between recording and review.

How do I catch risk earlier in the process?

Read intervention and assessment notes for safeguarding signals as they are written rather than at the next review, so a concern surfaces the day it is written. Sopact reads every note against your safeguarding framework on the Case Thread and ranks the flags, so the earliest signal is the one you act on.

Does reading the process mean changing my case system?

No. Keep your case system and its stage-based workflow; Sopact reads each stage’s documentation as it is written for barriers, risk, and progress. The process stays the same; what changes is that its documentation is finally read across, so compliance with the stages comes with visibility into their content.

Next: see the operational flow in case management workflow, or what good looks like in case management best practices.