Stronach Township Data Center Moratorium Ledger: Six Months To Get The Power, Water, And Zoning Receipts Right

Stronach Township did not ban compute. It bought itself six months to stop a high-load industrial use from outrunning the local record.

That distinction matters. Manistee News Advocate reported June 15, 2026 that the Stronach Township Board unanimously approved a six-month moratorium on data-center development that runs through Dec. 31, 2026. The outlet reported that the moratorium followed resident concern over a potential data-center project at or near the former Packaging Corporation of America property, while also noting that no formal application or zoning request had been submitted.

BadPD's view is simple: America should build compute. Michigan should compete for serious AI, cloud, industrial, research, defense, and public-sector infrastructure. But pro-compute does not mean local governments should approve high-load facilities before the public can see the power, water, sewer, noise, fire, tax, and zoning receipts.

Stronach is useful because the record is still early. The township is not responding to a completed permit file. It is responding to a pressure wave before a formal application, while its master-plan update is underway and while Michigan communities across the state are trying to decide how to classify data centers before developers turn zoning silence into leverage.

That is exactly when a temporary pause can be responsible. A moratorium should not become a lazy ban. It should become a work window.

What Is Confirmed

The township's own June 10, 2026 board agenda lists "Data Center information and update" as a separate agenda item. That is a primary local-government receipt that the topic was on the board's official calendar, not just circulating through rumor channels.

Manistee News Advocate reported June 15 that the board approved the six-month moratorium unanimously. It reported the moratorium is effective until Dec. 31, 2026, and that township officials said no formal application or zoning request for a data center had been filed. The same report said the township is updating its master plan and quoted the township supervisor framing the pause as a way to slow down and get zoning and planning in order.

Earlier local reporting in May described a packed community discussion over the potential site and later reporting clarified that a zoning request had not been received. The public source trail therefore points to three separate facts that need to stay separated: residents are concerned, officials are studying the issue, and a formal application is not publicly filed yet.

That separation is important. BadPD should not write as if a specific developer has already sought and received approval. It should write as if a township has seen enough signal to know its code may not be ready.

What Is Pending

The missing record is the adopted moratorium text and the June 10 meeting minutes. The township documents page currently exposes the June 10 meeting agenda and earlier planning materials, but the final June 10 minutes and a standalone moratorium resolution were not present in the source package I could retrieve at publish time.

That does not invalidate the local report. It does mean the next update should pull the actual resolution language as soon as it posts. The public needs to know exactly what the moratorium covers: applications, permits, zoning amendments, site-plan review, building permits, utility approvals, special-use permits, or only a narrower set of actions. It also needs the definitions. Does the pause cover hyperscale campuses, colocation facilities, AI training sites, cryptocurrency mines, high-performance computing, edge facilities, or every room with servers?

A good moratorium starts by defining the thing it is pausing. A weak moratorium creates a headline but leaves the loopholes intact.

Why This Is A Michigan Accountability Story

Michigan's data-center debate is no longer theoretical. Communities have already used moratoriums, utilities have raised water and sewer questions, residents have raised noise questions, and power companies have argued that large data-center customers can help spread fixed grid costs if contracts are designed correctly.

Stronach is smaller than the statewide headline fights, but it is a good test of local control. The township sits in Manistee County. Its official site lists zoning, ordinances, a master plan, planning commission materials, and meeting records. That is the machinery local residents use to understand what can be built near them and under what conditions.

If a potential project appears before that machinery has a data-center category, the township has three bad choices. It can stretch old industrial language to cover a modern high-load use. It can negotiate case by case under pressure from a developer, utility, or landowner. Or it can pause long enough to write a standard that responsible projects can meet and weak projects cannot dodge.

The third option is the one worth defending if the township uses the time well.

The BadPD Standard: Build It Right

BadPD is not anti-data-center. The United States needs domestic compute capacity. AI competitiveness, cloud resilience, cybersecurity, logistics, medicine, manufacturing, finance, education, weather modeling, defense, and public administration all depend on computing infrastructure that actually exists somewhere.

The question is not whether America should build. The question is whether local residents are forced to subsidize rushed builds through cheap public water, hidden grid upgrades, noisy equipment, backup-generator emissions, vague tax promises, or zoning categories written for a different era.

A build-it-right standard asks for receipts before approval. The first receipt is power. How many megawatts are needed at launch, at full buildout, and during peak demand? What substation, feeder, transformer, transmission, or generation work is required? Who pays? What happens if the project is delayed or the customer leaves? Is there battery storage, demand response, microgrid capacity, on-site generation, or power returned to the grid during stress events?

The second receipt is water. How much water is required for cooling, fire protection, humidification, cleaning, commissioning, and emergency operations? Is the system air-cooled, evaporative, hybrid, closed-loop, waterless, reclaimed-water, or something else? If the applicant says "closed loop," what does that mean in gallons, refill cycles, treatment chemicals, discharge, leaks, and maintenance?

The third receipt is noise. What fans, chillers, pumps, transformers, backup generators, and cooling towers will operate, and at what sound levels? What is the baseline sound at nearby homes? What are the nighttime limits? Who measures after construction? What happens when residents complain?

The fourth receipt is land use. Is the proposed site industrial, commercial, agricultural, or mixed? Does the use fit the master plan? What buffers, screening, roads, fire access, stormwater controls, hazardous materials rules, and emergency plans are required? How does the project affect nearby homes, farmland, wetlands, schools, roads, and emergency services?

The fifth receipt is public value. What permanent jobs are created? What construction jobs are created? What taxes are paid, and what abatements or incentives are requested? What public costs are shifted to the township, county, schools, fire department, utility customers, or state taxpayers?

Those are not anti-compute questions. They are adult infrastructure questions.

Why The Former PCA Site Question Needs A Public Ledger

The Manistee News Advocate reports tie the community discussion to the former Packaging Corporation of America property area. That kind of site can make a data-center idea attractive: existing industrial land, a large parcel, legacy utility access, a reuse story, and the promise that a dormant property becomes productive again.

Reuse can be good. A former industrial site may be better suited for compute than farmland or a residential edge. But a reuse story is not a substitute for a utility ledger. Existing industrial history does not automatically prove a modern data center can use the same power, water, sewer, road, emergency, and noise envelope.

A responsible review should start with the site history and then ask what changes. If the old use had one utility profile and the new use has another, the public should see the delta. If the old use created jobs and traffic but the new use creates a smaller permanent workforce and a heavier utility load, the tax and jobs math should be explicit. If the old site had environmental conditions, stormwater obligations, or cleanup issues, those records should be part of the review.

The township does not need to prejudge the site. It needs to prevent the site story from becoming a shortcut around the receipts.

What The Master Plan Window Should Produce

A master-plan update is the right place to decide what kind of compute a community wants, where it can go, and what conditions it must satisfy. The Stronach master plan and zoning records are older public documents, and the township site shows the planning and zoning system residents are expected to use. The moratorium should turn that system into something more specific.

At minimum, Stronach should create a data-center definition section. It should separate small office/server rooms from true data centers. It should distinguish enterprise, colocation, hyperscale, AI training, cryptocurrency mining, and high-performance computing uses if their impacts differ. It should use thresholds: square footage, megawatts, generator capacity, water demand, cooling method, and noise profile.

Then it should decide which zoning districts can even consider those uses. Some communities may allow small data centers by right in certain industrial districts. Larger or high-load projects should require special-use review, site-plan review, utility-impact review, public hearing, and enforceable conditions.

The ordinance should also require a utility-impact statement before completeness. If an applicant cannot disclose basic load, cooling, and water numbers, the application should not be complete. That is not a denial. It is a refusal to start the public clock with missing math.

Power: No Free Grid Ride

The power file is the heart of the issue. Data centers can be valuable customers, but they can also trigger infrastructure work that ordinary residents and small businesses should not subsidize.

A Stronach standard should require a maximum-demand estimate, load-ramp schedule, interconnection requirements, upgrades to distribution or transmission facilities, backup-power plan, emissions permits, emergency-generation testing schedule, battery-storage plan if any, and a public explanation of who pays if the customer delays, downsizes, or exits.

If a developer can bring its own power, use a microgrid, add battery storage, or support grid reliability, that should be encouraged and documented. If a developer simply needs a large public-grid draw, that may still be approvable, but only if the cost wall is clear.

"No free grid ride" is not anti-business. It is the condition that lets local residents support buildout without wondering whether their bills are carrying someone else's servers.

Water: Do Not Sell Cheap Public Cooling By Accident

The water file should be just as direct. A project should disclose average daily water use, peak use, source, cooling technology, closed-loop claims, blowdown or discharge, sewer impacts, treatment chemicals, spill prevention, fire protection, and drought contingency.

Data-center developers increasingly claim better cooling designs, and some of those designs may genuinely reduce public-water demand. Good. Put the design in the permit file. If the project uses waterless or low-water cooling, let that become a positive condition. If the project needs large water volumes, the township should know the gallons before it knows the ribbon-cutting date.

This is where the BadPD frame is deliberately pro-build and anti-shortcut. Build data centers that do not use cheap public water as a hidden subsidy. Reward designs that lower water risk. Make the numbers public enough that residents can tell the difference.

Noise, Fire, And Emergency Services

A rural or semi-rural community should not learn about data-center noise after equipment is running. Cooling equipment, transformers, generators, pumps, and trucks can change the sound environment even when a facility looks quiet from the road.

Stronach should require baseline sound studies, predicted operating levels, nighttime limits, tonal-noise analysis, generator-test schedules, and post-opening measurements. If nearby homes or farms are within a defined radius, the ordinance should require continuous or repeated monitoring after startup. Complaint handling should have deadlines and remedies.

Fire and emergency services also need a ledger. What battery systems are present? What fuel is stored on site? What coolants or treatment chemicals are used? What fire-suppression system is installed? What training and equipment do local responders need? Who pays for that training? What happens if a server hall, battery room, transformer, generator, or cooling system fails?

A project that answers those questions early is easier to approve. A project that treats them as afterthoughts is asking the public to underwrite uncertainty.

Confirmed, Alleged, Pending, Disputed

Confirmed: Stronach Township's June 10 agenda included a "Data Center information and update" item. Manistee News Advocate reported June 15 that the township board unanimously approved a six-month data-center moratorium effective through Dec. 31, 2026. The same reporting says no formal application or zoning request had been filed. The township maintains public zoning, documents, permit, master-plan, and meeting-record pages.

Alleged or reported: residents and officials have discussed a potential data-center idea connected to the former PCA property area. Local reporting describes public concern and a community meeting that drew a large crowd. Those concerns should be treated as public input and reporting, not as proof that any specific development application is pending.

Pending: the final moratorium resolution text, June 10 minutes, any definition of data center adopted by the township, any future application, utility letters, water and sewer records, site-control records, developer identity if an application appears, and the standards created during the pause.

Disputed: whether a data center would be a good reuse for the property, whether local infrastructure can carry the load, whether the tax and jobs math would help the township, and whether a temporary moratorium is a planning tool or an obstacle. Those disputes need documents, not slogans.

What Stronach Should Publish Next

First, publish the signed moratorium resolution and June 10 minutes. The public needs the exact text, the vote record, the scope, the expiration date, and the legal basis.

Second, publish a data-center study calendar. Residents should know when the planning commission or board will discuss definitions, zoning districts, utility review, water, noise, emergency response, and master-plan language.

Third, publish a document checklist for any future applicant. It should include load study, utility will-serve letters, water/cooling statement, sewer/discharge statement, noise study, backup-generator permits, fire and hazardous-materials plan, tax-impact estimate, job estimate, incentive request, stormwater plan, environmental records, and decommissioning or abandonment protections.

Fourth, require plain-English summaries. A township resident should not need to be an electrical engineer to understand whether a project asks for 2 megawatts or 200, whether cooling uses public water, whether backup generators burn diesel, or whether a utility upgrade will be paid by the project or the rate base.

Fifth, keep the moratorium temporary. The goal should be a clean path for projects that can prove they are quiet enough, water-smart enough, grid-responsible enough, and valuable enough to justify approval.

Bottom Line

Stronach's pause is worth acting on because it catches the data-center fight at the right moment: before a formal application, before old zoning language gets stretched too far, and before residents are told that asking for receipts is anti-growth.

It is not anti-growth to ask who pays for power upgrades. It is not anti-tech to ask how much public water a cooling system needs. It is not anti-American to ask whether a project helps the grid or rides it for cheap. It is not anti-business to require noise, fire, sewer, road, tax, and emergency records before approving a modern industrial use.

The country should build the compute. Michigan should compete. Stronach should use the six months to write a rulebook that lets responsible projects move and forces weak projects to show their math.

A moratorium is only useful if it turns into standards. The next receipt is the resolution text.

Source-Status Note

This article relies on Manistee News Advocate for the reported June 10 vote result and moratorium term, and on Stronach Township public pages and PDFs for the official agenda, zoning, document, and master-plan record. The June 10 minutes and signed moratorium resolution should be pulled and attached when posted.

Source Trail

• Manistee News Advocate: Stronach approves six-month data center moratorium (June 15, 2026; accessed June 15, 2026) – Local report on unanimous board approval, Dec. 31 end date, no formal application or zoning request, resident concern, and master-plan update context.
• Stronach Township documents and permits page (Accessed June 15, 2026) – Official township page where board agendas, meeting records, ordinances, and planning documents are posted.
• Stronach Township June 10, 2026 board agenda PDF (June 10, 2026; accessed June 15, 2026) – Official agenda listing "Data Center information and update" as a board-meeting item.
• Stronach Township zoning page (Accessed June 15, 2026) – Official zoning and ordinance access point showing the local land-use machinery that needs a data-center definition and standards.
• Stronach Township master plan PDF (Revised July 2, 2014; accessed June 15, 2026) – Official master-plan baseline relevant to land use, industrial reuse, zoning updates, and whether modern high-load compute fits the plan.
• Manistee News Advocate: officials clarify potential data-center zoning status (June 6, 2026; accessed June 15, 2026) – Local report used as source-status context that officials said no formal zoning request had been received.
• Manistee News Advocate: data-center discussion draws crowd in Stronach (May 13, 2026; accessed June 15, 2026) – Local report on the public concern and community meeting that preceded the moratorium debate.