At its May 26 meeting, the City Council introduced on first reading the city code amendments that implement AB 130 (Item 6.2). The headline result is good: qualifying housing projects that use the new statutory CEQA exemption will be approved at staff level, with no Environmental Planning Commission hearing and no Council hearing. Staff noted that over the past six months the city has approved more than 1,400 units across four projects using the AB 130 exemption, and Councilmember Kamei confirmed on the dais that projects like those four will no longer come to Council once these amendments take effect.
The vote was 7-0. There were two ordinances, one amending Chapter 36 (Zoning) and one amending Chapter 28 (Subdivisions) and Chapter 41 (Parkland Dedication), with second reading set for June 9, 2026 and the changes anticipated to be effective in early July.
So the city is moving in the right direction. But two of the things we asked for in our letter did not happen, and they are the two that matter most.
No deadline for the ministerial process
Council directed staff back at the January 27 study session to build a ministerial approval process for AB 130 projects. What came back on May 26 is an administrative process, which staff is recommending as an interim step because they could not convert every discretionary provision into an objective standard in the time available. An administrative process still leaves room for discretion, still allows a requested public hearing, and still allows an appeal to Council. A ministerial process would not.
We did not contest the interim step. Our letter accepted an administrative process as the starting point and put its weight behind getting to a fully ministerial one. Councilmember Hicks, who made the motion, framed the administrative approach as necessary because writing objective standards in a few weeks would mean discarding precise-plan provisions the community spent years on. Councilmember Ramirez added that some discretion will keep being necessary, pointing to the recent BMR alternative-compliance case as a policy judgment that does not reduce cleanly to a checkbox. We take a narrower view of how much of that discretion is worth keeping. Our letter asked staff to recommend, provision by provision, whether each remaining discretionary standard should be dropped or made less prescriptive rather than carried into the new code, on the theory that a standard more trouble than it is worth should not survive the move to ministerial review.
What we asked for was a date. Our letter recommended Council set a target like Q4 2026 to finish the fully ministerial process, so that applicants and the public know when the discretionary version goes away. The Chamber of Commerce’s Peter Katz asked for the same thing, urging a ministerial process “no later than by the end of 2026.” Kevin Ma, speaking for MV YIMBY and echoing our letter, made the point that a ministerial process may be required by state law next year regardless.
Council set no date. When Ramirez asked staff whether additional direction was needed to keep the ministerial work going, staff said no, and Ramirez left it there. So the ministerial process is “continuing,” on no schedule, with a state bill potentially mandating it anyway. We would rather have had a deadline on the record. Without one, “interim” has a way of becoming “current.”
The appeals process went in as proposed
Our larger concern was the appeals and requested-hearing process that staff added after the EPC review. As Kevin Ma noted, appeals were never discussed at EPC, so they appeared late. The Housing Accountability Act already strips almost all discretion at the Council level for these projects, which means an appeal hearing often cannot change the outcome. We have watched this happen: heritage-tree-removal appeals on ministerial ADU projects at the Urban Forestry Board went nowhere because state law left no room to act on them. What an appeal reliably adds is delay. Under the Permitting Streamlining Act an administrative appeal can pause the statutory clock (GOV 65922(b)), which is why we told Council the appeals process does more harm than good.
If Council was going to keep an appeals process, we asked for safeguards: a definite timeline for hearing appeals, a deemed-approved default if that timeline is missed, stricter criteria for what an appeal can even be based on, and an appeal fee set to full cost recovery. None of those went in. The ordinance as introduced has no appeal timeline except for subdivision maps, no deemed-approved backstop, and no criteria limiting the basis for an appeal.
The fee mechanics also came out sideways from what we wanted. There is no fee at all to request a hearing. And under the city’s cost-recovery model, when a member of the public requests a hearing or files an appeal on one of these projects, the applicant pays the staff and noticing costs out of their reimbursable deposit, with any overage also charged to the applicant. Director Murdock confirmed this directly under questioning from Ramirez: the applicant bears the cost of a hearing it did not want and did not request. That is the opposite of the incentive structure you want if the goal is to keep housing approvals fast and cheap.
Ramirez defended the appeals process on the grounds that, because some discretion remains in the interim, it is appropriate for both applicants and neighbors to be able to ask Council to weigh in. He is right that there is some discretion left. But he also named the exact failure mode we worry about: the tree-removal appeal where neighbors show up in good faith expecting to change something, and staff has to tell them state law forecloses it. His conclusion was to go in “eyes wide open.” Ours is that you do not need to build the trap in the first place, and that the discretion justifying the appeals process is supposed to be temporary anyway, which loops back to the missing ministerial deadline.
Kamei argued for the requested-hearing pathway from the other direction: three of the four recent AB 130 projects held no community meeting, and some neighbors wished they had been able to weigh in. We understand the impulse, but a requested hearing on a project that meets the objective standards hits the same wall the appeal does. Neighbors can show up and state their preferences, and the law still leaves the city nothing to act on. Adding more required process to a ministerial approval does not change that, and for projects on the streamlined track it is not even available, since state law caps hearings and forecloses discretionary review. The lever that matters is the objective standards themselves, which is the work staff is now doing, and getting those right counts for far more than a hearing that cannot change them.
What did go our way
The cleanup amendments we supported all went in. The package reconciles the zoning code with a stack of state laws, including child-care provisions under AB 1914-related changes, SB 234, AB 2162, and AB 101, and it brings the subdivision and parkland chapters into alignment with current practice. Showalter used her comments to note that AB 130’s exemption does not reach projects on hazardous sites, in floodways, in wetlands, in coastal zones, or in very high fire areas, where CEQA review still applies.
North Bayshore Area Plan amendment (Item 6.3)
Council, sitting as the Board of Directors of the Shoreline Regional Park Community, voted 7-0 to update the North Bayshore Area Plan, last amended in 1993. The amendment is mostly housekeeping: it incorporates by reference the precise plans and studies adopted since 1993, adds schools and affordable-housing and homelessness services to the public services the plan recognizes, and authorizes the tax-allocation proceeds for the Education Enhancement Reserve agreement with the school districts. At the request of three public speakers and several councilmembers, the motion added an explicit reference to the Burrowing Owl Preservation Plan.
The housing angle is worth noting even though nothing was entitled here. Ramirez read the Shoreline Regional Park Community Act’s statutory purposes into the record, four of which are about housing, including “provide needed additions to the general housing supply.” The plan that governs North Bayshore is built on a state mandate to produce housing there. Hicks signaled that a more holistic revisit of the North Bayshore plan is probably coming, given how much has changed since the precise plan was adopted. We will be watching what “holistic revisit” turns into, because in Mountain View that phrase has cut both ways.
Our take
This was real progress on AB 130. Taking four-hearing housing approvals down to staff-level sign-off is exactly the kind of process change that gets homes built faster, and a 7-0 vote with no opposition speakers is a healthy sign that streamlining is now the consensus position in Mountain View.
The two gaps are the ones we flagged before the meeting. First, Council should have set a date to finish the ministerial process, and did not. State law may force the question in 2026 anyway, but the city should be driving that timeline rather than waiting to be driven. Second, the interim appeals process has none of the safeguards we asked for, and its cost structure puts the bill for unwanted hearings on the applicant. As long as the Housing Accountability Act leaves Council with almost nothing to decide on these projects, an appeal is mostly a way to run the clock. We will be back on both of these at the June 9 second reading and whenever the ministerial amendments finally surface.
One thing to keep an eye on outside the housing items: the Parks and Recreation Strategic Plan (Item 7.1) was adopted with a stated citywide parkland shortfall of 53.5 acres and a roughly $722 million price tag, and it folds a review of the city’s privately-owned-publicly-accessible (POPA) standards into the upcoming park-fee nexus study due this fall. McAlister pressed on whether POPA percentages and park fees could be recalibrated to be less of a drag on development. That nexus study is where the parkland-dedication penalty on small ownership projects, which we have raised in the BMR context, could either get fixed or get worse. It is on our list for the fall.