Subscribe
Community and Policy

How to Read an Environmental Review for a Data Center Project

Environmental assessments and impact statements are long. This guide shows where to look and what to ask.

Key takeaways

  • An environmental assessment, or EA, is a shorter review. An environmental impact statement, or EIS, is a deeper one for larger effects.
  • Start with the purpose and need, the alternatives, and the mitigation sections, then read the topic chapters that matter to you.
  • Look for assumptions, thresholds and monitoring commitments, not only the conclusions.

Environmental reviews are written to inform decision makers and the public about the likely effects of a proposed project. Whether a data center needs one depends on the law, the funding and the permits involved. Some are required by federal rules, some by state rules, and many projects fall under neither. Where a review exists, it can be dense. A few reading habits make it manageable.

Know which document you have

  • Categorical exclusion or exemption: a finding that a type of action does not normally need detailed review.
  • Environmental assessment: a shorter study that decides whether effects are significant. It may end in a finding of no significant impact, or it may lead to a full statement.
  • Environmental impact statement: a detailed study with alternatives, public comment and a formal response to comments.

State and local reviews use their own names and thresholds, which vary by jurisdiction.

A reading order that saves time

  1. Summary: read it first to see what is proposed and what the document concludes.
  2. Purpose and need: this explains why the project is being done and frames the alternatives.
  3. Alternatives: look for a no-action option and at least one different site or design.
  4. Topic chapters: go to the issues you care about, such as noise, water, air, traffic, wildlife, wetlands, visual effects and cultural resources.
  5. Cumulative effects: this section considers the project together with other existing and planned activity.
  6. Mitigation and monitoring: these list what will be done to reduce effects and how it will be checked.
  7. Appendices: technical studies, modeling inputs and agency letters are often here.

What to check in each topic

  • Baseline: how was current conditions measured, and when? A single day of noise readings tells you less than a longer study.
  • Assumptions: water use, generator run hours, truck trips and power demand should be stated, with reasons.
  • Thresholds: what level counts as significant, and who set it?
  • Study area: is the area large enough to include the neighbors who would notice effects?
  • Uncertainty: does the document say what it does not know?

Red flags and good signs

Be cautious when conclusions are stated without data, when mitigation is described as "to be determined," or when a topic is dismissed in a sentence. Good signs include named responsible parties, specific limits, monitoring schedules and a clear response to earlier public comments.

Making comments count

Comments are most useful when they are specific. Cite the page or section, state the concern, and say what information or change you are asking for. Comment periods have fixed deadlines, so confirm the date as soon as you learn a review exists. Submit comments in writing even if you also speak at a hearing, so they are part of the record.

This article is general information, not legal advice. Review procedures and deadlines depend on the law that applies to the project.

Found this useful? Pass it on.

This article is general information for public education. It is not legal, tax, financial or engineering advice. Rules and conditions differ by location, so check with qualified local professionals. Spot an error? Write to info@datacenteroutreach.com and we will correct it.

Have news, a project or a question?Send a press release, your company details, a data center project or a question. We read everything.
Send it in