Unlocked covers what changes when housing assistance programs are built on a consistent operational standard — not what communities intend, but what the work actually looks like once the structure is in place. Each piece describes a real implementation: initial condition, what was broken, what changed, and how the work shifted as a result.

For our first Unlocked post for communities using Journey, we’re highlighting the incredible feat of HOM, Inc.’s work taking on one of the largest, most complex systems in the country— Los Angeles. You can read HOM’s full case study on their website, here.

What the Program Actually Looked Like

LAHSA’s TLS program means thousands of active leases, ongoing step-down subsidy management, landlord payment execution, and participant subsidy redeterminations — distributed across service provider organizations with varying administrative capacity and few shared operational standards.

Providers weren’t doing this wrong. They were doing it the only way the prior model allowed: independently. Each organization owned its piece of the program — landlord relationships, payment processing, compliance tracking. The result was a program that functioned differently depending on which provider a household was enrolled with, and gave LAHSA no reliable way to see across all of it.

What Was Broken Structurally

The inconsistency wasn’t a training problem or a staffing problem. It was an architectural one.

When rental assistance administration spreads across individual providers without a shared operational layer, compliance obligations are distributed too. Every payment, every subsidy adjustment, every step-down calculation happened in a separate workflow. LAHSA’s ability to reconcile, audit, or assess program performance depended on collecting and comparing data from organizations that weren’t generating it in compatible formats.

With 2,500 households in scope for the centralized launch alone, the scale made informal coordination untenable. The program needed a single operational standard — and that standard had to live somewhere other than a policy document.

The Structural Change

LAHSA procured HOM, Inc., as a centralized fiscal agent for the TLS program for opt-in providers. The model shifted payment execution, landlord management, and compliance workflows from individual providers to a centralized administrative function. But the model only works if the technology running it can carry the operational complexity of a multi-provider, multi-program rental assistance system.

HOM built the centralized operation on Padmission Journey. Brian Petersen, COO and President at HOM, Inc., reflected on the implementation after the dust settled:

“Journey enabled us to respond to the LAHSA RFP with confidence because it provides a proven, repeatable framework for centralized rental assistance administration. We were able to commit to an aggressive implementation timeline because Journey already embeds standardized, compliant workflows.”

The pre-launch work was substantial. The team reviewed, normalized, and migrated tenancy and payment data from each participating service provider — households, properties, units, leases, rental assistance amounts — into Journey in a consistent format. HOM designed and tested a two-way integration with LAHSA’s HMIS. HOM assigned accounting codes and expense categories across the program, collected and configured landlord payment preferences, and trained and validated support team workflows against the new operational model.

This is what technology-enabled system design looks like in practice: not a software deployment in isolation, but the deliberate encoding of an operational standard into a technology layer that every role in the new model runs on. The policy didn’t change how providers operated. The system did.

The July 1st launch — a hard deadline tied to the LAHSA fiscal year — required all of this to happen within 90 days of contract execution. Senior VP of Housing for HOM, Carlos Gonzalez, knew it was ambitious and that keeping relationships with property owners and managers central was key.

“Journey helped us execute on our commitments to landlords by receiving payments faster and with clearer communication early in the rollout. That reliability made it easier to bring landlords into a centralized model and maintain their trust during the transition.”

How Work Changed Across Roles

For LAHSA’s finance team: Program-level financial visibility, previously unavailable, became accessible in a single record. Payment status, subsidy amounts, participant contributions, and reconciliation data — all of it previously requiring coordination across multiple provider organizations — now lived in one place. Audit readiness shifted from a periodic, labor-intensive exercise to a near-continuous operational condition.

For service providers: The shift removed payment processing and landlord management from providers’ administrative workload. Providers serving TLS households had always carried both case management and fiscal responsibilities. The centralized model separated those functions. Providers no longer managed rent payments; they managed participants. Gonzalez — who has worked locally as a service provider for decades — notes:

“Journey helped us bring consistency to provider workflows without disrupting day-to-day service delivery. That stability was critical in a system as large and complex as Los Angeles, where providers needed clarity without losing momentum.”

Sarah Hoppmeyer, from Union Station Homeless Services, one of the TLS service providers, described the shift directly:

“We’re best when we focus on our client needs. HOM’s solution allows us more time to provide better service to our clients and to our landlord partners.”

For landlords: Payment execution moved from provider-by-provider timelines to a single centralized process. ACH participation increased from under 20% before launch to over 60% within the first three months. More predictable payment delivery changed the landlord relationship — and early feedback indicated a willingness to increase property participation in the program.

Thomas Harrison, Associate Director of Leasing at SOLA Impact, described what changed from the landlord side:

“The difference with HOM, Inc has been night and day from how TLS (rapid rehousing) subsidy operations were previously. The process is smoother, communication is stronger, and payments are timely and transparent. I truly believe HOM, Inc. will be the game-changer for third-party centralized subsidies in Los Angeles. This is a monumental improvement that deserves recognition.”

For HOM’s administrative team: Journey gave HOM’s LA office a single system for managing the full operational complexity of the TLS program: payment execution, subsidy adjustments, step-down management, new move-ins, unit changes, and program expansion — what would otherwise require coordination across disconnected tools and manual data management, held in one place.

What This Demonstrates

The LAHSA TLS centralization worked because HOM and LAHSA designed the operational model and the technology together, not in sequence.

Most efforts to standardize rental assistance across a provider network stall at the same point: the policy exists, the intent is clear, but there’s no shared system that translates the standard into daily workflows. Data stays inconsistent. Compliance remains distributed. Administrative burden shifts without actually reducing.

What HOM and LAHSA built demonstrates what centralized rental assistance administration throughout a Continuum of Care actually requires. Data in one place. Workflows that are standard by design, not by instruction. A technology layer built specifically for how rental assistance programs operate — not adapted from something built for a different purpose.

Padmission built Journey for this kind of work. The LAHSA TLS implementation is its clearest demonstration at the largest scale.