Every building project touches the environment, and a stack of federal and state laws exists to make sure that impact gets examined before construction starts. As a project manager, you won't personally write an Environmental Impact Statement or model energy performance, but you absolutely need to know what triggers these requirements, how long they take, and what happens when you ignore them.

Three regulatory domains dominate this topic. First, the National Environmental Policy Act (NEPA) requires federal agencies to evaluate environmental consequences before approving projects that use federal funding or require federal permits. Second, the Clean Water Act's Section 404 controls any filling or dredging of wetlands and other waters, requiring permits from the U.S. Army Corps of Engineers. Third, energy codes, primarily the International Energy Conservation Code (IECC) and ASHRAE Standard 90.1, dictate how buildings must perform thermally and mechanically.

State-level equivalents add another layer. California's CEQA is the most well-known state environmental law, but many states have their own versions. These can be more stringent than federal requirements, and the project manager must track both.

For the ARE, expect questions that test whether you can identify which review pathway applies to a given scenario, what triggers escalation from a Categorical Exclusion to a full EIS, and how energy code compliance paths differ. Getting the sequencing wrong on environmental clearances can stall a project for months or years.