The data center fight in Caledonia Township, Michigan
As of November 12, 2026, Caledonia Township, Michigan had a data center moratorium whose documented term has run out (action taken Feb 2026; it ended 2026-10-17).
Status is derived, not stored — a pause with a documented end date flips to Expired on its own — and the source is right next to the claim.
Status today
Board approved a six-month moratorium on zoning and building applications for data centers and digital mining (backdated to Jan 1, 2026) after developer inquiries about property at 68th Street and Kraft Avenue. On June 3, 2026 the board unanimously approved a resolution extending it until Oct 17, 2026, per its own minutes. Resolution text not read; any action after Oct 17 not found.
SourceNews
read 2026-10-14
An expiry date is the earliest a pause could have ended — extensions are common, so confirm with the clerk before citing it.
What to do next
- Questions to ask at the hearing — force specific answers onto the record.
- Estimate the impact — electricity, water, and rate pressure for any facility size in Michigan.
- Model CBA clauses — copy-paste language communities have actually won.
- Michigan briefing — rates, grid carbon, PUC contacts, and every fight in the state.
Nearby in Michigan
- Lowell Township (12 mi) — Rejectedterm not documented
- Zeeland Township (27 mi) — Enactedterm not documented
- Allendale Township (31 mi) — Enactedexpires 2027-06-08
- Texas Township (36 mi) — Enactedexpires 2027-07-05
- Saugatuck Township (36 mi) — Expiredterm ran to 2026-08-11
- Lansing (49 mi) — Enactedexpires 2027-01-25
- Michigan (HB 5594-5596) (49 mi) — Proposedterm not documented
- East Lansing (53 mi) — Enactedexpires 2027-03-17
All 66 tracked actions in Michigan are on the state page.
As of August 2026 (3m ago) · changes weekly — re-check before citing
Illustrative rather than exhaustive — dozens of localities churn weekly, and this tracks the ones we have read a source for. **Each row carries its own provenance.** Rows showing a verification date link to the ordinance, the enacting body's own page, or a datable report of the vote, and were read on that date. Rows marked *unverified* came from bulk compilation and have not been checked against a primary source — the locality, the year, and the status may all be off. Verify one of those with the town clerk before citing it as precedent. **Expiry is derived, not asserted.** A row with a documented end date flips to *Expired* on its own once that date passes. A time-limited moratorium whose start date was never documented keeps showing as enacted — that is a known gap, not a claim that it is still in force. Moratoriums are also routinely extended, so an expiry date is the earliest it could have ended, not proof that it did.
Part of the U.S. data center moratorium tracker — open data, CC BY 4.0.