Florida ERP Nutrient Loading Compliance: A Complete Guide to Section 8.3
By SWMLabs
Florida's Environmental Resource Permit program has governed stormwater management for decades. What changed fundamentally in 2024 was the performance standard at the center of that program. For the first time, ERP applicants are required to demonstrate stormwater compliance with specific Total Nitrogen (TN) and Total Phosphorus (TP) Nutrient Loading reduction thresholds — not just Total Suspended Solids (TSS) removal. That shift is codified in Section 8.3 of Volume I of the ERP Applicant's Handbook, and it applies to virtually every land development project in Florida that requires an ERP.
This post walks through the complete framework: what Section 8.3 requires, how the six subsections relate to each other, and what engineers need to confirm before beginning any Nutrient Loading calculation under the new rules.
Florida ERP Rule Change: The June 2024 Effective Date and What It Means
SB 7040 was signed into law on June 28, 2024. That date carries two distinct sets of compliance obligations. The new operation and maintenance requirements — including financial capability certification and O&M plan documentation — took effect immediately. A separate provision, the qualified inspector requirement, became effective one year later on June 28, 2025.
The new Stormwater Quality Nutrient Permitting Requirements in Sections 8.3 through 8.3.6 apply to all permit applications deemed complete after December 28, 2025 — eighteen months from the rule effective date. As of the date of this post, that threshold has passed and all new applications are subject to the full Nutrient Loading standard without exception.
Effective Date Has Passed
All ERP applications deemed complete after December 28, 2025 are subject to the full Section 8.3 Nutrient Loading standard. There are no transitional exceptions for new submittals.
The New Nutrient Loading Standard: Net Improvement Required for All ERP Projects
Before 2024, nutrient-based net improvement was required only for projects discharging to impaired water bodies. Under the revised rules, every ERP project — regardless of the downstream impairment status of the receiving water body — must now demonstrate net improvement for TN, TP, and TSS. The standard applies using the more protective of two approaches: a percentage-reduction method or a pre-versus-post-development comparison. Whichever result is more stringent controls.
The shift from a targeted impaired-waters standard to a universal one is the structural change underlying Section 8.3 and everything that follows from it.
The Six-Section Framework
Section 8.3 is organized as a tiered classification system. A project's location — specifically whether it falls within a HUC12 subwatershed that is upstream of an Outstanding Florida Water (OFW) or an impaired water body — determines which subsection governs the performance standard. The table below summarizes the required treatment efficiencies for each classification.
| Project Classification | TP Reduction | TN Reduction | Pre/Post Comparison | TSS Reduction | Handbook Section |
|---|---|---|---|---|---|
| Standard New Development (not upstream of OFW or impaired water) | 80% | 55% | Post-development ≤ pre-development loading | 80% | 8.3.2 |
| Upstream of OFW (within same HUC12) | 90% | 80% | Post-development ≤ pre-development loading | 95% | 8.3.3 |
| Upstream of Impaired Water (within same HUC12, no OFW) | 80% | 80% | Post-development ≤ pre-development loading AND post-development < pre-development for impaired pollutants | 80% | 8.3.4(a) |
| Upstream of Both Impaired Water and OFW (within same HUC12) | 95% | 95% | Post-development ≤ pre-development loading AND post-development < pre-development for impaired pollutants | 95% | 8.3.4(a) |
| Redevelopment Alternative (qualifying projects only — see 8.3.5 definition) | 80% (std) / 90% (OFW) | 45% (std) / 60% (OFW) | For impaired water projects: post-development < pre-development for impaired pollutants | 80% (std) / 95% (OFW) | 8.3.5 |
Section 8.3.1: Applicability and TSS Baseline
Section 8.3.1 establishes that every applicant must demonstrate — through modeling or calculations as described in Section 9 of the Handbook — that their proposed stormwater management system is designed to discharge to the required treatment level under the performance standards in Sections 8.3.2 through 8.3.5. It also establishes the TSS reduction baseline that runs parallel to the TP/TN requirements: an 80% reduction in average annual post-development TSS load for standard projects, elevated to 95% for projects within a HUC12 containing and upstream of an OFW. TSS compliance is a separate, concurrent requirement — not a substitute for the Nutrient Loading analysis.
Section 8.3.2: Standard New Development
This is the baseline standard for projects that are not upstream of an OFW or impaired water body. It requires the more protective of two compliance pathways: either an 80% reduction in average annual TP loading and a 55% reduction in average annual TN loading from the proposed project; or a reduction such that post-development average annual Nutrient Loading does not exceed pre-development loading. Both pathways must be calculated and the more stringent result governs.
The pre-development loading used in the comparison pathway reflects the actual existing condition of the project area, which may be developed land. The Handbook's land use categories in Table 9.1 include developed uses such as single family, multi-family, commercial, industrial, and highway as valid pre-development inputs. There is no requirement that the pre-development baseline represent undeveloped natural conditions for non-redevelopment projects.
Dual-Path Calculation Is Required
FDEP's ERP Stormwater FAQ clarifies that TP and TN must each be evaluated independently, and that the treatment system must meet the required level of treatment for both parameters. Engineers who calculate only the percentage-reduction pathway, or only the pre/post comparison, are not meeting the requirement. Both are required, and both results must be documented.
Section 8.3.3: Outstanding Florida Waters
Projects within a HUC12 subwatershed that contains an OFW and that are located upstream of that OFW face enhanced treatment thresholds: a 90% reduction in average annual TP loading and an 80% reduction in average annual TN loading from the proposed project; or post-development loading that does not exceed pre-development loading — whichever is more stringent. The upstream determination is based on the HUC12 drainage network, not physical proximity. A project can be subject to the OFW standard without having an OFW on or adjacent to the site.
Confirm OFW Status Early
OFW status should be confirmed through HUC12 drainage network analysis early in the design process — before the stormwater system has been sized, not as a late-stage submittal check.
Section 8.3.4: Impaired Waters
This is the most technically complex section of the framework. Projects within a HUC12 subwatershed containing an impaired water body and located upstream of that impaired water must satisfy three simultaneous conditions under Section 8.3.4(a): (1) an 80% reduction in average annual TP and TN loading from the proposed project, elevated to 95% for projects also upstream of an OFW within the same HUC12; (2) post-development loading that does not exceed pre-development loading; and (3) post-development average annual loading of impaired pollutants that is strictly less than pre-development loading. All three must be met concurrently. Meeting two of three is not sufficient.
An alternative pathway under Section 8.3.4(b) applies where a formally adopted Total Maximum Daily Load (TMDL), Basin Management Action Plan (BMAP), or approved alternative restoration plan contains basin-specific design and performance criteria for stormwater load reductions. The 8.3.4(b) pathway requires conditions that most impaired watersheds have not yet met, so the 8.3.4(a) three-part test governs the vast majority of current Florida ERP submittals.
Downstream Drainage Network Matters
Determining whether a project is subject to Section 8.3.4 requires correctly identifying the downstream WBID (Water Body Identification number) through the drainage network — not just the receiving water at the point of discharge. A project discharging to a non-impaired conveyance that eventually reaches an impaired water body can still trigger 8.3.4, depending on the upstream determination.
Section 8.3.5: Alternative Performance Standards for Redevelopment
Section 8.3.5 provides an alternative compliance pathway for qualifying redevelopment activities. The Handbook's Chapter 2 definition of "Redevelopment" establishes four simultaneous qualifying conditions: (1) the site must have an existing commercial, industrial, institutional, roadway, or residential land use — silviculture and agriculture are excluded; (2) the existing land use must not have been previously permitted under Part IV of Chapter 373, F.S. — meaning a site that already holds an ERP for its current development does not qualify; (3) all or part of the existing impervious surface must be physically removed and replaced with new impervious surface; and (4) the new impervious surface must have the same or lesser area as the existing impervious surface, with the same or less intense land use as measured by the applicable EMC values.
For projects that meet all four conditions, Section 8.3.5 provides alternative treatment thresholds in lieu of Sections 8.3.2 through 8.3.4: an 80% TP reduction and 45% TN reduction for standard projects; 90% TP and 60% TN for projects within a HUC12 containing and upstream of an OFW; and for impaired water projects, post-development loading of impaired pollutants less than pre-development loading.
A note on the pre-development baseline that applies beyond redevelopment: the pre/post comparison under Section 8.3.2 uses the actual existing condition of the project area as the pre-development baseline (which may be developed land) for any project, regardless of whether it qualifies as redevelopment. Section 8.3.5 provides a specifically defined alternative threshold for qualifying projects; it does not create the only route by which an engineer uses a developed existing condition in the analysis.
Section 8.3.6: Exemption from Minimum Performance Standards for Redevelopment
Section 8.3.6 provides a narrow exemption pathway for redevelopment sites under one acre. To qualify, the site must not be located within a HUC12 subwatershed containing a nutrient-impaired water body or OFW, and must not be upstream of that water body. The project must also result in reduced impervious surface or reduced pollutant loading.
This Is Not a Self-Executing Exemption
The applicant must submit a written request to the applicable Agency with supporting documentation demonstrating that the performance standards cannot be met. The Agency reviews each request on a case-by-case basis pursuant to Section 373.406(6), F.S. The activity shall not commence without a written determination from the Agency confirming qualification for the exemption.
How to Determine Your Project's Section 8.3 Classification
The starting point for every Section 8.3 analysis is a single geographic question: is the project located within a HUC12 subwatershed that contains, or is upstream of, an OFW or impaired water body?
FDEP has published the HUC12 Boundaries with Impaired Waters and OFWs interactive mapping tool that allows engineers to make this determination before beginning the Nutrient Loading calculation. The map is the correct first step. What the map does not resolve is the downstream determination question for ambiguous drainage network cases, which requires independent analysis of the drainage topology connecting the project to the downstream water body.
Once the applicable section is identified (8.3.2, 8.3.3, or 8.3.4) the calculation sequence proceeds through Section 9 of the Handbook, which covers the Nutrient Loading methodology, rainfall data, Best Management Practices (BMPs) treatment efficiencies, and determination of required treatment efficiency.
Practical Implications: What to Confirm Before You Begin
Getting the regulatory classification right before beginning calculations is not a formality — it is the foundation of the entire analysis. A project analyzed under Section 8.3.2 that should have been analyzed under Section 8.3.4 will produce a stormwater system sized for the wrong standard, a calculation record that does not survive agency review, and a Request for Additional Information (RAI) that could have been avoided.
Pre-Calculation Checklist
Before starting any Section 8.3 calculation: (1) Identify the receiving water body and trace the drainage network downstream using FDEP's HUC12 Boundaries interactive map to determine the correct regulatory classification: OFW, impaired, or standard. (2) Confirm whether the project is new development or redevelopment — verify all four qualifying conditions under Chapter 2 before applying Section 8.3.5 alternative standards. (3) If Section 8.3.6 exemption is being considered for a sub-one-acre redevelopment site, confirm HUC12 classification and submit the required written request to the Agency before commencing any activity. (4) Verify grandfathering status under Section 3.1.2 if the project has any prior permit history or stormwater design submissions predating June 28, 2024.
On the dual-path calculation: both the percentage-reduction pathway and the pre/post-development comparison must be fully calculated and documented for every project. The more stringent result is the binding standard. Document both pathways, apply the controlling outcome, and make the basis for that determination explicit in the Technical Appendix.
Florida's stormwater rules have always been about the relationship between land use decisions and water quality outcomes. Section 8.3 makes that relationship quantitative, explicit, and binding on every ERP project in the state.
The calculations are precise because the stakes are real — and because the water bodies downstream of every permitted project are documented and named. Getting this right isn't just a compliance exercise. It's how engineering becomes stewardship.