Chapter 6 — Environmental Procedures

Where the NEPA duty comes from — and how it lands on the LPA's desk

Chapter 6 sits on top of a stack of federal authority that you should be able to recite from memory before you ever pick up a PES form. The base layer is NEPA itself — the National Environmental Policy Act of 1969 — which requires any project "financed, assisted, conducted or approved by a federal agency" to undergo environmental review and a determination of whether the action may significantly affect the human environment. NEPA is implemented through 40 CFR Parts 1500–1508 (Council on Environmental Quality regulations) and, for highway projects, 23 CFR Part 771.

The second layer is the chain of legislation that has reshaped NEPA delivery for transportation: SAFETEA-LU (2005) created the Surface Transportation Project Delivery Pilot Program; MAP-21 (2012) made it permanent under 23 USC 327 and added 23 USC 326 for categorical exclusions; the FAST Act (2015) introduced the Efficient Environmental Review Process at 23 USC 139, with mandatory schedules, coordination plans, and combined Final EIS/ROD documents. The PDFs you'll cite — 326 MOU and 327 MOU — are operationalizations of these statutes.

The third layer is the assignment instrument: California is one of the states that has assumed FHWA's NEPA responsibilities, codified in two parallel MOUs. The 326 MOU (originally effective June 7, 2007; renewed every three years) transfers responsibility for Categorical Exclusion determinations and CE reevaluations to Caltrans. The 327 MOU (effective October 1, 2012; renewed December 23, 2016 for a five-year term) transfers full NEPA authority — including EAs, EISs, FONSIs, RODs, and consultation duties — to Caltrans. Together these are referred to within Caltrans as NEPA Assignment (formerly "NEPA Delegation"). Functionally, for the vast majority of LPA projects, FHWA does not sign anything — Caltrans does, acting in FHWA's stead.

The fourth and final layer is the LAPM itself, which operationalizes all of the above for Local Public Agencies on off-system projects. Chapter 6 is not freestanding policy; it is the LPA-facing procedural overlay on top of the federal statutes, the 326/327 MOUs, the Caltrans Standard Environmental Reference (SER), and the various Programmatic Agreements and Interagency MOUs.

A practical implication: when reviewing a project, the absence of a Caltrans-signed CE/FONSI/ROD doesn't mean a procedural step was skipped — it means the federal NEPA duty has not been satisfied at all. The signed document is the federal compliance record, not a Caltrans deliverable. This matters when defending a project in audit: you're not showing that "Caltrans reviewed it," you're showing that federal NEPA was satisfied under the assignment, and Caltrans is the agent who signed.

The cast of characters — and what each one personally signs

Chapter 6 names more actors than any other chapter in the LAPM. Get this map clear early, because every procedural question in Chapter 6 reduces to "who signs what, and is that signature delegable?"

On the LPA side, the duties are concentrated in a single, multi-paragraph paragraph (22 numbered items in §6.1). The LPA programs the project in the FSTIP, develops the project description and limits, completes the PES or PES (NI) form, retains environmental consultants under Brooks Act QBS (Ch 10), conducts required technical studies, prepares the NEPA document, runs public hearings (Ch 8), incorporates mitigation into PS&E (Ch 12), implements mitigation during construction (Ch 16), maintains records for three years post-reimbursement (and longer when mitigation monitoring is ongoing), and notifies the DLAE of any scope change. The LPA never signs the NEPA document itself. Caltrans signs.

On the Caltrans side, the players multiply. The District structure carries the day-to-day load:

A particular wrinkle: only a federal agency can post in the Federal Register. So for EISs, Caltrans approves the NOI and sends it to FHWA for FR publication, even under the 327 MOU. Same for the Record of Decision (after Caltrans signs it). This is the only routine point at which FHWA's signature is needed on a 327-assigned project, and it's mechanical rather than substantive.

Any federal involvement triggers NEPA for the entire project

The applicability rule is more aggressive than people realize. Under 40 CFR 1508.18(a), any local assistance project "financed, assisted, conducted, regulated or approved by federal agencies" is subject to NEPA. Chapter 6 then drives the point home: any amount of federal involvement in a project requires that the entire project be included in the process, regardless of phases or segments not funded by FHWA. The scope of NEPA responsibility is not determined by funding alone.

What that means operationally: a project that takes federal funds only in the construction phase still requires NEPA over the entire scope, including the privately-funded preliminary engineering and any locally-funded right-of-way work. You cannot segment a project to wall off the federally-funded portion from NEPA review. This is the principle behind the longstanding "logical termini and independent utility" doctrine — projects must have logical termini, independent utility, and not restrict consideration of alternatives for other reasonably foreseeable transportation improvements (23 CFR 771.111(f)).

Two related applicability rules: NEPA requires that environmental information be "of high quality based on accurate scientific analysis and expert agency comment" (40 CFR 1500.1(b)). LPAs are required to follow Caltrans policy and SER guidance to ensure NEPA documents reflect current scientific methodologies — which is why consultant qualifications matter (the SER specifies preparer qualifications by discipline), and why technical reports prepared by underqualified staff get rejected at QC. And NEPA further requires that "the NEPA document concentrate on the issues that are truly significant to the action in question, rather than amassing needless detail" — a discipline that pushes back on the consultant tendency to throw everything into the EA hoping something sticks.

PES vs PES (NI): the two-form entry to NEPA

Every project enters the NEPA process through one of two forms. The Preliminary Environmental Study (PES) form is the default — used for any project that involves engineering design, R/W acquisition, ground disturbance, or physical construction. The PES (NI) form — Preliminary Environmental Screening for Non-Infrastructure projects — is the lighter cousin, introduced in 2011 when program funds began flowing to non-infrastructure work (ATP, CMAQ, Transportation Enhancement programs).

The PES form does three things at once: (1) describes the project, (2) identifies which technical studies are required by checking 30-some categorical questions against the project, and (3) recommends a Preliminary NEPA Class of Action (CE, EA, or EIS). When the DLAE and SEP sign the PES, they are concurring with all three — and that signature unlocks the LPA's ability to begin technical studies.

The PES (NI) is far simpler: a 29-question Section A checklist, a Section B sign-off, and a continuation sheet for any "TBD" answers. If any question on the PES (NI) is justifiably "Yes" or remains "TBD" after coordination, the project is no longer non-infrastructure and the full PES form is required. The PES (NI) workflow exists to let pure outreach, education, ridesharing, and vehicle purchase projects bypass the heavier review — not as a shortcut around it.

Three things to internalize about the PES gate:

1. The LPA cannot start required technical studies until the PES is fully signed. Studies done in advance are at risk — Caltrans may direct different studies or different methodologies, and pre-PES work may need to be redone or supplemented at the LPA's expense.
2. The PES is the controlling description of project scope for NEPA purposes. When PS&E plans show features not described on the PES — added intersections, expanded footprint, new structures — the PES needs amendment before final design can proceed.
3. Caltrans signs the PES only after verifying the project is in the RTP and FSTIP. A project missing from the federally-approved program will not get PES signature, full stop. This is why FSTIP programming must precede PES submission, not run in parallel.

CE, EA, EIS — what each one is, and what unlocks the next tier

NEPA recognizes three Classes of Action, distinguished by the magnitude of expected environmental impact. The Class of Action determination drives the depth of analysis, the documents prepared, the public process required, and the time to delivery.

Categorical Exclusion (CE). Defined at 40 CFR 1508.4 and 23 CFR 771.117(a) as actions that do not (a) induce significant plan growth or land use impacts, (b) require relocation of significant numbers of people, (c) have significant impacts on natural, cultural, recreational, historical, or other resources, (d) involve significant air, noise, or water quality impacts, or (e) have significant impacts on travel patterns. CEs are the dominant Class of Action for LPA Federal-aid work — most StanCOG-scale projects qualify.

23 CFR 771.117 organizes CEs into three lists:

• (c) list: activities normally categorically excluded — no documentation required beyond the determination. Examples: planning and research activities, surveying, and certain types of repair work.
• (d) list: activities that may qualify based on individual project review — documentation required. Most LPA CEs are processed under this list.
• 326 MOU Appendix A: additional CE categories Caltrans is authorized to approve under the 326 assignment.

Projects outside these lists can still qualify for a CE under the 23 CFR 771.117(a)/(b) general criteria — Caltrans assumes that responsibility under 327. Even when a project would normally be a CE, 23 CFR 771.117(b) requires further study if unusual circumstances exist: significant environmental impacts, substantial controversy, significant Section 4(f) or Section 106 impacts, or inconsistencies with federal/state/local law. Unusual circumstances bump the project out of CE territory regardless of how cleanly it fits a (c) or (d) category.

Environmental Assessment (EA). Used when CE doesn't fit cleanly but significance isn't established. The EA tests whether impacts are significant; if they aren't, the result is a Finding of No Significant Impact (FONSI). If they are, the project moves to EIS. EAs come in two flavors:

• Routine EA — single alternative analysis, conventional public process, ~2–3 years to FONSI.
• Complex EA — multiple location alternatives, debate over purpose and need, strong public controversy, logical termini issues, individual Section 4(f) determinations, complex ESA issues, numerous cumulative impacts, or high mitigation costs. Reviewed by HQ EC and Legal in addition to district. Public review period of 30 days.

The Routine vs Complex determination is made by the DLAE and SEP with HQ EC concurrence. It's not optional — projects meeting Complex criteria must be processed as Complex, and an LPA that pushes for "Routine" to save schedule is setting up a later determination that the EA is inadequate.

Environmental Impact Statement (EIS). Highest level of analysis, used when significant impacts are expected. EIS process requires a Notice of Intent (NOI) published in the Federal Register, scoping meetings, a Draft EIS with multiple alternatives, a 45-day public review, a Final EIS, and a Record of Decision. EISs take 3–4 years on a best-case path. Complex EISs subject to 23 USC 139 (after December 4, 2015) must produce a coordination plan with schedule, identify participating agencies, and consolidate federal reviews into a single document where practicable.

One additional category outside the three classes: non-infrastructure projects processed via PES (NI). These are not technically a separate Class of Action — they're still processed as CEs — but the PES (NI) Section B serves in lieu of both the standard CE Checklist and the Transportation Air Quality Conformity Findings Checklist. Examples include public awareness campaigns, safety education, freeway service patrol, ridesharing activities, and vehicle purchases.

NEPA is the umbrella — but a dozen substantive statutes drive the analysis

NEPA itself is procedural — it doesn't mandate a particular outcome, it mandates a particular process for considering environmental consequences. The substantive law lives in a series of independent statutes that each protect a specific environmental element. Compliance with these is required prior to completion of the NEPA process; the NEPA document then summarizes how each was satisfied.

The most consequential ones for LPA Federal-aid work:

The NEPA/CWA Section 404 Integration MOU deserves a specific note. When a project will permanently impact 5+ acres of waters of the U.S. and requires an EIS, this MOU merges the NEPA and Section 404 processes into a single coordinated path. The USACE, USFWS, EPA, NMFS, FHWA, and Caltrans agree on early and ongoing coordination, with specified written concurrences required. If you're working on a project that might trip this threshold, the LPA, DLAE, and SEP must meet early to discuss MOU procedures.

And the Section 106 Programmatic Agreement (Section 106 PA), first amended 2014, is the most important streamlining instrument for cultural resources in California. The PA allows Caltrans to consult directly with SHPO for the Federal-aid program, exempts certain property types from evaluation, exempts certain project types from any Section 106 involvement, and defines Environmentally Sensitive Areas (ESAs) to avoid site excavations for evaluation. Every project must be screened by the district PQS to determine whether Section 106 applies — even when an LPA "knows" their project doesn't touch cultural resources, the screening is the procedural step that documents that conclusion.

One process, two legal frameworks — and the LPA is on the hook for both

NEPA is federal; CEQA is California-only. They are similar enough that most projects run a single integrated environmental process, but the underlying legal duties remain distinct. Chapter 6 is exclusively about NEPA, but it cannot be read without understanding that for off-system Federal-aid projects, the LPA serves as the CEQA lead agency — Caltrans serves as the NEPA lead agency.

The integration produces three joint document types, which the LPA can choose between based on project complexity:

• CE/CE Determination — joint CEQA Categorical Exemption and NEPA Categorical Exclusion. Separate determinations are made, but documented together.
• IS/EA — joint CEQA Initial Study and NEPA Environmental Assessment. Most common joint document for moderate-impact projects.
• EIR/EIS — joint CEQA Environmental Impact Report and NEPA Environmental Impact Statement. For significant-impact projects.

The document types don't have to match. An EA may be the right NEPA document when CEQA requires an EIR — they're independent determinations. The decision matrix is project-specific.

Key procedural differences to keep clear:

The lead-agency split is what trips LPAs up most often. When the LPA's environmental consultant prepares an "EA," it's the LPA's deliverable but Caltrans's signature that controls; when the same consultant prepares an "IS" alongside it, it's the LPA's signature that controls. For joint IS/EA documents, the LPA must understand which sections satisfy which framework — Caltrans QC reviews the EA portions against SER guidance, but the IS portions are the LPA's responsibility to defend under CEQA.

Why environmental almost always sets the critical path

Environmental compliance can occur simultaneously with Preliminary Engineering — but the LPA may not commence final design until Caltrans signs the CE, FONSI, or ROD. That single rule makes environmental the critical-path activity on nearly every Federal-aid project, because PE can be done in parallel but final design cannot be.

LAPM's best-case estimates assume sufficient consultant staff, no rework, no missed survey windows, no agency review delays, and clean public processes. Add 30–50% for real-world conditions:

1. CE, no required technical studies: ≈ 1 month, assuming PES and supporting docs are complete and sufficient.
2. CE with required technical studies: 6 months to 2 years, depending on which studies. Plant species surveys may have to wait for spring blooming windows. Cultural resource surveys can take a week (screened undertakings under the 106 PA) to 20+ months (complex projects with archaeological excavation).
3. Routine EA → FONSI: 2–3 years. Includes 30-day public review.
4. Complex EA → FONSI: Add HQ and Legal review time on top of routine, typically pushing to 3+ years.
5. EIS: 3–4 years. Includes scoping, NOI publication, Draft EIS, 45-day public review, Final EIS, and ROD.

Section 106 deserves special attention as a schedule risk. Section 106 requirements must be completed before the final EA or EIS can be approved — not the Draft. The preliminary Finding of Effect for cultural/archaeological resources must be done before the Draft EA or EIS can circulate for public review. This means cultural resource work has to start early and finish on the project's longest tail.

One useful timing rule: do not begin technical studies before the PES is fully signed. The LAPM is explicit: technical studies done before the PES signature are at risk of being directed differently after signature. Section 106 studies in particular should not begin until district PQS and DLAE give verbal approval of the APE map.

Where environmental commitments most often get lost — and how to catch it

Mitigation is where environmental review intersects with the rest of the LAPM most directly. The NEPA document identifies mitigation; the LPA compiles a list and provides it to the DLAE; the DLAE forwards it to the SEP for entry into LP2000; the mitigation must be incorporated into PS&E (Chapter 12); it must be implemented during construction (Chapter 16); and any long-term mitigation must be monitored for the duration of its required term.

The LPA must certify under 23 CFR 771.109(b) that all required mitigation has been completed or is included in the Final PS&E, and that any required ongoing maintenance is implemented. The DLAE, in coordination with the SEP, ensures that mitigation is a "reasonable expenditure of federal funds." Caltrans assures implementation by conducting periodic process reviews under 23 CFR 771.105(d)(2).

At PlanCheck, the verification you owe yourself is straightforward: open the signed CE/FONSI/ROD and the LPA's mitigation commitment list. Cross-reference each commitment against the PS&E special provisions. Every NEPA mitigation should appear in the specs as a contract requirement. Any that's missing is a returnable defect — and a much more common one than people realize, especially on consultant-led projects where the environmental and design teams don't share files.

The three triggers — and the three possible outcomes

NEPA approval is not permanent. Per 23 CFR 771.129, the original determination may need to be reevaluated when one of three triggers occurs:

1. Project is proceeding to the next major federal approval. Each time federal authorization is requested for a new phase (R/W, construction), the validity of the existing NEPA document is reconfirmed.
2. Project changes. Scope, footprint, schedule, or limits change in a way that may affect environmental conclusions. The LPA is responsible for notifying the DLAE; the DLAE notifies the SEP; the SEP determines whether reevaluation is needed.
3. Three-year timeline for an EIS. EIS revalidation is required every three years regardless of project changes, because conditions, agency policies, or affected resources may have evolved.

The reevaluation is conducted by a qualified environmental planner — typically the SEP or designee — with technical specialists assessing any topical areas affected by changes. The outcome falls into one of three buckets:

The schedule cost of reevaluation depends entirely on the outcome. Outcome 1 (still valid) is one form and a few days. Outcome 2 (needs updating) can add weeks for a CE supplement to months for an EA addendum with public review. Outcome 3 (no longer valid) means starting the NEPA process over — often a quarter or more of lost schedule.

The way an LPA gets to Outcome 3 unintentionally: a CE approved with a tight scope, then scope creep through PE — added intersections, expanded footprint, a new structure — and at PS&E submittal the project doesn't match the CE. The DLAE catches it (or the auditor does later) and the CE is no longer valid. The fix is to amend the PES and reevaluate proactively rather than reactively. The signal at PlanCheck: every PS&E plan feature should be traceable to the PES.