Track caseload progress by keeping dated observations connected to each person’s goals and service episode, then reviewing what is current, what is missing and what needs follow-up. Separate a lack of recorded information from evidence that a person has not progressed. A review list should help the team decide what to check, not automatically label people as stalled.
This lesson produces a caseload review table with definitions, evidence dates, coverage and next actions. It works alongside individual case review; an aggregate view should not erase the context of a person’s goals.
Define what progress means for the work
A service may aim to help someone gain a skill, maintain a stable situation, complete an agreed step or access support. These are different goals. A stable result can be a desired outcome rather than a sign that nothing is happening.
Write the goal and the observation that would inform it. For example, a fictional participant wants to attend a suitable session around their work schedule. Relevant observations include whether a place was offered, whether the person accepted it and whether attendance occurred. The number of notes in the record is not itself a measure of progress.
Agree the reporting unit: person, service episode, goal or action. One person can have several goals and participate in more than one program. Keep those relationships explicit before creating a caseload total.
Keep observations, contacts and actions distinct
| Record | What it establishes | What it does not establish by itself |
|---|---|---|
| A contact attempt | The team attempted contact at a stated time | That a conversation occurred |
| A participant account | What the participant reported at that observation point | That every related outcome has been independently confirmed |
| An agreed next step | A planned action and its responsible owner | That the action was delivered |
| A completed action | The recorded action occurred under the stated definition | That the participant’s longer-term goal was achieved |
| No current observation | The current evidence is missing or not yet due | That the person has failed or disengaged |
Retain observation dates, entry dates, sources and corrections. A note entered today about last month should not create apparent new progress today. If an earlier statement is copied forward, make clear whether its current status was checked.
Set a review cadence that fits the service
Define when the next observation or action is expected. A weekly service, a term-based program and a follow-up after an infrequent event need different schedules. Review an overdue item against its agreed timing, not a universal number of months.
Useful statuses may include not yet due, current evidence available, follow-up overdue, awaiting clarification and no further action agreed. These describe the work or evidence. They should not become automatic judgments about a person.
Some new information may require attention before the next routine review. Follow the appropriate service process rather than waiting for a record to cross an arbitrary age threshold.
Work through a small caseload example
Suppose 30 people belong to the defined review group. Twenty have a check-in due by the review date. Fifteen have usable current evidence; five are overdue or unresolved. The other ten are not yet due under their agreed schedule.
Report current-evidence coverage as 15 of the 20 due check-ins, or 75%. Keep the five unresolved items visible for appropriate follow-up. Do not call all 15 current records successful, and do not classify the ten not yet due as missing.
Within the 15 current records, you might describe which agreed actions happened or which outcome observations meet a defined criterion. State that separate denominator. A person can have a current record and still need support; another can have a missing record while progressing in ways not yet documented.
Review patterns without inventing causes
When several records describe similar difficulties, use a codebook to organize the accounts and keep source references. Distinguish a reported barrier from a confirmed explanation. Similar scheduling comments may justify reviewing session times; they do not establish the cause of every missed contact.
Check overlap and repeated entries. Several notes can describe the same unresolved action. Several actions can belong to one person. Choose the count that answers the review question and explain it.
Consult the people responsible for the work and, where appropriate, the participant. A cluster of records is an invitation to investigate and respond, not a substitute for understanding individual circumstances.
Compare locations with a shared core
Different schools, locations or service teams may retain their own collection tools and note formats. Agree the few fields needed for the common review: appropriate person or episode linkage, relevant dates, goal or action type, status meaning and review owner.
Use a data dictionary to map compatible local fields. A location that uses “complete” for an attended session cannot be combined with one that uses it for an achieved outcome without a more precise definition. Keep the local detail that helps interpret the result.
Reuse stable registration details where appropriate, and retain changes to location or program membership with effective dates. A participant moving between locations should not silently become two people in the network total.
Use the connected record to support review
In Sopact, the continuing record can bring check-ins, notes, documents and action history into the same review context where permitted. AI can assist with proposed themes or evidence gaps. Keep the source and definitions available, and have an appropriate reviewer decide what the information means and what should happen next.
Save the scope and date of a shared report. Later corrections should be explainable rather than making an earlier review impossible to reconstruct. An operational owner can maintain definitions and review rules within agreed responsibilities without treating every ordinary update as a new IT project.
Your exercise
- Choose a caseload group, goal and review date.
- Define which check-ins or actions are due.
- Separate current evidence, overdue items and not-yet-due records.
- Calculate coverage before summarizing progress.
- Inspect one repeated concern and identify whether it is a new event.
- Assign a next action with an owner and appropriate timing.
- Check whether a location comparison uses compatible definitions.
Frequently asked questions
What counts as a stalled case?
A record without recent movement is not enough to conclude that a person has stalled. Review the goal, expected timing, available evidence and context. Use an evidence or follow-up status until the situation is understood.
How often should a caseload be reviewed?
Use the service cadence, agreed actions and consequences of delay to set timing. Different types of work may need different schedules, with an appropriate route for issues needing earlier attention.
How do you make a review list actionable?
Name the unresolved evidence or action, its responsible owner and the next step. Keep reported explanations separate from confirmed causes, and record what happens after the review.