Palo Alto Commons expansion draws neighbors' ire; council pauses decision

The El Alto City Council on May 5 heard more than two hours of public testimony on a proposed amendment to the Planned Community ordinance for Palo Alto Commons, a 121‑unit assisted‑living and memory‑care facility, but did not take a final vote and moved to continue the matter for a later meeting.

City staff presented the proposal as a relatively small addition to an existing senior care campus: 16 additional assisted‑living and memory‑care units and 172 square feet of support space, totaling about 6,891 square feet of new floor area. Emily Callas of Planning and Development Services told the council that “the existing parking meets the zoning minimum requirements for the existing and for the proposed addition.” Staff also recommended a categorical exemption under CEQA for existing facilities and advanced an ordinance to amend the property’s PC (planned community) conditions.

Why it matters: the project sits behind single‑family homes along Wilkie Way and neighbors told the council the addition would worsen long‑standing problems — loss of privacy, reduced sky and daylight, and spillover parking on residential streets. Opponents urged the council to require stricter daylight‑plane limits and to adopt the Planning & Transportation Commission’s recommendation to approve only seven interior units that would not face Wilkie Way.

What happened at the commissions: the application has a mixed record in the city’s advisory bodies. The Architectural Review Board recommended approval, finding the scale and privacy measures acceptable. The Planning & Transportation Commission recommended approval only for seven units “that do not face Wilkie Way,” and attached conditions including return of the Transportation Demand Management (TDM) plan for further review. Planning staff noted the project relies on several prior PC ordinances (PC‑5116 and PC‑3775) and that the existing public‑benefit commitments in the current PC ordinance should remain in force.

Neighbors and neighborhood groups pressed three main points: that the proposed massing would encroach into previously protected daylight and privacy protections, that visitor and staff parking already spills into Wilkie Way and other nearby streets, and that conditions approved decades ago were not reliably enforced. “This expansion threatens to drastically devalue Wilkie Way properties,” said Shashank Devekar, a Wilkie Way resident, describing the project’s potential financial impact on homeowners. Several residents showed photographs of cars parked in nearby streets, visitor spaces occupied by vendor vehicles, and examples they said documented noncompliance with earlier conditions.

Developer and operator responses: members of the Reller family, who own the site, and WellQuest, the proposed operator, defended the project as a local response to growing need for senior care. Architect Daniel Bowman and owner Steve Reller said the design fills existing stepbacks without increasing building height or reducing the minimum setbacks adjacent to single‑family lots. “We mismanaged that for 35 years and we can do better,” Reller said, describing recent operational changes. WellQuest’s representative, Steve Sandholtz, said most residents do not have cars, described a recent $5 million renovation, and said the operator is implementing valet, employee parking incentives and other TDM measures to reduce street spillover.

Planning details and staff clarifications: staff said the proposal would not change the building’s maximum height (remaining at about 32 feet, 6 inches) and would not alter the property’s existing setbacks. The project team described landscaping and window changes intended to increase privacy for adjacent backyards, removal of some second‑floor balconies, and permits‑level changes limited to interior infill of stepped areas. Staff also estimated development impact fees in the range of roughly $382,000 related to the addition.

Points of technical disagreement: several neighbors and some commissioners argued that the project should be evaluated under the more restrictive daylight‑plane standard for nonresidential buildings adjacent to single‑family zoning (a 3‑inch rise per 6 inches run at 10 feet), rather than the older 45‑degree / 10‑foot rule cited in the existing PC. That choice affects upper‑story massing facing Wilkie Way and is central to the neighborhood’s objections.

Decision and next steps: after extensive public comment — both for and against the project — the applicant declined a three‑minute rebuttal and the council did not vote. Mayor Laowing observed the length of public concern and suggested continuing the matter for a future meeting; the council accepted that approach and the item was carried forward without a final action. No date for resumption of the hearing was set in the transcript.

What remains unresolved: council members and staff flagged several follow‑ups the full record will need to show before final action: (1) whether the city will require the stricter daylight‑plane standard for the portions of the building facing single‑family lots; (2) a definitive, enforceable TDM and parking plan with clear monitoring and reporting requirements; (3) confirmation that existing PC public‑benefit commitments continue to apply; and (4) whether certain units should be restricted to interior locations, per the Planning & Transportation Commission recommendation.

The council’s pause preserves the council’s option to require design or operational changes and to seek additional findings, technical analysis, or enforceable mitigation before returning the proposal for decision. Advocates for added senior housing said the city needs more local assisted‑living and memory‑care capacity; many neighbors said they support senior care but not at the cost of their yards, sky and streets.

Officials and advocates who appeared at the hearing and on the record included the Planning and Development Services presentations and the project team from the Reller family and WellQuest. The council did not adopt any ordinance or take a final vote on the project at this meeting.