Council Adopts an Interim AB 130 Streamlining Ordinance, No Date Set for the Ministerial Version
May 26, 2026
Mountain View City Council voted 7-0 on first reading to introduce city code amendments that let staff approve AB 130 housing projects administratively, without a Council hearing. Council adopted the appeals process we flagged as a risk and declined to set a deadline for the fully ministerial version.
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.
