Most explanations of the NEPA process stop at the flowchart. Categorical exclusion, environmental assessment, environmental impact statement, done. That’s the legal shape of the review. It’s not where an environmental firm actually loses time on it.
Every federal action that isn’t categorically excluded starts with an Environmental Assessment. If the EA finds no significant impact, the agency issues a Finding of No Significant Impact and the review ends there. If it does find significant impact, the project moves into the full Environmental Impact Statement track: a Notice of Intent and scoping period, a draft EIS that goes out for a minimum 45-day public comment window, a final EIS that responds to those comments, a mandatory 30-day wait, and then a Record of Decision. That’s the process EPA and CEQ describe, and it’s genuinely useful to see laid out end to end.
Where the process actually bogs down
None of the friction we see in NEPA work happens inside a single box on that chart. It happens in the connective tissue between boxes: document control across every draft of the EA or EIS, multi-party review where technical leads, the client agency, and outside counsel all mark up the same document on different timelines, comment tracking through a 45-day window that can bring in a large volume of individual submissions, each needing a logged response, and deadline management across a process that keeps moving even when three other live projects are also moving. A firm can be excellent at the science and still lose weeks to a comment log built in three different spreadsheets, or a Record of Decision held up because nobody can say for certain which draft was the one counsel actually signed off on.
That connective tissue got harder to manage in 2025, not easier. The Council on Environmental Quality rescinded its own NEPA implementing regulations effective April 11, 2025, ending 50 years of a single binding rulebook that every federal agency worked from. In its place, each agency is now writing its own NEPA procedures, due by February 2026, with a public comment window of 30 to 60 days on each agency’s proposed rules. Industry estimates put the result at upward of 15 separate procedural frameworks across the federal government, not one. A firm doing NEPA work for the Forest Service and the Army Corps on the same day may now be tracking two different rulebooks for what used to be one process.
Multiply a 45-day comment window and a 30-day wait period across a handful of live projects, each now potentially running a different agency’s procedure, and you get exactly the kind of coordination load our review of 48 environmental firms kept surfacing: three-quarters of the firms we looked at had a real gap between the systems that hold their technical work and the systems that hold their business and project tracking. NEPA document control is that same gap wearing a different hat. The science doesn’t get easier or harder because CEQ rescinded a regulation. Knowing which draft is current, who signed off on it, and which comment deadline is closest does.
I see this from the operations side rather than the regulatory side, which is where GaiaOps sits. When we go through a firm’s NEPA workflow, the recurring finding isn’t that anyone misunderstands the process. It’s that the process lives in someone’s head and a folder structure nobody else fully trusts, so every status question turns into a person stopping billable work to go find the answer. Fixing that is document control and version tracking, not more NEPA training.
If you want a sense of where your own firm sits on this kind of operational gap, the Digital Operations Maturity Rubric is a ten-minute self-score built from the same research. The full findings are in What 48 Environmental Firms Taught Us About Operations. How GaiaOps prices the fix is on the pricing page.
Or skip straight to where your own NEPA workflow is leaking hours. That’s what a diagnostic call does: thirty minutes, data-driven, before either of us decides anything else is worth talking about.