Explore IndiaCurrent IndiaTomorrow IndiaSearchReport a problem
India For Tomorrow
[google-translator]Language / भाषा
← Water library
From the IFT source library

Rainwater Harvesting & Recharge

Text from the existing IFT website. Sources and claims are still under editorial review.

Original source ↗

Section 01

Where the problem happens

Define the service failure before selecting infrastructure.

A standard structure may fail where soil, aquifer, contamination or maintenance conditions differ.

Harvesting performance is rarely measured after construction.

Required local context

Record state, district, city/block, village/ward or supply zone; season and date; source or asset; affected users; observed service; measurement or sample method; photo/document where safe; and uncertainty. Never imply 100-metre accuracy unless the evidence genuinely supports it.

Data reference table

Evidence Snapshot

Read each value with its reporting period, population and limitations. A historical national reference is not a local baseline or proof that an IFT proposal works.

1 source-linked reference record. 3 measurement records still need data and a review of their relevance.

Data references for Rainwater Harvesting & Recharge
SignalReference ValuePeriod / PopulationHow to Read ItSource Status
Assessed recharge from tanks, ponds and water-conservation structures

25.34 billion cubic metres

Historical reference

Groundwater assessment water year 2024

India; assessed recharge component

A national resource-assessment component relevant to recharge planning.

Limitations: It does not measure the benefit of an individual rainwater-harvesting project or prove that all structures function.

Ministry of Jal Shakti / Central Ground Water Board and States/UTs

Official government release

Record type: official resource assessment estimate

Ministry of Jal Shakti year-end review: Ground Water Resources

Published: 2025-01-25

Publication checked: 2026-11-04

Value, period and coverage checked in publication

Water captured

Not established

Data required — not zero

Reporting period: Information Required

Population and geography: Information Required

Proposed measure; no observed value is established here.

Limitations: Define the measure, unit, reporting period and covered population; obtain a traceable dataset and review its suitability for this topic before using a number.

Source organisation: Information Required

Direct source URL: not yet verified

Source publication date: not established

Verification status: Data required

Useful storage/recharge

Not established

Data required — not zero

Reporting period: Information Required

Population and geography: Information Required

Proposed measure; no observed value is established here.

Limitations: Define the measure, unit, reporting period and covered population; obtain a traceable dataset and review its suitability for this topic before using a number.

Source organisation: Information Required

Direct source URL: not yet verified

Source publication date: not established

Verification status: Data required

Overflow safely managed

Not established

Data required — not zero

Reporting period: Information Required

Population and geography: Information Required

Proposed measure; no observed value is established here.

Limitations: Define the measure, unit, reporting period and covered population; obtain a traceable dataset and review its suitability for this topic before using a number.

Source organisation: Information Required

Direct source URL: not yet verified

Source publication date: not established

Verification status: Data required

Different surveys, administrative records, estimates and reporting years are not interchangeable. No combined IFT score is calculated from these rows.

Section 02

Why the problem happens

Test the full source-to-service chain.

Design based on mandate not water balance

Treat this as a hypothesis until records, field observation, seasonal evidence and credible alternatives are checked.

Silt and contamination controls neglected

Treat this as a hypothesis until records, field observation, seasonal evidence and credible alternatives are checked.

Ownership of maintenance unclear

Treat this as a hypothesis until records, field observation, seasonal evidence and credible alternatives are checked.

Captured water lacks planned use

Treat this as a hypothesis until records, field observation, seasonal evidence and credible alternatives are checked.

Section 03

How the parts work together

Components that must work together.

Rooftop capture

Define the responsible actor, operating standard, input, handoff, maintenance requirement, failure trigger and evidence record.

Recharge wells where suitable

Village and farm ponds

Check dams and watersheds

Urban retention and rain gardens

Stormwater capture and reuse

Section 04

A solution suited to India

Match intervention to hydrogeology, settlement and service capacity.

Screen rainfall, catchment, soil, aquifer and water quality first.

Size storage and overflow for local extremes.

Provide first-flush, silt and maintenance systems.

Measure captured, used or recharged water.

Decision checks

Safety; Water balance; Affordability; Equity; Operations; Ecology; Climate risk; Accountability

Section 05

Roadmap

Diagnose, protect, pilot, measure and institutionalise.

  • 0–90 DAYS
  • Verify & protect

Confirm the location, affected users, service chain, immediate health or safety risk, responsible agency and existing evidence.

  • 3–18 MONTHS
  • Controlled pilot

Compare rooftop storage, landscape retention and recharge at representative sites with a full monsoon water balance.

  • 1–5+ YEARS
  • Durable system

Fund operations, preventive maintenance, skilled teams, monitoring, public reporting, correction pathways and independent evaluation.

Section 06

Results

Measure service and outcomes—not assets alone.

KPI 01

Water captured
Baseline · target · actual · unit · source · period · distribution

KPI 02

Useful storage/recharge
Baseline · target · actual · unit · source · period · distribution

KPI 03

Overflow safely managed
Baseline · target · actual · unit · source · period · distribution

KPI 04

Water quality
Baseline · target · actual · unit · source · period · distribution

KPI 05

Maintenance compliance
Baseline · target · actual · unit · source · period · distribution

Section 07

Risks and protections

Water interventions can transfer risk across people, places and time.

  • Risk: Contaminated recharge
    Prevention · accountable owner · trigger · remedy
  • Risk: Mosquito or drowning hazards
    Prevention · accountable owner · trigger · remedy
  • Risk: Downstream flow impacts
    Prevention · accountable owner · trigger · remedy

15 questions, answered clearly

Questions about Rainwater Harvesting & Recharge

What does Rainwater Harvesting & Recharge focus on?

A standard structure may fail where soil, aquifer, contamination or maintenance conditions differ.

What changes does the page propose?

Screen rainfall, catchment, soil, aquifer and water quality first. Size storage and overflow for local extremes. Provide first-flush, silt and maintenance systems. Measure captured, used or recharged water.

Which parts need to work together?

The proposed system connects Rooftop capture; Recharge wells where suitable; Village and farm ponds; Check dams and watersheds; Urban retention and rain gardens; Stormwater capture and reuse. Assign a responsible team, service standard, handoff and maintenance plan for each part

What local information is needed before taking action?

Record state, district, city/block, village/ward or supply zone; season and date; source or asset; affected users; observed service; measurement or sample method; photo/document where safe; and uncertainty. Never imply 100-metre accuracy unless the evidence genuinely supports it.

What could be causing the problem?

Possible causes to investigate include Design based on mandate not water balance; Silt and contamination controls neglected; Ownership of maintenance unclear; Captured water lacks planned use. Treat these as questions to test against local records and experience, rather than confirmed causes in every location.

What evidence should researchers collect?

Record the starting conditions, service records, affected users’ experience, costs and the source and date of each observation. Compare more than one explanation and state what is still uncertain. Use this evidence to assess Rainwater Harvesting & Recharge.

What could a first trial of Rainwater Harvesting & Recharge look like?

Compare rooftop storage, landscape retention and recharge at representative sites with a full monsoon water balance. Agree the place, responsible team, comparison, safety checks and measurement period before starting. The trial described here is a proposal, not a reported result.

How should improvement be measured?

The page proposes tracking Water captured; Overflow safely managed; Water quality; Maintenance compliance. Define each measure, record the starting value and reporting period, then compare later results using the same method. Report who benefits and any harm or uncertainty.

What risks and safeguards need attention?

Contaminated recharge. Mosquito or drowning hazards. Downstream flow impacts.

What is the suggested order of work?

Diagnose, protect, pilot, measure and build lasting services. 0–90 DAYS. Verify & protect. Confirm the location, affected users, service chain, immediate health or safety risk, responsible agency and existing evidence. 3–18 MONTHS. Controlled pilot. Compare rooftop storage, landscape retention and recharge at representative sites with a full monsoon water balance. 1–5+ YEARS. Durable system. Fund operations, preventive maintenance, skilled teams, monitoring, public reporting, correction pathways and independent evaluation. These stages are planning ranges. Actual timing depends on local conditions, resources, permissions and delivery capacity.

Who should take responsibility for delivery?

Information Required: the named organisation and accountable local team. Responsibilities must cover Rooftop capture; Recharge wells where suitable; Village and farm ponds; Check dams and watersheds; Urban retention and rain gardens; Stormwater capture and reuse. Assign an owner for each handoff, record how problems will be escalated, and agree who will fund and maintain the work.

What costs should be checked before approval?

A standard structure may fail where soil, aquifer, contamination or maintenance conditions differ. Define the responsible actor, operating standard, input, handoff, maintenance requirement, failure trigger and evidence record. Information Required: a local cost estimate, funding source and ongoing operating and maintenance budget. Include costs shifted to households or other services when comparing options.

How should access and fairness be checked?

Safety; Water balance; Affordability; Equity; Operations; Ecology; Climate risk; Accountability. Compare access, costs, safety and results across the groups affected in this location. Record missing information and correct exclusion before expanding the proposal.

When should the approach expand, change or stop?

Use the proposed measures — Water captured; Overflow safely managed; Water quality — to review benefit, harm, cost and the ability to keep the service working. Expand only when the evidence supports it; change a partly effective design and stop an unsafe or ineffective approach.

Does this page establish that the proposal has succeeded?

No verified local result should be inferred from the proposal alone. Information Required: a dated starting measurement, later results, costs, affected groups and an independent assessment. The proposed review should examine Water captured; Overflow safely managed; Water quality.