LA Homeless Shelters: LAHSA and HUD CoC Compliance Software

LA homeless service providers operate inside the most complex public funding environment for homeless services in the country. The funding sources are federal, state, county, and city, often layered on a single project. The administrator of most of it is LAHSA - the Los Angeles Homeless Services Authority - which acts as the regional Collaborative Applicant for HUD CoC funding and also administers ESG, Measure H sales tax-funded programs, and a range of state and city contracts. Providers that try to manage this environment with general accounting tools and a stack of program-specific spreadsheets eventually drown in reconciliation work or get a finding from a monitoring visit.

This article walks through the four-layer funding stack, the role of HMIS as the operational backbone of HUD CoC compliance, and what a grants management system has to handle for an LA homeless service provider to keep funding through CoC competitive cycles and Measure H renewal.

How HUD CoC funding works in LA

HUD CoC funding under 24 CFR Part 578 supports five program components: Permanent Supportive Housing (PSH), Rapid Re-Housing (RRH), Transitional Housing (TH), Supportive Services Only (SSO), and HMIS. Each component has its own eligibility rules, eligible cost categories, and reporting requirements. PSH and RRH are the dominant components in LA’s portfolio, reflecting the regional emphasis on permanent housing solutions.

Funding flows through the annual HUD CoC Notice of Funding Opportunity (NOFO). LAHSA, as Collaborative Applicant, submits the regional consolidated application that includes individual project applications from CoC-funded providers. HUD scores the regional application against system performance benchmarks (length of time homeless, returns to homelessness, exits to permanent destinations, employment income at exit) and against application quality. Within the regional application, individual project applications are ranked by LAHSA against locally adopted scoring criteria that weight heavily on HMIS data quality and performance.

CoC compliance starts with participant eligibility. The HUD definition of homelessness at 24 CFR 578.3 distinguishes literally homeless, imminently homeless, fleeing or attempting to flee domestic violence, and chronically homeless populations, and each PSH or RRH project has eligibility criteria tied to specific population definitions. Documenting that an enrolled household met the project’s eligibility definition at intake is foundational. The eligibility documentation must survive in the client file for the duration of the participant’s enrollment and for the required record retention period after exit.

Match is the next core obligation. CoC requires 25% match from non-CoC sources, in cash or in-kind, at the project level. Match must be from non-federal or eligible federal sources (most federal sources cannot be match for CoC) and must be documented with source-specific evidence. Match assembled retroactively at the Annual Performance Report stage is the documentation pattern most likely to fail HUD monitoring.

HMIS: the operational backbone

HMIS - the Homeless Management Information System - is the single most consequential operational discipline for an LA homeless service provider. HMIS is governed by HUD Data Standards published by the Office of Special Needs Assistance Programs and is operated regionally by LAHSA. Every HUD-funded project must enter client-level data into HMIS within timeliness windows specified by project type, typically same-day for entries and exits and within three to seven days for service transactions.

Data quality is measured on three dimensions: completeness (the universal data elements that must be present for every client), accuracy (data values that match HMIS standards), and timeliness (entries within the required window). LAHSA publishes provider-level data quality scorecards and uses those scores in CoC application ranking. The Annual Performance Report (APR) that HUD requires for every CoC-funded project is generated from HMIS data, and APR figures determine HUD’s view of whether a project is performing.

The practical implication for a grants management system is that HMIS is the system of record for client-level data and cannot be replaced by an internal CRM. The provider’s internal grants management system handles restricted fund accounting, contract deliverable tracking, match documentation, and the financial system trail. The bridge between the two is the APR and contract-specific reporting that pulls from HMIS but reconciles to GL data.

Measure H, county compliance, and Inspector General attention

Measure H is the LA County quarter-cent sales tax approved by voters in 2017, dedicated to homeless services. It is administered by the LA County Chief Executive Office’s Homeless Initiative and contracted out through LAHSA and other county departments. Measure H funds approximately $355 million annually for prevention, outreach, interim housing, and permanent housing programs.

Measure H is county money. It is not federal, and it does not trigger Uniform Guidance directly. But it does trigger LA County contracting rules, LA County Auditor-Controller oversight, and Office of Inspector General attention - the OIG has audited Measure H program providers multiple times since the measure passed. The Citizens Oversight Advisory Board adds public-facing accountability that has produced critical reports on specific Measure H program areas.

Providers that blend Measure H with federal sources on a single program must maintain source-specific cost allocation that survives a county audit. Allocating program staff time across funding sources, separating eligible costs by source, and producing source-specific financial reporting are not optional. The Uniform Guidance cost principles at 2 CFR 200 Subpart E govern federal sources; LA County contract terms govern Measure H; and the GL has to support both views from the same underlying transactions.

State HCD Homekey and the federal-state stack

California HCD’s Homekey program funds acquisition and rehabilitation of motels, hotels, and other properties for conversion to interim or permanent supportive housing. Project Homekey rounds have used a mix of state General Fund, federal American Rescue Plan, and state Building Homes and Jobs Act funds depending on the year. The federal-source rounds carry Uniform Guidance compliance and a Single Audit obligation; the state-only rounds carry state HCD compliance.

Providers that operate Homekey-acquired sites carry long-term affordability covenants - typically 55 years for Homekey 2 and successor rounds - that extend compliance well beyond initial acquisition and rehabilitation. Tenant income certification, rent restriction enforcement, and physical inspection compliance during the affordability period are operationally similar to LIHTC compliance and require systems that survive staff turnover across decades.

City HHH and the LA-specific overlay

The City of Los Angeles passed Proposition HHH in 2016, a $1.2 billion bond issue for permanent supportive housing development. HHH bond proceeds are administered by the LA Housing Department and add city-specific compliance on top of any federal sources used in HHH-financed projects. Local prevailing wage requirements under California’s prevailing wage statutes apply to HHH-financed construction, separately from any federal Davis-Bacon obligations triggered by HUD funding on the same project.

Coordinated Entry System participation

Coordinated Entry System (CES) participation is required for all HUD CoC-funded providers under 24 CFR 578.7. LAHSA operates CES regionally, and participation means using standardized assessment tools, entering assessments into CES, and accepting referrals through CES for available beds and services. Providers cannot maintain separate waitlists outside CES for HUD-funded resources. The HUD CoC monitoring framework treats CES bypass as a finding, and LAHSA contract terms make CES participation an explicit deliverable.

What a grants management system has to handle

For LA homeless service providers, the practical software requirements are: restricted fund accounting that tracks HUD CoC, ESG, Measure H, state HCD Homekey, and city HHH dollars separately at the project level; integration with HMIS for client-level data, with the system of record clearly defined; match tracking by project with source, date, amount, and eligibility evidence; contract deliverable tracking aligned to LAHSA contract milestones, including CES referral acceptance and outcome reporting; long-term affordability tracking for Homekey-acquired properties; and reporting that supports CoC APR generation, ESG CAPER reporting, Measure H deliverable reporting, and Single Audit preparation under 2 CFR 200 Subpart F.

The providers that have stabilized this stack tend to start with restricted fund accounting and HMIS data quality at the top of the priority list, because both are areas where general nonprofit CRMs and standalone accounting tools fall short. The grant tracking software shortlist for Los Angeles is a reasonable starting point for system selection. The HUD Continuum of Care reporting guide walks through APR generation in detail and is useful both for CoC providers and for board members who want to understand the federal compliance regime their organization operates inside.

Compliance work in LA homeless services is documentation work, and the documentation is unforgiving. HMIS data quality, match documentation, CES participation evidence, and source-specific cost allocation across blended funding are all measured continuously, not just at audit time. The grants management system either supports those disciplines or it does not.