Understand the topic
What this means in daily life
Drinking-water pipes, sewage pipes and rainwater drains have different jobs. This topic looks at places where those networks are wrongly connected, damaged or poorly recorded. The aim is to understand how a failure in one network affects the others and the people who depend on them.
The proposed work begins with one manageable area and the teams responsible for its services. Residents can describe recurring problems and help locate them. Authorised engineers and trained crews must inspect networks, judge water quality and carry out any physical correction. This is not a guide to opening drains or changing connections yourself.
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.
5 measurement records still need data and a review of their relevance.
| Signal | Reference Value | Period / Population | How to Read It | Source Status |
|---|---|---|---|---|
| Service coverage | 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 |
| Reliability and quality | 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 |
| Loss, overflow or flood duration | 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 |
| Treatment and safe reuse | 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 |
| Lifecycle cost and equity | 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.
Evidence coverage and review log (CSV) · Structured evidence register (JSON)
10 ideas for this topic
What could be done — and what needs testing
These are proposals for research and local testing. They are not claims that a project has been funded, implemented or proved successful.
A shared three-network street map
Bring water, sewer and drainage drawings onto one ward map. Mark unknown sections and suspected connections as unverified until the responsible teams inspect them.
What to check: Check whether crews can identify the correct network and owner before a road is opened.
An authorised cross-connection investigation
Create a joint inspection list for locations where residents report dirty water, sewage in drains or repeated overflow. Ask qualified teams to choose appropriate inspection and sampling methods.
What to check: Check evidence before naming a cause; an unpleasant smell or photograph alone cannot establish contamination.
A dry-weather drain observation route
Ask municipal teams to inspect selected storm drains during dry weather and record unexpected flows for further investigation. Keep sewage, commercial discharge and other possible causes separate in the record.
What to check: Check whether follow-up identifies a source rather than assuming every observed flow is sewage.
A coordinated road-opening schedule
Publish an internal shared schedule of planned water, sewer and drainage repairs so teams can compare access needs before excavation.
What to check: Check whether coordination reduces repeat digging without delaying urgent safety repairs.
An outlet-to-treatment handoff register
Record where each inspected sewer route is expected to lead and which team accepts responsibility at the next stage, including pumping or treatment facilities.
What to check: Check whether the receiving service can handle the proposed correction; avoid moving an overload downstream.
An accessible household connection explanation
Prepare simple diagrams showing the intended route for drinking water, wastewater and rainwater in local housing types. Offer explanations in relevant languages.
What to check: Test understanding with tenants and homeowners; do not turn diagrams into instructions for unqualified alterations.
A repair acceptance check across departments
After an authorised repair, ask both the repairing team and affected service teams to confirm the connection, surface restoration and follow-up responsibilities.
What to check: Check whether the record includes the receiving team's response, not just contractor completion.
A service-failure reporting trail
Give recurring mixed-flow complaints one traceable case record with dates, investigation findings, actions and unresolved questions.
What to check: Check whether residents can understand the response and report recurrence without starting from zero.
A monsoon readiness review of repaired locations
Before the wet season, revisit previously corrected locations with the relevant teams to identify unfinished access, maintenance or discharge arrangements.
What to check: Compare conditions under similar rainfall and operating circumstances rather than promising flood prevention.
A ward-level outcome review
Track repeat incidents, time to investigate, confirmed corrections and unresolved cases. Include resident experience and any harm caused by the works.
What to check: Separate confirmed network changes from assumptions about health or flood benefits.
References and evidence limits
- CPHEEO: Manual on Storm Water Drainage Systems (2019)
A technical reference for specialist planning, operation and maintenance review. It does not establish the condition of a local network or approve a proposed design.
Reference guidance informs the proposal. It does not establish local conditions, approve a design or prove that these proposed projects work.