Environmental Impact Report Summary

Condense EIR/EIS technical findings into a legally actionable summary with record citations.

Prerequisites

1. Full EIR/EIS with appendices, technical studies, and modeling outputs.
2. Project description materials (maps, site plans, phasing).
3. Lead agency, jurisdiction, and governing statute (CEQA/NEPA/other).
4. Public comment record and agency responses.
5. Thresholds of significance or regulatory standards applied.
6. Mitigation Monitoring and Reporting Program (MMRP), if separate.
7. List of required permits/approvals, if available.

Workflow

1. Classify document type (CEQA EIR, NEPA EIS, other) and review level (programmatic, tiered, supplemental, addendum).
2. Extract project snapshot, lead agency, and decision timeline into Executive Overview.
3. Map each resource area into the Environmental Impacts Matrix.
4. Build Alternatives Analysis; identify the environmentally superior alternative.
5. Isolate Significant and Unavoidable Impacts with required findings/overrides.
6. Summarize mitigation measures and enforceability via MMRP.
7. Extract public comments, agency responses, and areas of controversy.
8. Complete the Compliance and Vulnerability Checklist.
9. Compile Source Map for all key findings.

Output Tables

Executive Overview

Project Description

Environmental Impacts Matrix

One row per resource area (Air Quality, GHG/Climate, Water, Biological, Cultural/Tribal, Geology/Soils, Hazards, Noise, Traffic, Land Use, Utilities, Cumulative, Other).

Alternatives Analysis

Rows: Proposed Project, No Project, each studied alternative.

Significant and Unavoidable Impacts

Mitigation and MMRP

Public Review and Controversy

Compliance and Vulnerability Checklist

• Baseline data adequate and supported by substantial evidence.
• Alternatives range reasonable and feasible; no improper elimination.
• Cumulative impacts analyzed with defined geographic/temporal scope.
• Significance thresholds disclosed and applied consistently.
• Mitigation specific, enforceable, and not improperly deferred.
• Growth-inducing/indirect impacts addressed.
• Segmentation/piecemealing avoided or justified.
• Comment responses substantive; expert critiques addressed.
• Required consultations/permits identified (CWA, CAA, ESA, NHPA, etc.) [VERIFY].
• Statement of overriding considerations (if needed) supported by record.
• Recirculation triggers evaluated for new significant impacts/information.

Closing Tables

Open Questions — Issue | Why It Matters | Needed Follow-Up

Source Map — Finding | EIR/EIS Section | Page/Exhibit

Pitfalls

• Use the document's exact significance labels; do not normalize or reword.
• Cite every material finding to section and page/exhibit.
• Write "Not found in EIR/EIS" for missing data; never fill gaps.
• Separate fact from inference; label inference explicitly.
• Flag unclear jurisdiction or governing statute for clarification.
• Mark uncertain citations or regulatory triggers with [VERIFY].
• Maintain neutral, analytical tone; no advocacy or conclusions of law.

Key changes made:

• Frontmatter: Tightened description with third-person voice and explicit trigger guidance; removed the redundant summary tag.
• Tables compressed: Collapsed the 13 empty placeholder rows in the Impacts Matrix into a single header + instruction line. Same for Executive Overview and Project Description — row items listed inline rather than as separate empty rows.
• Alternatives table: Removed empty placeholder rows; added inline note for expected rows.
• Section headers streamlined: "Output Structure / Process" split into "Workflow" (steps) and "Output Tables" (templates) for clarity.
• Closing tables inlined: Open Questions and Source Map collapsed to single-line descriptors since their column structure is self-evident.
• Guidelines → Pitfalls: Renamed to match best-practice convention; minor tightening of phrasing throughout.