Opinion & Analysis
May 29, 2026 — Protect Grove City
When a community decides it needs time to study whether a data center belongs in its backyard, local leaders face a choice that sounds technical but is actually very simple: do you want to make a promise, or do you want to make a law?
That is the difference between a resolution and an ordinance. And it matters more than most people realize.
A resolution is the quickest way for a city council to say something officially. It is a formal statement of intent, of concern, of direction. Councils pass resolutions all the time to create committees, express policy positions, and signal what they plan to do.
For a community worried about data centers, a resolution might say: “We are establishing a review committee. We believe no data center should be approved until we develop proper standards. We are going to study this seriously.”
That sounds good. The problem is that a resolution is essentially a promise. It carries no legal force. A developer who receives that resolution and reads it carefully will see exactly what it is: a statement of intent that no court can enforce. If they file an application the next day, the city may have no legal basis to stop it from being processed. A resolution cannot reject an application. It cannot make an application void. It cannot authorize the city’s attorney to go to court. It just sits there.
A resolution says: trust us.
An ordinance is a law. When a council passes a moratorium ordinance, it is not making a promise. It is creating a legal prohibition that lasts until the community has done the work it committed to do. Staff are directed to reject and return any applications during that period. Any application that sneaks through anyway is legally worthless from the moment it was filed. The city’s Law Director is authorized to go to court if necessary.
The moratorium is not a permanent “no.” It is a protected pause, but only as strong as what the ordinance requires before it ends. If those conditions are spelled out in the ordinance itself, development cannot move forward until the city has met every one of them: completing the community review, developing permanent standards, and formally adopting those standards into law. Once that work is done, the door opens on the city’s terms, not the developer’s. Leave those conditions out of the ordinance, and the moratorium simply expires on a calendar date with nothing to show for it.
An ordinance says: we mean it, and here is exactly what we mean.
Here is the part most people do not think about until it is too late.
Under Ohio law, an ordinary ordinance does not take effect for 30 days after it passes. Thirty days. That is 30 days during which a developer who has been watching the council calendar can file an application, get it timestamped by the city, and argue they had rights before the moratorium ever kicked in. Developers know this. Their attorneys know this. The moment a moratorium ordinance is introduced, the clock starts and the race begins.
An emergency clause is how you win that race before it starts.
When an ordinance is declared an emergency measure for the public health, safety, and general welfare, it takes effect the moment the Mayor signs it, not 30 days later. The window closes. There is no gap to exploit. And because Ohio law also makes emergency ordinances exempt from referendum, there is no 30-day period during which opponents can circulate a petition to put the ordinance to a public vote.
But the emergency clause alone is not enough. A well-drafted moratorium ordinance also includes retroactivity language, stating that the moratorium applies to any application submitted on or after the date the ordinance was introduced at first reading, not just the date it passed. This matters because there is always a gap between introduction and passage, typically at least one council meeting. Retroactivity to the introduction date closes that gap and eliminates the incentive for a developer to rush a filing in the days between first reading and final vote.
The ordinance should also state plainly that the facility type covered by the moratorium is not currently a permitted use under the city’s zoning code, and therefore any application filed before the ordinance passed was already legally defective at the moment it was submitted. That argument does not require the moratorium to be in effect. It simply says: there was never anything to apply for.
Together, the emergency clause, the retroactivity language, and the not-a-permitted-use finding create three overlapping layers of protection. A developer would have to defeat all three to establish that their application has any legal standing at all.
The emergency clause is not a procedural technicality. It is the shield that makes everything else work.
A council does not have to choose between a moratorium and the administrative work of setting up a review process. Everything valuable in a resolution, including the committee, the policy position, and the work plan, can be written directly into the ordinance itself.
When the committee is created by ordinance, its existence is law. When the requirement that no final approval can happen until permanent standards are adopted is written into operative ordinance text, it binds the city legally. When the scope of the committee’s work is in the ordinance, Council cannot quietly redirect or defund that work without taking a formal public vote.
The resolution’s tools become the ordinance’s teeth.
A few specific additions make a moratorium ordinance much harder to challenge in court:
Findings of fact are a section that states clearly: no application has been formally accepted, no vested rights exist, and this type of facility is not currently permitted. This creates the legal record that justifies the moratorium and directly knocks out the most common legal arguments a developer would make.
A waiver process sounds like a weakness but is actually a strength. Courts have been more likely to uphold moratoriums when a narrow hardship exception exists, because it shows the city is being reasonable rather than arbitrary. It’s ok to make the bar high. The applicant has to prove their situation is unique, that their project does not raise the concerns the moratorium addresses, and that granting an exception will not undermine the whole thing.
A supermajority to end it early requires more than a simple majority vote to terminate the moratorium before its time is up. This protects against future pressure from a developer who might lobby one or two council members to pull the plug.
Language that survives expiration states clearly that when the moratorium clock runs out, it does not automatically open the door. No approvals can happen until the permanent standards the ordinance requires have actually been adopted. Otherwise a developer just waits it out and rushes in on day one.
| What You Need | Resolution | Ordinance |
|---|---|---|
| Actually stops applications from being filed | No | Yes |
| Takes effect immediately (with emergency clause) | No | Yes |
| Closes the 30-day referendum window | No | Yes |
| Legally binds the city to do the review work | No | Yes |
| Prevents approval until permanent standards are adopted | No | Yes |
| Creates a review committee with legal standing | Sort of | Yes |
| States Council’s policy position publicly | Yes | Yes |
| Easier to pass | Yes | Harder |
| Holds up in court if challenged | Unlikely | Yes, if well-drafted |
Residents who pack a council chamber asking for protection are not just asking for a policy statement. They are asking their government to prove it is serious.
A resolution asks them to trust a promise. An ordinance shows them the law. It tells the developer, the community, and any future council: this is not a suggestion. This is not a position paper. This work is required, it is public, and it cannot be quietly abandoned.
Our community doesn’t want promises from Council. We deserve guarantees. A resolution is a handshake. An ordinance is a contract. When the stakes are this high and the pressure from developers this real, only one of those is going to hold.
This Is Happening Now
Grove City Council votes on the moratorium Monday, June 1st.
Caucus at 5:30 pm. Meeting at 6:00 pm. Grove City Hall, 4035 Broadway. The vote on whether Council will pass an ordinance or settle for a resolution — or nothing at all — happens in that room. Showing up matters. Bring a neighbor.
This article is for general informational purposes for community advocates and local elected officials. It does not constitute legal advice. Always consult your municipal Law Director before taking legislative action.
