Housing-element compliance and builder's-remedy exposure: how to check any city

Builder's-remedy exposure starts with one fact you cannot memorize: whether the jurisdiction's housing element is in substantial compliance today. HCD tracks every city and county's status, and it moves weekly — adoptions, certifications, findings of noncompliance. So this page is a curated snapshot as of July 2026 that teaches the check rather than freezing a list, anchored to the statutory backbone: Housing Element Law and the Housing Accountability Act.

The stakes are asymmetric. A noncompliant element strips the city of its power to deny qualifying affordable projects for zoning or general-plan inconsistency — the builder's remedy — and feeds a chain of other consequences, from streamlining thresholds to state enforcement referrals. HCD's Housing Accountability Act advisory is the agency's own map of that terrain and the best companion to the status check below.

The check is mechanical. HCD publishes a statewide housing-element review table showing each jurisdiction's current status alongside the review and findings letters behind it. Pull the row, save a copy, and record the date — vintage disputes are won with contemporaneous evidence of what the status was on the day the application (or the SB 330 preliminary application) went in. For judging whether a "compliant" element is actually load-bearing, HCD's sites-inventory guidebook shows how the underlying site inventories are supposed to be built and tested.

The remedy itself comes from the HAA: while the element is out of substantial compliance, zoning and general-plan inconsistency come off the table as denial grounds for projects meeting the affordability gate — historically 20% lower-income or 100% moderate-income. AB 1893 (2024) recalibrated the remedy for newer applications: a lower affordability gate (13% lower-income among the options), paired with site screens and density parameters that traded some of the remedy's "anything goes" reputation for enforceability and cleaner processing. Which regime governs is a vintage question — an SB 330 preliminary application freezes the applicable rules as of filing, which is why the remedy playbook always starts with that filing.

• Underwriting watch-outs:
• The remedy is a shield against inconsistency denials — not a CEQA bypass and not immunity from objective health-and-safety standards.
• Cities contest status after the fact; your dated copy of HCD's table and letters is the counter-evidence.
• The pre- and post-AB 1893 regimes attach by application timing — confirm with counsel which set governs before choosing the affordability mix.
• Compliance can be restored mid-fight; the filing-date snapshot is what preserves the remedy for a pipeline project.

The library keeps two primary-source exhibits of how HCD polices this in practice: the December 2024 notice of violation to Beverly Hills over its handling of builder's-remedy projects, and the June 2023 letter to La Cañada Flintridge finding Housing Accountability Act violations in a builder's-remedy denial. Read them for the agency's actual reasoning — they preview the letters a stonewalled project can generate, and cities know it.

The other date to check is the rezone program. Elements that rely on rezoning to deliver adequate sites must complete those rezones on statutory schedules, and missed deadlines carry their own consequences — including by-right processing obligations on identified sites for qualifying affordable projects and compliance downgrades that can reopen the remedy. When you pull the status row, pull the element's rezone program dates too and compare them to the calendar.

• Verification watch-outs:
• NOVs are jurisdiction-specific, but the legal theories travel — cite them as persuasive framing, not binding precedent.
• The status table alone won't reveal a missed rezone deadline; the dates live in the element's own program commitments.
• Status can flip while an application is in process — calendar a re-check at every project milestone, and archive each pull.