Case management software for domestic violence organizations is used to track extremely sensitive clients and services. It needs to protect survivor identities, restrict staff access by role, comply with HIPAA where health information is involved, and support the reporting requirements tied to VAWA funding. Most general-purpose nonprofit case management platforms are built for contexts with far less strict privacy requirements., but a select group of software platforms do fit these needs.
What makes case management software different for DV organizations
Domestic violence organizations operate under a set of requirements that most nonprofit software vendors don’t encounter. Privacy controls and confidentiality protections are legal and ethical baseline requirements for any organization working with survivors, not optional features to weigh against other capabilities.
Generic case management software often handles data security adequately for most nonprofits, but it can fall short in the specific areas DV organizations need most: restricting which staff members can view sensitive location or identity data, customizing intake forms for DV-specific screening tools, and generating reports that satisfy VAWA funder requirements without exporting data into spreadsheets and reassembling it manually.
Survivor confidentiality and address protection
Shelter addresses and client location data require strict controls in DV settings. A platform that makes physical location visible to all users (including volunteers, administrative staff, or employees working in non-shelter programs) creates real safety risks. The same applies to client names, contact information, and any identifying details that could be accessed by someone with unauthorized interest in a client’s whereabouts.
Role-based field-level visibility is the technical solution to this problem. It means the system controls who can view each field based on the staff member’s assigned role, so a hotline volunteer and a licensed case manager see different information when they pull up a client record. Not every platform supports this level of granularity. It’s one of the first questions worth asking any vendor.
HIPAA compliance for health-related intake
DV organizations that collect health-related information during intake, including mental health screening results, medical referral documentation, substance use history, or lethality assessment data, are subject to HIPAA if the organization qualifies as a covered entity or business associate under federal law. The threshold is based on what your organization does and what data you collect, not on your tax status. The HHS guidance on covered entities is the clearest reference for understanding where your organization falls.
For DV programs where HIPAA applies, HIPAA-compliant case management means more than storing data on a secure server. It means encryption at rest and in transit, audit logs that track who accessed which records and when, role-based access controls that enforce the minimum necessary standard, and multi-factor authentication. A vendor who can’t clearly explain which of their configurations meet these requirements is a risk your organization shouldn’t take on.
Role-based access and staff visibility restrictions
Many DV organizations run multiple programs: a residential shelter, a legal advocacy program, a children’s services program, and a community education team. Staff across these programs may need access to the shared case management system, but they shouldn’t all see the same client data. A children’s program coordinator has different informational needs than a shelter case manager. A volunteer intake coordinator needs access to far less than a licensed counselor.
Robust role-based permissions let administrators define exactly what each staff role can view, create, edit, and export. This protects client safety and reduces the risk of data being accessed or shared inappropriately, whether through negligence or malice. It also supports the confidentiality documentation requirements that VAWA-funded programs must maintain.
VAWA-funded program reporting requirements
VAWA grantees must document specific data at intake, throughout service delivery, and at case closure to satisfy federal reporting requirements. The exact data points vary by grant program and funding stream, but they typically include demographic information, types of services provided, case outcomes, and confidentiality compliance documentation. Organizations that track this data in a platform designed for other purposes often end up doing manual data assembly at reporting time, copying from the system, reformatting in spreadsheets, and reconciling inconsistencies before a report can go out.
Software with customizable forms and structured data capture makes VAWA reporting substantially more manageable. If the platform lets you build intake forms around the specific fields your funders require, and generates reports directly from those fields, you eliminate most of the manual work. This is where the flexibility of a configurable platform starts to pay off in concrete time savings.
Key features to look for in a DV case management platform
These features are relevant to any vendor evaluation, regardless of which platforms you’re comparing. A DV organization’s requirements are specific enough that a feature checklist matters more here than in most nonprofit software decisions.
Customizable intake forms with restricted fields
DV intake forms need to capture information that doesn’t appear in standard nonprofit intake workflows: safety planning status, danger assessment scores, lethality screening results, prior contacts with law enforcement, housing history, and whether the client has children in the household. A platform that limits you to a fixed set of fields forces staff to document this information in case notes or paper files, which creates compliance problems and makes reporting significantly harder.
Platforms that let program staff build and modify forms without IT support are particularly valuable in this context. DV organizations often serve multiple populations with different screening needs, and the ability to adapt intake workflows without a development contract reduces both cost and turnaround time. Nonprofit case management software designed with staff-configurable forms gives organizations ongoing control over how they capture program data as their needs evolve.
Encrypted data storage and transmission
At-rest encryption protects client records stored in the database from being read if the storage medium is compromised. In-transit encryption protects data moving between the client’s browser and the server, which matters particularly in remote access contexts: case managers documenting in the field, hotline staff working from home, and mobile outreach workers updating records from their phones. Both are standard in reputable platforms today, but verifying that the vendor implements them correctly and can provide documentation is worth the extra step.
Audit logs and access tracking
An audit log records who accessed which client record, what changes were made, and when. In a DV setting, this serves two distinct purposes. First, it functions as a compliance mechanism: some funders and regulators require organizations to demonstrate that access to sensitive records is monitored and documented. Second, it works as a safety control. If a question ever arises about whether a client’s information was accessed inappropriately, the audit log provides the record to investigate.
Look for platforms where audit logs are comprehensive, retained for a meaningful period (at least several years), and accessible to administrators without requiring a support ticket to retrieve. Some platforms treat audit logging as a premium feature or restrict access to the log data itself. Both are worth flagging during a demo.
Multi-program support for organizations running shelter and non-shelter services
Many DV organizations run a residential shelter alongside legal advocacy, children’s programs, transitional housing, and community outreach services. When these programs each operate in separate software, staff spend significant time manually reconciling data, and program directors have no unified view of how clients move between services. A client who exits the shelter and transitions into the legal advocacy program is effectively invisible in the second system if that system doesn’t connect to the first.
Platforms that handle multiple programs in a single environment, with program-level access controls, solve this without requiring data exports or manual reconciliation. Client records travel with the person rather than the program, which means staff can see a complete service history while still operating within their appropriate access level. Integrated nonprofit platforms built for organizations running both direct service programs and development functions handle this structure natively and eliminate the additional cost of maintaining separate tools for separate programs.
Questions to ask before selecting a platform
These are the questions an executive director or program director should ask any vendor before agreeing to a demo, let alone a contract. The answers will tell you quickly whether a platform was designed with organizations like yours in mind.
- Can you restrict which staff roles see shelter location or client address fields at the field level, meaning individual fields rather than just entire records?
- Are intake forms fully customizable without developer support or additional cost?
- How does the platform handle data that falls under HIPAA, and which plan or configuration includes those protections?
- What does the audit log capture, and how long is it retained?
- Can we separate program-level access while maintaining a single unified client record across authorized staff?
- How is data encrypted at rest and in transit, and can you provide documentation?
- Does your pricing model stay flat as we add staff, or does it scale per user? (See our nonprofit CRM pricing guide for context on how each model plays out over time.)
A vendor who hesitates on any of these questions, particularly the first and third, probably hasn’t built for DV contexts specifically. That doesn’t disqualify them from consideration, but it does mean your implementation will require more custom work and more reliance on your own policies to close the gaps their software doesn’t address.
Case management software options for domestic violence organizations
The following platforms are among the options DV organizations commonly evaluate. Verify specific compliance requirements directly with any vendor before signing a contract.
LiveImpact is a configurable nonprofit case management platform with flat-rate pricing and staff-managed customization. Program staff can build intake forms, add custom fields, and adjust workflows without technical support. Role-based access controls support field-level visibility restrictions, and multi-program support lets a shelter, a legal advocacy program, and a transitional housing program operate on the same platform with appropriately separated data. HIPAA-compliant configurations are available. Request a demo to walk through how the platform handles your specific program structure.
Bonterra Apricot is widely used in the DV sector, with a template library that includes DV-specific intake structures and a track record with VAWA-funded programs. It carries HIPAA compliance and SOC 2 Type II certification. Pricing follows a per-user model. Reviews are available on G2’s nonprofit case management category.
CharityTracker is a low-cost, HIPAA-compliant option for intake and service tracking, built for multi-agency collaboration. It works well for smaller organizations with straightforward workflows, though its customization depth is limited for organizations with complex multi-program structures.
Eccovia (ClientTrack) has specific functionality built for victim services programs and has been used in federally funded programs requiring VAWA confidentiality compliance. It’s generally positioned for larger organizations or government-adjacent programs with dedicated administrative support and larger implementation budgets.
The 10 best case management software for nonprofits covers the wider category for organizations comparing options beyond the DV-specific context.
Frequently asked questions
What features should case management software have for domestic violence organizations?
DV case management software should include survivor confidentiality controls, role-based field-level access restrictions, HIPAA compliance where health-related data is collected, customizable intake forms that support DV-specific screening tools, encrypted data storage and transmission, audit logs, and reporting structures that align with VAWA funder requirements. The combination of strong privacy controls and flexible customization is what separates platforms suited for DV work from general-purpose nonprofit tools.
Does case management software need to be HIPAA compliant for DV programs?
HIPAA applies to DV programs that collect health-related information and qualify as covered entities or business associates under federal law. Many DV intake processes collect mental health screening results, medical referral documentation, or substance use history, which can trigger HIPAA applicability. Organizations should assess their status directly using the HHS covered entity definition rather than assuming either way. When in doubt, choosing a platform with HIPAA-compliant configuration options eliminates the compliance gap.
How do DV organizations protect client address and identity in their software?
Role-based field-level visibility restrictions are the primary technical mechanism. This means the platform controls which fields each staff role can view, so a shelter address field is only visible to staff roles that genuinely need it, typically shelter case managers and supervisors rather than volunteers, administrative staff, or employees in other programs. The configuration happens at the platform level, which means it’s consistently enforced rather than dependent on individual staff members following procedures correctly.
Can one platform handle both shelter case management and community advocacy programs?
Yes, if the platform supports multi-program structure with separated access controls. Look for platforms where programs can operate independently within the same system, with distinct intake forms, workflows, and reporting, while authorized staff can view a client’s complete service history across programs. This is the structure that eliminates manual data reconciliation between separate tools and gives program directors a unified view of how clients move through services.
What is VAWA and how does it affect software requirements for DV nonprofits?
VAWA, the Violence Against Women Act, is federal legislation that funds a significant portion of domestic violence, sexual assault, and dating violence services across the country through the Office on Violence Against Women. VAWA grantees must meet specific confidentiality and privacy provisions, including requirements around how survivor information is stored and shared. The act prohibits disclosure of personally identifying information without informed, written, reasonably time-limited consent from survivors. Software that supports VAWA compliance needs to enforce these restrictions through technical controls rather than relying on staff training and policy alone.