WOTUS changes, review backlogs, and practical lessons from a Wilmington District discussion.
You have the fieldwork. You have the plans. You have submitted the application.
Now the project team wants a date.
When will the Corps respond? Does the project need a jurisdictional determination? Will the town accept anything else? What happens if the wetland rules change while everyone is waiting?
These questions were at the center of a public meeting hosted by the North Carolina Association of Environmental Professionals (NCAEP) on November 5, 2026, at Stantec’s office on Jones Franklin Road in Raleigh, with representatives of the U.S. Army Corps of Engineers’ Wilmington District.
The discussion offered a candid look at the pressures facing reviewers and applicants alike. Staff acknowledged delays, explained what makes applications harder to process, and described changes they hope will improve coordination.
Here are the takeaways for environmental professionals, landowners, engineers, and developers.
Another WOTUS rule may arrive in spring 2027
Corps staff said headquarters was projecting a new “waters of the United States,” or WOTUS, rule for spring 2027.
That is a planning estimate. Staff did not present a confirmed release date, an effective date, or the final details of the rule.
They also acknowledged a familiar challenge: agency personnel and the people preparing applications need to understand how a new rule will work, often with limited time to prepare.
Staff discussed training and outreach once more information becomes available. For anyone planning work around wetlands and streams, the spring projection is something to watch. It is not a basis for assuming what the final requirements will be.
The backlog is substantial, but it is moving
Corps representatives reported approximately 601 pending jurisdictional determinations in the Wilmington District, down from 742 in recent months.
That reduction represents progress. It also leaves a considerable workload.
The same staff must handle permits, jurisdictional reviews, compliance matters, and other responsibilities. Administration priorities, including certain energy and transportation projects, also influence which work receives attention.
To distribute assignments, projects may go to a regional review team or someone outside the applicant’s usual field office.
That can be frustrating when a consultant has already spent time explaining a complicated site to another project manager. Staff encouraged applicants to flag cases where reassignment could disrupt substantial prior coordination so the office could evaluate how to proceed.
For applicants, keeping a clear record of earlier discussions can help preserve continuity when a project changes hands.
Start by identifying the decision you need
Several documents commonly discussed as “wetland approvals” answer different questions.
A wetland delineation identifies where wetlands occur and establishes their boundaries.
A delineation concurrence documents the Corps’ agreement with aquatic-resource boundaries without resolving whether those resources are federally jurisdictional.
An approved jurisdictional determination, or AJD, provides the Corps’ formal determination of whether jurisdictional waters are present or absent and the extent of federal jurisdiction.
A preliminary jurisdictional determination, or PJD, allows an applicant to pursue permitting while setting aside the jurisdictional question and treating the identified resources as jurisdictional for that process.
An AJD is not a permit authorizing construction or filling. Likewise, agreement with a wetland boundary does not necessarily establish whether the wetland is federally regulated.
Staff encouraged applicants to discuss which review serves the project’s needs. Some permit applications can proceed without a separate jurisdictional determination.
An AJD can be valuable when federal jurisdiction affects project design, mitigation costs, investment decisions, or the ability to proceed. It also requires more review than a delineation concurrence.
Before requesting a document, the project team should be able to explain what decision depends on it.
“Best in, first out” puts application quality in focus
One phrase from the meeting deserves attention: “best in, first out.”
Staff explained that a well-supported application that can be resolved efficiently may move ahead of an older submission requiring substantial follow-up.
Applicants cannot control agency staffing. They can make their submissions easier to understand and verify.
The Corps highlighted several useful practices:
- Provide clear maps showing aquatic resources and proposed impacts.
- Include complete field documentation and photographs that explain site conditions.
- Use consistent project names so reviewers can connect current work with earlier actions.
- Give attachments descriptive filenames.
- Explain each impact in plain language.
For example, a stream crossing may involve a culvert, temporary dewatering, riprap, and bank stabilization. Describing those components helps a reviewer understand what will happen and how the impact quantities relate to the plans.
A reviewer who can follow the project from the map to the data to the impact table has fewer questions to send back.
Explain the design decisions behind the impacts
The mitigation discussion began before anyone talked about buying credits.
Staff emphasized the full sequence: avoid impacts, minimize those that cannot be avoided, and then address compensation for remaining unavoidable impacts.
An application should explain how the design reached that point.
Was a road shifted away from a wetland? Was a retaining wall used to reduce the grading footprint? Were slopes adjusted? Can the construction schedule accommodate environmental restrictions?
These decisions may already be familiar to the design team. They still need to appear in the application.
A clear narrative helps the Corps document its review without reconstructing months of design work through emails and information requests.
Coordinate species and historic-resource reviews early
Corps representatives also discussed information about listed species, habitat, and historic resources.
They asked consultants to provide useful supporting information while coordinating with the Corps on the scope of its review. Depending on the project and applicable requirements, that scope may differ from the entire development site.
Staff explained that independent coordination with other agencies can create additional work when it addresses a different area from the one relevant to the Corps’ action.
An early conversation can help establish what information is needed and how consultation should proceed. Staff also asked applicants to provide access to relevant U.S. Fish and Wildlife Service project information when submitting applications.
The practical lesson is to establish the review approach before different participants begin working from different assumptions.
RRS improvements are still underway
The Regulatory Request System, or RRS, remains the Corps’ submission platform.
Staff acknowledged technical frustrations and described ongoing work to improve coordination with North Carolina’s joint application process. The goal is to reduce duplicate entries and improve information exchange between federal and state systems.
They encouraged specific feedback about problems that affect preparation or review.
A useful comment identifies the step, explains what happens, and describes the extra work it creates. Participants also discussed opportunities for consultants who frequently use the system to help test improvements.
Local approvals can depend on federal paperwork
Participants raised concerns about municipalities withholding building permits or certificates of occupancy while applicants wait for AJDs.
Corps representatives explained that a local requirement does not obligate the Corps to issue a determination on the municipality’s schedule. They offered to discuss documentation needs directly with local governments.
The discussion did not settle whether any particular local requirement is valid. Corps guidance recognizes that applicants may request AJDs to satisfy state or local authorization requirements, while also describing agency discretion and its general practice of honoring requests. Regulatory Guidance Letter 16-01 provides additional background.
When a project is stalled, the first step is to identify the exact document being requested and the concern it is intended to resolve.
Is the question about federal jurisdiction? Wetland boundaries? Compliance with an approved plan? An earlier permit?
Those questions may involve different documents, different professionals, and different paths forward.
More conversation before submission, and more outreach afterward
Staff encouraged pre-application coordination for projects with questions that would benefit from discussion before a full submission.
They also acknowledged that arranging those conversations has sometimes taken too long and discussed improving responsiveness.
Corps representatives expressed interest in more regular outreach through meetings, newsletters, and virtual presentations as new information becomes available.
That continued communication will matter as applicants work through the current backlog, adapt to the application system, and prepare for another possible WOTUS change.
For your next project meeting, consider putting three questions on the agenda: What decision do we need? What information supports it? Who needs to act next?
This article summarizes comments made during the November 5, 2026, public NCAEP meeting with Wilmington District staff. Projections and processing practices discussed at the meeting may change. The discussion did not establish new regulatory requirements or decide individual projects.
What question would you like the Corps to address at a future outreach meeting? Share it in the comments.
