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.
A case management pulse — Sopact's term for holding the same person across intake, mid-program, exit and follow-up on one ID; longitudinal, person-level.
A case management pulse is a structured, longitudinal cycle that holds the same person across intake, mid-program, exit, and follow-up under one persistent client ID — so the unit of analysis is the person over time, not the encounter, the form, or the fiscal quarter. Instead of counting how many people a program served, a pulse follows each person across repeated measurement points and reads what changed for them between waves. "Pulse" is Sopact's term for this longitudinal, person-level case-tracking design; the underlying practice is well established — it is longitudinal MEL (monitoring, evaluation and learning), outcomes tracking, and pre-/mid-/post measurement applied at program scale rather than research scale. If you already run baseline-and-follow-up outcome measurement on the same clients, you are already running a pulse; this page just names the architecture and its design rules.
Read this if you are: an M&E or MEL lead, a program director, or an outcomes team designing the cycle architecture under a case management workflow — and you want the same person to look like the same person across intake, exit, and a follow-up eighteen months later.
The fastest way to understand a pulse is to separate it from three adjacent things it resembles but is not. Each shares a surface feature — a question asked, a record kept, a number shown — and each is missing the one property that makes a pulse a pulse: the same person, held across time, on one ID.
Not a one-off satisfaction survey. A satisfaction survey is a single moment: it captures how someone felt about a service at one point in time, usually anonymously, and it is done. A pulse asks related questions at intake, mid-program, exit, and follow-up under the same client ID, so the signal is the change across waves, not any single answer. A satisfaction score tells you the workshop went well; a pulse tells you whether the family was still housed six months later.
Not a static case file. A case file accumulates — intake documents, service notes, an exit form — but it is a folder, not a cadence. It stores what happened; it does not compare a defined follow-up wave against a defined baseline. A pulse turns the same underlying record into a series of intentional measurement points with a comparison frame built in: this wave, relative to the wave before.
Not a point-in-time dashboard. A dashboard aggregates many different people at one moment — 1,200 cases open, 340 exited this quarter. That is cross-sectional. A pulse is longitudinal: it holds 1,200 people each followed across their own cycles, so "what changed for them" is answerable rather than reconstructed. Same data volume, different architecture, different funder conversation.
Platforms differ; pulse principles do not. A team that wires these correctly gets useful longitudinal outcome data even from a careful spreadsheet; a team that skips them gets assembly-by-hand reporting from any platform, including the expensive ones. Five principles carry the whole design.
One persistent client ID. The same person is held under one record across intake, mid-program, exit, and follow-up — and, ideally, across every program the organization runs. This single layer is what turns four separate data-collection moments into one longitudinal trail. Without it, every wave is a fresh record and longitudinal outcomes get reconstructed from scratch each quarter. Holding one client across capacity and time is the job of caseload management software.
A baseline captured at intake. Intake names the hypothesis — what the program expects to change for this person, beyond their current situation. That baseline is the reference every later wave is compared against. Skip it and exit becomes a status check ("apartment retained") rather than an outcome verification ("apartment retained, relative to eviction risk at intake").
Mixed quant and qual, read together. A pulse pairs structured fields (counts, screen scores, exit status) with qualitative narrative (case notes, open-text responses) so the number and the story arrive in the same answer — "912 evictions prevented, of which 87% were stably housed at six-month follow-up," with the case-note quote on what held the housing. The requirement is an analytical layer that can read case notes as evidence alongside the structured columns, not as attachments a human re-reads by hand.
Read on arrival, not at year-end. A pulse reads each wave as it lands — coding the note against the plan, surfacing risk in the cycle it happened — rather than sampling at the supervisor's month-end or reconstructing the picture at the annual report. Cadence over depth: a short cycle that runs reliably beats a long cycle that runs occasionally.
Follow-up planned at intake. The follow-up wave is what turns a program output into a verified outcome, so the contact channels and follow-up expectations are captured at intake, not improvised at exit. The longitudinal horizon is the entire point — it is what separates an exit survey from an outcome. This is standard outcome tracking discipline; the pulse just makes it the default shape of the record.
The principles are architecture; case intelligence is what runs them without a year-end reconstruction. Everything a client touches — intake, the baseline screen, every case note, the six-month follow-up — lands on one persistent client ID, aligned to your framework, so the same person looks like the same person across programs and years. The part that changes daily work is the Assistant: ask a question in plain language, get a defensible answer with citations to the underlying records, no dashboard hunting and no waiting for the one analyst who knows where the export lives. Because a program is never one user — program staff, supervisors, the board, funders, and clients all need different views of the same record — a chat interface reads the pulse for each of them directly, and turns the answer into a shareable report without copying numbers into a Word doc. The determinism matters here: the same question returns the same answer every time, which is what makes a longitudinal rollup safe to put in front of a funder. This connects the person-level record to stakeholder intelligence across the whole organization.
Two prompts turn the pulse from a diagram into something you can run today. The first compares a baseline wave to a follow-up wave; the second reads case notes across waves as outcome evidence. Both are copy-paste — the placeholders in brackets are yours to fill.
Compare the intake baseline to the [90-day / 6-month] follow-up for [COHORT OR PROGRAM] under one client ID: which outcomes moved, by how much, and with what confidence? Show change per indicator, flag where the sample is too small to conclude, and pair every number with a representative case-note quote from the same clients. Treat this as change over time on the same people, not attribution.
Read the case notes across all waves for [COHORT OR PROGRAM]: intake, mid-program, exit, and follow-up. For each client, summarize what changed between waves with the exact source sentence, code the notes against our outcome indicators, and flag any client whose follow-up wave is missing or overdue. Use the same coding method across every wave so the results are comparable.
The principles above are the argument; the Academy walkthroughs are the practice — each a hands-on companion for one part of running a pulse on your own data.
A case management pulse is a structured, longitudinal cycle that holds the same person across intake, mid-program, exit, and follow-up under one persistent client ID. The unit of analysis is the person over time. It is the architectural difference between a 1,200-cases-this-year report and a 1,200-people-each-followed-for-eighteen-months report. "Pulse" is Sopact's term for the design; the underlying practice is longitudinal outcomes tracking applied at program scale.
A satisfaction survey captures how someone felt at a single moment, usually anonymously, and then it is done. A pulse asks related questions at intake, mid-program, exit, and follow-up under one client ID, so the signal is the change across waves rather than any single answer. A satisfaction score says the service went well; a pulse says whether the outcome held six months later.
No — "pulse" is Sopact's framing for a longitudinal, person-level case-tracking design. The practice underneath it is entirely standard: longitudinal MEL, outcomes tracking, and pre-/mid-/post measurement have been used in evaluation for decades. If you already run baseline-and-follow-up measurement on the same clients, you are running what this page calls a pulse; the term just names the architecture and its design rules so a program can build it deliberately.
The person over time. Cross-sectional reporting aggregates different people at one moment (how many were served this quarter); a pulse follows the same person across multiple points in time (what changed for them between intake and follow-up). The persistent client ID is what makes the person, rather than the encounter or the reporting period, the unit that composes across cycles.
A pulse is longitudinal MEL operationalized at program scale. Pre-/mid-/post measurement is exactly the intake / mid-program / exit shape, and the follow-up wave adds the outcome-durability check that funders increasingly ask for. A longitudinal research study follows a large cohort across years; a pulse is the operational equivalent — a few hundred clients followed across the program plus a follow-up window, on the same person-level architecture but a faster, lighter deployment.
Case intelligence holds the case file as one longitudinal record under a persistent client ID, with structured fields and case notes in the same workflow. An analytical layer reads both deterministically — the same question returns the same answer every time — so the baseline-to-follow-up comparison and the case-note evidence roll up as a query instead of a hand-assembled quarterly report. The pulse cadence is defined by the program; the rubric for what counts as an outcome is defined by the team. See case management software for the platform view and nonprofit case management software for the buyer frame.
If your case files contain the answers but the funder report still gets written by hand each quarter, you have a pulse problem, not a platform problem. A short, contained conversation maps your existing cycles, finds the gap — missing intake baseline, no single client ID, notes-as-evidence, or rollup architecture — and shows whether a methodology change can ship without replacing the platform you already run. Related frames: what is case management, the case management process, and social work case management software. Map your pulse in 30 minutes →