What is a USACE district, and how do I find mine?

A USACE district is the US Army Corps of Engineers regulatory office with jurisdiction over a given site, and it is not a formality. The district is who reads your pre-construction notification, who has already layered its own regional conditions on top of the 57 federal nationwide permits, and who decides whether a borderline project stays nationwide or gets pushed into an individual permit. Two identical projects sitting either side of a district boundary can get two different answers, which makes identifying the right district one of the first things worth getting right, not an administrative afterthought at the end.

Boundaries follow watersheds, not the map you already have

District and division lines are drawn from watershed geography, not from state borders. Published USACE boundary data digitises district territory from HUC 12 sub-watershed polygons, which is a precise way of saying a river basin decides the line, a legislature never did. The practical result is one that trips up a lot of first-time applicants: a single state routinely spans several districts, and a single district routinely spans parts of several states. Assuming your project sits in “the district for my state” is exactly the kind of shortcut that produces a misrouted, and therefore slower, submission.

The 8 divisions, by district count

PermitBird's dataset compiles 38 districts running a Section 404 regulatory programme, organised under 8 regional divisions. Coverage is uneven by design, not by omission: a division spanning dense river-basin geography, such as the Great Lakes and Ohio River Division, carries more constituent districts than one covering a single large watershed region.

The spread is real, not a data-entry accident. The Great Lakes and Ohio River Division alone runs seven districts, Buffalo, Chicago, Detroit, Huntington, Louisville, Nashville and Pittsburgh among them, reflecting how many separate river basins converge in that part of the country. The Pacific Ocean Division, by contrast, covers its territory with just two, Alaska and Honolulu, because there is simply less watershed complexity, not less area, to divide up. Do not assume district count tracks landmass or population; it tracks drainage geography.

Why you might see a different number elsewhere

Search for how many USACE districts exist and you will find higher figures too, commonly 44 districts under 9 divisions. That count is not wrong, it is answering a different question: it describes the Corps' full organisational structure, civil works and military programmes included, not just the offices that run a Section 404 regulatory programme. PermitBird's 38is the narrower, permitting-relevant figure. Neither number is the “real” one in isolation; they are counting different things, and it is worth knowing which one a source is using before quoting it back to a client or a colleague.

Finding the district that actually has jurisdiction

The Corps runs its own locator for this at regulatory.ops.usace.army.mil/offices, where entering an address or clicking a project location on the map returns the name, contact details and website of the district with jurisdiction there, which is the most direct way to confirm a district before you submit anything to it. PermitBird's own district index is the faster way to browse all 38districts grouped by division and jump straight to a district's regional-conditions page once you know its name, but it is deliberately not a lookup tool: PermitBird holds no state-to-district or coordinate-to-district mapping of its own, for the same reason the district index page gives for skipping one, a state code alone is not precise enough to name the right district, and a wrong guess is worse than no answer at all.

Linear projects can sit in more than one district at once

A road, a pipeline, or a transmission line does not respect a district boundary any better than it respects a state line, and a corridor project long enough to cross one will usually have to deal with more than one district for the same build. Each district reviews the segment inside its own territory against its own regional conditions, on its own timeline, which means a single crossing project can carry two or three parallel PCN clocks rather than one, each capable of triggering its own completeness and review period. A schedule built around a single district's turnaround, applied to a corridor that actually spans several, is one of the more common ways a linear project's permitting timeline runs long. Map the corridor against district boundaries early, not once drawings are final, and budget separate PCN submissions for each segment rather than assuming one filing covers the whole route.

Getting it right matters more with a backlog running

USACE has reported more than 3,500 pending jurisdictional determinations awaiting review, a queue significant enough that Congress has stepped in. Representative Jeff Hurd introduced H.R. 3901, the Jurisdictional Determination Backlog Reduction Act, which passed the House in 2025 as part of the broader PERMIT Act and directs the Secretary of the Army to allocate the resources needed to clear it. Hurd put the stakes in plain terms: “Delays in permit approvals are stalling key infrastructure projects in Colorado and across the nation”, adding that the bill “pushes the Army Corps to clear this backlog so communities can get moving on critical projects without unnecessary delays.” A queue of that size is exactly the environment where a submission routed to the wrong office, or a PCN sent without confirming the district's current regional conditions first, loses time a project may not have.

Confirm your district through the Corps' own locator before you rely on anything else, then check that district's regional conditions on the district index. Once you know which office has jurisdiction, run the project through the determination tool to see which nationwide permits could apply and whether a pre-construction notification is triggered.