SB 1072 authorizes Napa County, during its current housing element planning period, to meet up to 15% of its existing regional housing need for lower‑income households by committing funds and constructing affordable units inside one or more cities in the county — but only if a detailed agreement, multiple findings, and state and regional reviews are completed. The agreement must identify exact sites, include a construction schedule, and follow public hearing requirements; the receiving city must have adequate site capacity or provide replacement sites and agree not to count the transferred units toward its own regional need.
The bill also ties the county’s credit to on‑the‑ground delivery: the county’s credit cannot exceed 40% of lower‑income units that are constructed and occupied in the county’s unincorporated areas during the same housing element cycle, requires certificate‑of‑occupancy notifications, imposes five‑year monitoring and reporting, and gives the council of governments authority to reassign unbuilt units back to the county. The text contains an anomalous date provision (June 30, 2007) that could affect usability unless addressed by subsequent law.
At a Glance
What It Does
The bill permits Napa County to satisfy up to 15% of its lower‑income RHNA by funding and constructing affordable housing in cities within the county, subject to a signed agreement, public hearings, COG approval (45‑day deemed approval rule), HCD review, and clearly identified sites. It bars receiving cities from counting those units toward their own RHNA and limits county credit to no more than 40% of lower‑income units built and occupied in unincorporated areas during the same cycle.
Who It Affects
Napa County government, cities inside Napa County, the regional council of governments that allocates RHNA, the Department of Housing and Community Development, affordable housing developers and finance partners, and lower‑income households targeted by the projects. Housing element consultants and city planning departments also face new amendment and reporting tasks.
Why It Matters
This creates a narrowly circumscribed intra‑county transfer option that can shift where units are built without changing regional totals — but only if multiple procedural and evidentiary gates are passed. For stakeholders, the bill changes incentives around site inventories, funding choices, and who bears delivery risk for lower‑income housing.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
SB 1072 creates an option for Napa County to address a portion of its lower‑income regional housing need by providing funds to construct affordable units inside one or more cities that sit within the county. The county may use this option only during the housing element planning period identified in Section 65588 and only for up to 15% of its existing share of the regional need for lower‑income households.
The statute makes the county’s ability to claim credit contingent on completing specific procedural steps and on the actual construction and occupancy of units.
Before any transfer can proceed, the county and the receiving city or cities must execute a written agreement after public hearings in both jurisdictions. That agreement must include a construction schedule, street‑address site identification, a statement about whether the sites were previously identified in the receiving city’s housing element, and an accounting of prior transfers during the planning period.
The council of governments that allocated the county’s RHNA must approve the agreement; if the council does not act within 45 days of receiving the agreement, the agreement is automatically deemed approved. Concurrently, HCD will evaluate whether the receiving city or cities substantially comply with the statute’s requirements and provide that evaluation to the parties.The bill requires the parties to make findings supported by substantial evidence: that receiving cities have adequate sites and zoning to accommodate the transferred units in addition to their own RHNA needs, that financing is available if needed, and that the receiving cities’ housing elements are in HCD‑compliant status.
If the county uses sites that were already counted in a city’s housing element, the receiving city must amend its element to identify replacement sites by street address and secure HCD’s finding that the amended element remains compliant. The receiving city must also demonstrate it has met at least 20% of its very low‑income RHNA share in the current or prior cycle.On delivery and oversight, the county only receives credit after units are built and occupied, and that credit cannot exceed 40% of the number of units affordable to lower‑income households constructed and occupied in the county’s unincorporated areas during the same cycle.
The county must notify the council of governments and HCD within 60 days of a certificate of occupancy. Parties must include the transfer in the annual report under Section 65400(b), and for five years after a transfer, reports must track the status of transferred units, implementation of the agreement, and any units constructed.
If units are not built within the five‑year period or required replacement‑site amendments or reporting are not substantially complied with, the council of governments may add the unbuilt units back onto Napa County’s RHNA for the next planning cycle. The bill also contains a dated prohibition (section (e)) that, as written, would bar Napa County from using this mechanism on or after June 30, 2007, unless another statute deleted or extended that date.
The Five Things You Need to Know
The county may meet up to 15% of its existing regional housing need for lower‑income households by funding and constructing units in cities within the county, but only during the current housing element planning period (Section 65588).
Any county‑city agreement must identify site street addresses, include a construction timeline, follow public hearings, and list the number/percentage of lower‑income needs previously transferred (a detailed evidentiary record is required).
The regional council of governments must approve each agreement within 45 days or the agreement is deemed approved; HCD conducts a concurrent review and reports its findings to the parties.
The county’s credit is limited to no more than 40% of the units affordable to lower‑income households that are constructed and occupied in the county’s unincorporated areas during the same housing element cycle; credit is granted only after units are occupied and COs are reported within 60 days.
For five years after a transfer, annual reports must detail implementation and unit status; if required conditions aren’t met or units remain unbuilt, the council of governments will add the unbuilt units back to Napa County’s allocation for the next planning period.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
County authority and overall conditions for intra‑county transfers
Authorizes Napa County to meet up to 15% of its lower‑income RHNA by committing funds and building units in one or more cities during the current housing element planning period, but only after satisfying the enumerated conditions in (a)(1)–(8). This provision sets the high‑level permission and the gatekeeping role of the subsequent, more detailed paragraphs.
Agreement content and public hearing requirement
Requires a written agreement between the county and receiving city or cities executed after public hearings in both jurisdictions; the agreement must include a construction plan and schedule, street‑address site identification, a statement about whether sites were listed in the receiving city’s housing element, and an accounting of prior transfers. Practically, this forces early site selection and a documented delivery plan before any transfer credit is sought.
Regional and state review: COG approval and HCD evaluation
Directs the council of governments that allocated RHNA to review and approve proposed agreements, with a 45‑day deadline after which nonaction equals approval. Simultaneous with the COG review, HCD evaluates substantial compliance and reports to the parties. That dual review creates both a fast‑track approval default and overlapping regional/state oversight aimed at preventing sham transfers.
Counting rules, site adequacy findings, and replacement‑site amendments
Requires receiving cities to agree not to count transferred units toward their RHNA; mandates findings supported by substantial evidence that adequate sites and zoning exist and financing is available; and, if using sites previously identified in a city’s element, obligates the city to amend its element to list replacement sites by street address and secure HCD’s continued compliance finding. This preserves the integrity of city site inventories but forces cities to replenish their identified capacity.
Reporting and five‑year monitoring
Mandates that the county and receiving cities complete the annual report under Section 65400(b) and provide it to HCD, and requires five years of post‑transfer reporting on status, implementation, and units constructed. These requirements create a multi‑year compliance trail and evidence base for reallocation decisions if delivery fails.
Receiving city delivery history threshold
Conditions eligibility on the receiving city having met at least 20% of its very low‑income RHNA share in the current or prior housing element cycle, which is a targeted performance screen intended to ensure receiving cities have a demonstrated record on very low‑income housing.
Credit cap tied to unincorporated construction and occupancy
Caps the county’s credit at 40% of the number of lower‑income units constructed and occupied in the county’s unincorporated areas during the same cycle; the county only receives credit after construction and occupancy, and must notify the COG and HCD within 60 days of a certificate of occupancy. This provision links transfer credit to local delivery metrics and creates a timing condition for recognition.
Reallocation of unbuilt units and anomalous date limitation
Gives the council of governments authority to add unbuilt transferred units back to Napa County’s RHNA for the next planning period if units aren’t constructed within five years or if certain statutory requirements weren’t met. Subdivision (e) contains a prohibition barring Napa County from meeting a percentage of its share on or after June 30, 2007, unless a later statute deleted or extended that date — language that appears outdated and could negate the bill’s practical effect unless reconciled.
This bill is one of many.
Codify tracks hundreds of bills on Housing across all five countries.
Explore Housing in Codify Search →Who Benefits and Who Bears the Cost
Every bill creates winners and losers. Here's who stands to gain and who bears the cost.
Who Benefits
- Napa County government — gains a narrowly defined tool to meet part of its lower‑income RHNA by financing construction in cities rather than building solely in unincorporated areas, potentially easing local siting and political constraints.
- Receiving cities that accept funding — receive capital for affordable projects and may attract developers or nonprofits, enabling new lower‑income units without necessarily using city general funds.
- Affordable housing developers and nonprofit builders — benefit from an explicit funding source tied to identified sites and schedules, which can improve project feasibility and underwriting.
- Lower‑income households in receiving cities — stand to gain additional rental or ownership opportunities if projects move forward, particularly where city site capacity and services already exist.
- Housing element consultants and planning firms — see new demand for compliance work (site inventory adjustments, element amendments, and the detailed agreement documentation).
Who Bears the Cost
- Receiving cities — must amend housing elements to provide replacement sites (if sites were previously counted), accept strict reporting obligations, and agree not to count transferred units toward their RHNA, which can reduce flexibility in meeting local goals.
- Napa County taxpayers and treasury — bear direct fiscal responsibility for committing funds to construction; the county also bears delivery risk if projects fail and reallocation occurs.
- Regional council of governments — takes on administrative review responsibilities, a 45‑day clock, and potential political pressure over deemed approvals and reallocation decisions.
- Department of Housing and Community Development and local planning departments — face increased review and monitoring workload to evaluate substantial compliance, review amendments, and process five‑year status reports.
- Developers and sponsors — must meet stricter upfront documentation, site identification, and post‑occupancy reporting, increasing predevelopment costs and compliance burdens.
Key Issues
The Core Tension
The central dilemma is between providing counties with a pragmatic tool to finance and deliver lower‑income housing where it can actually be built, and preserving the integrity and accountability of local housing element inventories and regional allocations — the bill tries to enable flexibility while imposing documentary and delivery safeguards, but those safeguards can either block practical transfers or be gamed if not robustly enforced.
SB 1072 mixes flexibility with layered safeguards, and those layers create both implementation friction and potential loopholes. Requiring street‑level site addresses and replacement site amendments protects housing element inventories but could be hard for cities that lack spare buildable parcels; identifying replacement sites by address may push cities to list parcels that are not realistically developable, increasing the risk of future noncompliance and reallocation.
The bill’s substantial‑evidence findings and HCD review introduce meaningful legal thresholds, but they also invite administrative disputes over what constitutes adequate sites or available financing.
The county credit cap — pegging credit to units constructed and occupied in unincorporated areas during the same cycle and limiting credit to 40% of that number — creates a circular dependency that could frustrate counties that lack capacity to build in unincorporated areas. The 45‑day deemed approval rule for COGs speeds decisions but risks rubber‑stamping complex agreements if regional staff are underresourced.
Finally, the text includes an anomalous dated bar (June 30, 2007) that, as drafted, would preclude Napa County from using the mechanism unless another statute already extended that date; that drafting glitch could render the entire transfer option unusable unless corrected, raising legal and operational uncertainty.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.