HUD Comparable Databases Explained: CoC APR and ESG CAPER for Victim Service Providers
Why domestic violence and sexual assault programs can't use HMIS, what a HUD comparable database must do, and how to produce a CoC APR or ESG CAPER that passes in Sage.
Key takeaways
- Victim service providers are prohibited from entering survivors' identifying information into HMIS, so HUD-funded DV/SA programs record client data in a comparable database instead.
- A comparable database must collect data to HUD's HMIS Data Standards and produce the same aggregate reports, such as the CoC APR and ESG CAPER, as HMIS.
- APR and CAPER reports are generated as a set of CSV files and uploaded to HUD's Sage HMIS Reporting Repository, which validates them before submission.
- Most Sage errors trace back to missing entry/exit data, project setup (inventory, tracking method) and households that were never linked correctly.
On this page
A comparable database is how domestic violence, sexual assault, dating violence and stalking programs meet HUD data requirements without putting survivors at risk. If your agency receives Continuum of Care (CoC) or Emergency Solutions Grants (ESG) funding, it is how you report. The two main reports are the CoC Annual Performance Report (APR) and the ESG Consolidated Annual Performance and Evaluation Report (CAPER).
This guide explains the rule, what the database must do, and how to get a report through Sage cleanly.
Why victim service providers can't use HMIS
Most homeless service providers in a community enter client data into a shared Homeless Management Information System (HMIS). Victim service providers are different. Federal confidentiality protections in the Violence Against Women Act prohibit them from disclosing survivors' personally identifying information, and that includes entering it into a shared HMIS that other agencies can see.
So HUD requires these providers to use a comparable database: a separate system that collects the same data to the same standards, while keeping survivor records under the agency's control.
What a comparable database must do
At a minimum, a comparable database should:
- Collect data to HUD's HMIS Data Standards, including universal data elements and the program-specific elements for each funded project type.
- Hold project descriptor data, such as project type, tracking method, CoC code, funding sources, and bed and unit inventory.
- Track enrollments as stays. That means entry, annual assessments and exit with destination, for each household member, with correct relationship-to-head-of-household.
- For night-by-night emergency shelters, record bed nights, because that is how length of stay is calculated.
- Produce unduplicated aggregate reports in HUD's CSV formats, including the APR and CAPER packages.
- Protect the data: role-based access, audit trails and encryption, with the agency (not the vendor) owning the records.
How APR and CAPER reporting works
- Set up the project correctly. Most "impossible" errors are project setup errors: wrong project type, missing inventory, or a tracking method that doesn't match how you record stays.
- Collect complete entry and exit data. Every adult and head of household needs the required elements at entry. Every exit needs an exit date and destination.
- Generate the report. The comparable database produces the APR or CAPER as a set of CSV files for the reporting period.
- Upload to Sage. HUD's Sage HMIS Reporting Repository validates the files and flags errors and warnings.
- Fix at the source and regenerate. Correct the client or project records, then rerun the export. Editing CSVs by hand creates mismatches next year.
The errors we see most often
- Missing data in required fields. "Client doesn't know" and "client prefers not to answer" are valid responses. A blank field is not.
- Households not linked. Children entered as separate heads of household skew every household-level table.
- Open stays that ended months ago. These inflate length of stay and leave exit destinations unknown.
- Inventory that doesn't match occupancy. Bed utilization above 100% or near 0% usually means an inventory or tracking-method problem.
A data-completeness worklist helps: a running list of the specific clients and fields that are missing, so staff can fix them weekly instead of at report time.
How NECX VS360 handles HUD reporting
VS360 works as a comparable database for victim service providers:
- HUD project setup in the agency profile: project type, CoC, funders, bed and unit inventory, and coordinated entry participation.
- Per-stay HUD data captured at shelter check-in, annual assessment and check-out (including exit destination), plus a nightly roll call for bed nights.
- Missing HUD Data worklist so gaps are fixed during the year.
- HMIS CSV export and a built-in Sage validator, so the CoC APR and ESG CAPER package is checked before you upload. HUD does not certify or endorse software; VS360's exports are validated against Sage.
Running shelters too? See how a live bed board replaces the shelter spreadsheet. If you also report to VOCA, read our VOCA PMT reporting guide.
Further reading
- What is HMIS? The Homeless Management Information System, explained
- HUD Exchange — HMIS: HMIS Data Standards, CSV specifications and Sage guidance.
- Office on Violence Against Women: VAWA confidentiality resources.
Frequently asked questions
Why can't domestic violence programs use HMIS?
The Violence Against Women Act's confidentiality provisions bar victim service providers from disclosing personally identifying information about survivors, which includes entering it into a shared HMIS. HUD therefore requires these providers to use a comparable database.
What makes a database 'comparable'?
It must be a relational database that meets HUD's HMIS Data Standards, keeps client data under the provider's control, and can generate unduplicated aggregate reports — including the CoC APR and ESG CAPER CSV packages — in HUD's required formats.
Does HUD certify comparable database software?
No. HUD does not certify or endorse software. Providers should confirm a product meets the current HMIS Data Standards and that its reports validate in Sage.
What is Sage?
Sage is HUD's HMIS Reporting Repository. Recipients upload the APR or CAPER CSV files there, Sage checks them for errors, and the recipient then completes and submits the report.
Do comparable databases share data with the Continuum of Care?
Only aggregate, de-identified data. The CoC receives report-level numbers, never survivor records.
Written by
Victim services & grant compliance specialists
The NECX team builds VS360 alongside victim service agencies, DV/SA programs, shelters and hotlines. We write about the reporting, confidentiality and operational problems we help agencies solve every week.
Keep reading
What Is HMIS? The Homeless Management Information System, Explained
A plain-language guide to HMIS: who has to use it, what data goes in, which HUD reports come out, and why domestic violence programs use a comparable database instead.
VOCA Grants Explained: How Victim Assistance Funding Works and What It Requires
Where VOCA money comes from, how it reaches local programs, what it pays for, and the reporting and confidentiality rules every VOCA subrecipient has to meet.
VOCA PMT Reporting: A Practical Quarterly Guide for Victim Service Providers
What VOCA subgrantees report in OVC's Performance Measurement Tool each quarter, the counting mistakes that trigger corrections, and a workflow that keeps the numbers ready before the deadline.