What Council Asked Staff to Do — Housing

When Mountain View City Council and the Environmental Planning Commission meet, they sometimes go beyond what staff recommended — adding conditions, asking for memos, redirecting staff time. The list below tracks the housing-relevant ones: zoning, project approvals, BMR, tenant protections, parking and TDM, state housing legislation. Council direction is shown by default; switch the Body filter to surface Planning Commission direction too. Click a row to jump to the source meeting transcript at the moment the direction was given. Updated as new transcripts are scanned.

109 directives across 17 councilmembers / commissioners. Generated .

IssuedDirectiveDueMemberMeeting
2026-04-28
1:08:26		Integrate Biodiversity Plan into objective design standards and roadway standards
detailsDirect staff to ensure that the upcoming objective design standards for private development and the design standards for roadways/streetscapes are explicitly informed by the Biodiversity and Urban Forest Plan, including shade trees over sidewalks/bikeways, lane reallocation for green infrastructure, and greener standards for townhome/rowhome hardscape. Mayor Ramos confirmed this in the straw-poll batch as 'objective design standards for private development and roadways' tied to the plan's concepts.
Why notable: Goes beyond the plan's existing soft references; ties Biodiversity Plan as a binding input into separate ongoing standards efforts.
Agenda item: 3.1
—Councilmember Alison HicksApr. 28, 2026 Joint Meeting of the City Council …
2026-04-15
2:25:04		Cleanup: restore office <10,000 sf exemption and TDM fee admin in standards
detailsFlagged that the office under 10,000 sf exemption mentioned in the staff report is missing from the ordinance applicability section, and that the ordinance references TDM fee administration details in the program standards but those details are not in fact included in the standards document. Asked staff to clean up both before the ordinance moves forward.
Why notable: Drafting gaps between staff report, ordinance, and standards document — caught by the commissioner during deliberation.
Agenda item: 6.1
—Commissioner Shwetha SubramanianApr. 15, 2026 Meeting of the Environmental …
2026-04-15
2:53:54		Credit mixed-use trip internalization in TDM toolkit
detailsAsked staff to develop a methodology for crediting mixed-use projects with the trip-internalization benefit they generate (residents walking to on-site commercial uses) as a TDM strategy, capturing the ADT delta between an equivalent single-use project and a mixed-use one. Straw poll showed commission support.
Why notable: Mixed-use internalization is currently only recognized as a VMT-screening exemption in the MTA handbook, not as a TDM credit; commission asked staff to extend it to the TDM toolkit to incentivize mixed-use development.
Agenda item: 6.1
—Commissioner Shwetha SubramanianApr. 15, 2026 Meeting of the Environmental …
2026-04-15
2:53:18		Add tiered parking-reduction credit to TDM toolkit (residential)
detailsAsked staff to evaluate adding tiered reductions in provided parking as a recognized TDM strategy that yields trip-reduction credit (an auxiliary measure), so residential projects in transit-poor areas can earn credit for going below required parking by varying amounts rather than the current binary reduced-parking option. Straw poll showed commission support.
Why notable: Existing toolkit treats reduced parking as one binary option; commissioner asked for a graduated credit structure to better align TDM with the housing-element goal of letting residential projects reduce parking.
Agenda item: 6.1
evaluation likely takes ~a year per Planning Manager AndersonCommissioner Shwetha SubramanianApr. 15, 2026 Meeting of the Environmental …
2026-04-15
2:50:08		Assess how often density-bonus concessions gut the TDM requirement
detailsAsked staff to evaluate, before the ordinance reaches Council, how state density-bonus concessions have been used against existing TDM requirements in peer jurisdictions and Mountain View precise plans — specifically whether developers walk away from TDM entirely vs. negotiate reduced versions — and adjust the program to keep some TDM floor in place rather than letting it become an all-or-nothing concession target.
Why notable: Staff acknowledged TDM cannot be made fully concession-proof under state density-bonus law; commissioner asked for a defense-in-depth assessment that wasn't part of the staff recommendation.
Agenda item: 6.1
—Commissioner Bill CranstonApr. 15, 2026 Meeting of the Environmental …
2026-04-15
1:28:38		Redefine 'single-occupancy vehicle' to cover zero-occupant/autonomous vehicles
detailsAsked staff to revise the TDM ordinance's definition of single-occupancy vehicle so it captures autonomous (Waymo) and zero-occupant vehicles, rather than the current 'occupied by only the driver during a commute or trip' wording. Staff agreed to look at adjusting the definition.
Why notable: Staff's draft definition assumed a human driver; commissioner caught that AV trips would slip through the ordinance and asked for the definition to be broadened.
Agenda item: 6.1
before the ordinance returns for Council first/second reading in Q2 2026Vice Chair Paul DonahueApr. 15, 2026 Meeting of the Environmental …
2026-04-15
1:07:36		Add strikethrough of small animal keeping from agricultural use category
detailsMotion amended the staff recommendation to include striking 'small animal keeping' from the agricultural use category in the residential land use table (it had been duplicated under both agricultural and accessory uses). Carried unanimously.
Why notable: Staff had not caught the duplication in the draft ordinance; commission added the cleanup as part of the recommendation rather than leaving it as a typo for staff to fix later.
Agenda item: 5.1
as part of the EPC's recommendation to Council (May 26 hearing)Commissioner Shwetha SubramanianApr. 15, 2026 Meeting of the Environmental …
2026-03-10
3:54:53		Add tree-saving direction into the 515-545 N. Whisman approval
detailsJust before the motion on 6.3, Hicks asked to add to the request that staff and the applicant save any trees that are possible at the 515-545 N. Whisman row-house site, on top of Showalter's earlier ask. The motion was then made and passed 6-0.
Why notable: Reinforces tree preservation as council direction tied to the project approval, beyond the staff conditions.
Agenda item: 6.3
—Councilmember Alison HicksMarch 10, 2026 City Council Meeting
2026-03-10
3:48:44		Have staff work with applicant to save additional trees along the front edge
detailsShowalter asked staff to work with the 515-545 N. Whisman applicant to see how many of the trees along the front edge of the site could be preserved beyond what the heritage tree removal permit currently allows, with each saved tree counting as a benefit to the community.
Why notable: Adds a tree-preservation effort beyond the heritage tree removal permit and conditions in the staff recommendation.
Agenda item: 6.3
—Councilmember Pat ShowalterMarch 10, 2026 City Council Meeting
2026-03-10
3:17:37		Clarify BMR ordinance to prevent layout/design end-runs on unit-mix proportionality
detailsRamirez raised concerns that applicants could use density-bonus concessions plus deliberate layout/design choices to clump small units in a way that effectively avoids the BMR ordinance's unit-mix proportionality intent. He asked staff to address this so the city does not end up with de facto end-runs on the ordinance. Housing Director Wayne Chen committed to clarifying through administrative guidelines, the City Attorney's office, and to incorporate the issue into the upcoming BMR ordinance update if it requires ordinance-level work.
Why notable: Adds a new scope item to the in-flight BMR ordinance update beyond what staff had teed up.
Agenda item: 6.3
in the upcoming BMR ordinance updateCouncilmember Lucas RamirezMarch 10, 2026 City Council Meeting
2026-03-04
2:21:23		EPC motion adds qualified-partner and AFFH-concentration provisions to staff rec
detailsMotion (passed 6-0-1) recommending Council adopt the BMR ordinance amendments with two additions beyond staff's recommendation: (1) language assuring qualified partners as part of alternative-compliance proposals, and (2) additional staff analysis to ensure off-site alternative compliance tracts do not exacerbate low-income concentrations in the city.
Why notable: Formal EPC recommendation to Council goes beyond what staff brought.
Agenda item: 5.1
—Vice Chair Alex NuñezMarch 04, 2026 Environmental Planning Commission …
2026-03-04
2:07:34		Analyze additional measures so off-site BMR doesn't worsen low-income concentration
detailsDirection to staff to do additional analysis, beyond reliance on the HCD opportunity-area map, ensuring that off-site alternative compliance does not exacerbate concentration of low-income residents in particular census tracts; suggested using the more granular housing element figures (98, 99, 100) as references. Incorporated into the EPC's adopted motion.
Why notable: Adds AFFH-grounded scrutiny step that staff had not built into the locational requirements.
Agenda item: 5.1
—Vice Chair Alex NuñezMarch 04, 2026 Environmental Planning Commission …
2026-03-04
2:01:09		Flag CSFRA-as-acquisition-preservation may add zero net units
detailsAsked staff to clarify to Council whether allowing acquisition of CSFRA units to satisfy the BMR requirement was understood to potentially yield no net new affordable units relative to the inclusionary baseline, since CSFRA units are converted to deed-restricted rather than newly produced.
Why notable: Raises whether Council was aware of the policy trade-off when accepting acquisition-preservation as an option.
Agenda item: 5.1
—Commissioner Bill CranstonMarch 04, 2026 Environmental Planning Commission …
2026-03-04
2:01:09		Bring rowhome/townhome 25% BMR requirement back to Council for re-evaluation
detailsRecommended that the 25% BMR requirement for rowhome/townhome projects (versus 15% elsewhere) be revisited and brought back to Council, on the basis that the original financial-equivalency analysis predates SB 330 and townhome production has since collapsed.
Why notable: Outside the scope of the current amendments; flagged as needing a separate Council look. Cites builder testimony at the meeting.
Agenda item: 5.1
—Commissioner Bill CranstonMarch 04, 2026 Environmental Planning Commission …
2026-03-04
2:06:21		Expand staff explanation in Council report on Chapter 36-vs-46 decision
detailsAsked that the staff report sent to Council include a more substantive (two-sentence) explanation of why staff is not recommending moving the BMR program from Chapter 36 to Chapter 46, since the original memo and presentation lacked any reasoning.
Why notable: Direction to staff to upgrade documentation before the Council hearing.
Agenda item: 5.1
—Commissioner Hank DempseyMarch 04, 2026 Environmental Planning Commission …
2026-03-04
1:41:05		Add city qualified-partner review authority over alternative-compliance proposals
detailsRecommended ordinance language giving the city final review/approval authority over the partnerships and alternative-compliance proposals submitted under the new third option, so the city can reject proposals where the proposed partner is not a qualified developer or financing/proforma is not credible. Incorporated into the EPC's adopted motion.
Why notable: Goes beyond staff rec; addresses Cranston's concern about unscrupulous BMR developers based on San Francisco precedent.
Agenda item: 5.1
—Commissioner Bill CranstonMarch 04, 2026 Environmental Planning Commission …
2026-03-04
1:23:50		Explore prioritizing among the three alternative compliance options
detailsAsked staff and the City Attorney to research whether AB 1505 allows the city to set a priority order among the three alternative compliance options (land dedication, off-site development, acquisition/preservation), with the goal of preferring options that deliver BMR units faster.
Why notable: Staff had not contemplated prioritization; City Attorney committed to research feasibility.
Agenda item: 5.1
—Commissioner Shwetha SubramanianMarch 04, 2026 Environmental Planning Commission …
2026-03-04
0:56:08		Include HCD high-resource-area map in Council staff report
detailsRecommended that staff include the HCD opportunity-area map shown to the EPC in the staff report sent to Council, because without it the locational criteria for alternative compliance read as a meaningful list of choices when in practice the HCD criterion subsumes the others.
Why notable: Cranston argues south-of-El Camino and Precise-Plan criteria are illusory once the HCD map is overlaid; Council needs the map to evaluate.
Agenda item: 5.1
—Commissioner Bill CranstonMarch 04, 2026 Environmental Planning Commission …
2026-03-04
0:53:42		Provide parcel-count data for 7-10 unit projects under SB 684
detailsAsked staff to provide the analysis of how many parcels in Mountain View fall within the 7-10 unit project range under SB 684, so the EPC and Council can put guidelines in place to address those sites quickly rather than deferring to the 2028 BMR review.
Why notable: Pushes staff to accelerate work staff had proposed deferring to 2028.
Agenda item: 5.1
—Commissioner Shwetha SubramanianMarch 04, 2026 Environmental Planning Commission …
2026-03-04
0:49:51		Consider Community Land Trust conveyance as alternative compliance option
detailsAsked staff to consider adding conveyance of land to a community land trust as an option for the alternative compliance pathway, on the theory that a CLT could help maintain affordability in perpetuity and reduce city carrying costs for dedicated parcels.
Why notable: Adds a new compliance vehicle not in staff's three-option proposal (land dedication, off-site, acquisition/preservation).
Agenda item: 5.1
—Commissioner Shwetha SubramanianMarch 04, 2026 Environmental Planning Commission …
2026-02-18
1:28:59		Recommend earmarking funds so adjacent future park is built sooner
detailsSubramanian noted the project's public path is 'a path to nowhere on both sides' and urged that earmarking of funds for the adjacent future park be recommended so the park comes into being sooner and provides value to both the development and the neighborhood.
Why notable: Reinforces Cranston's park-in-lieu earmarking ask; adds rationale tied to the project's pathway easement.
Agenda item: 6.1
—Commissioner Shwetha SubramanianFeb. 18, 2026 Environmental Planning Commission …
2026-02-18
1:28:59		Move toward more objective standards citywide via R3 update to reduce waivers
detailsSubramanian directed a comment to staff that the four density-bonus waivers required on this project show the city should move away from finely stipulated standards and toward more objective standards citywide, and that this should be considered as the R3 standards are implemented to speed up project review.
Why notable: Frames the R3 zoning update (already in progress) as a vehicle for reducing waiver-driven review burden; not in staff rec for 6.1.
Agenda item: 6.1
—Commissioner Shwetha SubramanianFeb. 18, 2026 Environmental Planning Commission …
2026-02-18
1:13:48		Earmark park-in-lieu fees from this project toward the adjacent future park
detailsCranston asked whether the EPC could earmark the project's park-in-lieu fees toward funding the adjacent future city park. Director Murdock confirmed the EPC could include this as a suggestion in its recommendation to Council, and Cranston pressed that 'the powers that be' do so.
Why notable: Adds a funding-direction suggestion to Council not in the staff recommendation; echoed by Donahue and Subramanian during deliberations.
Agenda item: 6.1
—Commissioner Bill CranstonFeb. 18, 2026 Environmental Planning Commission …
2026-02-18
0:38:02		Recommend pruning stale General Plan action items to free staff time
detailsCranston requested the Community Development Director consider removing General Plan action items that have not been a priority for 14 years from the action list, so staff time isn't spent reporting on them and can instead be redirected to higher-priority work like AB 130 implementation.
Why notable: Goes beyond staff rec (which was simply to accept the APR); proposes an active reorganization/pruning of the GP Action Plan that staff said council had previously declined to take up.
Agenda item: 5.2
—Commissioner Bill CranstonFeb. 18, 2026 Environmental Planning Commission …
2026-02-10
6:22:44		Constrain all R3 follow-on work to not delay 2026 adoption
detailsStaff (CD Director Murdock) requested, and Ramirez accepted into the motion, that all of the additional R3 follow-on directions be pursued 'to the maximum extent practicable' but not in a way that jeopardizes adoption of the R3 update in 2026.
Why notable: Schedule guardrail accepted by mover, requested by Vice Mayor Clark — bounds scope of the new directives.
Agenda item: 7.1
2026-12-31Community Development Director Christian MurdockFeb. 10, 2026 City Council Meeting
2026-02-10
6:20:25		Build a recurring update process for objective standards (massing, base treatment)
detailsDirection to staff to evaluate a process for periodically adding/modifying objective standards (with EPC and Council review and public input), initially focused on section 36.17.25 (massing features) and streetwall/base treatment, so the city does not wait decades between zoning updates again.
Why notable: Institutional fix: codifies a continual-improvement loop on objective standards rather than monolithic 7-year rewrites.
Agenda item: 7.1
—Councilmember Lucas RamirezFeb. 10, 2026 City Council Meeting
2026-02-10
6:20:15		Add riparian-corridor standards referencing Valley Water guidelines
detailsDirection to staff to explore incorporating R3 development standards related to riparian corridors, referencing Valley Water's regional riparian-corridor guidelines (top-of-bank setbacks for stability and habitat).
Agenda item: 7.1
—Councilmember Lucas RamirezFeb. 10, 2026 City Council Meeting
2026-02-10
6:20:07		Evaluate increasing FAR in R3-B for stacked flats
detailsDirection to staff to evaluate raising the FAR in the R3-B subdistrict to facilitate stacked-flat development, paralleling the R3-C ask.
Agenda item: 7.1
—Councilmember Lucas RamirezFeb. 10, 2026 City Council Meeting
2026-02-10
6:18:59		Evaluate additional required pedestrian connections from public input
detailsDirection to staff to take a fast look at additional required pedestrian connections in figure 36.10.73.1 based on public input already received and staff analysis, and add the ones that pencil — without launching new outreach.
Agenda item: 7.1
—Councilmember Lucas RamirezFeb. 10, 2026 City Council Meeting
2026-02-10
6:18:38		Add objective design standards for arcades / loggias / cantilevered overhangs
detailsDirection to staff to evaluate the role of arcades, loggias, and cantilevered second stories or ground-floor clerestories on private property as public-space-creating elements (without encroaching on public ROW), and develop objective design standards for them.
Why notable: Lets developers widen effective sidewalks via cover/overhangs while keeping the buildable envelope intact.
Agenda item: 7.1
—Councilmember Lucas RamirezFeb. 10, 2026 City Council Meeting
2026-02-10
6:18:15		Eliminate stoops from R3 building entry types
detailsDirection to staff to remove 'stoop' as an allowed building entry type in section 36.17.02, citing observed dead-zone behavior of stooped frontages in the San Antonio area / The Crossings.
Agenda item: 7.1
—Councilmember Lucas RamirezFeb. 10, 2026 City Council Meeting
2026-02-10
6:17:52		Add height exception for parkland dedication or heritage tree preservation
detailsDirection to staff to allow a height exception in R3 standards if the project facilitates dedication of land for a new public park or preserves heritage trees.
Agenda item: 7.1
—Councilmember Lucas RamirezFeb. 10, 2026 City Council Meeting
2026-02-10
6:17:09		Drop habitable-ground-floor depth requirement; evaluate 75% facade alternative
detailsDirection to staff to eliminate the habitable-ground-floor depth requirement from front-facade tables (36.10.70A/G/M/S) and instead evaluate alternative standards such as requiring at least 75% of a front facade to have habitable space behind it.
Why notable: Per Commissioner Subramanian; reduces a costly dimensional requirement that constrains floor plates.
Agenda item: 7.1
—Councilmember Lucas RamirezFeb. 10, 2026 City Council Meeting
2026-02-10
6:15:52		Add ornamentation/landscape alternatives to massing-feature options
detailsDirection to staff to amend section 36.17.25 (massing features) to include alternative options such as change in materials, change in ornamentation, change in window/transparency percentage, and landscaping — picking up Commissioner Subramanian's EPC suggestion.
Why notable: Lets architects satisfy massing-break standards through facade treatment instead of expensive geometric breaks; modular-housing friendly.
Agenda item: 7.1
—Councilmember Lucas RamirezFeb. 10, 2026 City Council Meeting
2026-02-10
6:13:42		Develop SB 79 objective design standards for front setbacks
detailsDirection to staff to use the SB 79 implementation ordinance to develop objective design standards/guidelines for front setbacks that support neighborhood-serving commercial and walkable environments; in the interim apply 'should' (not 'shall') guidelines to setback treatment so projects can move now.
Why notable: Explicit linkage of R3 setback policy to SB 79 implementation work; iterative two-track approach.
Agenda item: 7.1
—Councilmember Lucas RamirezFeb. 10, 2026 City Council Meeting
2026-02-10
6:12:39		Drop lot consolidation incentive; replace with affordability/anti-displacement bonuses
detailsDirection to staff (per EPC) to omit the lot consolidation incentive in R3 and instead develop alternative incentives — increased affordability requirements and stronger tenant relocation/right-to-return — with flexibility to be creative if direct substitution is infeasible.
Why notable: Significant departure from staff rec; targets developer behavior on existing-tenant displacement during R3 redevelopment.
Agenda item: 7.1
—Councilmember Lucas RamirezFeb. 10, 2026 City Council Meeting
2026-02-10
6:12:15		Allow commercial in R3-D and R3-B with live-work standards
detailsFinal R3 motion (carried 5-1) directing staff to adopt the EPC recommendation to allow commercial uses in R3-D and R3-B subdistricts with appropriate standards, including objective live-work design standards to activate streets.
Why notable: Extends commercial permissiveness across all R3 subdistricts.
Agenda item: 7.1
—Councilmember Lucas RamirezFeb. 10, 2026 City Council Meeting
2026-02-10
5:54:05		Allow commercial uses in R3-C; evaluate raising FAR for stacked flats
detailsMotion (carried 4-1) adopting EPC recommendation to allow commercial uses in R3-C with objective live-work design standards, AND directing staff to evaluate increasing the FAR in R3-C to better signal/ facilitate development of stacked flats and entry-level ownership.
Why notable: Adds an FAR-evaluation ask not in staff rec; aimed at unlocking stacked-flat condos which MV has struggled to produce.
Agenda item: 7.1
—Councilmember Lucas RamirezFeb. 10, 2026 City Council Meeting
2026-02-10
5:46:20		Allow (not require) commercial uses in R3-A subdistrict
detailsMotion (carried 3-1) directing staff to depart from the staff recommendation by allowing — not requiring — commercial uses in the R3-A subdistrict where appropriate (e.g. arterial frontage, large lots), so neighborhood-serving uses like the California Street Market are not foreclosed.
Why notable: Departure from staff rec; addresses 'commercial desert' problem in R3-A areas. Live-work / corner store-style flexibility.
Agenda item: 7.1
—Councilmember Lucas RamirezFeb. 10, 2026 City Council Meeting
2026-02-10
4:53:06		Get Rental Housing Committee input on CSFRA Charter cleanup
detailsDirection (consensus, articulated by Mayor) for the City Attorney to seek RHC input on the proposed CSFRA technical cleanup — at minimum the municipal-code reference fix, with willingness to consider any RHC-flagged additional technical edits.
Why notable: Compromise position: the Vice Mayor wanted a single ballot measure with no substantive RHC additions, but Council agreed RHC input was prudent.
Agenda item: 6.1
before next returnMayor Emily Ann RamosFeb. 10, 2026 City Council Meeting
2026-02-10
1:58:20		Include condo-conversion authority in condo-liability platform work
detailsAsked staff to add language so the condo-liability platform item also covers apartment-to-condo conversions (so existing rentals can be converted to ownership), as a complement to new-build condo defect reform.
Agenda item: 2.1
2026-02-24Councilmember John McAlisterFeb. 10, 2026 City Council Meeting
2026-02-10
1:51:48		Support worker housing in offices and offices-as-transitional-housing
detailsAsked staff to add platform support for legislation that allows or encourages worker housing in offices/public-storage and that facilitates use of offices as homeless transitional housing (a quicker fix than full office-to-apartment conversion).
Agenda item: 2.1
2026-02-24Councilmember Alison HicksFeb. 10, 2026 City Council Meeting
2026-02-10
1:50:08		Engage on housing-element treatment of homelessness
detailsAsked staff to engage early on state-level changes to how homelessness is treated in the housing element, including possibly adding a 15% AMI designation and resisting approaches that 'dump' homelessness solutions on a subset of cities.
Agenda item: 2.1
2026-02-24Councilmember Alison HicksFeb. 10, 2026 City Council Meeting
2026-02-10
1:48:03		Track SB 79 follow-on legislation; seek statutory CEQA exemption
detailsDirection to staff/lobbyists to track all SB 79 follow-on legislation, especially anything affecting local-alternative implementation, extended timelines for impacted cities, statutory CEQA exemption for SB 79 alternatives, and protections for mixed-use (not housing-only) at TOZ stations.
Why notable: MV is one of the most SB-79-impacted Bay Area cities (>20% land mass) so any tweaks materially change local exposure.
Agenda item: 2.1
2026-02-24Councilmember Alison HicksFeb. 10, 2026 City Council Meeting
2026-02-10
1:43:21		Rewrite platform item C-33 on inclusionary + density bonus
detailsAsked staff to revisit and clarify legislative platform item C-33 to add language supporting legislation that strengthens cities' inclusionary housing authority and opposes use of the State Density Bonus Law (or other mechanisms) to reduce the number or affordability of inclusionary units.
Why notable: Targets a specific MV concern: bad-actor developers using SDBL to dilute inclusionary requirements; revives a Eva-era MV-sponsored bill theme.
Agenda item: 2.1
2026-02-24Councilmember Lucas RamirezFeb. 10, 2026 City Council Meeting
2026-02-10
1:36:38		Pursue pro-housing-city carrots in housing-element process
detailsDirection to staff/lobbyists to push for state legislation giving pro-housing-designated cities meaningful process benefits (e.g. extended SB 79 local-alternative timelines, separate HCD review queues with assumed completeness, Builder's Remedy relief), rather than only funding incentives.
Why notable: Carrot-vs-stick framing for pro-housing designation; could buy MV more time on SB 79 implementation given >20% land impact.
Agenda item: 2.1
2026-02-24Councilmember Chris ClarkFeb. 10, 2026 City Council Meeting
2026-02-10
1:33:24		Add several new state platform items (pro-housing, soft story, condo liability)
detailsAsked staff to add to the state legislative platform: support legislation that rewards pro-housing cities with funding/permitting flexibility; support funding for soft-story seismic retrofits; support construction-defect liability reform for condos; CEQA tribal-consultation capacity assistance; stormwater management funding/TA; and ALPR regulation.
Why notable: Construction defect / condo liability reform is a long-running ask that would unblock for-sale condo production.
Agenda item: 2.1
2026-02-24Councilmember Pat ShowalterFeb. 10, 2026 City Council Meeting
2026-02-10
1:29:37		Add single-stair reform to legislative platform
detailsAsked staff to look into single-stair reform legislation (Asm. Lee's prior work) and bring it back as a possible addition to the city's state legislative platform.
Why notable: Single-stair reform is a YIMBY-priority code change that lets mid-rise multifamily be built more cheaply; not previously in MV's platform.
Agenda item: 2.1
—Councilmember Lucas RamirezFeb. 10, 2026 City Council Meeting
2026-01-29
1:50:53		Engage state legislators on BMR-unit-distribution loophole in housing law
detailsSuggested the City try to plug in with local state legislators who have advanced housing law to address the unsavory consequence that Density Bonus Law lets developers cluster smaller BMR units in one place; asked for state-level requirements for general consistency in size, quality, and material across BMR and market-rate units.
Why notable: Pushes a state legislative-advocacy angle from the EPC dais beyond project approval scope.
Agenda item: 5.1
—Chair Alex NuñezFebruary 4, 2026 Environmental Planning Commission …
2026-01-29
1:52:49		Plant more mature trees so the site has shade at opening
detailsRequested that the applicant (and staff via conditions of approval) include more mature-grown trees in the replanting plan so there is at least a semblance of shade when the project takes shape, given how small the canopy will be at start with 440 newly planted trees.
Why notable: Replanting is at 2:1 ratio per staff rec, but tree maturity at planting is not specified; commissioner wants larger specimens.
Agenda item: 5.1
—Commissioner Shwetha SubramanianFebruary 4, 2026 Environmental Planning Commission …
2026-01-29
1:41:02		Add Superfund/Cortese coverage to staff report before Council hearing
detailsAsked staff to add discussion of the site's Superfund nature and Cortese-list status to the staff report when this project goes to City Council, so Council members are not blindsided as he was by the late-arriving Hogan Lovells letter.
Why notable: Direct request to amend the report for the Council leg; not in current staff materials.
Agenda item: 5.1
before Council hearingCommissioner Hank DempseyFebruary 4, 2026 Environmental Planning Commission …
2026-01-29
1:40:30		Find a way to save heritage trees along North Whisman frontage
detailsJoined Commissioner Subramanian's request and asked staff/applicant to find some way to save the heritage trees along the Whisman frontage (which he described as the legitimate heritage trees on the site, unlike the decapitated redwoods along the south).
Why notable: Reinforces the tree-retention ask beyond staff recommendation; staff rec approved removal of 139 heritage trees.
Agenda item: 5.1
—Commissioner Bill CranstonFebruary 4, 2026 Environmental Planning Commission …
2026-01-29
1:40:09		Convey to Council that EPC opposes any future development-agreement extension
detailsAsked staff to convey to City Council that at least one Commissioner says no to any 10-year development agreement or further accommodations for this applicant beyond the concession and 20 waivers already granted; the applicant should live within the normal process going forward.
Why notable: Pre-emptive signal to Council against future giveaways; not part of staff's recommended findings.
Agenda item: 5.1
—Commissioner Bill CranstonFebruary 4, 2026 Environmental Planning Commission …
2026-01-29
1:36:46		Rework bioswale design to save best heritage trees on Whisman frontage
detailsAsked the applicant (and implicitly staff via conditions) to rethink the bioswale/bioretention design along North Whisman to preserve the four or five heritage trees identified by the arborist as in the best condition, rather than removing 139 of 151 heritage trees as proposed.
Why notable: Tree retention not in staff rec; staff said state Density Bonus Law gives little discretion to require design modifications.
Agenda item: 5.1
—Commissioner Shwetha SubramanianFebruary 4, 2026 Environmental Planning Commission …
2026-01-21
2:34:18		Encourage applicant to design in delivery/loading capacity for 490 E. Middlefield
detailsUrged the 490 East Middlefield applicant, while still in early development, to work with the city to find a solution for on-site delivery and loading capacity (Amazon, UPS, FedEx, DoorDash), citing observed enforcement and parking-tightness problems on the California/Rengstorff bike-lane corridor where designated loading spots are bypassed.
Why notable: Pushes applicant beyond staff's recommended conditions of approval to add loading-space capacity; staff cautioned against imposing a non-objective standard.
Agenda item: 5.2
—Commissioner José GutiérrezJanuary 21, 2026 Environmental Planning Commission …
2026-01-07
3:43:13		Expand ground-floor commercial beyond R3-D (start with R3-C, explore R3-B)
detailsBy majority sentiment, the EPC asked staff to allow ground-floor commercial in additional R3 sub-districts beyond just R3-D - at minimum R3-C, with staff to explore extending it to R3-B as well. Commissioners stressed letting the market decide viability rather than zoning out small neighborhood-serving retail.
Why notable: Directly modifies a core staff recommendation that limited dedicated commercial spaces to R3-D; follows public-comment requests including from MV YIMBY and SV@Home.
Agenda item: 5.1
—Commissioner Bill CranstonJan. 7, 2026 Environmental Planning Commission
2026-01-07
3:40:59		Replace the 'stick' lot-consolidation incentive with carrots
detailsBy majority sentiment (Nuñez, Pham, Donahue, Cranston, Gutiérrez), the EPC declined to support the staff's proposed lot-consolidation incentive (which would cap small R3-D lots at roughly half the zone's allowed density unless owners consolidate) and asked staff to come back with positive incentives (e.g. expedited review, density/height bonuses) rather than a punitive density cut.
Why notable: Direct rejection of the staff approach to one of the Council-set goals for the project; staff agreed to redesign before going to Council.
Agenda item: 5.1
—Commissioner Bill CranstonJan. 7, 2026 Environmental Planning Commission
2026-01-07
3:19:10		Add operational hours and noise limits to live-work standards
detailsSubramanian asked staff, when developing live-work operational standards, to add limits on operating hours and noise levels so commercial activity doesn't extend beyond residential living standards or disturb neighbors.
Why notable: The staff list of operational standards Anderson read out did not include explicit operating-hours or noise caps.
Agenda item: 5.1
—Commissioner Shwetha SubramanianJan. 7, 2026 Environmental Planning Commission
2026-01-07
3:09:45		Spell out targeted operational standards for live-work units to Council
detailsPham asked that when staff carries the live-work approach forward to Council, the report describe the targeted operational standards (use limits, signage, noise, customer/delivery limits, etc.) in more detail so Council can see what controls actually accompany allowing live-work throughout R3.
Why notable: Live-work is a new use type for MV; Council direction depends on being able to see the guardrails staff envisions.
Agenda item: 5.1
—Commissioner Tina PhamJan. 7, 2026 Environmental Planning Commission
2026-01-07
3:09:07		Map all R3/R4 ped cut-through opportunities, not just the two staff named
detailsPham asked staff, if R4 is going to be folded into R3, to at minimum identify all on-site circulation / pedestrian cut-through opportunities across all R3 and R4 areas before going to Council, rather than codifying only the two staff-identified locations (Rengstorff Park access and San Antonio Caltrain access).
Why notable: Public commenter Daniel made the same systemic point; a citywide map would lock in connectivity that is otherwise lost case-by-case.
Agenda item: 5.1
—Commissioner Tina PhamJan. 7, 2026 Environmental Planning Commission
2026-01-07
1:40:41		Include R3 acreage breakdown by sub-district in future memos
detailsDempsey asked staff to add the acreage share of each R3 sub-district (A/B/C/D) to future versions of the memo. He noted he'd assumed roughly equal shares but the actual figures (B=564 ac; C=134; D1=138; D2=138; A=61) materially change how to think about decisions like ground-floor commercial scope.
Why notable: Frames the policy debate; B is by far the largest sub-district, which changes the stakes of where retail and density rules apply.
Agenda item: 5.1
—Commissioner Hank DempseyJan. 7, 2026 Environmental Planning Commission
2026-01-07
0:58:45		Clarify whether interior 'pocket parks' on ped paths count as POPA
detailsCranston asked staff to clarify in the future whether the small open-space symbols shown along internal cut-throughs in the design diagrams would be treated as Privately Owned Publicly Accessible (POPA) open space. He worried developers could get parkland-dedication credit for tiny interior open areas not visible from the street.
Why notable: Goes to whether developers get parkland credit for amenities that aren't really publicly accessible.
Agenda item: 5.1
—Commissioner Bill CranstonJan. 7, 2026 Environmental Planning Commission
2026-01-07
0:40:19		Clarify shared-passage rules between adjacent R3 sites
detailsCranston flagged that the proposed 7-foot side setbacks plus an interim fence on the property line would yield two unusable strips rather than a single shared passage; asked staff to look at this and address how shared cut-throughs along property edges actually combine in practice.
Why notable: Could materially affect whether ped cut-throughs work on R3-D infill until both sides redevelop.
Agenda item: 5.1
—Commissioner Bill CranstonJan. 7, 2026 Environmental Planning Commission
2025-12-16
5:32:23		Prioritize biggest-impact homeownership programs and pursue funding partnerships
detailsOn the homeownership strategy scope, Hicks directed staff to focus on programs that produce the most results relative to resources used, and to actively explore funding partnerships given the disappearance of the BAFA bond and absence of federal funding for affordable housing.
Why notable: Adds a prioritization filter and a partnerships dimension that aren't explicit in the recommended scope.
Agenda item: 7.1
—Councilmember Alison HicksDec. 16, 2025 City Council Special Meeting
2025-12-16
5:35:11		Make Task 3 stakeholder outreach citywide and lifecycle-focused
detailsOn the homeownership strategy scope, the Mayor directed that Task 3 (stakeholder outreach) be citywide and consider the full lifecycle of someone's housing journey in Mountain View - e.g., a renter at The Sevens who might transition into ownership - rather than only large/small developers, financial institutions, and one general public meeting as proposed.
Why notable: Broadens staff's proposed Task 3 outreach list (which focused on developers, financial institutions, employers) to include current renters across the city.
Agenda item: 7.1
—Mayor Ellen KameiDec. 16, 2025 City Council Special Meeting
2025-12-16
5:34:19		Prioritize state legal-reform advocacy on construction-defect liability
detailsOn Task 6, McAlister directed staff to focus on what they can change including pushing for state legal reform on the 10-year construction-defect liability, arguing builders won't build condos until that law changes. Echoes Showalter's SPUR / construction liability ask, but framed as a Council advocacy priority.
Why notable: Adds a state-advocacy dimension to a study scope that, as proposed by staff, focused on local zoning/process barriers.
Agenda item: 7.1
—Councilmember John McAlisterDec. 16, 2025 City Council Special Meeting
2025-12-16
5:31:23		Look at SPUR's construction-defect liability reform work in condo barriers task
detailsOn the homeownership strategy scope, Showalter directed that as part of Task 6 (Barriers to Condominium Development) staff look into the work SPUR is leading on construction-defect / construction liability reform, as the 10-year liability period is widely cited as a key barrier to condo construction.
Why notable: Adds an explicit external partnership/topic to the Task 6 scope that staff did not include in their recommended scope of work.
Agenda item: 7.1
—Councilmember Pat ShowalterDec. 16, 2025 City Council Special Meeting
2025-12-16
5:34:03		Study AMI ranges higher than 200% in homeownership strategy
detailsOn the Low/Middle-Income Homeownership Strategy scope, McAlister voted 'yes and no' on the staff-recommended 50-200% AMI framework, asking staff to study an AMI range higher than 200% so analysis reflects realistic Mountain View ownership scenarios where 200% is borderline. Mayor Kamei said she would also be open to going above 200%.
Why notable: Modifies staff's recommended AMI scope (50-200%) for the homeownership study.
Agenda item: 7.1
—Councilmember John McAlisterDec. 16, 2025 City Council Special Meeting
2025-12-16
4:30:17		Lobby state legislators on impacts of recent housing laws
detailsShowalter directed that the Council needs to be advocating with state legislators about the consequences of recent housing laws (AB 2011, SB 6, etc.), arguing they go beyond intended consequences and that a pro-housing designation has not earned MV any trust or flexibility from the state. Hicks echoed this and Showalter said it would be discussed more in the next item (the legislative platform/work plan context).
Why notable: Future advocacy posture. Not part of the staff rec on item 6.1 but directs staff/Council to use the legislative platform process to push back on state housing laws.
Agenda item: 6.1
—Councilmember Pat ShowalterDec. 16, 2025 City Council Special Meeting
2025-12-16
4:45:08		Exclude three Evandale parcels from Housing Element 1.1G rezoning
detailsThe Mayor proposed, and the motion-maker (Ramirez) accepted as a friendly amendment, modifying the staff recommendation to exclude three Evandale Precise Plan parcels (existing small businesses including a market and dry cleaner) from the rezoning, using the alternative zoning option staff had analyzed. Goal is to preserve neighborhood-serving small businesses where AB 2011 does not apply.
Why notable: Direct modification of staff's recommendation on a Housing Element implementation item; staff had recommended rezoning all parcels including these three.
Agenda item: 6.1
—Mayor Ellen KameiDec. 16, 2025 City Council Special Meeting
2025-12-09
3:57:45		Prioritize completing the downtown historic register
detailsMcAlister moved to add "we direct staff to concentrate on finishing the register for the downtown area" as a priority ahead of citywide register work. The City Attorney advised this could be legally problematic (conflict-of-interest recusals would be needed for the downtown-specific segment), and Clark noted recusals would be required. The direction was modified to a general citywide criterion for prioritization rather than a geographically-specific instruction. Ultimately subsumed into the broader motion.
Agenda item: 6.1
—Councilmember John McAlisterDec. 9, 2025 City Council Meeting
2025-12-09
3:32:35		Return with community-nomination process for historic districts
detailsStaff's recommendation included a nominations/listing/delisting process but was silent on a detailed community-nomination procedure for historic districts. Ramirez added direction for staff to "think through how do we make sure that there's ample noticing and participation from everyone who would be impacted by the establishing of a district" and to return with district-nomination options. Incorporated into the motion.
Agenda item: 6.1
—Councilmember Lucas RamirezDec. 9, 2025 City Council Meeting
2025-12-09
3:09:37		Remove religious/institutional properties from register until Q2 2026 return
detailsStaff confirmed religious-site properties would be removed from the Q2 2026 recommendation due to the controversy that emerged from public comment. This was not explicitly in the staff recommendation as presented — it was a commitment made in response to Council questions.
Agenda item: 6.1
Q2 2026 returnMayor Ellen KameiDec. 9, 2025 City Council Meeting
2025-12-09
3:19:38		Annotate register list by federal/state eligibility and criteria type
detailsClark asked staff to annotate the draft register list with which properties would likely qualify for federal or state register listing, and which are on the local list solely because of design/age criteria versus a historic person, event, or association. This "matrix" approach was not in the staff recommendation. Incorporated into the final motion.
Agenda item: 6.1
—Councilmember Chris ClarkDec. 9, 2025 City Council Meeting
2025-12-09
4:15:10		Add owner sentiment to criteria matrix for historic register list
detailsClark added that when staff brings back the criteria matrix for the register, they should also include "outreach to the owners to obtain their sentiment." This was not in the staff recommendation. Adopted as a friendly amendment to the motion.
Agenda item: 6.1
when staff brings back the criteria matrixCouncilmember Chris ClarkDec. 9, 2025 City Council Meeting
2025-12-09
2:51:24		Streamline historic permits for rear additions and non-facade alterations
detailsThe staff recommendation had streamlining provisions, but Hicks pushed for more: specifically exempting rear additions that don't alter the front facade, and "things that show to some degree from the front but don't alter the front facade." She also asked staff to evaluate making ADU construction on historic properties easier. Ramirez incorporated the rear-addition streamlining into the motion; McAlister rejected the ADU portion as a seconder, creating a partial friendly amendment.
Agenda item: 6.1
—Councilmember Alison HicksDec. 9, 2025 City Council Meeting
2025-11-18
4:48:47		Staff to work with applicant on loading zone on Victor Way
detailsThe applicant had asked for a permanent loading zone on El Camino Real. Staff had not recommended this. Showalter suggested evaluating a loading zone on the quieter Victor Way instead. Kamei incorporated this into the motion: "for staff to work with the applicant to assign the loading zone on Victor Way." Passed unanimously.
Agenda item: 7.1
—Councilmember Pat ShowalterNov. 18, 2025 City Council Meeting
2025-11-18
4:34:43		Deny 8-year entitlement request; use standard 2+2 structure for 749 W ECR
detailsThe applicant had submitted a last-minute (day-of-meeting) letter requesting an 8-year entitlement period instead of the standard 2-year with 2-year extension. The staff recommendation was silent on this request (because the letter arrived hours before the meeting). Kamei's motion explicitly denied the 8-year request and directed use of the standard 2+2 structure.
Agenda item: 7.1
—Mayor Ellen KameiNov. 18, 2025 City Council Meeting
2025-11-05
2:02:23		Agendize SB 799 analysis before July 2026 effective date
detailsSB 799 (requiring cities with precise plans to allow upzoning in certain areas, effective July 2026) had just been signed by the Governor. Multiple commissioners explicitly asked that: staff prepare an analysis of SB 799's effect on the Downtown Precise Plan and Moffett Precise Plan before the law takes effect; the EPC be given an opportunity to recommend to Council before staff presents to Council; and the item be formally agendized. Staff (Murdock) did not commit to a timeline. The informal direction from the commission majority was to move faster than staff proposed.
Agenda item: 6
2026-07-01Commissioner CranstonNov. 5, 2025 Environmental Planning Commission
2025-10-28
3:02:47		Close TRAO temp-to-permanent relocation 'double-dip' loophole
detailsClark proposed, Ramirez relayed as a friendly amendment, and Ramos accepted: language clarifying that if a tenant who has been temporarily relocated voluntarily elects not to return (for reasons other than the landlord's failure to complete work timely), any temporary relocation assistance already paid is credited against the permanent relocation payment so the two cannot be stacked. If the landlord causes the unit to become unavailable, the tenant retains both temporary and full permanent benefits.
Why notable: Eliminates an incentive in the originally drafted ordinance for tenants to claim temporary relocation and then convert to permanent in order to receive both payments.
Agenda item: 6.3
—Councilmember Chris ClarkOct. 28, 2025 Regular Meeting of Mountain View …
2025-10-28
2:56:07		Address Section 8/voucher-tenant scenarios in TRAO admin guidelines
detailsHicks asked, and the motion-maker accepted, that staff gather additional information on tenants whose rent is covered by Section 8 or other housing-authority vouchers (where the agency, not the tenant, holds the lease) and incorporate handling of voucher situations into the TRAO administrative guidelines.
Why notable: Raised by a public commenter (small landlord with mostly subsidized tenants) and not addressed in the original staff recommendation.
Agenda item: 6.3
—Councilmember Alison HicksOct. 28, 2025 Regular Meeting of Mountain View …
2025-10-28
3:11:33		Staff to return with a specific recommended dollar figure for the moving-cost cap
detailsAfter Council expressed reluctance to set a cap from the dais, the City Manager confirmed (and Council accepted) that staff would come back with a specific recommended cap figure to be incorporated into the administrative guidelines, with the cap referenced in the ordinance and indexed to CPI.
Why notable: Operationalizes the Showalter cap direction with a concrete deliverable (a recommended dollar amount) tied to the second reading or follow-up agenda item.
Agenda item: 6.3
—City Manager Kimbra McCarthyOct. 28, 2025 Regular Meeting of Mountain View …
2025-10-28
2:49:56		Develop a cap on TRAO moving-cost reimbursements (true-cost up to a cap)
detailsShowalter offered, and Ramos accepted, a friendly amendment directing staff to develop a cap on moving expenses through the administrative guidelines, structured as reimbursement of actual costs up to the cap rather than a flat payment, and to modify the ordinance to reference that cap (per the City Attorney's clarification).
Why notable: Closes the open-ended moving-cost exposure (50-mile, no-cap) that staff had recommended; addresses concerns raised by landlords and Councilmembers about uncapped reimbursements (e.g. grand pianos, art).
Agenda item: 6.3
—Councilmember Pat ShowalterOct. 28, 2025 Regular Meeting of Mountain View …
2025-10-28
2:49:46		Hold landlord/tenant stakeholder meetings to develop TRAO temp-displacement admin procedures
detailsAs part of the TRAO motion, Vice Mayor Ramos directed staff to convene stakeholder meetings (CAA, other landlord groups including BAHN, and tenant groups) when developing the administrative procedures for the new temporary displacement section, providing flexibility to address unforeseen circumstances and other operational details before the procedures are finalized.
Why notable: Responds directly to public comment that no housing-provider outreach occurred between the Dec 2024 study session and this hearing; not in the original staff rec.
Agenda item: 6.3
—Councilmember Emily RamosOct. 28, 2025 Regular Meeting of Mountain View …
2025-10-28
0:15:04		Bring tenant relocation ordinance back for first reading on or before Dec 16
detailsModified motion directs staff to bring the tenant relocation ordinance back for first reading on or before December 16, 2025, incorporating all amendments discussed tonight, with second reading expected on consent at the next regular meeting (late January). Passed 5-2.
Why notable: Departs from staff's recommended path of adopting first reading that night; instead routes back through additional public input window before the holidays.
2025-12-16Councilmember Emily RamosOct. 28, 2025 Regular Meeting of Mountain View …
2025-10-15
3:34:10		Strengthen heritage-tree protections in tandem with BUFP
detailsGutiérrez asked when the heritage-tree ordinance will be revised to actually protect heritage trees, noting they 'are taken out over and over' under current rules. Staff confirmed work on a phased Heritage Tree Ordinance update (tree size and scope of protection, species considerations, appeal process) is already underway as a 'low hanging fruit' tied to BUFP. Commissioner Yin (ts 14467) reinforced the directive: clear, enforceable guidelines for when heritage trees can be removed, since 120+ mature trees can be lost 'in an instant.' Commissioner Donahue (ts 14663) added a specific ask that replacement trees be heritage-size from planting to prevent the cut-then-plant-dwarf workaround.
Why notable: Heritage Tree Ordinance reform is treated in BUFP as one of many actions; commissioners are pushing it forward as the top deliverable and adding teeth (no-net-loss / replacement-size requirements).
Agenda item: 6.1
—Chair José GutiérrezOct. 15, 2025 Environmental Planning Commission
2025-10-15
3:53:18		Tighten the 25-action list and identify low-hanging fruit
detailsCranston said the 25 actions are too many and too vague ('establish, conduct, explore' are weasel words) and asked staff to come back with a tighter list with more specificity, prioritized as low-hanging fruit the city can actually deliver — explicitly naming the heritage tree ordinance update as a candidate quick win. He warned against making this 'another general plan list' that sits undone.
Why notable: Staff treated the action list as a guiding/visionary document; commissioner is directing staff to make it tactical and prunable before adoption.
Agenda item: 6.1
—Commissioner Bill CranstonOct. 15, 2025 Environmental Planning Commission
2025-10-14
3:01:01		Remove floor plans from gatekeeper application package requirement
detailsThe staff recommendation and draft ordinance required floor plans as part of the gatekeeper application. Ramirez moved to remove this requirement, arguing that floor plans at the pre-application stage are premature and expensive, and that they "always change" before a formal application is submitted. This change was not in the staff recommendation. It passed as part of the substitute motion.
Why notable: Staff had not recommended this, McAlister and Kamei opposed it as a last-minute tweak that hadn't gone through the normal public process, and it represents actual policy relief for applicants.
Agenda item: 6.1
—Councilmember Lucas RamirezOct. 14, 2025 Joint Meeting of Mountain View City …
2025-10-14
3:00:00		Exempt conforming rezonings from gatekeeper process
detailsThe staff recommendation did not include this exemption. Ramirez moved to amend to "exempt from the gatekeeper process applications for a conforming rezoning" — specifically, rezonings that align an existing parcel with its General Plan land use designation. This would allow property owners with misaligned zoning to rezone without a full gatekeeper hearing. The substitute motion passed 4-3.
Why notable: Staff had not recommended this, McAlister and Kamei opposed it as a last-minute tweak that hadn't gone through the normal public process, and it represents actual policy relief for applicants.
Agenda item: 6.1
—Councilmember Lucas RamirezOct. 14, 2025 Joint Meeting of Mountain View City …
2025-10-01
3:51:04		Keep major alterations on State/National-eligible properties at Council, not ZA
detailsModify staff's three-tier development review proposal so that major alterations to properties eligible or listed on the California or National Register continue to require City Council review rather than dropping to ZA-level approval; minor alterations may go to ZA or staff.
Why notable: Walks back a streamlining piece of staff's recommendation; preserves Council jurisdiction over the most consequential historic projects.
Agenda item: 5.1
—Commissioner Bill CranstonOctober 1, 2025 Meeting of the Environmental …
2025-10-01
3:49:57		Treat downtown floor-plate / lot consolidation as a major alteration
detailsWhen staff defines the new minor/major-alteration tiers for the development review process, examine whether consolidating multiple downtown storefront lots into a single large floor plate — even behind a preserved facade — should be treated as a major alteration, because losing the granular storefront pattern destroys downtown's character even when individual facades remain.
Why notable: Pushes the integrity test beyond exterior facade preservation to interior floor-plan and lot pattern, which staff had not framed that way; adopted into Anderson's summary motion.
Agenda item: 5.1
—Commissioner Joyce YinOctober 1, 2025 Meeting of the Environmental …
2025-10-01
3:37:34		Exclude owner negligence as a delisting basis
detailsWhen staff drafts the delisting findings, write the language so that owner negligence (deliberately letting a property decay or become a hazard) cannot be used as a path to delist; pair this with stronger enforcement provisions so demolition-by-neglect is not a backdoor to removal from the register.
Why notable: Closes a perceived loophole staff had not foreclosed in writing; folded into final motion language.
Agenda item: 5.1
—Commissioner Bill CranstonOctober 1, 2025 Meeting of the Environmental …
2025-10-01
3:10:00		Recommend Council pursue proactive (not just passive) measures for downtown historic properties
detailsForward to Council a recommendation that, for the downtown 100–200 block properties on the ineligible list (Rogers Building, Scarpa's), the city consider active measures — persistent owner engagement and possible city financial resources — to push restoration before the 4-year/7-year delisting triggers, rather than relying solely on Mills Act and existing passive incentives.
Why notable: Adds an affirmative city-action ask absent from the staff recommendation; specifically targets the Rogers Building and downtown character. Passed by straw poll.
Agenda item: 5.1
—Vice Chair Alex NuñezOctober 1, 2025 Meeting of the Environmental …
2025-10-01
3:05:58		Add a 4-year HP-permit-application milestone inside the 7-year window
detailsWithin the 7-year phase-out, require owners of the five draft-ineligible properties to submit a historic preservation permit application with a restoration concept by year four; failure to submit results in delisting at that point rather than at year seven. Refined with Director Murdock.
Why notable: Two-stage gate (4yr submit / 7yr complete) replaces staff's single 5-year cliff and was not in the staff report.
Agenda item: 5.1
—Commissioner Joyce YinOctober 1, 2025 Meeting of the Environmental …
2025-10-01
2:54:42		Extend ineligible-property phase-out from 5 to 7 years
detailsReplace the staff-recommended 5-year window for the five draft-ineligible properties with a 7-year window before automatic delisting, to give owners realistic time to find a qualified architectural historian, design, permit, and construct restoration work.
Why notable: Lengthens staff timeline by 40%; tied to concern that historic-rehab consultants and permitting are slow and 5 years is unrealistic. Adopted by consensus.
Agenda item: 5.1
—Commissioner Tina PhamOctober 1, 2025 Meeting of the Environmental …
2025-10-01
2:38:43		Notify every candidate-listed property owner that they are on the list
detailsAs a condition of EPC support for including the draft list of properties on the MV Register, staff must affirmatively communicate with every property owner identified as a candidate so they learn from the city, not later by surprise, that their property is being considered for listing.
Why notable: Adds an outreach/notice condition that staff had not committed to in writing; staff confirmed letters were sent but Cranston pressed for it as an explicit obligation.
Agenda item: 5.1
—Commissioner Bill CranstonOctober 1, 2025 Meeting of the Environmental …
2025-09-23
0:04:20		Follow up on multilingual noticing compliance for tenant notification letters
detailsRamos noted that tenant notification letters for this project were in English only, and that one Spanish-speaking tenant received a Spanish version only because she physically attended a community meeting. Ramos pressed staff on whether residents had applied for relocation assistance. This was not a formal motion, but constituted direction to staff to follow up on multilingual noticing compliance — a gap the staff report did not address.
Agenda item: 6.1
—Vice Mayor Emily RamosSept. 23, 2025 Regular Meeting of Mountain View …
2025-09-09
0:30:06		Keep grant-eligible structure open for CLT Technical Assistance program
detailsStaff's recommendation structured the program strictly as a loan. Clark moved the staff recommendation but added direction to "keep the option open" for grants — specifically where a bond or matching funds from a nonprofit would benefit the CLT. Staff (Reed) immediately confirmed this would be incorporated by noting the NOFA would be "structured as a flexible loan, but keep the option open and include something in our implementation." This expansion from loan-only to loan+optional-grant was not in the original staff recommendation.
Agenda item: 7.1
—Councilmember Chris ClarkSept. 9, 2025 Joint Meeting of Mountain View City …
2025-08-26
2:20:40		Consult on single-stair design standards beyond current ordinance scope
detailsHicks says she wants staff to think about "other design elements that come along with single stairways" as the City moves to adopt the code. This appears to be a prompt for staff to consult further on design implications before the ordinance comes back for final adoption.
Why notable: The staff recommendation was to introduce the ordinances for first reading; Hicks is asking staff to do additional design consultation beyond the scope of the staff report.
before the ordinance comes back for final adoptionCouncilmember Alison HicksAugust 26, 2025 Special Meeting of the Mountain …
2025-08-26
2:07:04		Request status update on single-stair bill (AB 835) via intergovernmental relations
detailsDuring deliberation on the building code ordinances, Ramirez requests a status update on AB 835 (State Fire Marshal single-stair building standards). Kamei clarifies this should go through the city's state lobbying team, characterizing it as an Item 8 (informal staff direction) request rather than a formal motion.
Why notable: The building code ordinance staff recommendation made no mention of AB 835 advocacy or monitoring. Council is adding a state-bill tracking task to staff's work. Treated as informal Item 8 direction, which is itself notable (Item 8 is typically reserved for council-only reports, not directing staff).
—Councilmember Lucas RamirezAugust 26, 2025 Special Meeting of the Mountain …
2025-06-24
6:14:28		Study higher-density Option 1 (R3-D2) for four specific change areas
detailsStaff recommended studying Option 2A (lower density, R3-D1) for the 13 remaining change areas. Ramirez proposed a compromise: lower density for 9 areas, but higher density (Option 1/R3-D2) for 4 specific areas (Del Medio North, California/Ortega, California/Latham/Rengstorff, Solano Apartments). This motion failed 5-2. Clark then moved a modified version which passed.
Why notable: The R3 reconsideration was itself a Council-initiated override of a prior vote — and within the reconsideration, Council again diverged from staff's recommendation, this time selecting higher density for specific change areas. This is council directing staff to study a denser zoning option than staff recommended for those four areas.
—Councilmember Lucas RamirezJune 24, 2025 Joint Meeting of Mountain View City …
2025-06-24
10:44:20		Evaluate neighborhood-serving commercial as new gatekeeper performance criterion
detailsShowalter proposes adding "neighborhood serving commercial" as a new optional performance criterion in the gatekeeper policy (gym, coffee house, child care, dental, drug store, satellite library, nonprofit space). Staff's recommendation did not include this criterion. Council agrees to have staff evaluate it.
Why notable: A new category of community benefit that staff had not surfaced in the draft policy. Council is expanding the menu of qualifying criteria beyond what staff recommended.
—Councilmember Pat ShowalterJune 24, 2025 Joint Meeting of Mountain View City …
2025-06-24
9:21:38		Return with objective criteria for project reconsideration (beyond two-year clock)
detailsBased on staff's response to Council question 75, Ramirez directs "Staff to return with a recommendation for objective criteria for a project that was rejected to be reconsidered. So right now it says a project must wait two years before submitting again" — he wants the standard to be based on objective criteria, not just the two-year clock.
Why notable: The staff draft policy had a two-year waiting period as the reconsideration standard. Ramirez is asking for a different regime based on objective criteria, creating a new staff task not in the original recommendation.
—Councilmember Lucas RamirezJune 24, 2025 Joint Meeting of Mountain View City …
2025-06-24
9:19:09		Require study sessions for all gatekeeper applications including streamlined
detailsStaff's draft Gatekeeper Policy G-9 said streamlined gatekeeper applications do not require a study session. Ramirez amends the motion so that "a study session of the City Council would be required even for streamlined projects." This addition is specifically noted as a departure from staff's recommendation.
Why notable: Adds a procedural requirement that slows the streamlined track for all gatekeeper applications, directly contrary to staff's recommendation. The motion passes 6-1.
—Councilmember Lucas RamirezJune 24, 2025 Joint Meeting of Mountain View City …
2025-06-10
5:35:06		Develop objective standards for heritage tree removal ordinance
detailsRamirez states that "the answer that the community is looking for is an improved heritage tree ordinance" with objective rather than discretionary criteria. He is directing staff — through the upcoming urban forestry and biodiversity plan process — to develop objective standards for heritage tree removal.
Why notable: The master fee schedule item was procedural (fee levels); Ramirez used it to articulate a policy direction for the heritage tree ordinance that was not in the staff recommendation. The staff noted this would come back via the PRC and then Council in early 2026.
in early 2026Councilmember Lucas RamirezJune 10, 2025 Joint Meeting of Mountain View City …
2025-06-10
5:25:31		Exempt heritage tree fees from master fee schedule update
detailsHicks moves to "accept the fee schedule as proposed but leave the heritage tree fees in their current state" — exempting the heritage tree appeal fee from the proposed fee schedule update. This passes.
Why notable: Staff recommended adopting the full fee schedule as proposed, including the heritage tree fees. Council modified the recommendation by carving out the heritage tree category for future policy discussion via the urban forestry plan.
—Councilmember Alison HicksJune 10, 2025 Joint Meeting of Mountain View City …
2025-05-27
5:30:08		San Antonio Phase 3: set DA vesting date to July 10, 2025
detailsAfter a recess to incorporate applicant clarifications, Councilmember Ramirez restated the motion to authorize staff to work with the applicant to modify the development agreement to establish a vesting date of July 10, 2025 (30 days after the planned second reading), preserving the rules-in-effect-as-of date the applicant had bargained for.
Why notable: Specific staff direction adding a vesting-date workstream not in the published staff recommendation.
Agenda item: 6.1
2025-07-10Councilmember Lucas RamirezMay 27, 2025 Regular Meeting of the Mountain View …
2025-05-27
5:09:02		San Antonio Phase 3: explore alternatives if LASD school deal fails
detailsOn item 6.1 (Village at San Antonio Center Phase 3 / Merlone Geier development agreement), Councilmember Ramirez's motion (seconded by Hicks, passed unanimously) added direction for staff to explore other mechanisms to effectuate the project without Merlone Geier's purchase of TDR square footage from the Los Altos School District in the event the City and LASD cannot reach a new funding and joint use agreement; the DA was also made effective no sooner than December 19, 2025.
Why notable: Significant policy hedge against failure of the school-district community-benefit pathway, not in the staff recommendation; tied to MV's gatekeeper / TDR expectations.
Agenda item: 6.1
2025-12-19Councilmember Lucas RamirezMay 27, 2025 Regular Meeting of the Mountain View …
2025-04-22
2:50:22		Take "Watch" position on SB457 overriding staff's Support recommendation
detailsStaff placed SB457 (Becker — housing element compliance / builder's remedy changes) on the consent calendar as a Support. Council pulled the item and, after substantive debate, voted to take a "Watch" position instead of Support, with Kamei and others expressing concern that the bill weakens builder's remedy.
Why notable: A significant policy departure from staff's recommendation. Staff recommended support; the council majority disagreed with the substantive policy and changed the city's legislative position. Ramirez explicitly said he preferred Oppose.
—Councilmember Ellen KameiApril 22, 2025 Regular Meeting of Mountain View …