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

Separate Water, Sewer & Stormwater Networks

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.

Cross-connections and damaged pipes can contaminate drinking water.

Sewage entering storm drains reduces treatment and flood capacity.

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 Separate Water, Sewer & Stormwater Networks
SignalReference ValuePeriod / PopulationHow to Read ItSource Status
Estimated urban sewage generation

72,368 million litres per day

Reported value — scope clarification required

2021 published inventory; uniform underlying observation cut-off not established

Urban areas in India covered by the CPCB assessment

A historical national urban wastewater-load estimate.

Limitations: An estimate rather than a measurement of every discharge. It is not current city-level sewage generation or industrial effluent volume.

Ministry of Jal Shakti / Central Pollution Control Board

Official government release

Record type: official assessment estimate

Pollution in Rivers

Published: 2021-08-05

Publication checked: 2026-11-04

Period / coverage needs clarification

Assets accurately mapped

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

Cross-connections closed

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

Sewer overflow

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.

Incomplete or outdated as-built maps

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

Utilities installed without shared corridor records

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

Combined legacy systems

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

Maintenance access blocked

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.

Drinking-water network

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

Sewer/wastewater network

Stormwater network

Pipeline and utility mapping

Leak, pressure and flow monitoring

Asset access and lifecycle management

Section 04

A solution suited to India

Match intervention to hydrogeology, settlement and service capacity.

Create surveyed, versioned underground asset maps.

Use colour/asset identification and safe separation standards.

Detect and remove illicit connections.

Upgrade combined systems progressively with overflow and treatment plans.

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

Map and inspect one high-risk utility corridor, correct cross-connections and create maintainable access records.

  • 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

Assets accurately mapped
Baseline · target · actual · unit · source · period · distribution

KPI 02

Cross-connections closed
Baseline · target · actual · unit · source · period · distribution

KPI 03

Sewer overflow
Baseline · target · actual · unit · source · period · distribution

KPI 04

Break/repair time
Baseline · target · actual · unit · source · period · distribution

KPI 05

Preventive inspections
Baseline · target · actual · unit · source · period · distribution

Section 07

Risks and protections

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

  • Risk: Excavation damage
    Prevention · accountable owner · trigger · remedy
  • Risk: Maps exposing critical assets
    Prevention · accountable owner · trigger · remedy
  • Risk: Unfunded separation mandates
    Prevention · accountable owner · trigger · remedy

15 questions, answered clearly

Questions about Separate Water, Sewer & Stormwater Networks

What does Separate Water, Sewer & Stormwater Networks focus on?

Cross-connections and damaged pipes can contaminate drinking water.

What changes does the page propose?

Create surveyed, versioned underground asset maps. Use colour/asset identification and safe separation standards. Detect and remove illicit connections. Upgrade combined systems progressively with overflow and treatment plans.

Which parts need to work together?

The proposed system connects Drinking-water network; Sewer/wastewater network; Stormwater network; Pipeline and utility mapping; Leak, pressure and flow monitoring; Asset access and whole-life management. 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 Incomplete or outdated as-built maps; Utilities installed without shared corridor records; Combined legacy systems; Maintenance access blocked. 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 Separate Water, Sewer & Stormwater Networks.

What could a first trial of Separate Water, Sewer & Stormwater Networks look like?

Map and inspect one high-risk utility corridor, correct cross-connections and create maintainable access records. 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 Assets accurately mapped; Cross-connections closed; Sewer overflow; Break/repair time; Preventive inspections. 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?

Excavation damage. Maps exposing critical assets. Unfunded separation mandates.

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. Map and inspect one high-risk utility corridor, correct cross-connections and create maintainable access records. 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 Drinking-water network; Sewer/wastewater network; Stormwater network; Pipeline and utility mapping; Leak, pressure and flow monitoring; Asset access and whole-life management. 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?

Define the responsible actor, operating standard, input, handoff, maintenance requirement, failure trigger and evidence record. Safety; Water balance; Affordability; Equity; Operations; Ecology; Climate risk; Accountability. 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 — Assets accurately mapped; Cross-connections closed; Sewer overflow — 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 Assets accurately mapped; Cross-connections closed; Sewer overflow.