India’s hidden industrial water crisis
- Central Ground Water Board assessments place urban units around Bengaluru and Hyderabad as over-exploited and Chennai as critical — the same metros where the data-centre and fab pipeline is densest.
- Data centres and fabs are highly water-intensive and are landing where aquifers are already over-drawn and surface water is monsoon-dependent.
- The missing tool is the corridor-level industrial-water audit; until it is published, water risk stays invisible until it binds.
- Central Ground Water Board assessments place urban units around Bengaluru and Hyderabad as over-exploited and Chennai as critical — the same metros where the data-centre and fab pipeline is densest.
- Data centres and fabs are highly water-intensive and are landing where aquifers are already over-drawn and surface water is monsoon-dependent.
- The missing tool is the corridor-level industrial-water audit; until it is published, water risk stays invisible until it binds.
India's industrial-water risk is hiding in plain sight. The Central Ground Water Board's assessment places many of the urban units around Bengaluru and Hyderabad in the over-exploited category and Chennai's position as critical — and these are precisely the metros where the data-centre and advanced-manufacturing pipeline is densest. The geography of new high-water-intensity industry overlaps with the geography of water stress.
Data centres, through cooling and humidity control, and fabs, through ultrapure water, are among the most water-intensive facilities being built, and they are landing in city-regions whose groundwater is already drawn down faster than it recharges. The mitigation — municipal supply, treated-wastewater reuse and recycling — exists, but it competes with household and agricultural demand and leans on monsoon-sensitive surface sources.
Why this stays hidden
The risk is under-discussed because it is assessed at the wrong resolution. National water-availability figures look adequate; CGWB categories are reported by assessment unit; and individual project clearances treat water as a line item rather than a system. What does not exist publicly is the corridor-level audit: for a given industrial cluster, the firm water available across sources, the committed industrial draw, the competing municipal and agricultural demand, and the resilience under a weak monsoon. Without it, water risk is invisible until it binds.
This is the Dholera lesson generalised. Dholera's exposure is a single canal; the metros' exposure is over-drawn aquifers plus monsoon-dependent reservoirs. In both cases the binding question is corridor-level, and in both the audit is missing.
The signal to watch
- CGWB category changes in the assessment units hosting data-centre and fab clusters.
- Treated-wastewater reuse ratios actually achieved by industrial clusters, versus targets.
- Water allocations granted to new industrial load against municipal and agricultural demand.
- Whether any state publishes a corridor-level industrial-water audit.
The water position will not announce itself. It will surface as a permitting delay, a tanker bill, or a curtailed ramp in a dry year. The clusters to watch are the ones where the pipeline is densest and the aquifer is already over-exploited — and the document to demand is the corridor-level audit that no one is yet publishing.
Track the systems we watch
Signals, reports and briefings on India’s industrial transformation.