USACE Divisions

USACE operates through nine regional divisions; eight run the domestic regulatory program that oversees compensatory mitigation banking, and those eight are tracked here. Division boundaries follow watersheds, not state lines — a bank's regulator is set by which basin it sits in, not by its state.

Figures mirrored from USACE RIBITS · ORM · RRS · synced

The read

Nationally, a bank clears the regulator in about 10 months — the median from complete draft instrument to decision, pooled across every division.

Across 145 banks with a measurable regulator clock, the median is 299 days — half clear between 197 and 483 days. This clock is the regulator's own: draft instrument to decision, excluding the time an applicant spends revising. Where a division runs faster or slower than this figure is the whole of the comparison table below.

Regulator clock
299days, median
Draft instrument to decision
n = 145 banks · IQR 197–483
Full clock
642days, median
First public notice to decision
n = 177 banks
National

Median review time by decision year

2 years
Median review time by decision year, 2 rows
Decision yearRegulator clockBanks (n)
2025Regulator clock303 daysBanks (n)71
2026Regulator clock291 daysBanks (n)74
Coverage

USACE divisions map — approval speed by division

USACE divisions approval timeline comparison

8 divisions
USACE divisions approval timeline comparison, 8 rows
CodeDivisionRegulator clockFull clockBanks
CodeSWDSouthwestern DivisionRegulator clock237 daysFull clock554 daysBanks19Southwestern Division overview
CodeMVDMississippi Valley DivisionRegulator clock271 daysFull clock556 daysBanks38Mississippi Valley Division overview
CodeLRDGreat Lakes & Ohio River DivisionRegulator clock280 daysFull clock613 daysBanks45Great Lakes & Ohio River Division overview
CodeSADSouth Atlantic DivisionRegulator clock289 daysFull clock989 daysBanks42South Atlantic Division overview
CodeNADNorth Atlantic DivisionRegulator clock310 daysFull clock609 daysBanks21North Atlantic Division overview
CodeNWDNorthwestern DivisionRegulator clock335 daysFull clock512 daysBanks15Northwestern Division overview
CodePODPacific Ocean DivisionRegulator clocknot enough dataFull clocknot enough dataBanks0Pacific Ocean Division overview
CodeSPDSouth Pacific DivisionRegulator clocknot enough dataFull clocknot enough dataBanks3South Pacific Division overview
Supply

Credits available nationally, by class

Wetland
403,550credits
+2.2%year on year
Stream
7,086,583credits
+7.4%year on year
Species
105,788credits
−0.5%year on year
NRDA
941credits
Demand

Recent federal permit applications, by division

8 divisions
Applications recorded
327since 2026-07-02
Standard permits & EIS on public notice
Open for comment
79of 327
The rest have closed, and remain pending
Recent federal permit applications, by division, 8 rows
CodeDivisionApplicationsOpenShare of national
CodeSADSouth Atlantic DivisionApplications135Open31Share of national41%
CodeNADNorth Atlantic DivisionApplications55Open11Share of national17%
CodeLRDGreat Lakes & Ohio River DivisionApplications36Open10Share of national11%
CodeMVDMississippi Valley DivisionApplications32Open5Share of national10%
CodeNWDNorthwestern DivisionApplications29Open12Share of national9%
CodeSWDSouthwestern DivisionApplications24Open6Share of national7%
CodePODPacific Ocean DivisionApplications9Open1Share of national3%
CodeSPDSouth Pacific DivisionApplications7Open3Share of national2%

USACE divisions and districts — common questions

How many USACE divisions are there?

USACE operates through nine regional divisions. Eight of them run the domestic regulatory program that oversees mitigation banking — the eight tracked on this site. The ninth does not oversee the domestic compensatory-mitigation program, so it does not appear here.

How many USACE districts are there?

USACE has 44 districts, per the Corps' own unit-websites page. Not all 44 carry a domestic regulatory mission; the ones that oversee mitigation banking are the districts you'll find on each division's page here.

What is a USACE division?

A division is a regional command that groups several regulatory districts along watershed lines. The district — not the division — issues a bank's permit and runs its approval clock; the division is the level at which those districts are organized and compared. Each division's page here carries its own district breakdown.

Where do these numbers come from?

Approval timelines are from USACE ORM; credit supply and pending-bank counts from USACE RIBITS; permit demand from the USACE Regulatory Request System. All are public federal records, derived in git. District boundaries on the map are fetched from EPA's published USACE District Boundary layer when the page loads. Counts and medians only — no modeled averages, and district rows live on the division pages, not here.

About the data on this page

Bank details, status and credit balances are mirrored from the USACE RIBITS registry, the federal public record for mitigation banks. Single-client banks are excluded from supply figures. Credit balances count only banks that can sell today — sold-out, suspended, terminated, withdrawn, closed-out and not-yet-approved banks are left out. Credit classes offset different resources and are never added together. Totals across many banks are rounded to whole credits — a single bank’s own balance never is. Approval timelines come from the USACE permit-processing record (ORM). We calculate the median from every bank’s milestone dates in the division. Full clock means from the first public notice of the prospectus to the final decision — it includes the applicant’s own time. Regulator clock means from the complete draft instrument being received to that same final decision — the part the Corps controls. A median is shown only where at least four banks have both milestone dates. In-lieu fee instruments are excluded throughout. Public notices come from the USACE Regulatory Request System (RRS). Notice text is the Corps’ own; the one-line summary beside it is an AI generated summary.

The map on this page is drawn live from the EPA NEPAssist RIBITS MapServer when you load it.

How these figures are builtReport an issue