Georgia is now the second-largest data center market in the country, and most of that growth is landing in exactly the kind of outlying counties where the local water system was never built to carry it. A single AI data center campus can request anywhere from a few hundred thousand gallons a day to several million — and water utilities across metro Atlanta are pushing back, some for the first time in their history, as drought conditions tighten an already stretched supply. That fight over water is reshaping fire protection planning too. When a large water user moves into a rural or semi-rural service area, the flow and pressure margin everyone else was counting on for their sprinkler system can disappear along with it — which means more commercial and industrial projects, not fewer, are going to need a dedicated fire protection tank going forward.

Here's the plain-English version: who decides you need one, how much water it actually has to hold, what kind of tank qualifies, and what to do next — without wading through the NFPA 22 standard yourself.

🖥️ Why This Is Suddenly Urgent: AI Data Centers and Georgia's Water Supply

Metro Atlanta is now the second-largest data center market in the United States by total capacity, behind only Northern Virginia, and for net new data center demand in 2024 it actually passed Virginia outright. What's different about this wave is the water: a large AI data center campus can request anywhere from roughly 5,000 gallons a day on the low end (closed-loop cooling) up to several million — some proposals have run as high as 9 million gallons a day, more than most of the small water systems in these counties have ever been asked to deliver to a single customer. Utilities across the region are pushing back, and several have started asking developers to cut projected usage or move off evaporative cooling entirely, a direct response to drought conditions that are already straining supply.

📍 Where the Data Centers Are, Right Now

This isn't a hypothetical problem for some future site — it's happening in counties around Atlanta right now:

• Bartow County — Project Bunkhouse, a 12-building, 1,830-megawatt campus from Digital Realty/Taurus DC near Stilesboro, in planning with rezoning approved.
• Coweta County — Project Sail, a 900-megawatt campus from Prologis/Atlas Development, working through rezoning and environmental review.
• Rockdale County (Conyers) — DC BLOX Atlanta East, 216 megawatts, already under construction.
• South Fulton County — T5 Atlanta IV, 200 megawatts, targeted for delivery by 2027.
• Douglas County — a Microsoft campus in Douglasville and DC BLOX Atlanta West in Lithia Springs, both under development.
• Fulton County (Palmetto) — another Microsoft campus, currently under construction.
• Fayette County (Fayetteville) — a roughly 600-acre QTS campus, and the site at the center of Georgia's biggest data-center water controversy so far.

💧 How Much Water, In Real Numbers

The Fayette County QTS site gives us the clearest real-world figures available. Records show a single water line at that site pulled 20.6 million gallons since February 2024, and county investigators found 109 million gallons had moved through all 13 water lines serving the site — roughly the equivalent of 5,500 backyard swimming pools. The investigation only started after a neighboring resident complained about low water pressure. QTS says it didn't use water improperly or without paying, and the county ultimately billed the company $147,000 tied to the unauthorized-line investigation rather than fining it for the volume used.

To be fair to the industry, most of that 109 million gallons is construction-phase water — dust control, concrete work, site prep — not the steady-state draw once the facility is actually running servers. QTS projects that once fully operational, its closed-loop cooling system will bring usage down to roughly the water use of four American households, around 9,000 to 12,000 gallons a month. Whether that projection holds up at full capacity is something residents and county officials say they'll be watching.

⚡ What About the Power — Are Mini Nuclear Reactors the Answer?

Small modular reactors (SMRs) get a lot of attention nationally as the long-term answer to AI's power appetite, and companies like Google have signed deals for next-generation nuclear projects elsewhere in the Southeast. But it's worth being straight about where Georgia actually stands today: Georgia Power's own $16 billion, 10-gigawatt generation expansion — approved by the Public Service Commission in December 2025, with roughly 90% of that new capacity earmarked for data centers — leans on natural gas, battery storage, and solar. Nuclear isn't part of the near-term build-out, and coal plants previously scheduled for retirement are being kept online longer specifically because of data-center demand, which Georgia Power now forecasts will grow by 8,200 megawatts by the winter of 2030-31 — more than three times the output of the newest reactors at Plant Vogtle. So while SMRs may be part of the story eventually, the honest answer today is that Georgia's new data-center power is coming mostly from gas and coal, not mini reactors on-site. Not everyone agrees the demand forecasts driving all of this are even accurate — Georgia Tech energy researcher Marilyn Brown has said there's "a real overestimation of power requirements throughout the Southeast."

💰 Will Your Rates Go Up?

On electricity, the Public Service Commission has required that data-center revenue reduce, not increase, residential bills, and approved a rate freeze for Georgia Power customers through 2028. Georgia Power CEO Kimberly Greene put it directly: "Large energy users are paying more so families and small businesses can pay less." Even so, residential electricity prices in Georgia still rose from 14.93 to 15 cents per kilowatt-hour between May 2024 and May 2025, and customers using over 1,000 kilowatt-hours a month are paying roughly $43 more than they were at the end of 2022 — driven by a mix of factors including Plant Vogtle construction costs and storm recovery, not data centers alone. A push in this year's legislature for stronger ratepayer protections specific to data centers didn't pass.

On water, there isn't yet the same kind of statewide rate-protection framework that exists for electricity. Water is billed locally, county by county, and the Fayette County case is the clearest example of how much can move through a system before anyone outside the utility notices.

🏢 Who's Building These, and Who's Fighting Over Them

The companies behind metro Atlanta's data centers include Microsoft, QTS, Digital Realty, Prologis, and DC BLOX, alongside AI-specific players like OpenAI, which announced a $20 billion campus on the Georgia coast in Effingham County — outside the immediate metro, but part of the same statewide build-out. The pace of that build-out has become a genuine issue in the 2026 governor's race. Former Atlanta mayor Keisha Lance Bottoms, the Democratic nominee, has called for a pause on new data-center construction. Republican candidate Rick Jackson has backed continued expansion, citing the tax revenue these projects bring to host counties. The Georgia Chamber of Commerce launched a "Georgia Digital Infrastructure Alliance" to push back on negative public sentiment, while groups including Science for Georgia, the Chattahoochee Riverkeeper, the Southern Environmental Law Center, and Georgia Watch have raised concerns ranging from water loss to the risk of residential ratepayers absorbing costs if projects underdeliver. Control of the Public Service Commission itself — the body that approves these power deals — is also on the ballot in 2026.

Here's why all of this matters for a fire protection tank: your sprinkler system's hydraulic calculation was sized against a flow and pressure assumption. If a data center — or any other high-volume user — moves onto the same water system, that assumption can change out from under you before your building even breaks ground. A dedicated on-site tank takes your project out of that competition entirely.

⚖️ Georgia's Water Rate Fight: AI Data Centers, Legislation, and Who's Taking Sides

Here's the direct answer: electricity rates in Georgia are already going up because of data center growth, and local water rates are starting to feel the same pressure. Georgia Power customers have absorbed six rate increases totaling roughly 40% over the past three years, including a 25% jump tied to the Plant Vogtle nuclear expansion in May 2024. Starting June 1, 2026, residential customers began covering a share of the costs for expanding Plant Bowen and Plant Wansley — gas plants built largely to keep up with data center demand. A $26 billion federal loan to Georgia Power's parent company, Southern Company, is funding further grid expansion, but there's no binding commitment that the data center industry will cover that debt instead of ratepayers (AJC, Georgia PSC data center fact sheet).

Water rates are a step behind but heading the same direction. Douglas County — already home to Google and Microsoft data center campuses — is planning a $390 million water treatment upgrade to keep up with demand, a cost that eventually shows up on local water bills. In Coweta County, the proposed "Project Sail" data center could use up to 9 million gallons of water a day, with roughly two-thirds of that lost to evaporation and never returned to the river (WABE).

Where does the water even come from? Most of metro Atlanta's drinking water is pulled from the Chattahoochee River and its main reservoir, Lake Lanier — part of the Apalachicola-Chattahoochee-Flint (ACF) river basin that Georgia has fought Alabama and Florida over for decades in the "tri-state water wars." Lake Lanier already runs low during drought years, which is exactly when data centers' cooling systems tend to pull the hardest (Chattahoochee Riverkeeper, Atlanta Regional Commission).

🏗️ How Big Are These Sites, and Who's Buying the Land?

These aren't small buildings tucked into office parks — they're hundred-plus-acre campuses, and most are landing in the exurban and rural counties ringing Atlanta rather than the urban core, where land is cheaper and transmission capacity is easier to secure. Google purchased 950 acres in Monroe County for a potential campus. Microsoft paid $13.8 million for 93 acres in Douglas County. Amazon closed a $270 million land deal that raised local concerns, and OpenAI has announced plans for a $20 billion data center campus near the Georgia coast. QTS, Digital Realty, Prologis, and DC BLOX have also been active buyers across Fayette, Coweta, and Newton counties (Data Center Dynamics, AJC).

📜 What's Moving Through the Georgia Legislature

Georgia lawmakers introduced a wave of bipartisan bills in the 2026 session aimed at data centers, and nearly all of them died before reaching the Governor's desk:

• SB 34 (Sen. Chuck Hufstetler, R-Rome) — would have barred data center infrastructure costs from being folded into everyone else's utility rates. Polling showed roughly 80% of Georgians supported it; Georgia Power opposed it, and the Senate adjourned before it came up for a final vote.
• HB 528 (Rep. Debbie Buckner, D-Junction City) — would require any facility drawing 30+ megawatts to publicly report its annual energy and water use.
• SB 410 (Sen. Matt Brass, R-Newnan) — would have frozen new data center tax credits while leaving existing ones in place.
• SB 408 (Sen. Nan Orrock, D-Atlanta) — would have sunset the data center tax exemption in 2027, five years early.
• HB 1012 (Rep. Ruwa Romman, D-Duluth, with Rep. Jordan Ridley, R-Woodstock) — proposed a statewide moratorium on new data center construction through February 2027.

None of the ratepayer-protection or transparency bills reached the Governor's desk, and lawmakers left the existing data center tax breaks intact while punting the harder question of who pays for new power and water infrastructure (Georgia Recorder, Georgia Watch).

🥊 Who's For It, and Who's Against It

On the opposition side: Mark Woodall, a lobbyist for the Sierra Club of Georgia, has called industry PR efforts "trying to put lipstick on a pig," and notes the opposition crosses party lines — independents, Democrats, and Republicans alike. Chris Manganiello, water policy director at Chattahoochee Riverkeeper, argues state policy "is not really designed to respond to this new, unprecedented demand." Amy Sharma, executive director of Science for Georgia, is pushing for transparency requirements, surety bonds, and long-term ratepayer protections. Democratic gubernatorial candidate Keisha Lance Bottoms has called for a pause on new data center approvals.

On the industry side: the Data Center Coalition — whose members include Amazon, Google, and Microsoft — backs a Georgia-focused advocacy arm called Connected Georgia, led by the Coalition's Josh Levi, which launched a multimillion-dollar ad campaign defending the industry's water and energy practices. The Georgia Chamber of Commerce, under CEO Chris Clark, launched its own "Georgia Digital Infrastructure Alliance" to brief lawmakers statewide starting in September 2026. Republican gubernatorial candidate Rick Jackson has argued data center tax revenue could eliminate property taxes in more than 70 Georgia counties (Georgia Recorder, Rough Draft Atlanta).

What this means if you're building or expanding in Georgia right now: the rules around water availability and on-site fire protection water storage aren't waiting on the legislature to sort this out. Utilities are already tightening requirements in the counties feeling the most data center pressure — see our guide on fire protection water storage for development in areas with limited infrastructure for what that looks like on the ground.

🔥 Fire Protection Water Tank Requirements in Georgia, Explained

Georgia adopts a statewide set of fire and building codes, but enforcement runs through your local fire marshal or building department — and requirements can vary in the details from county to county. The trigger is almost always the same: your site sits outside reliable municipal hydrant coverage, so the sprinkler or standpipe system needs its own dedicated water supply. Miss this step and it isn't just your sprinkler contractor who feels it. A fire protection tank that isn't sized, sited, and documented correctly can hold up your certificate of occupancy, which means a finished building that still can't legally open its doors.

This applies almost exclusively to commercial, industrial, and institutional projects. Warehouses, event venues, agricultural facilities, and manufacturing buildings on well systems or on the edge of a rural water district are the sites that consistently trigger this requirement in Georgia — a single-family home rarely does.

🙋 Who Decides If You Need One?

In practice, two kinds of projects account for most of the fire tanks we sell. The first is rural and semi-rural sites — a property on a private well or served by a small rural water association, where the static pressure and available flow simply can't meet what the sprinkler system's hydraulic calculation requires, no matter how the piping is sized or how much booster pump you throw at it. The water isn't there, so stored volume has to make up the difference.

The second, and increasingly the more common trigger in Georgia right now, is a shared water system that's already under strain from a large industrial or institutional neighbor — AI data centers are the clearest current example, alongside distilleries, breweries, food and beverage processing, textile plants, and other water-intensive manufacturing. When one of these operations is drawing hundreds of thousands of gallons a day off the same main or the same rural water association, the flow and pressure margin the rest of the district was counting on can shrink fast, and a fire marshal will require your project to cover its own supply rather than assume the district can.

Either way, your county or city fire marshal makes the final call, usually during plan review for new construction or a significant addition. If your project includes a sprinkler system and your site isn't within the flow and distance limits of a public hydrant — or your process water use is already competing for the same supply — expect a fire protection tank to be part of the conversation early. This surfaces early, and it surfaces in writing. Your civil engineer or architect submits a site plan; the fire marshal's office reviews it alongside your sprinkler contractor's hydraulic calculation, and the water-supply requirement gets flagged before a building permit is issued — not after steel is on order.

📏 How Much Water Do You Actually Need?

Volume isn't a guess — it comes from your sprinkler or fire pump engineer's hydraulic calculation: required flow multiplied by required duration, plus hose stream allowance if your AHJ requires it. We break the full math down in sizing a fire protection tank, or download our Tank Sizing & Buying Guide for the reference sheet version.

That number moves with the building, not just the sprinkler head count. Occupancy and hazard classification — light, ordinary, or high — set the design density and area of application under NFPA 13; a standpipe system adds its own flow and duration on top of that; and hose stream allowance gets layered in per NFPA 22. A single-story light-hazard warehouse and a high-piled storage building on the same lot can carry very different required volumes even at a similar square footage.

A typical mid-size commercial sprinkler system might call for 500 gpm over 60 minutes — 30,000 gallons of required effective volume before dead storage and freeboard are added back in. Larger storage or high-hazard occupancies push that number into six figures.

This is where we spend most of our time on a quote. Anyone can multiply gpm by minutes — the real work is reconciling your engineer's hydraulic calculation against your actual site conditions: what the well or water district can already deliver, how much of that gap the tank needs to close, and how much margin to build in so you're not back here in five years when the building expands. Send us the calc and we'll size it, sanity-check it, and tell you straight if a smaller or larger tank actually makes more sense.

🧱 What Kind of Tank Qualifies?

NFPA 22 governs the tank itself: dedicated fire use, anti-vortex protection, level indication, correctly sized overflow and vent, an access manway, and a way to keep it full. Bolted steel — we stock SBS Tanks and Pioneer Water Tanks — FRP panel, poly, and underground fiberglass can all meet that standard — which one fits depends on your volume and site. See our full comparison of NFPA 22 fire protection tank types.

Bolted steel scales cleanly past 10,000 gallons and is the default once volume climbs into commercial territory. FRP panel tanks earn their keep on tight or corrosive sites — a mechanical room, a parking deck, a retrofit with no room for a one-piece tank. Poly and underground fiberglass cover the smaller end, though most commercial hazard classifications outgrow them quickly.

🗺️ Your Next Step

Two moves put you ahead of the timeline: get your hydraulic calculation started with your fire protection engineer, and call your local fire marshal's office to confirm their plan review requirements before you finalize a site plan. It's a much cheaper problem to solve before the slab goes down. Once the tank's on order, see our site-prep checklist and installation timeline so delivery day doesn't catch you flat-footed.

🔧 Fire Protection Tank Accessories & Fittings

The accessories on a fire protection tank aren't optional extras — NFPA 22 requires most of them, and the rest are there because stored water sitting for months, sometimes years, between uses behaves differently than water moving through a normal system.

• Liquid level indicator: a visual or remote gauge so facilities staff — and the fire department, during pre-plan — can confirm the tank is at capacity without opening the manway.
• Altitude valve: controls the fill line, closing automatically once the tank reaches capacity so it doesn't overflow through the vent or overflow line, and opening fully on demand so it never restricts flow to the fire pump.
• Anti-vortex plate: mounted over the outlet so the pump can draw the tank down near-empty in an emergency without sucking air and losing prime.
• Vent and overflow: sized separately and located so overflow discharge doesn't undermine the foundation or create an ice hazard in winter.
• Access manway: for inspection, cleaning, and liner maintenance over the tank's service life.
• Corrosion- and bacteria-resistant connections: fittings that penetrate the shell or liner use isolation hardware to prevent galvanic corrosion between dissimilar metals, and the interior liner itself is a non-nutrient surface that resists bacterial growth and biofilm buildup in water that can sit still for long stretches between fire events.

🗓️ What to Expect After You Order: A Sample Schedule

Every site is different, but here's roughly how a commercial fire protection tank project breaks down once you decide to move forward:

1. Site Configuration (Week 1): We collect your static water pressure, inlet and outlet sizing and location, available electrical power for the transfer and building pumps, tank placement, and access constraints like crane clearance and setbacks — the form that lets engineering finalize a build spec instead of guessing.
2. Engineering & Plan Review (Weeks 1–4, running alongside site configuration): Your hydraulic calculation gets matched against tank volume, and the fire marshal's office reviews the site plan.
3. Fabrication (Weeks 3–10, depending on tank type and size): The tank is built to your official estimate spec once the deposit and completed site configuration are both in hand.
4. Interior Liner Installation & Cure (where applicable): tanks specified with an interior liner have the liner installed and seam-tested during fabrication, then given a manufacturer-specified cure time before the tank can be hydrostatically tested — this is one of the more common places a tight schedule gets squeezed, so we build the cure window in up front rather than discover it late.
5. Site Prep (Weeks 4–10, running parallel with fabrication): Pad or foundation work, utility rough-in, and any crane access prep happen on your schedule while the tank is being built.
6. Delivery & Installation (1–3 days on-site for a bolted steel tank; longer for underground fiberglass): Crew sets the tank, ties in the inlet, outlet, and overflow, and runs initial leak testing.
7. Hydrostatic Test & Fire Marshal Final Inspection: The tank is filled and pressure-tested, and the AHJ signs off before the system goes into service.
8. Certificate of Occupancy: The fire protection requirement is cleared, and the rest of the building's C of O checklist can move forward.

🧾 What Goes Into a Site Configuration

Before engineering can finalize a build spec, we need a completed site configuration — the same short form our estimating team sends on every commercial job. Every field on it changes something about how the tank gets built:

• Application: fire protection, plus any secondary use — domestic water booster, rainwater harvesting, and so on — if the tank is doing double duty
• City water supply: static pressure, and the size and location of the inlet and outlet
• Electrical power available: for the transfer pump and, if applicable, the building pump
• Tank placement: where it's going, plus space and access constraints — crane access, clearance, setbacks
• Standby / isolation valve location

A typical fire protection example looks something like this: 65 psi static pressure, a 3-inch inlet, a 6-inch outlet with anti-vortex protection at the wall, and confirmed crane access along one side of the pad. Small details, but they're the difference between a build spec that's right the first time and a change order after the tank's already on a truck.

We've broken the rest of the process into its own set of guides: how the required volume gets calculated, which tank material fits your site, what a Georgia fire marshal's office checks during plan review, and what site prep looks like before delivery. Jump to whichever piece you're working through right now.

Send us your project details and we'll help you figure out what's required, size the tank, and send a CAD drawing and quote at no charge.

At 1020 Spring Street (Ten Twenty Spring) in Midtown Atlanta, the rainwater harvesting system was designed with one clear mission: provide cooling tower makeup water—exclusively.

That focus matters, because cooling towers represent one of the most consistent, high-volume non-potable water demands in a commercial high-rise. And once a building reaches roughly 7 stories or taller, cooling tower makeup demand is often strong enough that the system can use essentially all the rainwater that hits the rooftop (depending on rainfall patterns, operating hours, and tower load).

This is exactly the kind of application where rainwater harvesting shines: steady demand, predictable control strategy, and real measurable offset of potable water use.

A Modern Midtown Tower with Real Water Demand

Ten Twenty Spring is part of the Spring Quarter district and is positioned as a high-performance, hospitality-forward office destination. The tower is 25 stories and roughly 525,000 SF of Class-A office, with ~32,000 SF floor plates and major tenant amenities and terraces.

In other words: it’s a large building, with large mechanical loads—exactly the environment where rooftop rainwater capture can become a meaningful utility strategy instead of a token sustainability feature.

Atlanta Requires Stormwater Management—& Rainwater Harvesting Can Help Meet It

In Atlanta, post-development stormwater management is required for new development and redevelopment. The City’s Post-Development Stormwater Management Ordinance requires projects to manage the first inch (1.0”) of rainfall using green infrastructure. That's the minimum; we recommend about 1 gallon per s.f. of impervious.

This is where rainwater harvesting earns double credit: a properly designed capture-and-reuse system can function as a stormwater management device by reducing runoff volume through capture, filtration, and reuse. The City explicitly includes cisterns as a green infrastructure approach intended to capture stormwater for reuse.

And the City’s ordinance update Q&A materials get even more specific: rainwater harvesting and reuse systems must be designed around the demand they serve and include a plan to draw down stored water so capacity is available for the next storm—exactly why cooling tower makeup is such a strong match. Even during an Atlanta winter, a large 25 story building like this will need air conditioning in places.

The Payoff: Potable Water Savings that Actually Matter

Because cooling towers can consume water day after day, this approach can save hundreds of thousands of gallons of potable water over time—often more—by substituting harvested rainwater for municipal supply.

That’s good for the building owner (utility savings and resilience), and it’s good for the broader community by supporting Atlanta’s water conservation goals and reducing stress on infrastructure.

The System Philosophy: Do the Job Well, Without Extra Complexity

This system was designed in-house and installed by McKenney’s Inc., creating a streamlined design-build workflow from engineering through commissioning. For 1020 Spring, the equipment stack is intentionally clean and operator-friendly:

• Concrete cistern for storage
• Single pump for delivery to the cooling tower makeup system
• Orival ORG sediment filtration doing most of the particulate removal
• Yaskawa iQpump VFD handling all pump controls

No unnecessary layers. No “controls sprawl.” Just a system that’s built to run.

Concrete Cistern: Durable, Stable, and Built for Long Service Life

Concrete storage is a great fit for dense urban sites and high-use applications. It’s robust, stable, and well suited to long-term ownership—especially when the system is expected to operate routinely, not occasionally.

Orival ORG Sediment Filters: Doing the Heavy Lifting

Rooftop runoff can carry a surprising amount of fine material—dust, pollen, and city grit. The Orival ORG sediment filters are designed to remove that load so downstream equipment (pump components, makeup controls, tower internals, and treatment systems) don’t become the filter of last resort. When filtration is doing most of the work, everything downstream tends to last longer and run cleaner.

Why We Love the Yaskawa iQpump VFD on Projects Like This

We use a lot of drives across water applications, but the Yaskawa iQpump VFD stands out on rainwater systems because it can execute the controls we want without requiring a separate PLC and touchscreen.

That one decision has big long-term benefits for building operators:

• Fewer devices to fail.
• Fewer communication handoffs between “panel logic” and “drive logic”
• No programming language to learn. No proprietary code.
• Easier troubleshooting for technicians. Excellent support directly from Yaskawa.
• A cleaner, more serviceable control architecture overall.

Cooling tower makeup applications typically need reliable pressure/flow control, robust pump protection, clear alarm handling, and straightforward enable/disable and interlock logic. The iQpump platform is a great fit for that “do it right, but don’t overcomplicate it” control strategy.

Why Cooling Tower Makeup is the Perfect Demand for Stormwater-Focused Harvesting

The City’s guidance emphasizes that harvesting systems should be sized and operated with a plan to draw down storage so there’s capacity available for future storms.

That’s exactly why cooling tower makeup is such a strong end use:

• It creates consistent demand (so the cistern empties between rain events)
• It helps the harvesting system perform as functional green infrastructure
• It turns rooftop runoff into a utility resource instead of a stormwater burden
• It reduces potable consumption where the volume is meaningful

The Takeaway in Rainwater Harvesting for Cooling Tower Makeup

Not every building needs a multi-branch rainwater system feeding irrigation, toilets, and hose bibbs. Sometimes the best solution is the simplest one—pick the strongest end use and build a system that does that one job extremely well.

At 1020 Spring Street, rainwater harvesting is engineered to be a workhorse: capture rooftop runoff, filter it, and deliver it to cooling tower makeup using a durable concrete cistern, proven sediment filtration, and streamlined controls driven by a Yaskawa iQpump VFD.

It supports Atlanta’s stormwater management intent, reduces runoff burden, and can save hundreds of thousands of gallons of potable water over the life of the building—good for the owner, and good for community-wide conservation.

https://www.mckenneys.com/preconstruction-2/