Endangered Species Review for Data Center Sites: What Triggers It and What to Check

Data center campuses are large, often greenfield, and frequently cleared and graded in one or two big phases. That makes them more likely than a small infill project to touch habitat. They also come with linear pieces, such as transmission lines, gas laterals, water lines and fiber, that cross land the developer does not control.

The Endangered Species Act (ESA) prohibits “take” of listed fish and wildlife, which includes harming, harassing or killing them, and harm can include significant habitat modification that actually injures or kills wildlife. Listed plants are treated differently, and protection on private land is generally narrower unless a federal nexus or state law applies. The ESA is administered by the U.S. Fish and Wildlife Service (USFWS) for most terrestrial and freshwater species and by the National Marine Fisheries Service (NMFS) for most marine and anadromous species.

The first step is a desktop screen. USFWS’s Information for Planning and Consultation tool (IPaC) lets you draw a project area and returns the federally listed, proposed and candidate species that may occur there, any designated critical habitat, and related resources such as migratory birds. It is a starting list, not a finding. A species on the list may have no suitable habitat on the site, and the list depends on the area you draw.

• Draw the IPaC area to include the full campus and the likely utility and road corridors, not just the main parcel.
• Check the state natural heritage program or wildlife agency for state-listed species and known occurrences. State rules and data access vary.
• Compare species habitat needs to what is actually on the site: forest type, streams, wetlands, caves, grassland or open water.
• Note species that are proposed for listing; their status can change during a long project.
• Check for bald and golden eagle nests and migratory bird issues, which fall under separate federal laws.

A qualified biologist then confirms whether suitable habitat is present and whether surveys are needed. Many species surveys can only be done in certain seasons, which is the first place a schedule can slip.

How the ESA reaches a project depends on whether there is a federal nexus. For data centers, the most common nexus is a Clean Water Act Section 404 permit from the U.S. Army Corps of Engineers for wetland or stream impacts. Federal funding, federal land, or a federal license for a related facility can also create one.

Under Section 7, many projects end with informal consultation, where the agency concurs that the action is not likely to adversely affect listed species, often because the project commits to avoidance measures such as timing restrictions. Formal consultation takes longer. Some regions also have programmatic consultations or regional HCPs that streamline review for common species, so ask what exists locally.

Without a federal nexus, there is no consultation requirement, but the prohibition on take still applies. The usual approach is to design the project to avoid take, document the analysis and follow seasonal restrictions. A Section 10 permit is the formal route when take cannot reasonably be avoided. This is why the wetlands review and species review are often linked: avoiding a 404 permit can also mean avoiding Section 7, while needing one brings both.

The most common way species issues affect a data center schedule is timing. Where listed bats roost in trees, agencies often recommend or require that tree clearing happen only in the season when bats are hibernating elsewhere. Migratory bird nesting seasons create similar windows for clearing and grading. Aquatic species can limit when in-stream work is allowed. The specific windows vary by species, region and agency guidance.

Survey seasons matter just as much. Presence or absence surveys for many species are only valid at certain times of year. Missing a survey season can push a decision, and the clearing window that follows it, by close to a year.

Critical habitat is a specific area designated as essential to a listed species’ conservation. The legal effect is narrower than many assume. Under Section 7, federal agencies must make sure the actions they authorize, fund or carry out do not destroy or adversely modify critical habitat. The designation does not, by itself, impose requirements on a private project with no federal nexus.

In practice, critical habitat on or near a site is still a meaningful flag. It signals that the species is present or the habitat is important, it raises the stakes of any federal permit, and it can draw public attention. Treat it as a reason to plan avoidance and expect closer review, not as an automatic stop or an automatic pass.

The campus parcel is not the only footprint. A new transmission line, substation, gas lateral, water line or fiber route may cross habitat the developer never considered. These are often built by utilities or providers with their own permitting and their own federal nexus, but delays on them still delay the campus.

Screen the likely corridors at the same time as the site. A clean parcel with a transmission route through a known species area has a species question, just one step removed. The site due diligence checklist shows where this fits among other environmental items.

1. 01Run IPaC on the campus and likely utility corridors and save the official species list output.
2. 02Check state natural heritage and wildlife agency data for state-listed species and known occurrences.
3. 03Have a biologist assess habitat and identify any required surveys and their seasons.
4. 04Decide whether a federal nexus is likely, starting with wetlands and streams.
5. 05Map clearing windows and survey seasons against the deal and construction schedule.
6. 06Plan avoidance in the layout: buffers on streams, forest blocks, caves or known nests.

When we screen a site, species data is layered with wetlands, floodplain and forest cover, because the same stream corridors and wooded areas usually drive all of them.