Yes—but only if power, water and land availability help decide where data centers are built, rather than being problems to solve after a project is approved. A facility can be efficient inside its boundary and still place an unreasonable burden on the surrounding community.
For India, the practical question is not simply how much data-center capacity to add. It is how much each location can support without weakening electricity reliability, competing for scarce water or passing infrastructure costs to residents.
Plan around local limits, not just investment targets
- Assess clusters, not isolated projects. Several facilities drawing from the same substation or water system can create pressures that individual project assessments miss. Approvals should consider existing users, proposed developments and seasonal shortages together.
- Make electricity connections conditional on capacity. Grid studies should identify the generation, transmission and distribution upgrades needed before large loads connect. Clear cost-sharing rules can prevent dedicated infrastructure from being subsidized unfairly by other consumers. Renewable power procurement helps, but annual renewable-energy purchases alone do not prove that electricity is available locally during every operating hour.
- Set water rules for dry periods. Water demand should be assessed against local water stress, including summer conditions and drought restrictions—not just annual availability. Treated wastewater can reduce freshwater use where reliable supplies exist, but its treatment, transport and competing uses also need assessment.
- Choose cooling for the site. Data center cooling systems involve trade-offs: some water-saving designs require more electricity, particularly in hot weather. Liquid cooling does not automatically mean low water consumption; the method used to reject heat outside the building matters too.
- Look beyond the building footprint. Land selection should account for flood exposure, drainage, nearby housing and the noise and emissions associated with backup generators. Moving a facility away from an established hub only helps if the new location has suitable infrastructure and connectivity.
Measure the burden that neighbours actually experience
Power usage effectiveness measures facility energy efficiency, while water usage effectiveness tracks water use relative to IT energy consumption. Both are useful, but neither replaces reporting absolute consumption. A very large, efficient campus can still use more electricity or water than a smaller, less efficient one.
Planning authorities should therefore require reporting of total electricity demand, peak load, water withdrawals and consumption by source, and backup-generator operation. Those figures need to be read alongside local supply conditions. Water consumed in a stressed catchment has a different consequence from the same volume consumed where supply is more secure.
There is also some flexibility in where computing happens. Services needing very low latency may need to remain near users or network hubs, while some batch processing and other delay-tolerant workloads can be placed elsewhere. That creates room to direct suitable investment toward locations with stronger resource capacity rather than concentrating everything in a few clusters.
The credible promise is manageable impact, not zero impact. Phased approvals, developer-funded upgrades where appropriate, enforceable consumption limits and public reporting can make growth more compatible with local needs. Where a district cannot support another large load without compromising essential services, delaying, downsizing or relocating the project should remain a real option.
