NewsDesksDirectoryBuildersGuidesValvesValve specs
Home / Guides / City council checklist
Community and Policy

A City Council Checklist: 12 Questions to Ask About a Data Center Proposal

Twelve plain questions for council members, planners and neighbors to ask before voting on a data center. What a good answer sounds like and what should raise a flag.

A data center proposal usually arrives with a lot of numbers and a short vote date. You do not need to be an engineer to ask good questions. These twelve cover power, water, noise, money, jobs, land and the promises that should be written down. Use them in a hearing, in a staff memo or at a kitchen table. Mark each answer as you go, then copy the summary to share with your team.

0 of 12 marked

How much power will it use, and who is supplying it?

Power is the first limit on any data center. Large sites can need as much electricity as a small city, and the grid may need new lines or substations before they can open.

A good answer: A number in megawatts for the first phase and for full build out, the name of the utility, and a signed or filed service request. A plain answer on who pays for grid upgrades.

A flag: Only a range with no utility named, or a claim that the power question is settled when no agreement is on file.

How much water will it use, and where does it come from?

Cooling choices change water use a lot. Some designs use water on hot days, some use very little but use more electricity.

A good answer: The cooling type, expected use on an average day and a peak day, the source (city supply, reclaimed water, well), and what happens in a drought.

A flag: A single yearly number with no peak figure, or a plan that depends on a source nobody has confirmed.

What backup power will be on site, and how often will it run?

Most sites keep diesel or gas generators for outages. They run for tests and in emergencies, and they need air permits.

A good answer: The number and size of generators, fuel type, planned test hours, the air permit status and where the units sit on the property.

A flag: No count of units, or a statement that testing hours are not decided.

How loud will it be, and who measured it?

Cooling fans, chillers and generators can be heard from a distance. Noise is one of the top complaints near existing sites.

A good answer: A sound study by an independent firm, expected levels at the property line and at the nearest homes, and the steps taken to reduce it.

A flag: A promise that it will be quiet with no study, or numbers measured only inside the fence.

What does the tax and incentive deal look like?

Tax breaks can be worth a lot to the company and cost the community revenue. The terms decide who benefits.

A good answer: The length of any abatement, what the company pays in lieu, the expected net income to the city and schools, and any clawback if promises are missed.

A flag: A deal that is not public until after the vote, or no way to recover value if jobs or investment fall short.

How many permanent jobs will it create?

Construction brings many workers for a short time. Operating a data center takes far fewer people than most factories.

A good answer: A job count by type, the pay range, how many are local hires and a time frame, separate from construction jobs.

A flag: A single large jobs figure that blends construction and permanent work.

What will it do to local electric rates?

The cost of new power plants and lines has to be paid by someone. Rate rules decide whether it is the data center or other customers.

A good answer: The rate class the site will be placed in, any large load tariff, a minimum bill or long contract, and a regulator or utility statement on cost sharing.

A flag: No answer on who pays, or an answer that only says rates will not change.

Where will it sit, and what will it look like?

Size, height, lighting and screening affect neighbors every day. Zoning decides what is allowed.

A good answer: Site plans, building heights, setbacks, fencing and landscaping, night lighting rules and what the current zoning allows.

A flag: A request to change zoning with no drawings, or plans that show only the first building.

What is the construction plan?

Building takes years. Trucks, noise and dust come with it, and roads take the wear.

A good answer: Work hours, truck routes, the length of each phase, a road repair bond and a named contact for complaints.

A flag: No traffic plan, or construction described only as a few months.

Who owns it, and who will use it?

The owner, the operator and the end customer can be three different companies. Public bodies often sign agreements before anyone says who the tenant is.

A good answer: The legal owner, the operator, the expected tenant if known, and how long they commit to the site.

A flag: Project code names with no company behind them, or agreements that expire before the tax breaks do.

What happens if it closes or the equipment is replaced?

Buildings last longer than equipment. Plans for the end of life protect the town.

A good answer: A decommissioning plan, a bond or guarantee to pay for it, and what the building can be used for later.

A flag: No plan at all, or a plan that relies on the city to cover the cost.

What can the community see and enforce?

Promises that are not written down are hard to hold anyone to. Reporting and penalties turn promises into rules.

A good answer: A development agreement that puts water, noise, power and hiring commitments in writing, regular public reports and penalties for missing them.

A flag: Verbal promises, or reports that go only to the company.

Your read so far

Mark each question as you hear the answers. Your summary shows up here.

How to use this in a hearing

Send the twelve questions to the applicant ahead of the meeting and ask for written answers. Written answers can be checked later. At the hearing, ask the same questions in the same order so the record is easy to follow. Where an answer is vague, ask what document would show it, a utility letter, a sound study, a water plan, and ask for it to be filed with the application.

What a strong development agreement includes

The best outcomes tend to put the main promises in a written agreement with the city or county: power and water limits, noise limits measured at the property line, reporting dates, hiring targets, road repair funds and a plan for the end of the site's life. If a promise matters to you, it belongs in the agreement, not just in a presentation.

Related reading

Need the data or a price?
Copy the guide spec, basis of design and schedule rows, or ask for pricing and stock on butterfly valves for chillers, condenser water, liquid cooling and critical facilities.