Ali Gaylord is the senior vice president for Affirmed Housing’s Northern California region. She can be reached at Ali@affirmedhousing.com.

Across California, efforts to find permanent homes for unhoused residents are often delayed or stopped altogether — not because of financing gaps or flawed policy, but because of local opposition. For many cities, community pushback becomes the greatest project risk. But it doesn’t have to be.

In practice, the difference between a stalled project and a successful one often comes down to a small set of repeatable risk reduction strategies that cities deploy before and during the approval process. The goal is not to eliminate opposition altogether (that would be unrealistic) but to manage it.

Start early and reframe the site

Many proposed homeless housing sites are already familiar to neighbors, particularly when they are vacant, underutilized, or already used for shelter by unhoused individuals. These sites can feel like liabilities: costly to maintain, disruptive to the surrounding area, and often perceived as unsafe.

Cities can productively reframe the conversation by acknowledging those realities and explaining why professionally managed affordable housing — particularly housing that serves formerly homeless residents — is a better long-term use than leaving a site vacant or blighted.

This framing is especially important on city‑owned land. Public agencies are often spending scarce resources maintaining vacant sites while receiving scant benefits. Early engagement gives cities the opportunity to explain how redevelopment can stabilize the area and bring a higher level of care and oversight to a site that currently lacks it.

Invite input on practical design elements

Sharing a clear vision for development and creating opportunities for meaningful community input is another critical step. While cities cannot redesign projects by committee, residents are often eager to engage on practical elements, such as site access, building orientation, landscaping, lighting, and entry and exit location points. Inviting people into these conversations early — before decisions are finalized — builds trust and often leads to better project outcomes.

Clarify operations and set expectations

Operational clarity is just as important as design. Many community concerns stem from uncertainty about how a building will function and who will be accountable if issues arise. Cities and developers can reduce anxiety by being explicit about management practices, staffing, and on‑site services and clearly distinguishing permanent supportive housing from shelters, interim housing, or other temporary models.

Permanent supportive housing is often misunderstood. Unlike shelters or temporary housing, it is permanent, professionally managed housing. Residents sign leases, pay rent, and must comply with lease terms and house rules. On-site supportive services help residents maintain housing stability. Being clear about this distinction is essential to building credibility with concerned community members.

Make accountability visible

Accountability must also be concrete. Committing to identifiable points of contact sends a strong signal that the city and its partners take neighborhood concerns seriously. During construction, a designated contact from the general contractor can address issues like noise, parking, or construction logistics. Once the building is operational, a named property management representative provides neighbors with a clear pathway to raise concerns and get timely responses.

The message is not that problems will never arise, but that there is a system in place to address them quickly.

Select experienced and engaged development partners

Equally important, but often overlooked, is the role of the affordable housing developer itself. Neighbors are more likely to trust a project when they believe the team behind it is experienced, competent, and engaged. Developers with a strong track record of delivering and operating affordable and supportive housing bring institutional knowledge that cities cannot easily replicate, and that experience matters to the community.

Cities can and should use their leverage to select developer partners with demonstrated success, strong property management capacity, and a willingness to engage directly with community members. A developer who is visible, accessible, and prepared to answer difficult questions can play a critical role in reducing opposition and building trust. The developer is not just delivering housing; it is an extension of the city’s commitment to responsible implementation.

Bring in trusted community voices

Service providers, property managers, and public safety partners often have established relationships within the community and can address concerns in ways that city staff or developers alone cannot. In one particularly effective example, a city invited members of the police department’s homeless response unit to attend a community open house for a proposed project. Neighbors concerned about safety heard from officers who were familiar with unhoused residents and explained why stable housing leads to better outcomes for homeless residents, first responders, and the broader community. As trusted messengers, their presence significantly reduced anxiety and reframed the discussion.

Be clear about how success will be measured

Finally, cities should be transparent about how they will measure success and what steps they will take if issues arise. Trust is built not by promising perfection, but by clearly articulating expectations, performance standards, and escalation processes. This clarity reinforces that homeless housing is not an experiment, but a proven model with well-established management and oversight practices.

Community opposition to homeless housing will never disappear entirely. But cities that engage early, select experienced partners, leverage design and operations thoughtfully, and communicate accountability clearly will find that opposition is far more manageable than it may initially appear. These tools, when used intentionally, can mean the difference between a project that stalls and one that gets built.