Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Municipal Budget topic
No spam. Unsubscribe anytime.
Salisbury officials flag structural budget gap and propose removing collective bargaining constraints
Summary
City staff told Salisbury City Council that rising personnel costs and reliance on one-time funds could exhaust reserves by FY2030 and recommended removing collective bargaining constraints to gain flexibility; council members debated alternatives including tax-base expansion and legal costs.
Get email alerts on the Municipal Budget topic
No spam. Unsubscribe anytime.
City Administrator Nick Rice told the Salisbury City Council at a work session on April 13 that the city’s long-term finances reflect a structural imbalance that could exhaust surplus reserves by about FY2030 if current trends continue. "Today we are coming before you to remove the collective bargaining rights," Rice said, framing the proposal as part of a broader effort to regain budgetary flexibility.
The presentation, which followed a staff overview of revenue and expense projections, showed that Salisbury received more than $11 million in one-time funding from 2020–2025 and that payroll and benefits increases — together with rising overtime — have pushed operating costs higher than recurring revenues. Rice and other staff highlighted specific liabilities: a recently awarded $14 million loan from the Maryland Department of Environment tied to water/wastewater; projected FY2027 health-insurance increases of about $1 million (roughly an 18% rise); and a long-underfunded OPEB (other post‑employment benefits) liability that is approximately 35% funded.
Administration officials and the mayor said bargaining-unit provisions constrain the city’s ability to address pay, retention and cross-departmental tradeoffs. "With three bargaining units there is some constraint where you are bargaining individually with each unit," Rice said, arguing that removing collective bargaining would give the city more flexibility to target retention and recruitment problems one-off rather than across all units.
Council members pressed administration officials on alternatives. Some members urged expanding the tax base or pursuing other near-term revenue sources: one council member noted possible county fire‑service payments, a poverty-grant allocation and development projects as immediate revenue options and requested clearer accounting of ongoing legal costs tied to past permit and development disputes. Another council member directly accused the mayor and administration of halting developments and increasing litigation exposure, saying, "We are in this pickle because of you, Mr. Mayor." The mayor and several colleagues disputed that characterization and pointed to insurance coverage and the complexity of pending cases.
Multiple council members emphasized the need for further due diligence before a final policy decision. A council member who said she had been in her seat since December described conducting research and meeting with staff and urged that public input and careful budget hearings continue. Several council members reiterated that the April 13 session was a work session and that no final decision was being made that night.
What’s next: staff will return with more detailed budget materials in the coming weeks, including an itemized list of projects related to the proposed bond and further cost projections. Council members signaled willingness to continue study rather than immediately adopt a policy that would remove collective bargaining rights.

