The Richardson City Council started its annual budget workshop August 3, 2026. Day 1 focused on the General Fund revenues and expenditures. Day 2 is scheduled to focus on the Operating Funds. (Note: this article was written after Day 1 but before Day 2.) The graphic above is one slide from the city's presentation. I am not going to discuss the $190 million General Fund Expenditures in the proposed budget. That would be too logical. Instead, I'm going to discuss one proposed $5,000 expenditure. Why? Because that's what the council spent time talking about. Too much time, in my opinion, given its tiny impact on the budget.
Here are some budget line items and the amount of time the council spent discussing each.
Personnel Services: $129.5 million, no discussion of reductions.
Water & Sewer contracts: $83.1 million, no discussion during Day 1
(perhaps to come)
Canadian Pacific mowing: $60,000, discussed by most members.
Economic Development Study: $200,000, discussed for a few minutes.
Moving State of the City venue: $5,000, discussed for roughly 8–10 minutes.
The cost of moving the venue for the annual State of the City from the Bank of America Theater in the Eisemann Center to the Hill Hall ($5,000) was the smallest discretionary budget item in the 157-page presentation, yet it received the most discussion. The $83 million water contract received no suggestions for cuts. Not even the $129 million devoted to personnel services spurred any suggestions for how that huge line item in the budget could be reduced. Yet the council spent ten minutes on how they could save the city $5,000. There's probably a case study in this somewhere.
Case study #1: Penny wise, pound foolish. The council members focused their attention on things that don't even amount to a rounding error in the budget, while leaving the biggest spending categories largely unquestioned. Personally, if I were on the council and another member felt strongly about this proposal, I might have trusted that judgment rather than spend valuable workshop time dissecting a $5,000 expenditure in a $190 million budget.
Case Study #2: All politics is personal. There's a striking mismatch between time spent debating an item and the money at stake. I find that an interesting phenomenon. I leave it for readers to judge for themselves why council members behaved that way. Perhaps relationships and personalities matter more than dollar amounts. I leave that for readers to speculate.
Case Study #3: How seriously does our council take its own Goals? A key council strategy is "Work to increase public engagement and input." Mayor Amir Omar advocated for a venue change for the annual "State of the City" presentation. He said it would add roughly 1,000 seats, it would enhance the purpose of the State of the City presentation, which is to market Richardson, and it would cost only $5,000 more (production cost only, not including the cost of the additional canapés, etc.). Mayor Pro Tem Hutchenrider opposed the venue change as an unnecessary expenditure in a tight budget year. Council member Justice opposed moving the venue, saying she'd prefer directing limited funds towards employee needs. Council members Dorian, Barrios, and Arefin said they were open to the idea, but wanted to see attendance and full cost data first. Given that the Mayor argued the venue change would advance one of the council's own goals, I could have understood Dorian, Barrios, and Arefin suggesting ways to increase public interest in this event. But instead, they asked for more information, delaying consideration of a proposal that the Mayor argued supported one of the council's own stated goals. I prefer Corcoran's take on the matter. He said, "I've heard such good feedback about our State of the City and just how superior it is compared to other cities. Let's make it even more superior for $5,000. That's easy." Of all the arguments offered, I found Corcoran's the most persuasive.
Quotes have been lightly edited for clarity and brevity.
"Millions flow downstream,
Council builds a careful dam
To catch one raindrop."
—h/t ChatGPT
No comments:
Post a Comment