The first-in-nation NPDES permit for data centers.

A Clean Water Act NPDES permit authorizes a facility to discharge pollutants into surface waters, subject to specific limits, monitoring, and reporting requirements. Most large industrial facilities get individual permits negotiated site-by-site. A general permit is a pre-written standard permit that qualifying facilities can apply for in a fraction of the time — weeks instead of the 12 to 24 months a typical individual permit takes.

Ohio EPA's draft OHD000001 is the first US general permit scoped specifically to data centers. The intent is to standardize the application process for a category of facility that is now common enough to warrant it. The theory is: data center cooling discharge looks similar enough across projects that a standard permit framework saves everyone time.

In practice, the draft is a political document as much as a technical one. It reflects Ohio's explicit economic development posture toward data centers — the permit draft includes language authorizing 'lowering of water quality' for 'important social and economic development' — and it reflects the state's willingness to trade some environmental rigor for speed.

The draft authorizes qualifying data centers to discharge cooling tower blowdown, non-contact cooling water, HVAC condensate, and stormwater under specified conditions. Facilities applying under the general permit commit to monitoring for a standard set of parameters — pH, total dissolved solids, temperature, biological oxygen demand, nutrients — and to reporting violations within defined windows.

The effluent limits in the draft are state-of-the-art for traditional industrial parameters: temperature differentials from receiving water, chlorine residuals, and biocide residuals all have specific caps. The draft also requires best management practices for cooling water treatment and sets up a framework for evaluating emerging contaminants through a periodic permit review.

The gaps are what matter most. The draft does not specifically address PFAS (per- and polyfluoroalkyl substances), which are common in some cooling fluids and are the subject of active EPA rulemaking. It does not specifically address microplastics from cooling tower drift. It does not require comprehensive source-water characterization for water taken from Lake Erie versus inland rivers. And it leaves 'lowering of water quality' as an authorized exception for economic development purposes — a notable deviation from the zero-degradation posture of most recent state NPDES frameworks.

The immediate value is for operators with sites in Ohio. If the final rule issues in something like the draft form, Ohio DC projects gain a significantly faster path to discharge authorization. The application timeline could compress from 12–24 months (individual) to weeks (general), which changes the critical path for every project in the state.

The longer-horizon value is template risk and opportunity. Ohio is demonstrably an early mover on data center regulation — the AEP 85% take-or-pay tariff, the HB 1210 community benefit contribution requirement, and now the first general NPDES permit — and other states watch Ohio the way early adopters always get watched. If the Ohio framework holds, expect similar drafts in Indiana, Michigan, Virginia, North Carolina, Georgia, and Texas within 12–24 months.

For operators already committed to the zero-PFAS cooling chemistry path, the lack of PFAS provisions in the Ohio draft creates a strategic choice. Do you disclose your PFAS-free chemistry as a competitive advantage (inviting regulator interest and possibly a stricter follow-on permit), or do you stay quiet and let the general permit framework cover you as-is? Most operators we talk to are choosing some version of proactive disclosure, usually packaged as a community benefit commitment.

State environmental agencies typically do not write NPDES general permits from scratch — they borrow heavily from precedent. Every state agency staff member watching the Ohio framework is asking the same set of questions. What did Ohio authorize? What did Ohio leave out? What comments did the agency receive? How did the agency respond to the PFAS silence?

Our read of the Ohio process: the agency will issue a final permit that incorporates most of the draft structure with modest tightening on best management practices and monitoring frequency. The PFAS silence will probably persist in the first issue and be addressed through a follow-on amendment once EPA rulemaking lands nationally. The 'lowering of water quality' authorization will probably survive with narrower triggering language.

If that forecast holds, operators in other states should expect their own state agencies to start drafting similar general permits within six months of the Ohio final rule. Being ready with a standard application package — monitoring plans, cooling chemistry certifications, source-water assessments — saves weeks of application time and significantly improves approval odds.

Site Intelligence now includes an environmental overlay that tracks NPDES general permit activity state-by-state. Every candidate site in the index is scored against its state's current NPDES framework, with specific flags for states that have drafted or are drafting general permits.

Predevelopment Services offers a fixed-fee NPDES application preparation package — $22,000 for a general permit application under an adopted framework, $55,000 for an individual permit negotiation in states without a general framework. Both include the source-water characterization, cooling chemistry certification, and monitoring plan.

We publish the Ohio draft schema as part of our public research. State agency staff, operators, and counsel can reference it directly. The goal is to make the NPDES workflow auditable from the first filing — no mystery, no surprise, no retainer cycle to read the rulemaking.

Finally, we maintain a watchlist of every state publicly considering a data center general permit, with predicted adoption timelines and specific policy levers we think will shape each state's framework. Customers access the full watchlist; the public version lives on the research page with updates as drafts emerge.