A case is any stakeholder who moves through your organization over time — and whose outcome you are accountable for. Most software built for this work stores that journey and logs services; it can tell you what you did, never what changed. Case intelligence reads the whole journey as one connected record, the moment each piece arrives — so did their situation improve? becomes a question you can answer with evidence.
Key takeaways
- A case is one stakeholder on a long journey — application, surveys, notes, follow-ups — whose outcome you must prove.
- Case intelligence reads that journey on arrival instead of storing it for a reporting scramble months later.
- Three shifts vs a CRM: analysis on arrival · one record per person · a workflow that adapts as you learn.
- It fits long, qualitative-heavy journeys where outcomes are owed — and doesn't fit clinical, crisis, or one-off work.
- This is Chapter 1 — the map. The course teaches everything the demo shows.
What case intelligence is
Case intelligence means treating everything a stakeholder touches — applications, surveys, interviews, case notes — as one connected record, and analyzing it the moment new data arrives instead of months later.
If you lead a program where people stay a while — workforce training, youth development, scholarships, an accelerator — you already collect data at every step. But the touchpoints land in tools that never talk to each other, so by reporting season nobody can line up one person's beginning against their end. Teams report what they can count, and the change itself stays anecdotal. The question funders and boards now ask has moved from how many did you serve to did their situation improve, and can you show it — and record-keeping alone cannot answer it.
How this differs from traditional case management
Record-keeping software stores the journey. Case intelligence reads it. Three shifts make the difference:
- Analysis happens on arrival. When an application, a survey answer, or a mentor note lands, it is read right then — open-ended answers classified, needs flagged, scores applied, every conclusion tied to the person's exact words. A transport barrier is found the week a bus pass still fixes it, not in month three when it has become a dropout.
- The workflow adapts as you learn. Change how something is scored after the first ten responses, and everything already collected is re-read against the new standard automatically. You do not need the perfect form on day one.
- One record connects the whole journey. Each stakeholder carries one ID across every form they ever touch, so intake, mid-program, exit, and follow-up line up as one story you can query in plain language.
None of this requires abandoning what you have — many organizations keep their system of record and add intelligence as the reading layer on top.
Start with the word "case"
Forget the case-file connotation for a moment. In this series, a case is any stakeholder who moves through your organization over a long period — and whose outcome you are accountable for. A trainee who applies in January, learns through spring, and starts a job in fall. A student an after-school program follows across grade levels. A scholarship recipient tracked through graduation. A founder moving through an accelerator toward investment. Each is a case: one person, one long journey, many touchpoints.
Where case intelligence fits — and where it doesn't
Honest boundaries first, because the fastest route to disappointment is applying a good approach to the wrong problem. A strong fit shares three traits: the journey lasts months to years, much of the evidence is qualitative, and someone is owed proof of outcomes.
Where case intelligence is a strong fit
| Strong fit | Why |
|---|
| Workforce training & job-readiness | Long journey from application to employment; rich qualitative evidence; outcomes owed to funders |
| Youth development & mentoring | Multi-month relationships; progress lives in notes and reflections |
| After-school & school outcome tracking | Same students across terms and grades; growth measured against a baseline |
| Scholarships & fellowships | Multi-year journeys from application through graduation and beyond |
| Accelerators & incubators | Cohorts of ventures from application to outcomes, heavy on narrative evidence |
| Apprenticeship & job placement | Two-sided journey — candidates and employers — that must reconcile |
| Reentry, housing & self-sufficiency | Long horizons where early-warning signals matter most |
Where it is not the right fit
| Not the right fit | Why |
|---|
| Clinical & patient care | Governed by HIPAA and clinical workflows — EHR territory |
| Crisis lines & emergency response | Episodic contact measured in minutes; safety protocols, not journeys |
| Statutory child-welfare casework | Court-mandated, compliance-driven systems with their own requirements |
| One-time events & surveys | No journey to connect — a single touchpoint doesn't need a connected record |
| High-volume customer support | Tickets are transactions; there is no outcome to prove |
The rule of thumb: if the same person shows up in your data more than twice across months, and their words carry the evidence, case intelligence fits.
Throughout this series we follow two organizations, chosen because together they cover both halves of most readers' reality. The nonprofit — grant-funded, taking people from application to job-ready; its year ends with a funder report. The social enterprise — placing job-ready candidates with employer partners; its year ends with an investor and board report. Most readers will find they are partly both.
See it work — many touchpoints, one connected record
Applicationscored on arrival
Baselinethe "before"
Mentor noterisk signal
Exitchange measured
Follow-upwage / retention
Every touchpoint read the moment it arrives — graded green, amber, red — and joined on one ID.
1Framework
Paste a program description — Sense draws a graded Theory of Change and turns it into a data-collection workflow.
Chapters 2–3
2Workforce training → funder report
Applications scored on arrival, a baseline captured, at-risk flagged mid-program, change measured at exit, SROI computed — then rolled up into a funder report, every claim cited.
Chapters 4–9, 12a
3Job placement → investor report
A job description becomes a requirements checklist, candidates matched to roles without bias, and the same cohort rolls up into an investor report — social outcomes beside unit economics.
Chapters 10–11, 12b
Throughout: ask the assistant across every wave — in Sense, or from Claude/ChatGPT over MCP.
First, a framework — any framework
Case intelligence begins with a clear statement of the change you intend to cause. Any standard framework works — a theory of change (the one this series uses), a logic model, a logframe, or a results framework. They differ in format, not essence. Chapter 2 builds one.
The one thing to do this week
Answer one question in writing: who is your "case," and what journey do they take through you? Name the stakeholder, list every touchpoint from first contact to final follow-up, and mark which ones vanish into disconnected tools. That single page is the raw material for every chapter that follows.
Who this is for
Program directors who can report attendance but not change. Evaluators stitching five exports together every reporting season. Founders of social enterprises who need social outcomes and unit economics in the same sentence. If people move through your organization over months and years, and their outcomes are the point — this course was written for you.
Frequently asked questions
What is case intelligence?
Treating everything a stakeholder touches — applications, surveys, notes, follow-ups — as one connected record, and analyzing it the moment it arrives, so you can prove whether their situation improved.
How is it different from a CRM or case-management system?
Those store the journey and log services; case intelligence reads it. Three shifts: analysis on arrival, one record per person on a persistent ID, and a workflow that re-reads everything when you change how you score.
What kinds of programs is it for?
Long, qualitative-heavy journeys where outcomes are owed — workforce training, youth development, scholarships, accelerators, reentry and housing.
Where does it not fit?
Clinical/patient care (EHR territory), crisis lines, statutory child-welfare, one-time events, and high-volume support — episodic or transactional work with no journey to connect.
Do I have to replace my current system?
No. Many organizations keep their system of record and add case intelligence as the reading layer on top.
How is this different from reporting or M&E software?
Reporting tools summarize what you already structured; case intelligence does the reading — classifying open text, flagging risk, connecting one person's waves — so the report becomes a query over evidence.
Next: Chapter 2 · Build a Theory of Change → · or Try the Case Intelligence demo in Sopact Sense →
