FAQ

20 questions about SB 79

Sharper, more curious questions about SB 79 — what it really does, who decides what, and how it lands in Palo Alto. Each question gets a quick answer up top and a deeper explanation plus sources below.

How it actually works

The mechanics. Who decides, who approves, what the city can and can't change.

If a setback or sloped-roof rule effectively prevents an SB 79 building, who wins?

Short answer: SB 79's apartment-size minimums win. Cities keep their measurable rules (setbacks, materials, street-level design) only as long as those rules don't actually prevent a building of the state's minimum size.

SB 79 lets cities apply measurable design and development rules to projects — but those rules can't shrink the building below the state minimum. So a 5-foot side setback is fine; a setback rule that shrinks the buildable footprint below the state-required size doesn't apply.

Where this gets contested is when rules combine: a "modest" setback + a sloped-roof rule + a square-footage cap together can effectively block the state-minimum building, even if each rule looks reasonable on its own. The state housing department reviews each city's SB 79 rules and can find a city out of compliance — at which point a developer can sue, invoke a separate state law (the builder's remedy) that bypasses local zoning, or wait for the state to step in. Expect lawsuits in the first 18 months to set the line on what counts as a "measurable" rule.

Where to go for more: SB 79 bill text · State housing department — SB 79 page · Holland & Knight legal analysis

What does "automatic approval" actually mean?

Short answer: staff check the project against a checklist. No Council vote, no public hearing, no judgment call, no environmental lawsuit — if the boxes are checked, the project is approved.

Most large housing projects in California today go through what's called discretionary review: Council or a planning commission can ask for changes, hold public hearings, require traffic studies, and reject the project for not "fitting in." Environmental lawsuits are common because discretionary decisions trigger environmental review.

SB 79-qualifying projects use a different path called automatic approval (officially, "ministerial" approval, from a 2017 state law called SB 35). Staff verify each item: zoning rules, height, density, parking, affordability percentage, union-scale labor for buildings over 85 feet, design rules. Approve or deny based on the checklist alone. There's no public hearing; residents can't object on subjective grounds during the approval. They can still send written comments during the staff review, and they can challenge a project in court if staff misapplied the checklist — but they can't stop a project that meets the rules.

Where to go for more: SB 35 streamlining (Gov. Code §65913.4) · State housing department — SB 79 page

What happens if Palo Alto refuses to comply on July 1?

Short answer: the state minimums apply anyway. Refusing also opens the door to the state housing department finding the city out of compliance, an Attorney General referral, and a separate state law (the builder's remedy) that lets developers bypass local zoning entirely.

SB 79 takes effect on its own on July 1, 2026 — no city action required. If a developer files a qualifying project and Palo Alto denies it on grounds the law doesn't allow, the developer can sue and will likely win — Huntington Beach has been losing similar lawsuits over earlier housing laws since 2023. The state housing department can also find a city formally out of compliance, which triggers escalating consequences: the city's official housing plan can be invalidated, state grant funding can be withheld, and the Attorney General can refer the city to the courts.

The bigger threat is what's called the builder's remedy: when a city's housing plan is out of compliance, developers can propose projects that ignore local zoning entirely (as long as they meet affordability requirements). That's the law the 156 California Ave proposal is using, separate from SB 79. So a city that refuses to engage with SB 79 can end up getting both — SB 79-sized projects on top of builder's-remedy projects.

Where to go for more: HCD enforcement page · CA AG Housing Strike Force · CalMatters — cities scramble

Does SB 79 override environmental review (CEQA) and historic preservation?

Short answer: California's environmental review law (CEQA) still applies in most cases. Projects using the automatic-approval path skip CEQA. Historic exemptions exist but are narrow.

An SB 79 project that goes through normal discretionary city review still triggers CEQA (the California Environmental Quality Act, the law that forces environmental impact studies on most big projects). An SB 79 project that uses the automatic-approval path skips CEQA — that's the central time-saver. So in practice, most large SB 79 projects will use the automatic-approval path specifically to skip CEQA.

Historic properties are protected differently. SB 79 lets cities exempt sites listed on a National, California, or local historic register. But the bar for "historic" is real evidence of historic significance — not just "this is an old building." Under a long-term TOD Alternative Plan, local-register exemptions are also capped at 10% of a TOD zone; a near-term temporary ordinance can cover all locally-designated historic resources. Palo Alto staff are recommending a fast-track historic-property exemption ordinance for adoption before SB 79 takes effect July 1, 2026, paired with a 50% rezone — on the council agenda for June 1, 2026 — live status.

Where to go for more: Governor's Office — CEQA · State housing department advisory (PDF) · Allen Matkins legal alert

Will anything actually get built?

Allowing buildings on paper is one thing. Whether developers actually build them is a different question.

Do the financial numbers actually work for developers in Palo Alto?

Short answer: for high-rise steel-frame towers, the numbers are tight. For 5–7 story wood-frame buildings, Palo Alto's rents make it work — but only on the right lots.

High-rise steel-frame buildings in the Bay Area cost roughly $700K–$900K per apartment, all-in (land + construction + design and permit fees + financing). To make the numbers work, monthly rents need to clear about $5K–$6K for the mix of units. That's achievable in Palo Alto, but only on the most desirable lots — ones near Caltrain that the city has historically been most protective of. Wood-frame mid-rise buildings (5–7 stories) cost closer to $500K per apartment and the financials work more easily.

What this means: the 95-foot zone (the lots immediately wrapping each station) will see fewer projects than the 75-foot zone, because steel-frame buildings are harder to make work financially than wood-frame ones. The quarter-mile and half-mile rings, where 65–75 feet is the minimum, are where most actual construction is likely to happen. Look at Mountain View's El Camino corridor: lots of mid-rise activity, very few high-rise towers. Expect a similar pattern here.

Where to go for more: Terner Center construction-cost research · Urbanize Bay Area — project tracking

Will SB 79 produce moderate-income housing or just luxury?

Short answer: mostly market-rate, with a 7%–13% deed-restricted slice. Whether the market-rate units are "luxury" vs. "moderate" depends on the building type and how supply moves the broader market.

SB 79 itself includes baseline affordability requirements: projects of certain sizes must include a percentage of deed-restricted units (lower-income, very-low-income, or moderate-income depending on size and tier). On public-transit-agency land, the requirements are stricter. But the bulk of any SB 79 building will be market-rate.

"Luxury" vs. "moderate" is mostly about what the building is, not what gets advertised. Mid-rise rental apartments — the most common SB 79 form — typically rent for 60–90% of comparable single-family-home rents in the same neighborhood, because the unit type is different. New construction always costs more than older units. The argument for SB 79 is that adding supply at any price point reduces the cascade of bidding wars in the rest of the market; the argument against is that subsidized affordable housing is what Palo Alto actually needs and SB 79 doesn't deliver that directly.

Where to go for more: Bill text — affordability sections · Terner Center on supply & rents

What's a realistic 25-year build pace?

Short answer: probably uneven — clusters of activity in 2027–2030 once the law settles, then steady ~80–120 units/year. Boom-bust around interest-rate cycles is more likely than a smooth line.

The city's projection of ~2,700 units across 25 years averages to ~108 units/year. In practice, housing production is cyclical: it surges when interest rates fall and rents rise, and collapses when financing gets expensive. The 2008–2012 period in Palo Alto saw almost zero multifamily completion; 2014–2019 saw a steady stream.

What's realistic: the first 18 months after July 2026 will be slow as developers and the city work through how the law applies in practice. By 2028, expect a wave of projects on the easiest sites (parking lots, single-story commercial). Mountain View's El Camino corridor went from ~50 units/year before its big rezone to ~400/year five years after — a useful comparison, even though Palo Alto's land prices and parcel sizes are different.

Where to go for more: Bay Area Council Economic Institute · PA Housing Policies & Projects

What's the track record of SB 9, SB 35, AB 2011, AB 2097?

Short answer: mixed. SB 9 has been a disappointment (very few duplex conversions). SB 35 produced significant ministerial-approved housing in cities that were out of compliance. AB 2011 is just starting. AB 2097 (parking) is harder to measure but appears to be unlocking deals.

SB 9 (2021) — duplex conversions in single-family zones. As of late 2025, fewer than 1,000 statewide. Reasons: lot-merger restrictions, owner-occupancy requirements, and the kind of homeowners who'd benefit don't typically build small infill. SB 79 won't repeat this trap because it targets developers, not homeowners.

SB 35 (2017) — ministerial approval where housing-element compliance is missing. Real impact: thousands of units approved in Cupertino, Santa Monica, Lafayette, etc. SB 79 inherits this machinery.

AB 2011 (2022) — converting commercial corridors to housing with prevailing wage. Pipeline is filling now, mostly in LA. Early signs are positive.

AB 2097 (2022) — parking minimums removed near transit. Hard to count, but developers are pursuing tighter parking ratios on transit-adjacent sites that wouldn't have been feasible before. SB 79 stacks with this.

Where to go for more: Terner Center research library · California YIMBY tracking

Strategic / political

Why this law, why now, and how it sits in California's bigger housing toolkit.

Why "near transit" — not everywhere?

Short answer: climate, infrastructure cost, and political coalition. Building near transit means residents drive less; it uses sewer and road capacity that's already there; and it pulls in transit and labor allies that "upzone everywhere" wouldn't.

The legislature has tried "everywhere" upzoning before — SB 50 died in 2020 after years of attempts. SB 79 took the opposite tack: scope tight, mandate strong. Targeting transit areas specifically does a few things at once: it reduces vehicle-miles-traveled (each home near rail produces ~30–50% less driving, which is the single biggest lever on the state's emissions); it concentrates new water, sewer, school, and road demand where infrastructure already exists; and it builds a coalition that includes transit agencies, MTC/CARB, environmental groups, and the building trades — not just housing advocates.

The trade-off: large parts of California stay zoned the way they are. SB 79 doesn't touch low-density inland sprawl, exclusive single-family enclaves more than ½ mile from rail, or coastal communities without qualifying transit. That's a deliberate compromise.

Where to go for more: Sen. Wiener — signing statement · CA YIMBY framing

SB 9 vs. SB 35 vs. AB 2011 vs. SB 79 vs. builder's remedy — what's the difference?

Short answer: they each preempt local control on a different axis. SB 9 = duplexes in SFH zones. SB 35 = ministerial approval where the city is out of compliance. AB 2011 = housing on commercial corridors. SB 79 = state floors near transit. Builder's remedy = zoning bypass when housing element is non-compliant.

SB 9 (2021): owner-driven, two units + lot split on a single-family parcel.

SB 35 (2017): developer-driven, ministerial approval (no CEQA, no hearings) on multifamily projects in cities not meeting their housing-element targets. Affordability-tied.

AB 2011 (2022): developer-driven, lets housing be built on parcels currently zoned for offices, retail, or parking lots along commercial corridors. Prevailing-wage and affordability conditions.

SB 79 (2025): developer-driven, sets state minimum heights and densities near transit. Projects can use SB 35 to be ministerial.

Builder's remedy (Housing Accountability Act): if a city's housing element is non-compliant, developers can propose projects that ignore zoning entirely, as long as 20% of units are affordable to lower-income households. This is a stick, not a track — it goes away once the city gets compliant.

These stack. A single project at Cal Ave could potentially use SB 79 (height/density), SB 35 (ministerial), AB 2011 (commercial-conversion), and AB 2097 (no parking minimum) all at once, if it qualifies for each.

Where to go for more: HCD — housing laws library · Lozano Smith — 2025 housing legislation roundup

What does Palo Alto's "half as many homes" option actually buy?

Short answer: up to ~6 years of breathing room, in exchange for the city actually doing real upzoning itself (about 1,350 new homes total). A separate, bigger option lets the city move where the new homes go — but the total still has to add up to what SB 79 would require.

There are actually two different things people sometimes both call "Track 2." The first is a full alternative plan to the state: the city writes a plan that allows the same total number of new homes SB 79 would, just distributed differently inside the half-mile area around each station. So Palo Alto could zone some lots to less than SB 79's minimums if it zones other lots (still inside the half-mile area) to more, and the totals balance. The state housing department reviews and signs off.

The "half as many homes" rule is a different option: if a city's own zoning already allows at least half as many new homes as SB 79 would, the full SB 79 minimums get pushed back about 6 years (until ~2032). That's not a cap on the upzoning; it's a delay before the state version kicks in. The city is also looking at this as a separate path.

The trade-off differs by path: the "half as many homes" delay reduces near-term capacity to 50% in exchange for ~6 years; a full alternative plan keeps the total but lets the city move it around. Importantly, the 50% delay can be done fast — a temporary/urgency city ordinance adopted in weeks, no state sign-off — whereas a full alternative plan is the multi-year, HCD-reviewed effort. The SB 79 item was deferred from May 4, 2026 and is now on the June 1, 2026 agenda, where staff recommends the 50% rezone paired with a historic exemption. See council watch for the current status.

Where to go for more: Live council status & the four options · SB 79 bill text — alternative plan section · PA Online — city looks at exemptions and rezoning

Will SB 79 survive a court challenge?

Short answer: probably yes. Cities have been suing over state housing laws for years and have mostly lost. Expect lawsuits over SB 79, but don't expect them to undo the law as a whole.

The main legal argument against SB 79 is that California "charter cities" (Palo Alto is one) have constitutional authority over their own municipal affairs — and zoning, the argument goes, is one of those affairs. Cities have made this argument against earlier housing laws (SB 9, SB 35, the housing-plan law, the Surplus Lands Act) and have mostly lost, because courts have ruled that housing supply is a statewide concern, which trumps the municipal-affairs argument.

What to expect: at least one city will sue within a few months of July 1, 2026; the case will take 12–24 months to reach an appeals decision; and the law will come out battered but largely intact. Specific pieces might get trimmed (the union-scale labor requirement has been challenged in other contexts), but the core idea — that the state can override local zoning near transit — is likely to stand.

Where to go for more: Holland & Knight — analysis · Allen Matkins — alert

Palo Alto specifics

The local angles — projects, parcels, and the politics on the ground.

Is Redco's 156 California Ave project an SB 79 project?

Short answer: no — it's a builder's remedy project, a state mechanism that predates SB 79. On May 18, 2026 the Council voted 4–2 to clear the way for a negotiated revised version: shorter towers, slightly more units, fewer affordable.

Redco Development's proposal at 156 California Ave (the Mollie Stone's site) was first filed in 2023 as a builder's remedy project — available because Palo Alto's housing element was out of compliance during the relevant window. The originally filed version ("Builder's Remedy 1.0"): 382 units across a 17-story tower, an 11-story tower, and a 7-story podium, topping out at 177 feet, 20% of the units affordable, with a relocated Mollie Stone's on the ground floor, 290 parking stalls, and 400 bike spaces.

After Redco threatened litigation, a Council ad hoc committee (Vice Mayor Stone and Councilmember Lauing) negotiated a revised concept — "Builder's Remedy 2.0": three towers of 14, 12, and 12 stories, 390 units, 144 feet maximum. The revised version relies on AB 1893 (2024), which lowered the builder's-remedy affordability minimum from 20% to 13% — so affordable units drop from about 78 to 50. On May 18, 2026 the Council voted 4–2 (Reckdahl and Burt opposed; Mayor Veenker absent) to add a project parcel to the city's Housing Element Sites Inventory — the step that lets Redco pursue the 2.0 version. Had Council declined, the developer would likely have proceeded with the original 1.0 design.

Why it matters here: this is the closest preview of what large buildings near Cal Ave actually look like. Both versions are taller than SB 79 itself would mandate (SB 79 caps at 95 ft at adjacency) — builder's-remedy projects aren't bound by SB 79's envelope. And under AB 130 (2025), the project is now statutorily exempt from CEQA environmental review as an urban infill housing development, superseding the draft EIR circulated in 2024.

Where to go for more: PA Online — divided council signals support (May 2026) · May 18 council agenda & Item 14 staff report · City project page — BR 1.0 & 2.0 plans

Why did Palo Alto pause the Downtown Coordinated Area Plan in November 2025?

Short answer: SB 79 was about to upend most of the assumptions behind it. The Council paused so staff could focus on SB 79 instead of producing a downtown plan that would be obsolete on July 1.

The Downtown Coordinated Area Plan was a multi-year city-staff effort to write a new downtown vision — bike infrastructure, ground-floor retail, building heights, transit-center redesign. It launched well before SB 79 was a serious bill. By November 2025, with SB 79 signed and the state floors known to be coming July 2026, the city decided continuing the plan as written would produce numbers that wouldn't survive contact with the new law.

The pause is real but probably not permanent. The city's plan-of-record for downtown will likely emerge as part of whatever SB 79 ordinance or alternative plan Palo Alto adopts — meaning the downtown vision and the SB 79 response merge into a single document rather than running on parallel tracks.

Where to go for more: PA Online — pause coverage · PA Online — transit-center panel

Are all three Palo Alto Caltrain stations actually Tier 1?

Short answer: yes, all three. We pulled Caltrain's GTFS feed and counted: University Ave gets 104 trains/weekday, California Ave and San Antonio each get 90 — all comfortably above the 72-train Tier 1 floor.

Per the HCD MPO advisory (March 20, 2026), commuter-rail stations qualify as Tier 1 if they get ≥72 trains per weekday averaged across both directions. 48–71 trains makes a station Tier 2. The averaging is the sum of scheduled stops across the five weekdays, divided by five.

Caltrain's post-electrification schedule (effective Jan 31, 2026) runs 112 weekday trips total (~56 each direction). University Ave is a major stop where every train stops. California Ave and San Antonio are local-pattern stops where about 14 trains skip in each direction — so they get 90 each instead of 104. All three still clear Tier 1 with margin.

Why this matters: Tier 1 unlocks the strongest floors — 95 ft adjacent, 75 ft within ¼ mile, 65 ft within ½ mile. Tier 2's floors are lower. With all three stations confirmed Tier 1, the full Tier 1 envelope applies across all of Palo Alto's transit-adjacent parcels starting July 1, 2026.

The official map still comes from ABAG/MTC in mid-2026 with a rebuttable presumption of validity. But since the inputs (Caltrain's GTFS, HCD's threshold) are public, anyone can verify.

Where to go for more: Our methodology page (show your work) · HCD MPO advisory (PDF) · Raw JSON output

What about Stanford-owned land near downtown?

Short answer: SB 79 applies to Stanford-owned parcels on the same terms as anyone else's — but most Stanford-owned parcels in Palo Alto are governed by the 2000 General Use Permit and historic land-use agreements that complicate redevelopment in their own way.

SB 79 doesn't carve out university-owned land. If a Stanford-owned parcel is within ½ mile of University Ave or Cal Ave Caltrain, zoned for residential, mixed, or commercial use, it qualifies. The downtown area includes several Stanford-owned commercial properties, and Cal Ave is largely surrounded by Stanford Research Park land.

The complication: Stanford's use of its own land is separately regulated through agreements with Santa Clara County (the General Use Permit) and historical commitments to the City of Palo Alto. Whether Stanford chooses to develop housing at SB 79 scale on its parcels is a different question from whether SB 79 makes it legal — and Stanford's housing decisions historically prioritize its own faculty, staff, and student housing over open-market development.

Where to go for more: Stanford Land Use & Environmental Planning · Santa Clara County — Stanford planning

Common pushback

The recurring concerns from neighbors. Short, sourced answers.

Won't this cause more traffic?

Short answer: probably less than people fear. Households within ½ mile of frequent rail drive 30–50% fewer miles on average. Peak-hour intersection congestion will still be real.

The transit-oriented-development literature is unusually consistent: residents within a half-mile of frequent rail drive significantly fewer miles per day than residents elsewhere — across multiple US studies, the reduction is in the 30–50% range. Caltrain electrification (now running) makes that effect stronger by improving frequency.

That doesn't mean zero new car trips. Peak-hour pinch points at Alma & University and El Camino & Page Mill will see real pressure. Complete-streets investments and intersection redesigns are reasonable adjacent demands — but the "more housing = catastrophic gridlock" intuition isn't borne out near transit.

What about parking? Will my street fill up?

Short answer: SB 79 + AB 2097 reduce or remove parking minimums, but most large developers near transit still build some parking. Resident permit programs prevent overflow into adjacent streets.

SB 79 stacks with AB 2097 (which removed parking minimums within a half-mile of major transit). Developers can choose to build less parking now, but the market still expects some — Mountain View's recent transit-corridor projects build at ~0.5–0.8 stalls per unit, not zero. Cities can keep on-street residential permit zones, which are the actual mechanism preventing spillover from new buildings.

Will Palo Alto's schools be overwhelmed?

Short answer: ~2,700 units over 25 years is roughly 100 homes a year — well within normal PAUSD enrollment swings. Multifamily produces fewer school-age children per unit than single-family.

PAUSD enrollment varies by 200–400 students year-over-year on its own, before any new housing. ~100 new homes a year produces a smaller demographic shift than that natural swing. Per-unit school-age-child generation rates for multifamily housing are well-studied and consistently lower than for single-family — typically 0.1–0.3 children per unit vs. 0.5–0.7 for single-family. Districts adjust class sizes and boundaries year-to-year as a normal part of operations.

What about the character of the neighborhood?

Short answer: SB 79 only touches parcels within a half-mile of qualifying transit. In Palo Alto that's downtown, Cal Ave, and San Antonio — already commercial/mixed cores. The classic residential neighborhoods sit outside the bands.

Old Palo Alto, Crescent Park, Professorville, most of Midtown, all of Barron Park — none are within a half-mile of a Caltrain station. Their zoning is unaffected by SB 79. The character debate inside the bands is a real conversation; the character debate outside them isn't a SB 79 question.

Have a question we should add? Open an issue on GitHub or reach out — see About.