This Week in Permitting Tech June 29, 2026: EPA Pulls Three NEPA Levers in One Week
The EPA proposed sweeping NEPA reforms with hard deadlines on June 25, issued a new Section 309 comment-letter memorandum, and closed the comment period on its New Source Review pre-permit construction rule this week. USDA's consolidated NEPA rule reaches its first EIS milestone on July 2. New York's data center moratorium remains unsigned, while EO 14318 and Florida's SB 484 both take effect on July 1, pulling data center permitting policy in three directions at once. And Honolulu reported a 40% drop in permit wait times after a year with CivCheck, the first published deployment results for a vendor already absorbed into a larger platform stack.
EPA proposes NEPA reforms with hard deadlines and a 150-page EIS cap
On June 25, EPA published a proposed rule updating its NEPA regulations with binding timelines and page caps the agency has never before attached to environmental review. Environmental Impact Statements would be capped at 150 pages, or 300 pages for extraordinarily complex actions. The agency would be required to complete an EIS within two years and certify that it met the statutory deadline. The proposal also creates a streamlined process for establishing new categorical exclusions and adopting other agencies' existing ones. Comments close July 27.
EPA's announcement positions the rule as restoring NEPA to its "original purpose," but the operational change is a binding-deadline regime where none existed before. Page caps and time limits are easy to write into a regulation. What happens when an EIS cannot be completed in two years because the underlying technical work is not done is a different question. The rule says the agency must certify compliance with the deadline; it does not say what happens to the analysis when the clock and the science diverge.
The proposal also clarifies that NEPA analysis covers reasonably foreseeable effects, not speculative or indirect ones. That sentence is the one that will get litigated. The line between "reasonably foreseeable" and "speculative" has driven NEPA case law for decades. A regulatory definition changes the starting point of those arguments without resolving them. The comment record after July 27 will show how state agencies, applicants, and litigators plan to draw that line.
EPA news release · Engineering News-Record · SBA Office of Advocacy
EPA's Section 309 memo narrows how the agency comments on other agencies' EISs
EPA also released a separate implementation memorandum this week guiding staff on comment letters under Clean Air Act Section 309 and NEPA Section 102(2)(C). Section 309 gives the EPA a statutory advisory role on other federal agencies' Environmental Impact Statements. Those comment letters become part of the public record and have historically influenced both the underlying analysis and downstream litigation. The new memorandum reframes EPA as "an advisor, not the lead or final decisionmaker," directing staff toward "plain-language and practical recommendations in EPA's lane."
EPA's announcement is direct: "previous administrations have sometimes misused this process, deploying unhelpful and expansive comment letters that went well beyond EPA's statutory authorities to stymie unfavored projects, causing confusion and costly delays." Whether that characterization is fair depends on which projects and which comment letters you read. The procedural shift is the news. A narrower comment posture changes the incentive structure for both lead agencies and applicants. Lead agencies face less external pressure on EIS scope. Applicants face fewer late-stage technical objections that require additional analysis. Litigators lose a source of record evidence.
The Section 309 memo and the NEPA rule together describe a coordinated EPA strategy: compress the timeline on EISs the agency writes, and narrow the comments on EISs other agencies write. Whether both halves hold up under litigation is a separate question. The proposed rule will be challenged. The Section 309 memo, as guidance rather than rulemaking, is harder to challenge directly but easier to reverse.
EPA news release on Section 309 · EPA Section 309 program page
EPA's pre-permit construction rule comment period closes today
The comment deadline on EPA's proposed New Source Review rule change arrives today. This newsletter covered the proposal in the June 8 and June 22 issues; the substance has not changed. The rule would allow developers to begin constructing non-emitting components before receiving a final air permit, with the "at developer's risk" provision doing the heavy lifting on the legal side.
The volume and content of the comment record will signal how seriously the rule's opponents intend to litigate. Industry comments will be supportive and largely formulaic. The ones worth reading are from state air permitting authorities and environmental NGOs, which will preview the legal arguments. EPA's final rule, if issued, lands sometime in the fall, by which point the agency will also be processing comments on the broader NEPA package. Both rulemakings are likely in the same litigation queue.
USDA's consolidated NEPA rule hits its first EIS milestone on July 2
The USDA NEPA final rule, finalized April 3, consolidates seven agency-specific NEPA regulations into a single department-wide framework and reduces the overall regulatory volume by 66 percent. The implementation timeline staged its application across two thresholds: EAs published more than 45 days after the rule (after May 18) and EISs with a notice of intent published more than 90 days after the rule (after July 2). The EA threshold has already passed quietly. The EIS threshold arrives this week.
USFS and the other USDA agencies are the practical test of whether consolidation actually changes how environmental review gets done. The pre-rule regulatory text was layered across decades of agency-specific procedures, each with its own definitions, categorical exclusions, and practitioner expectations. A consolidated framework is easier to teach and amend, but every USDA NEPA practitioner has to relearn procedures they have been following for years. Whether the consolidation reduces actual review time or just relabels the existing complexity will not be visible for at least a year.
USDA news release · WilmerHale analysis
New York data center moratorium sits on the governor's desk past the statutory window
The New York legislature passed the Responsible Data Center Development Act on June 4 with bipartisan margins. The bill establishes a one-year moratorium on new hyperscale AI data centers. This newsletter covered the legislative vote in the June 22 issue. As of late June, Governor Hochul has neither signed nor vetoed the bill nor announced a position. Under New York procedure, the governor has 10 days from formal delivery to act. The bill passed June 4; the formal delivery date has not been made public, and as of late June, Hochul had not announced a position.
Hochul's public statements have framed data center siting as a municipal-authority question, which positions her against a statewide moratorium without saying so directly. She is up for re-election. The bill's supporters include constituencies she needs; its opponents include constituencies the state needs. A pocket veto would let the bill expire without a public vote on a veto; a chapter-amendment negotiation would let her sign something narrower. Both paths lead to the same harder question: not whether to allow data centers statewide, but under what conditions and at whose expense.
The Hochul decision is the first state-level test of whether the local moratorium wave (63 jurisdictions and counting, per the trackers covered last week) translates into state-level policy. If New York signs, other states get political cover. If it dies, local actions remain the operative constraint.
Tomorrow, two other data center laws take effect. Executive Order 14318, signed in July 2025, designates projects above 100 megawatts and $500 million in capital expenditure as "Qualifying Projects" entitled to accelerated federal permitting. Florida's SB 484, signed by Governor DeSantis, operates on a different premise: local governments retain their zoning and permitting authority, utilities cannot pass data center power costs on to residential ratepayers, and data centers above a size threshold must secure separate water consumption permits. Florida sets conditions rather than a ban. That model requires state agencies with the capacity to actually enforce those conditions, which is a different problem than the one a moratorium sidesteps.
Mintz analysis · GovTech · Data Center Dynamics · Florida SB 484 (DCD) · EO 14318 (Federal Register)
The municipal AI permitting market is consolidating around a small vendor set
Smart Cities Dive ran a piece this past week on Lancaster, California's deployment with Labrynth, framing it as the latest in a small set of named-vendor municipal AI permitting deployments. Lancaster is Labrynth's inaugural municipal partner. Los Angeles and Austin are both running Archistar for plan review. The original Lancaster-Labrynth announcement came in September 2025; the trade press is now reading the pattern across deployments rather than covering individual launches.
The named vendors in the municipal AI permitting space are a much shorter list than the broader permitting-tech inventory suggests. Archistar, Labrynth, CivCheck (acquired by Clariti last year), Symbium, Set4, and a handful of others account for most of the deployments getting trade-press coverage. The market is consolidating before it has fully developed. Every deployment is publicly framed in vendor-supplied metrics: faster screening, reduced backlog, percentage cost reduction. The independent municipal evaluations that would allow practitioners to compare across deployments are not yet published.
Trade-press coverage is a useful directional signal but unreliable due diligence material. Cities that bought on demo three years ago are now asking different questions: which vendors have the deployment count and integration depth to keep running when IT leadership turns over? Most are still figuring out that this is the right question to ask.
Honolulu posted the first concrete results this month. The city deployed CivCheck in December 2025 and reported that median building permit wait times dropped by 40% over eight months, with a pilot group of residential projects clearing pre-screening in 32.5 days instead of the previous 70 days. Commercial applicants get access by late summer. CivCheck was acquired by Clariti last year, which makes Honolulu's numbers the first published deployment data for a vendor that has already changed hands. When a city builds its permit workflow around a vendor, and that vendor gets acquired, the city's ongoing relationship is tied to the acquiring company's roadmap and pricing structure. Most municipal procurement processes have no trigger for re-evaluating a tool when its ownership changes.
Smart Cities Dive · StateScoop on Lancaster · Construction Dive · Honolulu Civil Beat · GovTech on Honolulu AI
CEQ Permitting Innovators Expo set for July 31, attendee form now open
CEQ opened the attendee interest form for the Permitting Innovators Expo on July 31 at the Hilton Arlington Rosslyn, The Key. Up to 50 solutions from the June 2 submission pool will be presented to federal agencies. A Solutions Catalog goes to agencies in late 2026.
This newsletter has covered the Expo across four issues now. The selection announcement is the next thing worth covering substantively. The relevant question is whether the Solutions Catalog produces any procurement traction once it lands. Federal agencies receive solution catalogs regularly. The ones that actually move procurement tend to have a named agency champion with a funded problem already on the table.
CEQ announcement · Permitting Innovators
Permitting Tech is an independent news site covering investment, products, and policy in permitting technology. Written by Boon Sheridan.
