Five Common Mistakes in Section 7 ESA Consultation Documentation

Why documentation fails before the science does

Section 7 consultations under the Endangered Species Act are one of the most litigated parts of federal permitting. A study of 88,290 Fish and Wildlife Service consultations between 2008 and 2015 found that jeopardy findings came up in only 0.03% of formal consultations ⁷. During this period, zero projects were permanently stopped by a jeopardy finding ⁷. The process almost never blocks a project on its merits, but the federal government recently defended over 570 ESA lawsuits, which likely cost taxpayers millions of dollars ². The problem is in how these calls are documented, not that the underlying decision making is wrong. When a Biological Opinion or Biological Assessment gets challenged in court, difficulty usually arises because the record is hard to defend, not because the science was indefensible ^2,13.

March 2026 reset the standard

In March 2026, the U.S. District Court for the Northern District of California removed four regulatory provisions from the Trump-era Section 7 rules and reinstated stricter standards from before 2019 ¹³. The court rejected the "reasonably certain to occur" standard for effects analysis, removed the "as a whole" qualifier from the definition of habitat protection, and tightened what counts as acceptable mitigation ¹³. A day later, the Endangered Species Committee convened for the first time in 30 years and granted a unanimous national security exemption for oil and gas in the Gulf of Mexico ². Documentation habits that were tolerable under the old rules are now more exposed to litigation ^6,13.

1Non binding mitigation as a basis for no jeopardy findings

This is the most consequential documentation failure in Section 7 practice. Agencies include mitigation measures in Biological Opinions to support a no-jeopardy conclusion but do not make sure those measures are enforceable ¹³. Under the reinstated standards, mitigation must be legally binding, fully funded, and guaranteed ^2,13.

The Moapa dace case shows what survives review. FWS evaluated cumulative groundwater withdrawals that could affect an endangered fish with a population of about 1,300 ⁴. The Ninth Circuit upheld the BiOp because conservation commitments were specific and enforceable, including funded habitat restoration over a defined schedule ⁴. Anything less than that mix of funding, schedule, and obligation becomes a liability under the restored standards.

2Guild analysis instead of species specific review

Section 7 requires effects to be evaluated for each listed species individually. Some agencies shortcut this by grouping species into "guilds" and analyzing impacts at the guild level ³. In CBD v. Michael Regan (2024), a court vacated Florida's assumption of Clean Water Act permitting because FWS used guilds rather than species-specific analysis for 139 listed species ³.

This is a documentation problem as much as a methodological one. Even if the underlying science accounts for each species, the written record has to show it. When a BiOp combines 139 species into groups and does not walk through effects on each one, the record does not support the conclusion.

3Incidental Take Statements without evidence of species presence

An Incidental Take Statement authorizes a specific amount of take as part of an otherwise lawful activity. The authorization needs evidence that the species is actually in the action area and that take is reasonably certain to occur ^1,8. In Arizona Cattle Growers v. FWS, the Ninth Circuit called it unreasonable to issue an ITS when FWS could not prove species existed on large grazing allotments ¹.

If species surveys are outdated, incomplete, or based on range maps rather than field data, the ITS does not have a factual foundation ¹. Under the reinstated standards, agencies relying on desk reviews and historical range data should expect those documents to be challenged ¹³.

4Wrong "effects of the action" standard

The definition of what counts as an effect has shifted repeatedly. The Trump-era rules narrowed it to consequences "but for" caused by the action and "reasonably certain to occur" ¹³. The March 2026 ruling rejected that narrowing because it let agencies ignore scientifically supported but uncertain long-term impacts ¹³. The reinstated pre-2019 definition is broader: effects include consequences that are reasonably foreseeable, not only certain ones ¹³.

Any BA or BiOp drafted under the 2019 rules that applied the "reasonably certain" standard may now be deficient ^6,13. The fix is revisiting the effects analysis so it accounts for reasonably foreseeable consequences. For projects still in permitting, that can mean reopening documents that were treated as complete, which again ties back to record keeping ⁶.

5Confusing ESA cumulative effects with NEPA cumulative impacts

NEPA cumulative impacts include past, present, and reasonably foreseeable future actions by all parties. Under Section 7, "cumulative effects" has a narrower definition: future state, tribal, local, or private actions reasonably certain to occur in the action area ^11,14. Federal actions are excluded because they receive their own consultation ¹¹.

The Ninth Circuit has held that a full cumulative effects analysis is not required for informal consultations in some circumstances ⁹. Perkins Coie clarified that the circuit distinguishes between the two frameworks ¹¹. When agencies import NEPA methodology into a BA, it can go wrong in both directions. Overcounting buries the record with actions that are not legally relevant. Undercounting misses private and state actions that should be there.

6Localized habitat degradation and the "as a whole" problem

Before March 2026, the regulatory definition of adverse modification of critical habitat included the qualifier "as a whole" ¹³. Agencies used that language to argue that damage to a specific habitat unit did not count as long as the overall designation remained functional ¹³. That qualifier is gone, and even incremental or localized degradation can support an adverse modification finding under the reinstated standard ¹³.

BiOps that evaluated habitat impacts only at the range-wide or designation-wide scale are more exposed ^5,13. Defenders of Wildlife v. U.S. Forest Service showed courts examining whether agencies evaluated localized impacts adequately ⁵. If the document does not address site-specific habitat quality and how the action affects the particular unit where the project sits, that is a gap.

7Programmatic consultation standing in for project level review

Programmatic Biological Opinions provide a framework that individual projects tier from. The problem is when agencies treat the programmatic BiOp as the entire Section 7 obligation and skip adequate review at the project level ¹². Sierra Club v. Department of Interior (Rio Grande LNG) involved the Fifth Circuit examining whether project-level analysis held up when a project leaned on programmatic coverage ¹².

The programmatic BiOp sets parameters and assumptions. When a project falls within those parameters, the agency still needs to document why the specific action is consistent with the programmatic analysis, what site conditions exist, whether species composition has changed, and whether reinitiation triggers have been met. Usually this project-level documentation is thin or missing. When a challenge comes, the administrative record has a programmatic BiOp from years earlier and little connecting it to the actual project.