Episode Sixteen -Council Wrap Up (4/16/26) and Reflections

This week’s Wilmington City Council meeting was shorter than usual, but it still covered a wide range of topics, including long-term fire department planning, routine legislation, and a fast-moving zoning change that raised important procedural questions.

In this episode, Matt walks through the full meeting from start to finish, including:

• Fire department staffing and long-term planning
• Routine council business and infrastructure updates
• The return of the data center conditional use discussion
• A detailed breakdown of Ordinance O-26-21
• What actually qualifies as an emergency under council procedure
• How framing, urgency, and presentation shape decisions in real time

The episode closes with a broader reflection on how information is presented in public meetings, how decisions are guided, and why that matters for transparency and public trust.

Whether you watched the meeting or are catching up now, this episode is designed to slow things down and make the process clear.

Transcript

Intro

SPEAKER_00 0:02

Hello everyone, it's Matt, and it's time for episode 16 of Wilmington Weekly. I'm celebrating with my family this weekend, so I wanted to get this out a little bit early. And this month has five Thursdays, so we won't have another council meeting until May 7th. Maybe that's a good time for me to finish one of these special episodes I've been working on. Anyway, this was not a long meeting, but there were a couple moments where how decisions were made mattered just as much as what was decided. And with

Meeting Review

SPEAKER_00 0:36

that. But it does raise the question of what gets said and what does not, and whether the pace of the meeting matches the weight of the decisions being made. Our workshop tonight opened with a presentation from Safety Director Eveland and Fire Chief Mason on the future structure of the fire department. The current staffing ordinance has not been meaningfully updated since 2008, and what they laid out was essentially a long-range framework for where the department may need to go over the next 10 to 15 years. That includes removing outdated positions, shifting toward a captain structure, and creating room for additional staffing down the road. The repeated phrase in that presentation was that council holds the purse strings. None of the added positions are funded yet. Every future hire would still require supplemental appropriations and separate council approval. There were also a few clear signals built into that presentation. One was that the department is already juggling staffing pressure with the roster it has. Another was that pay structure issues are coming because Evelyn referenced a disparity in the current scale. And another was that this is all tied to growth, whether that means the air park, future development, or the possibility of a second fire station down the road. After that, the workshop moved more quickly through routine business. The annual ODOT road salt contract came through with no discussion beyond the reminder that it happens every year and I had to move on it in three readings because of a deadline. Finance was straightforward, but not empty. Auditor Vance gave useful context on the supplemental appropriations, explaining that TIFF revenue tied to the Sugar Tree Entertainment Corridor is finally coming in through the county, and that the city needed to account for the deductions and handling of those funds. The other two finance items were simple enough: a donated metal detector for the police department and two sanitation pickup trucks that are well past their useful lives and headed for the surplus sale. One other important item came out of the workshop. Near the end, after Snarr asked about the status of making data centers a conditional use in light industrial zoning, that issue came back into the room. Crow said the earlier Planning Commission tabling had been driven by confusion and by public pressure. Deputy Law Director Haran pointed out that conditional use standards are already spelled out in the code. Tolliver argued that the city got lucky with AWS because they voluntarily went above and beyond, and that Wilmington needs better tools for future projects. Council then voted to send a letter asking that the issue be brought back to Planning Commission for reconsideration. So the workshop didn't just set up the adult family homes ordinance, it also formally reopened the data center conditional use question. Once the regular meeting began, the opening portion was pretty thin. The mayor presented a proclamation for ALS Awareness Month. The deputy law director gave a brief acknowledgement of the public dispatcher's week and thanked them for their service. Crow and Evelyn had no additional reports. Old business then moved quickly and cleanly. Curtis Drive passed on third reading without discussion. North Spring Street passed the same way. The Union Township Fire and EMS Agreement got its second reading without additional discussion. The Minor Subdivision Review Committee Ordinance passed unanimously. The Cemetery Foundation Ordinance got second and third reading and was passed without any dissent. Those are not small items. Curtis Drive and North Spring both continue real infrastructure work. The Union Township Agreement is a five-year public safety agreement, and while routine, it's necessary. The cemetery ordinance creates actual operating rules and penalties, but in the regular meeting, all that moved as throughput. New business stayed in that same rhythm for a while. The road salt contract passed cleanly on three readings, supplemental appropriations passed without additional discussion after Auditor Vance's workshop explanation. The police donation moved without controversy. The surplus vehicle resolution passed after a brief explanation from Knowles about the two pickup trucks. So a lot of government happened Thursday night. This was not an empty meeting, but much of it moved in the low friction way that routine city business often has. Then council reached ordinance 2621. And that's where the real tension of the night reappeared. The most significant discussion of the night centered on ordinance 02621, which would change adult family homes from a permitted use to a conditional use in certain residential areas. In simple terms, that change does not prohibit those uses. It adds a layer of review. Site plans, parking, traffic considerations, and a chance for public input before approval. And I want to be clear here. I'm not against conditional use. In this case, I'm actually for it. Same with data centers, especially data centers. They are too complex to have access to by-right approval. But the presentation, the pressure, and the method worked against the issue itself. If conditional use is the right answer, then make that case cleanly. What I heard instead was a kind of double message. There is no boogeyman, but we have to move now before a boogeyman could show up. That kind of argument does not build trust, it undercuts it. Because during the workshop, Crow explicitly asked for ordinance 2621 to move that night as three readings and as an emergency. Then, in the regular meeting, he came back to the same urgency. He kept pressing the idea that the city needed this in place before an application came in under the current code. That urgency was largely built on hypotheticals, parking, traffic, future use. Even the Airbnb example, where he said that if an Airbnb were going next to his house, he would want to have a say. And again, this is where the method matters. He was not just explaining the ordinance, he was building pressure around it. There were some good questions, especially from Snarr. He pushed on what would happen if all conditions were met, but neighbors still opposed the use. He pushed on why this should be treated as a business use. He pushed on the timing, asked why council needed all three readings that night. There was also a public comment that raised a narrower question about what would happen if a property with an existing family home use changed hands and was transferred to a ministry or a similar operator. Crow responded in that context by talking about a commercial application and a business use and a residential area. I don't ascribe that to anything. I think it was hypothetical, but I do take it as another example of how much this urgency argument depended on future scenarios and possible uses rather than a clearly stated immediate problem in front of council that night. Council's response was mostly supportive. Tolliver backed it and said this should have been done years ago, which is a revealing way to frame the same night rush. Because if it really should have happened years ago, that raises the obvious question of why it suddenly had to happen tonight. And that's where the procedure piece matters. The agenda was amended early in the meeting, but what Schleibaugh actually moved to amend was simple. He asked for three readings that night instead of a first reading only. He did not say as an emergency. Osbourne repeated it that way. Council approved it that way. Then later, when Deputy Law Director Haran read the ordinance, she read the ordinance title. No emergency language there either. The emergency rhetoric in the room was coming from Crow. That is important because once council got into the item itself, there was visible hesitation. Schlebal, who had amended the agenda for three readings, was not the one trying to force through the second and third reading. In fact, he openly asked whether council should just do one reading and come back to it later. That led to some confusion on the floor about who could actually move the item forward. In the end, the rules were suspended, the ordinance moved through second and third reading, it passed six to one, with Snarr voting no. Schleba ultimately voted yes, but his hesitation still matters because for a moment it showed there was at least some recognition in the room that council didn't have to force this through that night. And regardless of what Crow was asking for, the way O twenty six twenty one actually moved through council does not appear to make it an emergency measure. As I understand the process, that means the ordinance still carries the normal 30-day window before taking effect. So if the concern was that something might come in immediately under the current code, the city may not have actually solved that problem Thursday night. Council moved quickly. But again, the legal effect appears to be much slower. And that was the bulk of the meeting.

Upcoming Meetings

SPEAKER_00 11:06

Public Works Committee is scheduled to meet on Tuesday, April 21st at 5 30 in Council Chambers. The only topic on the agenda is stormwater rates. I mentioned that at the top of the show, but there will not be another city council meeting until May 7th. But there are some other meetings worth paying attention to in the coming weeks. Also on April 21st at 4 15 is Civil Service Commission in Council Chambers. And as we roll into May, the BZA and Park Board meeting both have their meetings at the same time again. May 4th at 5.30. Park Board is downstairs in the community room, and the Board of Zoning Appeals will be upstairs in Council Chambers. Then on Tuesday, May 5th at 4.30, Planning Commission will have its next meeting. Given the outcome of this week's council meeting, I'm anticipating a more robust discussion about the conditional youth zoning change for data centers at this meeting, as well as some updates on the AWS site plan since their last meeting.

Community Note

SPEAKER_00 12:06

Mayor Haley also issued a proclamation recognizing May as ALS Awareness Month. It was brief, but it acknowledged the impact of ALS and the ongoing work to support those affected by it. This is one of those moments that can get lost in a meeting recap, but it's still worth noting.

Reflection

SPEAKER_00 12:25

What stood out to me about the workshop was the way its two major segments, though very different in subject, worked in a similar way. In both cases, administration was not just giving council information. It was framing the issue in a way that pointed council toward a preferred direction. Evelyn did it on staffing and future fire department planning. Crow did it on zoning, control, urgency, conditional use. The workshop lasted about 43 and a half minutes, and by the end it felt less like a simple review of agenda items and more like a carefully guided set of public briefings. Under both Ohio law and our local council rules, the role of mayor, directors, and administration in the room is pretty clear. They're there to answer council's questions, provide information, and make recommendations for council to consider. What I saw Thursday night move beyond that. It felt less like answering questions and more like selling a direction. Evelyn did it in a polished, forward-looking way. He kept reminding council that it holds the purse strings, which is true in a formal sense, but everyone in the room knows how that plays out when public safety makes its case. If the fire department comes back and says it needs more staffing, counsel is never going to want to be on the hook for saying no, and then owning the consequences of a short staff branch of public safety. So, even though Evelyn framed it as counsel retaining control, the presentation still guided counsel toward future buy-in. Crow did it differently. He leaned on urgency, control, the hypothetical scenarios to push toward a decision. He kept returning to the need to act now, even while acknowledging there was no immediate application in front of counsel. The examples were built around what could happen, not what was happening. Different presentation styles, same practical effect. In both cases, the administration was not just explaining an issue, it was shaping the outcome. And this is where the broader pattern comes in. We're seeing complex issues framed in a way that points toward a preferred outcome, followed by council moving relatively quickly within that framing, often without a lot of public stress testing. We've seen versions of that before. Recycling is part of that pattern. At two different meetings, Crow did not simply lay out options and trade-offs, he built a case against every path that might preserve curbside recycling, including the argument that the condition of the truck was so environmentally poor that it could wipe out the broader environmental value of the program itself. That is the same governing style in a different policy arena, not just information, direction. Go back to February 19th, when zoning changes were pushed through, only to be met with a successful citizens' referendum effort that paused the issue until November. This is what can happen when things move faster than the public is ready to accept them. So you end up with a meeting that moves quickly on what is in front of it, while other active public conversations seem to sit off to the side without clear movement. And that, to me, is the larger concern. Not just speed, but selectivity. Some issues get urgency, structure, momentum, but other once hot button issues like water fluoridation, curbside recycling, even the AWS data center updates are just left to sit and wait.

Closing

SPEAKER_00 16:18

And that's where I'll leave it for this one. It was a short meeting, lots of routine business, moving cleanly, a forward looking presentation from public safety, a fast moving zoning change, and a reminder that speed in the room does not always mean clarity in the process. Until next time, thanks for listening to When We Twin We Clean.