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.
Caseload notes are unstructured gold — needs, progress, risks, and next steps are all in the free text, just not in fields you can act on. Here is how to extract them into structured data with Sopact Sense.
In short: A caseworker's free-text note is unstructured gold — needs, progress, services, risks, and next steps are all in there, just not in fields you can act on. Point the Sopact Sense Assistant at the note, extract those fields describing only what is written, and grade each one. You get structured, comparable data and the one input that fixes whatever the note left out.
Tell the Assistant which dataset it is working over and load your Decision Brief first, so the extraction 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.
From the case note for [CLIENT_ID], extract needs, progress, services, risks, next steps, stage-of-change (if derivable). Describe only what's written. Grade green/amber/red.
The prompt carries five elements. Dataset: the case note the Assistant reads. The fields: needs, progress, services, risks, next steps, and stage-of-change. Only what's written: no inference beyond the text. Mark missing: any field the note never recorded. Grade: a green / amber / red call on every field.
Run on the Caseload dataset (DEMO-08) already loaded in Sopact Sense.
GRADE: green | Explicit | needs · amber | Inferred | stage · red | No | next steps
The Assistant pulls each field and grades it. Green is an explicit need stated plainly in the note. Amber is an inferred stage-of-change — read between the lines rather than written down. Red is a missing next step: no follow-up action was recorded at all.
Take the lowest-graded element and fix it with something the program could realistically capture.
Take the missing next-steps element above and fix it: require a 'next step + owner + date' line before a note can be saved. 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.
Describe only what's written. The fastest way to break trust in extracted data is to let the model invent a status the note never stated. Keep the "only what's written" instruction in the prompt and let missing fields stay missing.
Treat inferred fields as amber, not green. Stage-of-change is often derivable but rarely stated. Grading it amber tells your team it was inferred, so they know to confirm it rather than trust it as fact.
Fix the template, not the note. When the same field is missing across many notes, the problem is the note template. Add a required line once and every future note is structured at the source.
Keep the field list identical across caseworkers. That is what makes notes comparable.
Run the same extraction prompt on every caseworker's notes so one client's record reads the same as the next.
Extract a fixed set of fields — needs, progress, services, risks, next steps, and stage-of-change — from each free-text note, describing only what the caseworker actually wrote. The Sopact Sense Assistant does this in one pass and grades each field green, amber, or red, so unstructured notes become comparable structured data without rewriting how staff work.
Only when you mark them as inferred. Stage-of-change can be derived from the text, but it should grade amber so your team knows to confirm it. Everything else should describe only what is written, and anything missing should be flagged rather than guessed.
Add a required "next step + owner + date" line to the note template. It is the field most often missing, and making it mandatory at the source turns red elements green for every future note.
Open Sopact Sense, paste your program description, and put it to work.
Try in Sopact