Ordinance checklist
What a data center ordinance could cover
A moratorium buys time to write rules. These are the subjects those rules usually have to settle, written as questions a council, a board or a planning commission can put to itself and to an applicant.
General guidance, not legal advice. What a local government may require differs from state to state, and a limit that suits one place does not suit another. A county or city attorney should review any ordinance before it is adopted.
0 of 37 marked. Tick what your community has settled; the ticks stay in this browser.
Where it can go
0 of 5Most disputes start with a site nobody expected. Saying where a data center may go, before one is proposed, settles the largest question first.
Electricity and electric bills
0 of 4A large load can need new lines and substations. The question residents ask is who pays for them.
Water
0 of 5Cooling can use a great deal of water or almost none, depending on the design. An ordinance can ask which it is.
Noise
0 of 3Cooling equipment runs day and night. Sound is a common complaint from neighbors once a facility is running.
Air quality and backup generators
0 of 3A campus can hold dozens of diesel generators. They run rarely, but they are tested on a schedule.
Neighbors, roads and the view
0 of 4A data center is a large building with little traffic once it is built and a great deal while it is being built.
Taxes, benefits and jobs
0 of 4What a community receives is decided by what is written down before approval, not by what is said at a hearing.
An open process
0 of 3Trust is lost fastest when residents learn of a project late, or cannot learn who is behind it.
Keeping the promises
0 of 4A condition nobody checks is a condition nobody keeps.
When it closes
0 of 2Buildings outlast the companies that build them.
Take it to a meeting
Every county, city and township scenario comes with a council packet: the place on a map, an illustrative scenario with its numbers, and this checklist printed with a box beside each line.
