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 seven-step case management workflow and the handoffs that make or break it — referral to closure — plus workflow automation and case intelligence.
A case management workflow is the operational sequence a team actually runs to move a case from first contact to outcome — referral, intake, assessment, service planning, service delivery, monitoring, and closure or follow-up — together with the handoffs, owners, and triggers that connect one step to the next. It is the concrete, configured-in-software version of the case management process: where the process names the conceptual stages a case passes through, the workflow says who does each step, when, and what moves the case forward. Almost every workflow failure is a handoff failure — the record does not carry forward, so someone re-keys it, re-matches the client by name, or drops the case between two steps.
Searches for "case management workflow" and "case management workflow diagram" usually want two things: the ordered list of steps, and a picture of how they connect. Both are below, step by step, with the specific handoff to watch between each. For the conceptual version of these steps, see the case management process; for the wider field, what is case management.
Read left to right. Each name is a step, each arrow is a handoff, and the loop is real — monitoring routinely sends a case back into reassessment until goals are met. The persistent client ID assigned at intake is the single thread that runs through all seven steps.
Referral → Intake (assign the client ID) → Assessment (capture the baseline) → Planning (set measurable goals) → Service delivery (case notes) → Monitoring ↺ (loops back to reassessment) → Closure / follow-up
Decision branches: after Intake, an eligibility branch (eligible continues to Assessment; not eligible exits to referral-out). After Monitoring, a goal-met branch (goal met moves to Closure; not yet loops back into reassessment and an updated plan). Keep the whole thing to one page — the most useful diagrams also mark where data is captured, because that is where a workflow either builds one continuous record or fragments into separate tools.
The steps are easy to name; the workflow is what connects them. Below is each step, what it produces, who typically owns it, and — the part that decides whether the workflow holds — the handoff risk at the arrow leaving it.
First contact: a self-referral, a partner agency, a hotline, a court order. The referral source and reason are the beginning of the record. Owner: intake coordinator or front-desk staff. The handoff to watch (Referral → Intake): the referral detail — who sent this person and why — is captured on a form that never links to the intake record, so the "why they came" is gone by Step 3. Carry the referral into intake as structured data, not a note stapled to a folder.
Eligibility screening, consent, and the first structured profile. This is the single most important handoff in the entire workflow. Owner: intake worker. The handoff to watch (Intake → Assessment): assign the persistent unique client ID here, at intake, or every later step re-matches the client by name — and name-matching is where duplicate records, split histories, and lost re-engagements are born. The eligibility decision branches here: eligible continues; not eligible is referred out, and that exit is still recorded on the ID.
Needs, risks, protective factors, validated screens — the reference point every later step is measured against. Owner: caseworker or clinician. The handoff to watch (Assessment → Planning): the baseline must be captured as structured data, not buried in a free-text narrative. If the baseline is unstructured, monitoring later has nothing to compare against, and "did the situation improve" becomes a year-end reconstruction instead of a measured change. Lock the baseline before services begin.
A service or treatment plan built from the assessment: each need mapped to an observable goal, a service, and the outcome it should move. Owner: caseworker, agreed with the client. The handoff to watch (Planning → Service delivery): the plan is agreed but never written where case notes are later read against it, so delivery drifts from the plan and no one notices until review. The plan is the thing notes get scored against — keep it on the same record as the notes.
Services delivered, sessions held, case notes written. This is where the richest evidence of what is actually happening accumulates. Owner: caseworker. The handoff to watch (Service delivery → Monitoring): notes are filed but unread — the single most common workflow failure. The narrative that would flag disengagement, a missed appointment, or a safeguarding concern sits in the system until a supervisor samples it at month-end, which is usually too late.
Progress reviewed against the plan; the case either advances toward closure or loops back into reassessment with an updated plan. Owner: caseworker plus supervisor. The handoff to watch (Monitoring → Closure or back to Assessment): the goal-met branch is decided on stale information because monitoring only happened at the review meeting. When monitoring reads the note as it lands, the loop-back decision is made on current evidence, not a quarterly snapshot.
The case is closed against the baseline, and follow-up is scheduled. Owner: caseworker and program lead. The handoff to watch (Closure → follow-up): follow-up is improvised at exit instead of planned at intake. Capture the follow-up channel and cadence back in Step 2, on the same client ID, so the 90-day, one-year, and three-year waves land on the record they belong to — and a re-engaging client arrives with their whole history attached rather than as a new intake.
The same seven steps can run three ways, and the difference is entirely in what carries the case across each handoff — a person's memory, a trigger, or the content of the note itself. In a manual workflow the client ID is re-matched by name, staff remember the next step, data is re-keyed between tools, and the case note is filed unread. In an automated workflow the ID is assigned once and carried, the next step is triggered from the last, and overdue items are flagged by rule — routing improves, but the note is still only stored, not read. Most teams live somewhere between the two, and the jump that changes the outcome isn't more routing.
That jump is the intelligent workflow, where the software reads the note instead of just moving it. You can automate every handoff in the seven steps and still end the year unable to say what changed — because automation moves the record without reading it, and the evidence of an outcome lives in the case note. This is where the handoffs that break — re-keying at intake, the lost baseline between assessment and planning, notes filed and never read — get fixed by two things at once: reading on arrival, and one persistent client ID that threads every step.
Case intelligence configures the whole workflow in plain English — the steps, the triggers, the owners — and adds the layer a routing engine can't: it reads each case note and assessment as it lands, scores it against your framework with a citation trail, and surfaces risk before the next step. The part that changes daily work is the Assistant: caseload analysis, screen scoring, and open-text note reading are unified into one chat-based function — ask a question, get a defensible answer with citations to the underlying records. 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 instead of routing everything through one analyst. When the analysis is done it doesn't die in the chat — shareable reports are generated per audience, each number traceable to the source note.
The prompts below are copy-paste; the placeholders in brackets are yours to fill. Use them to build, run, and evaluate the workflow on your own data.
Map our case management workflow from this program description: [PROGRAM URL OR DOCUMENT]. List the steps from referral to closure, name the owner and the trigger for each, and mark every handoff where data must carry forward. Flag any handoff where the client is currently re-matched by name instead of a persistent ID, and any step where the case note is filed but not read.
Read this batch of case notes against our service plans: [NOTE BATCH]. For each client, summarize progress 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, so monitoring happens on arrival instead of at month-end.
Build an evaluation checklist for a case management workflow tool: does it assign one client ID at intake and carry it through every step, trigger the next step automatically, prevent duplicate records, flag overdue or missing items before a deadline, and read the case note on arrival rather than just storing it? Score [VENDOR LIST] on each, evidence required, not vendor claims.
The steps above are the argument; the Academy articles are the practice — each a hands-on companion for one part of the workflow, written to run on your own data.
A case management workflow is the defined sequence of steps a case moves through from intake to outcome — referral, intake, assessment, service planning, service delivery, monitoring, and closure or follow-up — along with the handoffs, owners, and triggers that connect them. Where the broader case management process describes the practice conceptually, the workflow is the operational version a team configures in software: who does what, when, and what triggers the next step.
A typical workflow has seven steps: referral or first contact; intake and eligibility; assessment and baseline; service planning with measurable goals; service delivery and case notes; monitoring and review; and closure or follow-up. Each step produces a record and triggers the next — a completed assessment opens planning, for example. The persistent client ID assigned at intake is what lets the workflow carry one record across all seven, and monitoring loops back into reassessment until goals are met.
The process is the conceptual sequence of stages every case moves through; the workflow is the operational implementation of that process in a tool — the specific steps, owners, triggers, and handoffs a team configures. The process answers what should happen; the workflow answers who does it, when, and what moves the case to the next step. See the case management process for the conceptual version.
Workflow automation removes the failure points that live in the handoffs: it assigns the persistent client ID once and carries it forward, triggers the next step from the last automatically, prevents duplicate records, and surfaces overdue or missing items before a deadline instead of at it. The newest layer adds intelligence — the software reads the case note and assessment on arrival and scores or routes on content, so monitoring and risk-flagging happen continuously rather than at a quarterly review.
Yes. Map the steps left to right from intake to outcome, draw each handoff as an arrow, and mark the decision points — eligible or not after intake, goal met or not after monitoring — as branches: Referral → Intake (assign ID) → Assessment (baseline) → Plan → Service delivery → Monitoring ↺ → Closure/follow-up. Note who owns each step and what triggers the next, and mark where data is captured, because that is where a workflow either builds a continuous record or fragments. Keep it to one page.
Modern platforms let you configure the steps, triggers, owners, and forms in plain language rather than in code or through a consultant, so a first intake-to-report cycle can be live in days rather than the months a coded or consultant-built workflow takes. A case-intelligence platform goes further: it configures the entire workflow — data dictionary, forms, rubrics, reporting — in plain English, and then reads each case note on arrival, scores it against your framework with citations, and surfaces risk before the next step, turning a workflow that routes paperwork into one that accumulates evidence. See the case management platform layer and case management software hub.
No demo theater. Tell us the steps your cases move through and where the handoffs break. We'll show you the workflow running on Sopact — one client ID assigned at intake, the case note read on arrival, the outcome as one query. Related reading: case management best practices, case notes software, and human services case management software. Book a 20-min walkthrough →