Victim services case management software that holds one confidential survivor record from intake to outcome - VAWA-aligned access controls, the case note read on arrival, and the VOCA PMT report as one query, not a year-end rebuild.
The case management software most victim-service agencies run was built to collect for compliance — log the intake, record the service, file the VOCA report. Collection is solved. The new bottleneck is the workflow that reads every advocacy note on arrival — and surfaces the survivor whose safety or stability is slipping before the next contact.
The survivor is the unit of work, and the record has to be intelligent and confidential. When the intake, the safety plan, the advocacy note, and the follow-up live on one survivor-controlled record — one ID, one story, under your own access controls — the outcome a funder asks about shows up on Tuesday, not at year-end. That is the difference between case management and case intelligence.
Victim services case management software is a platform that holds one confidential record per survivor across every interaction — intake, safety planning, advocacy and counseling, services delivered, and outcome follow-up — so advocates and directors get answers without a spreadsheet merge, under access controls aligned with VAWA confidentiality requirements. It is the separate, dedicated system DV and SA programs use instead of a shared HMIS database.
It is also searched as domestic violence case management software, DV/SA case management software, or victim advocacy software — all naming the same need: one confidential survivor record that proves outcomes, not just logs services for compliance.
Used by:
Not the same as a shared HMIS database (which VAWA prohibits for survivor PII), a CRM that tracks donors, or an EHR for clinical billing. Victim services software tracks survivors through a confidential service-and-outcome lifecycle, with the advocacy note and outcome evidence at the center.
For two decades the category was defined by compliance collection: enter the service so the VOCA report ties out, and keep the survivor’s data confidential. That was the right tool for the problem — a defensible, separate record that meets VAWA. Collection is now solved. Every platform runs a basic intake → service → report flow under access controls.
The work moved. The hard part is no longer logging the service for the funder — it is reading the advocacy note, the safety plan, and the follow-up as they arrive, and carrying one confidential survivor record so the outcome story is one query. AI without a workflow is a clever intern with no desk. The agencies winning with AI are the ones whose survivor data has a place to land — one record, one ID, one story, under their own control.
| The compliance-collection era | The case-intelligence era |
|---|---|
| Log the service so the VOCA report ties out | Read what changed and surface risk as data lands |
| A separate record per program, reconciled by hand | One confidential survivor record across every program |
| Advocacy notes filed as documents, read by nobody | Every note read on arrival; risk surfaced before the next contact |
| Outcome follow-up lives in a spreadsheet off to the side | Intake and follow-up on the same record, scored together |
| The VOCA PMT and coalition reports are multi-week rebuilds | Each report is one query off the same records, note attached |
Open Play Foundation had been running programs for years. The notes, attendance logs, and outcome surveys lived in different systems, the way they do at almost every service agency. The structured system recorded what was delivered. It was never built to read what changed. Until those records lived on one client, Marco couldn’t see what was happening across the caseload — only what each spreadsheet told him.
Same logic for a victim-services advocate: when the intake, the safety plan, the advocacy note, and the follow-up live on one confidential survivor record, the reading nobody could do before shows up on Tuesday, not at year-end — without ever pooling identifiable survivor data into a shared database. The pattern that was buried across files — the survivor quietly disengaging, the program that isn’t moving anyone toward safety — becomes a single query.
Every survivor passes through the same five stages from intake to outcome. Case intelligence builds the spine once; every program plugs into it, under your own access controls. This is what a system bought to log services for compliance can’t do.
The survivor arrives with structured fields, open-ended answers, a safety plan, and consent on one form — a confidential record, not a folder, under field-level access controls.
Your theory of change or VOCA outcome rubric, encoded as the framework every survivor record is evaluated against. The funder’s questions, built in.
Every field and code list in one dictionary, configured in plain English — what keeps the record readable and consistent across advocates and turnover.
Built-in skills read each advocacy note on arrival and code it against the rubric with attribution — not a black box, and never pooled into a shared database.
The VOCA PMT, VAWA / OVW, and state coalition reports — each one query, each number citing its advocacy note. Clean exports drop into Looker Studio, Power BI, or Tableau.
Whatever a victim-services agency runs, the service gets logged for compliance and the outcome evidence ends up scattered across notes, surveys, and spreadsheets. Each lifecycle below has its own intake, its own outcomes, and its own funder report — and one confidential survivor record holds them all on one ID.
Intake, safety planning, shelter stay, and stable-housing outcomes — reported to VOCA and HUD-adjacent funders, but never into a shared HMIS for DV survivors. Continuity from crisis to stability is the whole point.
Hospital accompaniment, advocacy, and follow-up across a sensitive arc. The qualitative note carries the evidence; the survivor controls what is released and to whom.
Protective-order assistance, court accompaniment, and case status over months. Outcomes — order granted, safety improved — live in notes that rarely connect to intake.
Counseling and advocacy for child and teen survivors, with stronger consent and access safeguards. Developmental follow-up across a long arc is hardest to keep without one record.
Complex, multi-agency support over a long horizon — housing, legal, benefits, counseling. The cross-service story is the report, and it’s the hardest to assemble by hand.
The same survivor in shelter + legal advocacy + counseling at once. The agency sees the whole story on one confidential ID; the funder report stops double-counting across services.
| Program shape | Before (compliance database + spreadsheets) | After (one confidential survivor record) |
|---|---|---|
| Emergency shelter | Stay logged for VOCA; stable-housing outcome never connects back to intake. | Intake-to-housing outcome on one ID; the safety arc is one query. |
| Sexual assault advocacy | Advocacy notes filed and unread; evidence of change is anecdotal. | Each note read on arrival and themed; the qualitative outcome is defensible. |
| Legal advocacy | Court status in one tool, intake in another; outcome reassembled by hand. | Protective-order outcome native to the record; reportable on demand. |
| Children & youth | Stronger consent rules make the data even harder to connect across tools. | Access safeguards built into one record; follow-up automatic at any scale. |
| Human trafficking | Multi-agency services scattered; the cross-service story never completes. | One survivor record across services; the full journey is one query. |
| Multi-program center | One record per program; the same survivor double-counted in the report. | One confidential ID; each program contributes to one record; no double-counting. |
A boundary, named honestly: the 24/7 crisis hotline is real-time work, and real-time crisis dispatch is not what Sopact is built for. Sopact is for the advocacy-and-outcome arc that follows — intake, services, follow-up — not the live hotline itself.
Most agencies lose continuity at every tool boundary — the intake is in one place, the advocacy note in another, the follow-up in a third. Case intelligence keeps survivor #14837 the same record at every moment: intake, safety plan, services, follow-up, outcome — under your own access controls, never pooled into a shared database.
Survivor #14837 created with a safety plan and consent on one confidential record. AI codes the presenting needs from the intake note.
Goals and risk factors attach to #14837, scored against the framework already built in. Access is limited to the assigned advocate.
Shelter, legal, and counseling notes link to the same record. No re-matching, no pooling of identifiable data.
Outcome and safety status update #14837. A survivor-controlled link lets them fill the one missing field — no duplicate record.
Long-term safety and stability — queryable on one ID. The VOCA PMT report writes itself; nothing was reassembled by hand.
These are real, capable systems — Osnium and EmpowerDB are purpose-built for DV/SA agencies; Collaborate serves the DV/SA space; Bonterra Apricot and Penelope are widely deployed across social services. The rows below aren’t about whether they log a service for compliance. Every one of them does, with confidentiality controls. They ask the third question a funder, board, or auditor asks: does the software read the advocacy note, carry one survivor across programs, and hand you the VOCA report as one query.
| Capability | Sopact | Osnium | EmpowerDB | Collaborate | Bonterra Apricot | Penelope |
|---|---|---|---|---|---|---|
| Time to first cycle live | Days | Weeks | Weeks | Weeks | 2–4 mo | 2–5 mo |
| AI reads advocacy note on arrival | Yes · native | No | No | No | No | No |
| Rubric scoring & citation trail | Yes · native | No | No | No | No | Custom build |
| One confidential survivor ID across programs | Yes · native | Yes | Yes | Yes | Yes | Yes |
| VOCA PMT / coalition report as one query | Yes · native | Yes | Yes | Yes | Partial | Partial |
| VAWA-aligned confidentiality & access control | Yes | Yes | Yes | Yes | Yes | Yes |
| Configuration in natural language | Yes · native | Partial | Partial | Partial | Consultant | Consultant |
| White-label survivor-facing forms | Yes | Limited | Limited | Partial | Partial | Partial |
| Built for small organizations (under 15 staff) | Yes | Yes | Yes | Yes | Heavy lift | Heavy lift |
| Multi-site / multi-program | Yes | Partial | Partial | Partial | Yes | Yes |
| Longitudinal outcome tracking (1–3 yr) | Yes · native | Custom build | Custom build | Custom build | Custom build | Custom build |
Honest reading: the domain tools (Osnium, EmpowerDB, Collaborate) are strong on confidentiality and VOCA compliance and are trusted systems of record; Apricot and Penelope bring breadth across social services. Where none was designed to compete is the case-intelligence layer — reading the advocacy note on arrival, scoring it against a rubric with a citation trail, and being live in days. Vendor capabilities change; confirm current details with each before deciding.
There’s no seat math and no tier puzzle. The real question is fit. Sopact is most powerful for victim services when three things are true — and most honest about the two places it won’t pretend to be the system of record.
If your funder asks whether the survivor’s safety and stability changed over time — not only how many were served — that is the exact question Sopact is built to answer.
The longitudinal arc is where Sopact is strongest — the same survivor from intake to a long-term safety outcome on one confidential record.
When the proof of change lives in advocacy notes, Sopact codes it on arrival — every number traces back to the source. Not “survivors felt safer” but “38 of 120 follow-ups, e.g. survivor #2841: I have a protective order and a lease in my name.”
Sopact is built for program cadence — intake, advocacy, follow-up. The real-time 24/7 crisis hotline and emergency dispatch are a wall we don’t engineer around, and we’ll say so on the first call.
If you need Sopact to be the EHR, the legal case-management system, or a shelter bed-management tool, that’s the wrong shape. Sopact is the case-intelligence layer on top of those systems of record.
The whole spine — data dictionary, built-in skills, white-label survivor-facing forms, mixed-model auto-indicators with attribution, and definitive reporting (VOCA PMT, VAWA / OVW, coalition) — is configured in plain English, not by a consultant on retainer. That is why the first intake-to-report cycle is live in days while a legacy build runs months.
The annual VOCA report gets the attention. But the day-to-day reports that change how a program runs are simpler — and rarely built, because the evidence is stuck in advocacy notes and spreadsheets. Case intelligence ships all four, under your access controls.
Survivors with an intake but no follow-up. Cases with no safety-plan review logged. Surfaces the gap before the VOCA PMT deadline does.
A survivor whose risk indicators rose between contacts. An advocacy note flagging a danger nobody escalated. The supervisor sees what to look at before the next contact.
Outcomes, services, and coded advocacy-note themes — the VOCA PMT or coalition report as one query, in whatever format the funder wants.
Year-over-year safety and stability outcomes, cross-program overlap, retention — de-identified for the board meeting, not the raw export.
Sopact is used by small DV programs and by multi-program victim service centers. The system is the same; the complexity dial moves.
A shelter or advocacy program with a few hundred survivors a year, currently on a domain database plus spreadsheets, that needs a first defensible VOCA outcome report.
Tags: single-program, confidentiality-first, spreadsheet-to-system migration.
A center running shelter + legal advocacy + counseling on one survivor, reporting to VOCA, VAWA, and the state coalition with different outcome questions.
Tags: multi-program, multi-funder, longitudinal tracking, coalition reporting.
A coalition or multi-site agency rolling up de-identified outcomes across member programs, that needs one confidential survivor ID to survive across locations.
Tags: multi-site, coalition rollup, white-label, de-identified analytics.
If you need a 24/7 crisis-hotline platform, a clinical EHR with medical billing, or a pure shelter bed-management tool, Sopact is not that system — and we’ll say so on the first call. Sopact is the case-intelligence layer for the confidential service-and-outcome lifecycle, sitting alongside those systems rather than replacing them.
Questions on victim services case management software — also searched as domestic violence or DV/SA case management software — from confidentiality and security to how it compares to the systems agencies already run.
Victim services case management software is a platform that holds one confidential record per survivor across every interaction — intake, safety planning, advocacy and counseling, services delivered, and outcome follow-up — so advocates and program directors get answers without a spreadsheet merge, under access controls aligned with VAWA confidentiality requirements. It is the separate, dedicated system DV and SA programs use instead of a shared HMIS database.
There’s no single best tool, because most platforms in this category were built to log services for compliance, not to read outcome evidence. For a small DV or SA agency, the deciding factors are confidentiality controls, time to first cycle live, whether the software reads advocacy notes on arrival, and whether VOCA PMT reporting is one query. Domain tools like Osnium and EmpowerDB are purpose-built for collection and compliance; Sopact adds the case-intelligence layer that proves the outcome.
Sopact is priced by use-case complexity, not seats or records. A small single-program DV agency pays less than a multi-site victim service center running shelter, legal advocacy, and counseling. Pricing reflects the number of programs sharing one survivor record, multi-site footprint, longitudinal depth, custom rubrics, white-label depth, and integration. There are no Starter / Agency / Enterprise tiers.
There are low-cost and grant-funded options, and some state coalitions provide a shared database. They cover basic service logging for compliance, but outcome work outgrows them fast: no reading of the advocacy note on arrival, limited qualitative analysis, and confidentiality models that vary in strength. A tool that forces a year-end hand reconstruction to prove outcomes is not free once advocate time is counted.
VAWA confidentiality provisions restrict victim-service providers from entering survivor personally identifying information into shared databases such as HMIS, and require survivor-controlled release of information. Sopact supports this with field-level role-based access, encryption at rest and in transit, full audit logging, white-label survivor-facing forms, and a record that is yours alone — not a shared comparable database. Sopact is not currently HIPAA-certified — if your program handles Protected Health Information under HIPAA, confirm whether your specific workflow falls inside or outside the HIPAA boundary before implementation.
Under VAWA, domestic violence and sexual assault providers are prohibited from entering survivor personally identifying information into a shared Homeless Management Information System (HMIS), because aggregating identifiable survivor data in a comparable database creates a safety risk. DV programs instead use a separate, dedicated, comparable database with equivalent reporting. Victim services case management software is that separate system — one confidential record per survivor, under the program’s sole control.
It should, within the program’s confidentiality model. A victim service center often serves the same survivor in shelter, legal advocacy, and counseling at once. Legacy systems create a separate record per program, so the survivor is double-counted and the cross-program story is reassembled by hand. Sopact carries one confidential survivor record across every program under the program’s own access controls, so the full history is one record and the funder report stops double-counting.
Outcome-focused victim services software should produce the reports a victim-services funder asks for as a single query off the same records: the VOCA Performance Measurement Tool (PMT), VAWA / OVW reports, state coalition and STOP-grant reports, and the board-ready outcome report. The difference is that each number carries the supporting advocacy note, so the report is defensible, not a year-end reconstruction.
Those are real, capable systems — Osnium, EmpowerDB, and Collaborate are purpose-built for DV/SA confidentiality and VOCA compliance; Bonterra Apricot and Penelope bring breadth across social services. They win on being trusted systems of record. Where none was designed to compete is the case-intelligence layer: reading the advocacy note on arrival, scoring it against a rubric with a citation trail, configuring in plain English, and being live in days. Vendor capabilities change, so confirm current details with each before deciding.
Migrate in four stages: stop new intake from flowing into the old spreadsheet, pilot with one program and a small set of current survivors, standardize all new intake through Sopact with a unique confidential ID assigned at intake, then backfill historical data in priority order. Full migration for a small agency typically takes 4–8 weeks, the confidentiality model is configured up front, and most teams never backfill the oldest records — and nothing breaks.
CSBG, housing, energy assistance, and multi-program agencies on one client record.
Child welfare, behavioral health, and field casework with mobile support.
Shelter and stable-housing outcomes — the housing arc many survivors travel.
The plain-English hub — the process, models, and best practices behind the work.
What a system must do and how to choose one — the selection view.
No demo theater. No discovery phase. Tell us what you run, how confidentiality has to work, and which funder reports you owe — VOCA PMT, VAWA, coalition. We’ll show you what the first 30 days look like on Sopact.
