Florida's site-civil permitting stack has a center of gravity that Texas and Colorado don't: the Environmental Resource Permit (ERP). Where other states hand you a separate stormwater permit, a separate wetlands permit, and a separate water-quality certification, Florida bundles all three into one review. That makes the ERP the permit to understand first — but it is rarely the only one a project needs. This guide covers the full stack: the ERP, FDEP's construction stormwater program, FDOT access, coastal review, and local floodplain permitting.
What permits does a Florida land-development project need?
Most Florida site-civil projects need some combination of: an Environmental Resource Permit (ERP) from FDEP or the applicable Water Management District, an FDEP Construction Generic Permit (CGP) for NPDES stormwater coverage, an FDOT driveway/connection permit if the project fronts the state highway system, a Coastal Construction Control Line (CCCL) permit if the site is seaward of the CCCL, and a local floodplain development permit if any part of the site is in a FEMA Special Flood Hazard Area. Add local site-plan and building-permit review, and a Section 404 permit with FDEP Section 401 certification for larger wetland impacts not covered by the ERP's own wetlands review. The table below maps the core set.
| Permit | Agency | Triggered by |
|---|---|---|
| Environmental Resource Permit (ERP) | FDEP or the applicable Water Management District | Land development affecting stormwater quantity/quality or wetlands |
| Construction Generic Permit (CGP) | FDEP | ≥1 acre of disturbance (NPDES construction stormwater, requires SWPPP + NOI) |
| Driveway/connection permit | FDOT | Access connecting to the State Highway System |
| CCCL permit | FDEP | Construction seaward of the Coastal Construction Control Line |
| Floodplain development permit | Local floodplain administrator | Development within a FEMA-mapped Special Flood Hazard Area |
| Section 404 permit / Section 401 certification | USACE / FDEP | Discharge of dredged or fill material into waters of the U.S. |
What is the Environmental Resource Permit, and why does it matter more than any single permit elsewhere?
The ERP is Florida's defining site-civil permit because it bundles stormwater quantity, stormwater quality, wetlands, and water quality into a single review for land development — a scope that Texas and Colorado split across three or four separate permits. It's administered jointly by FDEP and Florida's five Water Management Districts, with the delegation split between FDEP and the WMD depending on the project type and location. Because one application covers the ground that a Texas or Colorado project needs a stormwater permit, a wetlands delineation, and a 401 certification to cover separately, the ERP application itself needs to be scoped early and completely — a design change that affects the stormwater model or the wetland footprint after submittal reopens the whole permit, not just one piece of it. See the full Environmental Resource Permit guide for application mechanics and design standards.
This bundling cuts both ways. On a straightforward upland site with no wetlands and a conventional stormwater pond, the single-permit structure genuinely saves coordination time compared to a state that requires separate wetlands and stormwater filings. On a site with any wetland acreage, jurisdictional water, or a stormwater design that needs iteration, the bundling means every one of those issues sits inside the same review clock — a stormwater comment and a wetlands comment can arrive in the same round, but a delay on either one holds up the whole permit rather than just its own piece.
Which Water Management District handles my project?
Florida is divided among five WMDs, and which one reviews your ERP depends on where the site sits: the South Florida WMD (SFWMD) covers the southern peninsula, the Southwest Florida WMD (SWFWMD) covers the Tampa Bay and southwest coast region, the St. Johns River WMD (SJRWMD) covers the northeast and central east coast, the Suwannee River WMD (SRWMD) covers north-central Florida, and the Northwest Florida WMD (NWFWMD) covers the Panhandle. Some ERP applications are processed directly by FDEP instead of the WMD depending on project type and location, so confirm the reviewing agency before you build your submittal — the application forms, GIS data requirements, and review staff are specific to each district.
Do I also need a separate stormwater NPDES permit in Florida?
Yes, for most projects disturbing an acre or more. The ERP addresses long-term stormwater management design, but construction-phase NPDES compliance runs through the FDEP Construction Generic Permit (CGP), which requires its own SWPPP and Notice of Intent before soil disturbance — the same federal Clean Water Act obligation Texas covers under TXR150000. The CGP and the ERP are reviewed by different parts of FDEP's program and serve different purposes: the ERP governs the permanent stormwater system design, while the CGP governs erosion and sediment control during construction. Budget for both in your permitting schedule; see the FDEP Construction General Permit guide for the construction-phase requirements.
Do I need an FDOT access permit?
Yes, if the project's driveway or access point connects to a road on the State Highway System. FDOT reviews connections under its State Highway System Access Management program, codified in Rule Chapter 14-96, F.A.C., covering connection spacing, turn-lane requirements, and drainage impact to state right-of-way. Access limited to local or county roads goes through the municipality instead. See the FDOT driveway/connection permit guide for the submittal package and design standards.
What if my site is near the coast?
Any construction seaward of the Coastal Construction Control Line (CCCL) requires a separate CCCL permit from FDEP, on top of the ERP and any local building permits. The CCCL permit reviews impacts to the beach-dune system and storm protection value of the coastal zone, and it applies regardless of whether the ERP has already addressed stormwater and wetlands for the same site. If your project has any coastal frontage, confirm CCCL applicability at the same time you scope the ERP — the two run on parallel but independent timelines.
What about floodplain development permits in Florida?
Florida floodplain permitting follows the same federal driver as every NFIP-participating state: any development within a FEMA-mapped Special Flood Hazard Area requires a floodplain development permit from the local floodplain administrator, and work in a regulatory floodway typically requires an engineer-sealed no-rise certification. Florida has no separate statewide floodplain-permitting agency layered on top of the local process the way it does for stormwater and wetlands through the ERP — floodplain review stays local, so confirm the specific city or county administrator and submittal requirements for your site.
How does Miami-Dade differ from the rest of the state?
Miami-Dade routes environmental, stormwater, and water/sewer review through its own RER (Regulatory and Economic Resources) department and, within it, DERM (Division of Environmental Resources Management), in addition to the ERP review handled by SFWMD. Building code compliance follows the Florida Building Code with the added High-Velocity Hurricane Zone (HVHZ) provisions that apply in Miami-Dade and Broward — relevant context for the design team even though vertical building code isn't the site-civil wedge. If your project is in Miami-Dade, the local review layer is thicker than a typical Florida county; see the Miami-Dade site-civil permit guide for the RER/DERM-specific process.
What's the typical permitting sequence for a Florida site-civil project?
Most Florida land-development projects move through a similar rough order, though the exact steps depend on the WMD and local jurisdiction involved:
- Delineate wetlands and confirm FEMA floodplain status during due diligence, before finalizing the site layout.
- Determine the correct reviewing agency for the ERP (FDEP or the applicable WMD) and begin pre-application coordination early — this is the long pole in most Florida schedules.
- Submit the ERP application covering stormwater design, wetlands impact, and water quality together.
- Pursue the FDEP CGP (SWPPP + NOI) in parallel, timed to construction start rather than the ERP's design-review timeline.
- File for the FDOT access permit and, if applicable, the CCCL permit, in parallel with the ERP.
- Secure the local floodplain development permit and any local site-plan approvals.
- Coordinate Section 404 with USACE if wetland impacts exceed what the ERP's own review resolves, with FDEP issuing the accompanying Section 401 certification.
The single biggest scheduling mistake on Florida projects is treating the ERP like a rubber stamp because it's \"just one permit.\" Because it carries the combined weight of stormwater, wetlands, and water quality review, an ERP resubmittal cycle costs more time than a comparable single-issue resubmittal would in a state that splits those reviews apart. Get the pre-application meeting with FDEP or the WMD on the calendar as early in design as the site plan allows.
It's also worth separating the ERP conversation from the local land-use conversation. County or city zoning, comprehensive plan consistency, and local site-plan approval run on their own track through the local planning department and are independent of FDEP and the WMD — a project can hold a fully permitted ERP and still be waiting on local site-plan sign-off, or vice versa. Coordinate the two tracks rather than assuming state environmental approval implies local land-use approval, particularly in jurisdictions like Miami-Dade where the local review layer (RER/DERM) is unusually thick relative to the rest of the state.