AB 920 adds Government Code Section 65940.3 to require cities and counties meeting a 150,000-population threshold to provide a centralized application portal on their websites for housing development projects. The portal must collect the materials an applicant needs to submit and allow tracking of application status; it need not show the status of permits or inspections handled by other agencies.
Counties’ population is measured by their unincorporated population for the threshold.
The bill sets a January 1, 2028 deadline with a narrowly defined route to delay implementation to January 1, 2030 if the local legislative body both finds that meeting the earlier deadline would substantially increase permitting fees and initiates procurement for a portal by January 1, 2028. The statute applies to all cities, including charter cities, and declares no state reimbursement is required because localities may fund the requirement with fees.
At a Glance
What It Does
Requires cities and counties with at least 150,000 people to operate a centralized online application portal for housing development projects by Jan 1, 2028, with a conditional extension to Jan 1, 2030 if a local finding and procurement initiation occur. Portals must collect application materials and provide status tracking but are not required to report on third‑party permits or inspections.
Who It Affects
Directly affects California cities and counties that meet the population threshold (counties measured by unincorporated population), planning departments, applicants and their consultants, and vendors who build municipal permitting systems. Charter cities are included under the Legislature’s statewide‑concern finding.
Why It Matters
Standardizing online intake and adding status tracking aims to reduce administrative friction and opacity in housing permitting, potentially speeding project reviews. It also shifts upfront technical and procurement costs to local governments and creates a new market for e‑permitting vendors, while leaving interagency coordination optional.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
AB 920 imposes a concrete online intake requirement on larger California local governments. If a city or county meets the 150,000‑person threshold, it must post a centralized application portal on its website to receive housing project submissions; for counties the count is based only on people living in unincorporated areas.
The statute defines a portal as the municipal web or software system used to gather the documents and data the city or county needs to consider a housing development project.
The law sets a firm date of January 1, 2028, for compliance but builds in a narrowly circumscribed two‑year extension. To qualify for the later deadline (January 1, 2030) the local legislative body must, on or before January 1, 2028, both enter a written finding that meeting the 2028 deadline would substantially increase permitting fees and begin a procurement process to acquire a portal.
The twin requirements aim to prevent indefinite delay while recognizing some jurisdictions need time and resources to implement a system.Operationally, the portal must allow applicants to track the status of their submissions. The statute explicitly says a city or county does not have to provide status for any permit or inspection that is required by a different local agency, a state agency, or a utility provider — so the portal’s tracking obligation is limited to the approving jurisdiction’s own workflows.
The bill ties the term “housing development project” to the existing definition in Government Code Section 65905.5(b)(3), anchoring scope to an established statutory meaning.Finally, the Legislature declares the provision a matter of statewide concern so it applies to charter cities, and it states that no state reimbursement is required because local agencies can fund the requirement through service charges, fees, or assessments. The statute therefore places the financial and operational responsibility at the local level rather than creating a new state funding stream.
The Five Things You Need to Know
The bill requires cities and counties with 150,000+ population (counties measured by unincorporated population) to provide a centralized housing application portal on their website.
Deadline is Jan 1, 2028, but a city or county can delay to Jan 1, 2030 if, by Jan 1, 2028, its legislative body issues a written finding that the 2028 deadline would substantially raise permitting fees and initiates procurement for a portal.
The portal must collect the documents and information necessary for the jurisdiction to consider a housing development project and must allow applicants to track application status.
Cities and counties are not required to display or track the status of any permit or inspection controlled by another local agency, a state agency, or a utility provider.
The statute applies to charter cities under the Legislature’s statewide‑concern finding and expressly provides no state reimbursement, placing funding responsibility on local fees or charges.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Mandate for centralized portals and threshold
This subsection creates the basic duty: any city or county at or above the 150,000‑person threshold must make a centralized application portal available on its website. Practically, that obligates larger jurisdictions to establish a single online intake point for housing projects rather than relying on disparate department pages or paper filings. The 150,000 cutoff focuses the rule on larger urban jurisdictions that process more projects and have greater technical capacity, rather than imposing the requirement on small municipalities.
County population measured by unincorporated population
For counties the statute measures population by the number of people living in unincorporated areas rather than the countywide total. That narrows which counties must comply: a county with large incorporated cities may fall below the threshold for its unincorporated area and therefore avoid the requirement. This detail matters for county administrators planning whether to invest in a portal.
Conditional extension to Jan 1, 2030
Subdivision (b) provides a limited path to delay implementation to Jan 1, 2030. To use it the legislative body must (1) make a written finding that meeting the 2028 deadline would substantially increase permitting fees and (2) initiate a procurement process for a portal, and both actions must happen on or before Jan 1, 2028. The combination of a fiscal finding and procurement initiation signals to the Legislature that the locality has both fiscal concerns and a concrete plan; it also prevents jurisdictions from claiming delay without starting acquisition or development work.
Tracking requirement with scope limits
Subdivision (c) requires the portal to allow tracking of an application’s status; subdivision (d) narrows that duty by saying a jurisdiction does not have to provide status for any permit or inspection required by another local agency, a state agency, or a utility. Together those clauses create a user‑facing tracking function for the city/county’s own processes but stop short of compelling technical integration with outside agencies — a practical concession that limits interagency coordination obligations.
Definitions and cross‑reference to housing project definition
This subsection defines “centralized application portal” as the website or software used to collect materials necessary for the city or county to consider a housing development project, and it adopts the existing statutory definition of “housing development project” from Gov. Code §65905.5(b)(3). By anchoring the scope to an existing definition, the provision avoids creating a new statutory category but also imports any ambiguities or limits contained in that earlier definition.
Statewide‑concern finding and reimbursement rule
Section 2 declares the portal requirement a matter of statewide concern so the rule applies to charter cities. Section 3 states that no state reimbursement is required because localities can levy fees or charges to fund the mandate. Those two short provisions resolve two predictable legal and fiscal questions up front: the Legislature asserts authority to bind charter cities and shifts funding responsibility to local governments rather than the state budget.
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
- Housing developers and applicants — gain a single online intake point and status visibility, reducing uncertainty from fragmented submission channels and helping teams track outstanding materials and deadlines.
- Local planning and permitting staff — benefit from standardized submissions and centralized records, which can reduce time spent chasing missing documents and improve internal workflow management.
- Third‑party consultants and permit expeditors — receive a clearer, machine‑readable gateway for filings that can reduce administrative back‑and‑forth and make project scheduling more predictable.
- E‑permitting vendors and system integrators — see new procurement opportunities from multiple larger jurisdictions needing portals, integrations, and ongoing hosting or support services.
Who Bears the Cost
- Cities and counties with 150,000+ populations — must fund, procure, implement, and operate portals (or accelerate existing programs), including upfront IT costs, project management, staff training, and ongoing maintenance.
- Local taxpayers and applicants — the statute permits funding via increased permitting fees or service charges, so users and residents may bear higher costs to cover development and operational expenses.
- Local procurement and IT teams — face added workload and compressed timelines if a jurisdiction seeks the 2028 deadline or must demonstrate procurement initiation to qualify for the delay, with attendant contract management and oversight responsibilities.
Key Issues
The Core Tension
The bill balances two legitimate goals — speeding and clarifying housing permit intake for applicants versus avoiding costly, rapid IT buildouts for local governments — but it does not fully reconcile them: standardization helps applicants and housing goals, while decentralized funding and limited integration place financial and operational burdens squarely on localities, risking uneven implementation and continued fragmentation.
The statute resolves a transparency problem by requiring a portal, but it sidesteps several practical implementation issues. It does not require technical integration with other permitting agencies or utilities, so applicants may still confront a siloed experience across city departments and outside agencies; the portal’s tracking function only covers the jurisdiction’s own approvals.
That design choice minimizes mandatory cross‑agency IT work but preserves a fragmented user journey unless jurisdictions voluntarily coordinate.
The bill’s limited delay mechanism reduces the risk of open‑ended postponements, but the written‑finding requirement creates a predictable avenue for delays that may be defensible on fiscal grounds. Because the statute allows funding through fees, jurisdictions can justify slower timelines by pointing to the need to avoid sudden fee increases — yet the law contains no guidance on how to measure “substantial increase” or how procurement initiation must proceed, opening room for disputes and inconsistent application across localities.
Finally, the measure is silent on enforcement, data governance, accessibility standards, and cybersecurity expectations for portals. Those operational details will determine whether portals meaningfully improve permitting outcomes or become another bureaucratic layer; absent statewide technical standards, results will likely vary by jurisdiction and vendor capacity.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.