1- What Is Case Intelligence?

For: leaders of programs where people stay a while — workforce training, youth development, scholarships, accelerators — and where “did it work?” matters as much as “did we deliver?”

Why: most software for this work was built to store records and log services. It can tell you what you did. It cannot tell you what changed. Case intelligence closes that gap.

Outcome: a clear picture of what case intelligence is, whether it fits your work, and a chapter-by-chapter path through this series.

This is Chapter 1 of the Case Intelligence series — the map for everything that follows. No product setup, no prompts yet. Read this first, and every later chapter has a place to land.

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 your after-school program follows across grade levels. A scholarship recipient you track through graduation. A founder moving through your accelerator toward investment. Each is a case: one person (or one venture), one long journey, many touchpoints — an application, a baseline survey, mentor notes, a mid-program check-in, an exit reflection, a six-month follow-up.

Here is the problem every one of these programs shares. The journey produces rich data at every touchpoint — most of it in people’s own words — but the touchpoints land in different tools that never talk to each other. The application sits in one system, surveys in another, mentor notes in documents, follow-ups in a spreadsheet. By reporting season, nobody can line up one person’s beginning against their end, let alone a whole cohort’s. So teams report what they can count — enrollments, sessions, completions — and the change itself, the thing everyone actually promised, stays anecdotal.

What case intelligence is

Case intelligence means treating everything a stakeholder touches as data on one connected record — and reading that data the moment it arrives, not months later.

Three shifts make it different from record-keeping software, and each one changes daily work:

1. 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. The pile of unread narrative that haunts every program simply never forms. A transport barrier gets found the week a bus pass still fixes it, not in month three when it has become a dropout.

2. The workflow adapts as you learn. Change how something is scored after seeing 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 — you need one honest form and the freedom to improve it without redoing anything.

3. One record connects the whole journey. Each stakeholder carries one ID (usually an email) across every form they ever touch. Their intake answer, mid-program dip, exit reflection, and follow-up wage line up as one story — so “did their situation improve?” becomes a question you ask in plain language and answer with evidence, line by line.

None of this requires abandoning what you have. Many organizations keep their existing system of record and add intelligence as the reading layer on top. The point is not new software for its own sake — it is that the question funders and boards now ask has changed from how many did you serve to did their situation improve, and can you show it, and record-keeping alone cannot answer it.

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 stakeholder journey lasts months to years, much of the evidence is qualitative (essays, reflections, notes, interviews), and someone — a funder, a board, an investor — is owed proof of outcomes.

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.

The two organizations this series follows

Case intelligence serves a broad range of organizations, but a series needs concrete hands to watch. Throughout these chapters we follow two — chosen because together they cover both halves of most readers’ reality:

The nonprofit. A grant-funded organization that takes people from application to job-ready — recruiting cohorts, training, mentoring, tracking growth. Its money comes from grants and donations, so its year ends with a funder report: outcomes against targets, cost per outcome, evidence behind every claim.

The social enterprise. An organization that places job-ready candidates into apprenticeships and jobs with employer partners. Its money comes partly from placement fees, so its year ends with an investor and board report: social outcomes beside unit economics — fees earned, cost recovery, the path to sustaining itself.

If you run a scholarship program, an accelerator, or a youth program, you will recognize yourself in the nonprofit’s chapters — swap “job-ready” for your own outcome. If you run anything with a placement, matching, or marketplace side, the social enterprise’s chapters are yours. Most readers will find they are partly both.

First, a framework — any framework

Case intelligence does not begin with software. It begins with a clear statement of the change you intend to cause. Any of the standard frameworks works:

• Theory of change — the most common, and the one this series uses: a causal chain from activities to outcomes to impact.
• Logic model — inputs → activities → outputs → outcomes, the classic funder-friendly grid.
• Logframe — the 4×4 matrix common in international development.
• Results framework — objectives laddering to intermediate results, common in government-funded work.

They differ in format, not in essence: each names the outcomes you promise. That is all the rest of the series requires. Chapter 2 builds one; if you already have a framework you trust, skim it and move on.

What you will learn, chapter by chapter

The series is one continuous journey, in three segments. Everyone reads the foundation; then follow your own track — most readers will use both.

Foundation — your framework and your workflow (everyone)

• Chapter 2 · How to Build a Theory of Change — name the change you intend to cause, as a chain from activities to outcomes to impact, with each link graded by the evidence behind it. (Logic model, logframe, and results framework work identically — links in the section above.)
• Chapter 3 · How to Turn a Theory of Change into a Data-Collection Workflow — one measure per outcome, a home and a moment for each measure, and the build order that shows value first: applications, then baseline, then the moments that prove change.

The nonprofit track — from application to funder report

The grant-funded journey: recruit a cohort, train, support, prove the change — and report it to the people who funded it.

• Chapter 4 · How to Review Applications Without Reviewer Bias — one rubric, every application scored the moment it arrives, each score backed by the applicant’s own words. No reviewer committees, no weeks of coordination.
• Chapter 5 · How to Design an Intake Form That Captures a Usable Baseline — the “before” numbers that make change provable later, captured at zero extra cost because the application already asked.
• Chapter 6 · How to Spot At-Risk Participants Mid-Program — catch the people who are drifting while intervention is still cheap, including the ones perfect attendance hides.
• Chapter 7 · How to Measure Change at Exit — close the before/after pair the baseline opened. Completion is not change; this chapter measures the change.
• Chapter 8 · How to Catch At-Risk Participants Early with Mentor Notes — turn weekly mentor and staff notes into early-warning signals, from evidence only — never inferred feelings.
• Chapter 9 · How to Calculate SROI — Live, Sourced, and Honest — cost-per-outcome and social return computed from live records, with measured value kept honestly separate from benchmarks.
• Chapter 12a · How to Turn a Cohort into a Funder Impact Report — the payoff: outcomes against targets, every claim cited and graded, written as a query over records that were analyzed all along — not a month of copy-paste.

The social enterprise track — from employer demand to investor report

The earned-revenue journey: understand employer demand, match candidates fairly, and report social outcomes beside unit economics. (It draws on the same participant journey above — most social enterprises run both tracks.)

• Chapter 10 · How to Turn a Job Description into a Requirements Checklist — parse any employer’s job description into structured requirements, each marked disqualifying or trainable, the day it arrives.
• Chapter 11 · How to Score Candidate–Role Matches Without Bias — every candidate–role pair scored on one rubric, so unfilled openings and unplaced candidates become one diagnosis instead of two mysteries.
• Chapter 12b · How to Turn a Cohort into a Social-Enterprise Investor Report — the payoff: blended value for investors and the board — social outcomes beside fees earned, cost recovery, and the path to self-funding — from the same records that produced the funder report.

Read in order for the full arc, or jump to the chapter that hurts most right now — each stands alone.

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 the touchpoints from first contact to final follow-up, and mark which touchpoints you currently collect — and which ones vanish into un-connected 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 series was written for you.

See a stakeholder journey read on arrival in Sopact Sense — sopact.com/academy.

Next in the series: How to Build a Theory of Change — before any data is collected, name the change you intend to cause. Chapter 2 builds the framework the rest of the series proves.