Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Budget Transparency topic
No spam. Unsubscribe anytime.
Council divided over nonbinding call for earlier preliminary budget release
Summary
Councilmembers debated Resolution 2-26, which urges the County Executive to provide an earlier preliminary budget snapshot (April 1) to increase public input. Supporters said it would help stakeholders plan; the administration warned it could create extra workload for a small budget office and produce misleading drafts before state and union negotiations conclude.
A nonbinding resolution urging the County Executive to release a preliminary FY27 budget snapshot earlier in the year generated an extended debate on Feb. 10.
Councilman Volke, sponsor of Resolution 2-26, argued that earlier preliminary information — even if not final — would let community groups, unions and constituents provide input before the formal May 1 budget submission. "I'm asking you for a preliminary budget idea, and other counties do this as well," he said, stressing that transparency with the public differs from the frequent one‑on‑one briefings council members receive.
Budget Officer Chris Trumbauer cautioned that the county’s small budget staff is already under heavy workload constraints preparing the May 1 submission and said producing an additional formal product could jeopardize the charter-mandated deadline. He offered an alternative: provide memos or incremental updates and continued one-on-one briefings rather than creating a new deliverable that could be misread as final.
Councilmembers split on practical grounds. Supporters said an earlier snapshot would allow the public and stakeholders to prepare and respond; skeptics said state budget volatility and ongoing union negotiations could make an April snapshot misleading and that the budget office’s capacity is limited.
What’s next: The council did not take a vote at the work session; administration agreed to continue providing information to councilmembers and to discuss what additional public updates might be feasible without jeopardizing the May 1 deadline.
