Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Special Project Policy topic
No spam. Unsubscribe anytime.
Cupertino council adopts new special‑project policy; residents urge $50,000 cap
Summary
The City Council voted to adopt a new special‑project policy that narrows what qualifies as a special project and requires council reapproval to reappropriate savings. Residents urged adding a fiscal cap and limits on staff time before projects proceed.
Get email alerts on the Special Project Policy topic
No spam. Unsubscribe anytime.
The Cupertino City Council adopted a new special‑project policy after a staff presentation and public comment, voting to approve the policy by unanimous vote.
City finance staff presented the policy changes and said the document narrows which items qualify as special projects, establishes reporting frequency and follow‑up, and requires council authority to reappropriate savings into new special projects. "Most notably, the policy requires that even if sufficient appropriations or budget exist to create a new special project ... we will need to come back to council on a consent item for the authority to reappropriate those funds," said Christine Alfaro, director of administrative services.
The policy removes recurring maintenance items and routine capital work from the special‑project listing; examples staff cited include annual pavement maintenance, small minor repairs and ongoing development projects. Alfaro told council that special projects are intended for one‑time operational efforts that are not part of a department’s base budget and sometimes require consultant support when staff vacancies or capacity prevent in‑house completion.
Councilmembers asked how the policy would work in practice. Councilmember Wong confirmed there is no dollar threshold in the policy: "There's no limit on the special project," Alfaro said. Vice Mayor Moore said she supported the clearer reporting and frequency provisions and requested the policy be brought back as part of the annual budget and policy review so council has time to consider implications separate from budget adoption.
Public commenters urged additional fiscal and process limits. Peggy Griffin said residents should set a lower discretionary threshold and asked council to require council review for any contract or project above "$50,000." She also urged limits on staff hours spent defining proposed projects before council review. Jennifer Griffin and another resident, Sam R., supported that position and urged tighter fiscal controls; Sam R. said he "heartily support[ed] this policy" and urged the council to adopt a $50,000 cap until public trust in discretionary spending is restored.
Council discussion clarified related contracting limits set by state law: staff said the municipal code references a state contract limit and that some contract‑approval authority rests with the city manager for amounts at or below the state threshold. Alfaro said that even where the city manager can approve contracts under that limit, the new policy would bring requests to reappropriate funds back to council on consent when projects fall outside base operations.
The policy was approved on a council motion and second; the council decision was recorded as carried unanimously. Staff said they will include special projects reporting in future quarterly financial updates and the annual policy review.
Next steps: staff will post the special‑project reporting format and include the policy in the materials for the next annual budget review and the city's policy inventory.
Ending: Council and staff noted the policy is intended to increase transparency around one‑time projects and consultant use; some residents asked the council to return with a dollar cap and a limit on pre‑agenda staff hours, items councilmembers said could be considered in future policy refinements.

