This law declares that when a daycare center operates within or on the same grounds as multifamily housing, the daycare is a residential use and must be treated as a “use by right” under local land‑use rules. Local governments may not require discretionary land‑use approvals that would constitute a “project” under California’s environmental laws, and they cannot impose a charge, tax, or fee tied to a business license or permit for the privilege of operating such a daycare.
At the same time, the statute preserves parity: cities and counties can apply building‑height, setback, lot‑dimension, health, safety, and nuisance ordinances so long as they apply identically to the colocated multifamily housing. The bill also clarifies that the daycare still must meet state building, fire, and licensing requirements, and it expressly applies to all cities, including charter cities.
At a Glance
What It Does
It reclassifies daycare centers that are colocated with multifamily housing as residential uses that are eligible for “use by right” status, forbids local business‑license or permit fees tied to operating those daycares, and narrows the scope of discretionary land‑use reviews that localities can impose. The statute preserves local application of technical safety, building, and nuisance rules so long as those rules are identical to those applied to the housing.
Who It Affects
Multifamily developers and property owners who want to provide or host onsite childcare, daycare operators colocated on apartment or condominium grounds, and local planning, building, and revenue departments responsible for permitting and fee collection. Public‑health and fire authorities remain involved because state safety and licensing laws continue to apply.
Why It Matters
The measure eliminates common local barriers — discretionary permits and license fees — that slow or add cost to integrated housing‑childcare projects, creating a clearer path for colocated childcare. It also establishes a statewide default rule that reduces local variability, which matters for project feasibility and for cities' fee revenue and land‑use control.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The statute creates a simple legal baseline: if a daycare center operates within or on the same grounds as residential housing with five or more units, local governments must treat that daycare as a residential use and allow it as a matter of right rather than as a discretionary project. In practice, that blocks local governments from insisting on conditional use permits, planned unit development permits, or other discretionary approvals that would qualify as a “project” under California’s environmental review statutes.
The law leaves room for design review, but says design review cannot be treated as a project triggering environmental review.
Localities cannot levy a charge, tax, or fee tied to a business license, an equivalent instrument, or a permit for the privilege of operating a colocated daycare. That language prohibits the common practice of imposing municipal license fees or permit charges specifically because an operator runs a daycare; however, the text does not list every kind of local fee, so questions will arise about other revenue mechanisms such as development impact fees or utility connection charges.The bill protects the application of technical health, safety, and building rules: a city may limit building height, setbacks, or lot dimensions for a daycare only if those limits are identical to those applied to the multifamily housing on the same site.
Likewise, local ordinances on building standards, environmental impact, and nuisance abatement can apply to a daycare but cannot treat the daycare differently than the colocated housing. Separately, the law does not change state obligations: the facility must comply with California Building Standards Code, the California Fire Code, and state licensing requirements for day care centers.Two definitional points drive the statute’s scope.
First, “multifamily housing” is defined as residential housing with five or more units, which excludes smaller apartment houses and many accessory dwelling situations. Second, “colocated” covers facilities operating within or on the same grounds as the housing, which captures on‑site childcare rooms, dedicated buildings on the same parcel, and some courtyard or campus arrangements.
The Legislature also framed this as a matter of statewide concern so that the rule binds all cities, including charter cities, limiting arguments that local home‑rule authority can defeat the statute.
The Five Things You Need to Know
The law defines multifamily housing as residential housing with five units or more and defines colocated as operating within, or on the same grounds as, that housing.
Local jurisdictions may not impose a charge, tax, or fee tied to a business license, equivalent instrument, or permit for the privilege of operating a daycare colocated with multifamily housing.
Local governments may not require conditional use permits, planned unit development permits, or other discretionary approvals that would make the daycare a “project” under California’s environmental review statutes; design review may be required but must not trigger CEQA.
Cities and counties may enforce height, setback, lot‑dimension, health, safety, and environmental ordinances against a colocated daycare only if those rules are identical to what the multifamily housing on the same site faces.
The statute preserves compliance obligations under the California Building Standards Code, the California Fire Code, and state daycare licensing laws, and it expressly applies to charter cities via a legislative finding of statewide concern.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Daycare as residential use and use by right
Subsection (a) converts the zoning classification: a daycare colocated with qualifying multifamily housing counts as a residential use and must be permitted as a ‘use by right.’ Practically, this prevents local governments from treating these daycares as commercial land‑uses requiring discretionary approvals that delay projects or invite litigation.
Ban on local business‑license and permit fees
Subsection (b) prohibits local charges, taxes, or fees tied to a business license, equivalent instrument, or permit for the privilege of operating the colocated daycare. That language directly targets municipal business license regimes and permit‑based privilege fees that are often levied on child‑care operators. It does not, however, enumerate or define all other possible local fees — an ambiguity likely to surface as local finance offices evaluate revenue impacts.
Parity for zoning and nuisance rules
These clauses allow localities to retain standard zoning controls — height, setback, lot‑dimension — and to enact health, safety, and environmental ordinances or nuisance abatement, but only if the ordinances, as applied to the daycare, are identical to those applied to the colocated multifamily housing. The practical intent is parity rather than exemption: a city can still regulate form and safety, but it cannot single out the daycare for tougher rules than the housing beside it.
State standards and licensing remain mandatory
Subsections (d) and (e) make clear that the state Building Standards Code, the Fire Code, and state licensing requirements continue to bind daycare operators. The statute therefore lowers local land‑use barriers without altering technical safety regimes that often involve separate building, fire, and social‑services inspections.
Key definitions and how 'use by right' is defined
Subsection (f) supplies operational definitions: the daycare term refers back to an existing definition in Section 1596.76; multifamily housing is set at five or more units; colocated covers on‑site or same‑grounds operations. Importantly, the statute defines ‘use by right’ to exclude discretionary approvals that would be a ‘project’ under PRC Division 13, while allowing design review so long as the design review itself does not qualify as a CEQA project.
Statewide applicability and preemption of local home‑rule
Subsection (g) contains a legislative finding that the subject is a matter of statewide concern, making the rule applicable to all cities, including charter cities. That finding limits home‑rule challenges and signals the Legislature’s intent to preempt local variations that would otherwise frustrate the statute’s uniform application.
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
- Residents of multifamily developments that include childcare: they gain easier access to onsite childcare because operators face fewer local land‑use hurdles and no local business‑license or permit fees tied to operation.
- Multifamily developers and property owners: the removal of discretionary approvals and certain local fees can shorten entitlement timelines and lower carrying costs for projects that integrate childcare spaces.
- Daycare operators colocated with qualifying housing: operators avoid municipal business‑license or permit‑privilege fees and the uncertainty of discretionary land‑use reviews, improving project bankability for nonprofit and private providers.
Who Bears the Cost
- Local governments (planning, building, and finance departments): cities and counties lose a revenue stream from business‑license/permit privilege fees and lose a discretionary review lever they use to negotiate project mitigations.
- Nearby residents and neighborhood organizations: they may have fewer local procedural tools (like public hearings triggered by discretionary entitlements) to shape or oppose childcare operations, increasing reliance on nuisance and safety codes instead.
- Daycare operators and developers who must still comply with state technical standards: although land‑use barriers fall, operators must still absorb costs to meet California Building Standards, Fire Code, and state licensing, and they cannot rely on local variance or waiver routes for those technical requirements.
Key Issues
The Core Tension
The central dilemma is straightforward: the law removes local procedural and financial barriers to expand onsite childcare within larger apartment projects, but doing so reduces local discretion, potential mitigation leverage, and fee revenue—forcing a choice between increasing childcare supply and preserving local control and fiscal flexibility.
The statute packs straightforward lines but leaves operational ambiguities. The instruction that local rules must be “identical” when applied to a daycare and its colocated housing begs interpretation: must rules be textually identical, or is equivalence in practical effect sufficient?
Localities could argue for differential treatment based on differences in occupancy patterns or hours of operation, prompting litigation or negotiated administrative guidance.
Another unresolved question concerns the scope of the ban on local charges. The plain language bars charges, taxes, or fees for a business license, equivalent instrument, or permit for the privilege of operating the daycare, but it does not expressly address development impact fees, utility connection fees, or other exactions tied to new construction.
Cities facing revenue shortfalls may attempt to recast fees or conditions in ways the statute does not explicitly prohibit, which will produce enforcement and litigation issues.
Finally, the rule on design review creates a narrow path: design review remains available but must not be treated as a “project” under CEQA. That distinction leaves open disputes about when design review comments or conditions cross the line into substantive project changes that could trigger environmental review.
Implementation will require careful coordination among planning, building, fire, and licensing officials and will almost certainly produce case law clarifying how tightly courts construe the statute’s parity and use‑by‑right constraints.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.