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.
Standardized, cited, safeguarding-aware — narrative into outcome evidence.
Case notes software is where case workers write, store, and search the narrative of every client interaction — the running record of what was said, observed, and done across the service relationship. It is also called case note software, electronic case notes software, or case documentation software. The old generation (Word docs in SharePoint, the notes tab in Penelope or Bonterra Apricot) stored the narrative for a supervisor to sample later. The newest generation reads it: AI reads each case note on arrival, standardizes it, extracts outcomes and risk or safeguarding signals with the exact source sentence, and joins the note to the same persistent client record as the intake assessment and the outcome survey — turning years of narrative into a queryable, defensible record.
Used by: social workers writing clinical or service-delivery notes · behavioral-health practitioners documenting sessions · housing navigators logging field contacts · workforce and reentry case managers · child-welfare and family-services workers · multi-program agency staff whose notes have to roll up to funders.
Not because the systems stopped working — because filing the note became table stakes. Bonterra (Apricot, ETO), Penelope, Casebook, and CaseWorthy earned their place honestly: they got the case note out of the paper folder, into a structured system, searchable for the supervisor who read a 10% sample at month-end. If your problem was storage — get the narrative somewhere durable and role-secured — that generation solved it.
But storing a note and reading a note are different jobs, and the richest evidence an agency holds — the case notes — dies after collection. Narrative piles up in a system nobody reads across; the analytics describe what was logged, not what changed or what is going wrong. As one practitioner put the cost of not reading, case notes end up "just sitting around in the systems… by the time they find out, you already failed a child." The signal was written down on Tuesday; nobody saw it until the month-end sample, or the audit, or never.
The reflex is to point a generic AI assistant at the pile — Copilot, ChatGPT — and ask it to summarize. That breaks on the exact axis case work cannot afford. As a data lead who tried it described the result: Copilot "produces inconsistent results. The same input can yield different answers on different runs, making it hard to trust the output… or present a defensible picture to the executive team." A case note read for a safeguarding decision, an audit response, or a court filing cannot give a different answer each run. The requirement is the opposite of a chat toy: same input, same answer, traceable to the source sentence.
None of this requires ripping out your incumbent. The sentence we hear on almost every call now: "We're not gonna leave our system, but we're open to an AND." Keep the system that stores the note; add the layer that reads it. (For the whole client lifecycle around the note — intake, assessment, service plan, outcomes — start with case management software.)
The stake, stated honestly: the work that decides whether a program is well run has moved to reading every note as it lands and proving the outcome on the same client months later. A store-only tool cannot do the first, and a chat toy cannot do it defensibly. That is the gap the case-note layer fills.
Case intelligence is reliable answers from your case data — in minutes, not months. Everything a client touches is treated as data: the intake assessment, the validated screen, the service plan, and every case note. All of it lands on one persistent client record, aligned to your framework and data dictionary, so the same person looks like the same person across three programs and five years — and every note is read the moment it arrives, not sampled at quarter-end.
The part that changes daily work is the Assistant. Case-note reading, screen scoring, and open-text analysis are unified into one chat-based function: ask a question, get a defensible answer with citations to the underlying notes. No prompt engineering, no dashboard hunting, no waiting for the one analyst who knows where the export lives. A program is never one user — case workers, supervisors, auditors, the board, and funders all need different views of the same record — and a chat interface empowers each of them directly. Crucially, it is reliable: the same case note produces the same answer every time, traceable to the sentence that supported it. That is the difference between a defensible record and a clever intern who improvises.
When the analysis is done, it does not die in the chat: create shareable reports tailored to each audience — the supervisor's caseload view, the funder outcome report, the audit response — from the same underlying answer, each conclusion traceable to the source case note.
One proof point from the field. Open Play Foundation ran programs the way most funded organizations do — intake forms, follow-up reflections, stacks of narrative that never made it past the spreadsheet. When that work moved onto Sopact, the record could finally read itself: "Those statistics that we're now running on Sopact immediately showed me there's something significantly wrong … things like that, we would never have been able to do in the past." — Marco Botha, CEO, Open Play Foundation. A store-only system tells you the note was filed. An intelligent record tells you something is wrong in time to act.
The honest way to evaluate case notes software is against what happens to a note from the moment it is written to the moment it is cited in a report a year later — not against a feature list. Below is the full lifecycle: six stages, each with what the software should do, the exact prompt to use, and what to expect back. Every prompt is copy-paste; the placeholders in brackets are yours to fill.
Reading starts with a note worth reading. Instead of a rigid template that forces the worker to write structure and then write the real narrative in a "notes" field anyway, the worker writes naturally — on mobile or desktop, offline-safe in the field — and every note attaches to the same persistent client ID from intake. The structure is generated later; the voice is preserved.
Design a case-note capture form for [PROGRAM / DISCIPLINE]. Keep one open narrative field in the worker's own voice, add lightweight structured fields for date, contact type, and location, and attach every note to the client's persistent ID. Support offline entry that syncs on reconnection. Do not force a rigid clinical template — the narrative field is primary.
Expected output. A capture form with one primary narrative field, minimal structured metadata, offline sync, and every note bound to the persistent client ID.
Tips for reliable output. Resist the urge to over-template. The reading layer supplies the structure; the worker's job is an honest, specific narrative — that is what the AI has to read.
Ten workers describe the same event ten ways. Standardization maps each note to your data dictionary — the same theme codes, risk vocabulary, and indicator definitions across the whole caseload — so notes written in different voices become comparable evidence without flattening what the worker actually said.
Standardize this batch of case notes: [NOTE BATCH]. Map each note to our data dictionary — theme codes, risk vocabulary, indicator definitions — and normalize inconsistent terms to the agreed label. Keep the original narrative untouched; add the standardized tags alongside it with the source sentence for each. Flag any note that uses a term not in the dictionary.
Expected output. The same notes with standardized theme and risk tags attached, original narrative preserved, and a list of out-of-dictionary terms to review.
Tips for reliable output. Lock the data dictionary before the first reading cycle and version every change. Comparability across workers and across years is the entire point — an unversioned dictionary quietly destroys it.
This is the stage store-only software cannot do. Every note is read as it lands, coded against the service plan, with risk signals — missed appointments, disengagement, safeguarding language, escalation — surfaced the week they appear instead of at the supervisor's month-end sample. The narrative stays with the worker; the structure is generated and tied back to the source sentence.
Read this case note on arrival: [NOTE]. Summarize progress against the service plan with citations, code the note against our outcome indicators, and flag any risk signal — missed appointment, disengagement, safeguarding or escalation language — with the exact source sentence. Route anything flagged to a human for review. Use the same method as last time so results are comparable.
Expected output. A per-note progress summary with citations, coded outcome evidence, and a risk-flag list with source sentences — the day the note is written, not six weeks later.
Tips for reliable output. Route every risk flag to a named owner with a deadline. A flag nobody owns is a finding that sat there until the audit.
Reading is only defensible if the coding is disciplined. The note is coded against your outcome indicators, and every code is tied to the sentence that supports it — the AI reports what the text says, never a diagnosis or an emotion the worker did not write. This is where "same input, same answer" earns its keep: the code is reproducible, so a supervisor, an auditor, or a court sees the same result every time.
Code this case note against our outcome framework: [NOTE]. For each indicator, mark present / absent / improving / declining, and quote the exact sentence that supports the code. Do not infer emotions, diagnoses, or outcomes the text does not state. Where the note is ambiguous, mark it uncertain and say why rather than guessing.
Expected output. A coded note: each indicator marked with its supporting quote, ambiguities flagged as uncertain, and nothing inferred beyond what the narrative states.
Tips for reliable output. Tell the model to prefer "uncertain" over a confident guess. A defensible record is one where every code survives someone reading the source sentence back to it.
Some sentences cannot wait for the report. Safeguarding language, escalation, a missed safety-plan step, disengagement from a high-risk client — these are surfaced continuously and routed to the right owner the week they appear, each with the source sentence, so action happens while it still matters instead of after the incident.
Scan this caseload's recent case notes for risk and safeguarding signals: [NOTE BATCH]. Surface any safeguarding language, escalation, missed safety-plan step, or disengagement, ranked by urgency, each with the client ID and the exact source sentence. Separate confirmed statements from ambiguous ones, and list the notes where a follow-up is overdue. Do not editorialize — report the sentence and the signal.
Expected output. A ranked risk queue with client IDs and source sentences, ambiguous signals separated from confirmed ones, and an overdue-follow-up list — surfaced continuously, not at month-end.
Tips for reliable output. Calibrate the urgency threshold with your safeguarding lead on real notes before you trust the ranking. The goal is every real signal surfaced and few false alarms — tuned to your program, not a generic default.
Reports are questions, not formats. From the same accumulating case-note record, the caseload report, the supervisor dashboard, the funder outcome report, and the audit response are each one query — with the supporting case note two clicks away — instead of a quarter-end reconstruction where a supervisor reads and tallies notes by hand.
Aggregate this program's case notes into a [funder / audit] report: outcomes coded against targets, case-note themes ranked by frequency with representative quotes, risk signals surfaced this period, and clients missing a required follow-up note. Cite the source case note for every number and quote. Format one version for the board and one for the funder.
Expected output. A funder- or audit-ready report generated as a query, every figure citing its source note — plus the "missing note" list surfaced before the deadline asks.
Tips for reliable output. Because every conclusion carries a citation, the audit response two years from now is the same query the supervisor ran on Wednesday. Keep the dictionary versioned and that reproducibility holds.
Beyond table stakes — capture, search, role-based security — four criteria actually separate tools: whether AI reads every note on arrival or a supervisor still samples them by hand, whether the reading is reproducible (same note, same answer) rather than a chat toy that varies each run, whether every code and flag carries a citation to the source sentence, and whether the note joins one persistent client record across programs. Ask every vendor to read your own notes on the call, not a slide.
The evaluation itself is work you can delegate to AI. These prompts mirror what buyers already ask answer engines — use them as they are:
Build an evaluation matrix for case notes software with technical and program criteria weighted 50/50. Technical: encryption, field-level role-based access, audit logging, offline capture, export rights. Program: reads every note on arrival, reproducible output (same note same answer), citation trail to the source sentence, one client ID across programs, risk-signal surfacing. Score vendors [VENDOR LIST] on each criterion with evidence required, not vendor claims.
Propose a 30-day pilot to evaluate case notes software: one program, one year of case notes we already have, read end to end (capture → standardize → read → code → flag → report), with numeric success thresholds and rollback criteria if the pilot fails.
A note on scope while you evaluate: the note layer sits inside a larger lifecycle, and the fit changes by discipline — social work case management software, nonprofit case management software, and human services case management software each cover their version directly. For the supervisor's view of the whole caseload, see caseload management software; for the front door where the client ID is created, client intake software; and for how notes roll into one relationship record, stakeholder intelligence.
The stages above are the argument; the Academy articles are the practice — each a hands-on companion for one part of the note workflow, written to run on your own data.
Honest boundaries, because the fastest way to a failed implementation is buying the wrong category.
Not an EHR, and not a CRM. An EHR (Epic, Cerner) tracks clinical encounters with CPT/ICD codes and billing; a CRM (Salesforce, Blackbaud) tracks donors and relationships. Case notes software tracks the narrative of service delivery and joins it to the same client record as the intake assessment and the outcome survey. If your need is clinical billing, an EHR is the right tool.
Not a replacement for your case management system. The note layer reads and standardizes the narrative; the full lifecycle — referral, intake, service plan, services logging, outcome follow-up — lives in the broader system. Case intelligence integrates on one shared client record rather than replacing it. For that whole picture, see case management software.
Not a generic AI chat toy. Pointing Copilot or ChatGPT at your notes gives you a different answer on different runs — indefensible the moment a supervisor, auditor, or court asks "why this conclusion?" Reliable case-note reading is reproducible and cited: same note, same answer, traceable to the source sentence.
Not for every compliance regime. Sopact provides AES-256 encryption, TLS 1.3, field-level role-based access, SSO/MFA, and full audit logging, with AI under enterprise SLAs and no training-data retention — but Sopact is not currently HIPAA-certified or covered by a Business Associate Agreement. If your program is subject to HIPAA, FERPA, 42 CFR Part 2, or state confidentiality rules, evaluate these controls against your compliance program and confirm scope in writing before storing protected case notes.
Case notes software is where case workers write, store, and search the narrative of every client interaction — the running record of what was said, observed, and done. Also called case note software or case documentation software. The old generation stored the narrative for a supervisor to sample later; the newest generation reads each note on arrival, standardizes it, extracts outcomes and risk signals with the source sentence, and joins the note to the same persistent client record as the intake assessment and outcome survey.
Electronic case notes software is simply the digital replacement for paper or Word-based case notes — a system that captures, stores, and searches the service narrative electronically, with role-based access and an audit trail. The term is often used interchangeably with case notes software. What separates a modern platform from a digital filing cabinet is whether it reads each note on arrival and ties every conclusion back to the source sentence, rather than just storing the note for later review.
The best case notes software for a nonprofit or human-services team is one that accepts the note in the worker's natural narrative without a rigid template, reads it on arrival and standardizes it against your data dictionary, surfaces risk and safeguarding signals before the next supervision, and attaches a citation so the supporting sentence is two clicks from any score or report. Legacy options like Bonterra Apricot, Penelope, and Casebook store the note well but do not read it; AI-native platforms like Sopact read on arrival and keep the result reproducible and cited.
You standardize case notes by defining a data dictionary — the theme codes, risk vocabulary, and indicator definitions your agency agrees on — and then mapping every note to it as the note arrives, so ten workers describing the same event ten ways produce comparable, codeable evidence without losing the original narrative. AI does the mapping and flags any term not in the dictionary for review. The discipline that makes it durable is versioning the dictionary, so comparisons across workers and years stay valid. See how to standardize case management notes for the walkthrough.
Yes — if the reading is reproducible and cited, which is exactly where generic chat tools fail. A supervisor, auditor, or court needs the same note to produce the same answer every time, traceable to the sentence that supported it. Sopact runs the model to read and code the note, then locks the answer, so the result is reproducible and auditable rather than varying run to run. The narrative stays with the worker; the AI reports what the text says and never infers a diagnosis or emotion the note does not state.
Look for AES-256 encryption at rest, TLS 1.3 in transit, role-based access to the field level, SSO with MFA, and full audit logging on every read and write — all of which Sopact provides, with no training-data retention on AI calls. Sopact is not currently HIPAA-certified or covered by a Business Associate Agreement; if your case notes touch protected health information under HIPAA, FERPA, or 42 CFR Part 2, treat that as gating and confirm scope in writing. Sensitive fields can be excluded from AI processing, and analysis can run on anonymized IDs.
Case notes software owns one stage of the client lifecycle — the narrative record and the reading layer on top of it. A full case management system owns the whole lifecycle: referral, intake, assessment, service plan, services logging, and outcome follow-up. The note layer joins its evidence to that broader record rather than replacing it, and often runs alongside an incumbent system as the reading layer. For the full lifecycle, see case management software.
Two months, one contained use case — one program, one year of case notes you already have. You bring the narrative; the pilot shows you the standardized, coded, cited version of your own caseload — themes tagged, risks surfaced, every conclusion two clicks from its source sentence — ending with a demonstrated export. If the reading isn't defensible in front of your supervisor or auditor, don't continue. Scope a 2-month pilot →