Tagging barriers system-versus-individual changes what you fix. This shows how to surface the barriers a whole caseload keeps hitting in Sopact Sense — counted, quoted, and classified.
In short: Whether a barrier is system or individual changes what you fix. In Sopact Sense the analysis names each barrier across the whole caseload, counts it, quotes a client, tags it system-versus-individual, and notes where barriers co-occur — so you fix the pattern, not the anecdote.
Point the Assistant at clean open-text barrier responses with persistent contact IDs so each client's barriers stay tied to them. Load your Decision Brief first — the decision, the audience, the program, and your evidence standard — so the analysis surfaces barriers that map to something you can act on.
Across clients in [PROGRAM], identify common barriers: name, count, quote; tag system vs individual; note co-occurrence. Grade green/amber/red.
The prompt carries five elements. The dataset is the loaded barriers survey. Barriers plus counts names each barrier and how often it appears. System versus individual classifies whether the barrier is structural or personal. Co-occurrence flags barriers that show up together. Grade G/A/R rates how solid each tag is.
Run on the Open-Text Barriers dataset (DEMO 04) already loaded in Sopact Sense.
GRADE: green | 1 | System barrier; amber | 1 | Individual tag; red | 1 | Compounding barriers
Sense returns each barrier counted and tagged with a quote. A clearly structural barrier like transport or housing comes back green. A barrier read as 'individual motivation' that might be a system gap in disguise comes back amber — the tag needs a second look. Clients hitting two barriers at once that aren't counted as a pattern come back red: the compounding case is invisible.
Take the lowest-graded element above and fix it using only what the program could realistically measure. Show the before → after grade and the single indicator/edit that moves it to green.
For the compounding red, the fix is to capture co-occurrence so that transport plus childcare shows up as one fixable cluster rather than two separate tallies. That single change reveals the clients your program is failing twice over.
Create a 'missing & incomplete' report from this analysis in Sopact branding [or paste your website URL / brand guideline to apply your own]. 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 and open it in a new tab.
Tag against an explicit rule. Don't let the model decide system-versus-individual on vibes. Write down what counts as structural and apply it consistently.
Always keep a quote with the count. A barrier tallied without a verbatim line behind it is hard to trust and harder to act on.
Co-occurrence is where the program fails twice. Single-barrier counts hide the clients carrying two or three at once. Capture the overlap.
Re-check the 'individual' pile first. It's where mis-tags hide.
Re-read the quotes behind every 'individual motivation' tag — a missed bus or a closed childcare slot often reads as a personal failing.
Across the whole caseload, name each barrier, count how often it appears, quote a client, and tag it system-versus-individual — then note where barriers co-occur. Sopact Sense does this in one prompt over clean open-text responses.
Because it changes the fix. A structural barrier like transport calls for a program-level change; an individual one calls for a different response. Mis-tagging a system gap as personal sends you after the wrong solution.
A compounding barrier is two or more barriers a client hits at once — transport plus childcare, say. It grades red when co-occurrence isn't captured, because the most stuck clients stay invisible until you count the overlap.
Open Sopact Sense, paste your program description, and put it to work.
Try in Sopact
