Citizen Portal
Sign In

Get Full Government Meeting Transcripts, Videos, & Alerts Forever!

Get email alerts on the Financial Policy topic

No spam. Unsubscribe anytime.

Committee advances financial‑policy package: nonrecurring revenue limits, debt cap and two‑year budgeting (as amended)

Budget and Finance Committee · October 26, 2011
AI-Generated Content: All content on this page was generated by AI to highlight key points from the meeting. For complete details and context, we recommend watching the full video. so we can fix them.

Summary

The committee advanced a package of ordinances and a resolution to codify rules on nonrecurring revenues, set a 3.25% cap on general‑fund‑backed debt subject to a two‑thirds exception, harmonize budget calendars, and allow enterprise departments to adopt fixed two‑year budgets with a 5% trigger for adjustments; the budget analyst urged narrowing the controller’s discretion, and public commenters urged preserving flexibility for safety‑net programs.

The Budget and Finance Committee considered four related measures to strengthen the city's fiscal framework: (1) a nonrecurring revenue policy to restrict certain one‑time revenues (sale of land, abnormal fund‑balance peaks, prepayments) to nonrecurring expenditures; (2) a debt‑management policy establishing a 3.25% cap on general‑fund‑backed debt (with an exception available by two‑thirds Board vote and exclusions for debt that produces general‑fund savings or is backed by nondiscretionary revenue); (3) updates to administrative code and budget calendars to support a full two‑year budget cycle and five‑year financial planning; and (4) a resolution authorizing enterprise departments (Airport, Port, PUC) to adopt fixed two‑year budgets with a 5% trigger for second‑year adjustments.

Controller Ben Rosenfield framed the package as implementing Proposition A (2009) and described the package's tools to smooth year‑to‑year volatility, including a five‑year rolling average test to identify nonrecurring prior‑year fund‑balance above historical norms. He and budget staff also proposed an amendment of the whole to clarify interaction among rainy‑day reserves, the budget stabilization reserve, and the effective date of the policy, and to define discretionary revenue for the debt cap. The budget analyst supported the principle of restricting one‑time revenues to one‑time expenditures but recommended narrowing the ordinance’s open‑ended definition of eligible nonrecurring expenditures and giving the Board clearer recourse to challenge the controller’s future classifications.

Public testimony split: several speakers supported limits on certificates of participation and greater planning discipline; others — including the San Francisco Human Services Network — argued that one‑time funds have been essential to avert program closures and urged retaining flexibility to protect safety‑net services. Supervisors adopted the clerical amendment of the whole, discussed trade‑offs between fiscal discipline and program flexibility, and sent the package forward as amended with a committee recommendation.