Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Municipal Finance topic
No spam. Unsubscribe anytime.
Task force recommends earlier budget introduction, portfolio work sessions and clearer amendment rules
Summary
A budget review task force recommended moving the mayor’s budget introduction up 16 days, organizing council budget work sessions by department portfolios and adopting a standardized amendment process to give council more time and clearer procedures to review the city’s FY26 budget.
RJ Warren, the council chief of staff, presented recommendations from the Budget Review Task Force aimed at improving how Richmond’s mayoral budget is developed and reviewed by council. The group’s principal proposals include advancing the mayor’s budget submission by 16 days, structuring budget work sessions around departmental portfolios, instituting a standardized amendment process and increasing early collaboration between the mayor’s office and council.
Under the recommended schedule the mayor would introduce the budget on March 11; the first public hearing on the proposed budget would follow March 23. Council amendments would be due in early April (an example date cited was April 8), with subsequent public hearings on council amendments and a final adoption timeline allowing for May ordinances and a May 11 final vote if needed. The task force also recommended separating the school budget into a distinct ordinance to accommodate timing required by charter.
Warren said the recommendations are intended to provide council members, staff and the public more time to review a complex multi‑billion‑dollar budget, reduce last‑minute changes and make amendment deliberations more orderly. The task force proposed that council members seeking amendments gather co‑patrons so amendments could be considered in descending order of co‑patron count to expedite deliberations.
Several council members welcomed the extra time but pushed for codifying steps in ordinance or council rules so that the new timeline and practices are consistent year to year. Newer council members and some veterans called for greater transparency on department submissions, earlier public engagement, more readily accessible departmental budget requests and better training or tools (including Oracle/ERP access) for council staff to analyze departmental spending.
Council members also asked for a follow‑up discussion about non‑departmental grant processes and for the mayoral administration to publish its town‑hall schedule tied to budget development. The task force said it will reconvene after the next adopted budget to assess what worked and what still needs improvement.
No formal vote was taken on the task force report; members asked staff and the administration to proceed with drafting code changes, public schedules and standard operating procedures to implement the recommendations.
