Some clients quietly stop moving, and the quarterly review is the first place anyone notices. Here is how to track caseload momentum over time and surface stalled clients early with Sopact Sense.
In short: Some clients quietly stop moving, and the quarterly review is usually the first place anyone notices. Point the Sopact Sense Assistant at your caseload, track progress per client over time, surface the clients with no movement in N months, and cluster the reasons — so you spot stalled cases while you can still act on them.
Tell the Assistant which dataset it is working over and load your Decision Brief first, so the momentum read ties back to the decision, audience, outcomes, indicators, and evidence standard you already set.
You are the Sopact Sense Assistant working over the DEMO-08 · Caseload dataset (clean data + persistent contact IDs). Load my Decision Brief (decision, audience, outcomes, indicators, evidence standard) first, then wait for my task.
For [PROGRAM], track progress per client over time; identify no-movement-in-[N]-months clients, cluster reasons, report cohort momentum. Grade green/amber/red.
The prompt carries five elements. Dataset: the caseload across the program. Momentum over time: progress tracked per client, not a single snapshot. Stalled list: clients with no movement in N months. Cluster reasons: group the stalls by likely cause. Grade: a green / amber / red call on each client.
Run on the Caseload dataset (DEMO-08) already loaded in Sopact Sense.
GRADE: green | Active | client · amber | Follow-up | pending · red | Stalled | client
The Assistant tracks each client over time and grades momentum. Green is an active client who is moving. Amber is a follow-up pending — progress is recorded but recent contact is overdue. Red is a stalled client with no movement logged in months.
Take the lowest-graded element and fix it with something the program could realistically capture.
Take the stalled-client element above and fix it: capture a reason-for-stall field at each touchpoint so the cluster, not just the count, is actionable. Show the before → after grade and the single edit that moves it to green.
Create a 'missing & incomplete' report from this analysis in Sopact branding. List every element graded amber or red, what is missing, and the one input that fixes each. Lead with the decision this report informs.
Create a shareable link for this report & open it in a new tab.
Define "stalled" with a number. No-movement-in-N-months only works if N is set. Pick a threshold that matches your program's cadence so the flag fires at the right time, not too early or too late.
Cluster the reasons, don't just count. A list of ten stalled clients is a workload; ten stalls grouped into two root causes is a plan. Ask for the clusters so the report points at a fix.
Use the amber tier as your early warning. Follow-up-pending clients haven't stalled yet. Acting on amber is how you stop a client from sliding to red before the next review.
Re-run it on a schedule. Momentum is only useful if it is fresh.
Run this prompt at a fixed cadence so the stalled list is current the day you review it, not a month old.
Track each client's progress across touchpoints rather than at a single point, then flag anyone with no movement in a set number of months and cluster the reasons. The Sopact Sense Assistant does this over your whole caseload and grades each client green, amber, or red, so stalled cases surface before the quarterly review catches them.
A client with no recorded movement for the threshold you set — for example, three months. They grade red. A client whose progress is logged but whose recent contact is overdue grades amber, an early warning that they may stall next.
Capture a reason-for-stall field at each touchpoint so the Assistant can cluster the stalls by cause. That turns a flat list of names into grouped root causes you can actually plan against.
Open Sopact Sense, paste your program description, and put it to work.
Try in Sopact
