Beyond design return period — managing extreme events that exceed system capacity. Urban flood vulnerability mapping, AMRUT 2.0 storm water plans, NDMA Urban Flooding Guidelines (2010), early warning systems, emergency response, post-event learning, climate adaptation strategies, integration with disaster management framework.
Urban flood management is the chapter that distinguishes 21st-century professional drainage practice from 20th-century 'design + forget' engineering. The reality of climate change + densification + chronic O&M neglect means every Indian city floods periodically, regardless of design.
The two-check framework is the modern standard:
1. Design return period (5-25 yr typical) sizes the drainage system — the system functions normally up to this.
2. Extreme event check (100 yr + climate uplift) verifies that consequences are acceptable beyond design capacity. Streets may flood (acceptable inconvenience), but buildings + critical infrastructure must not (unacceptable loss).
Mumbai July 2005 (944 mm/24hr), Chennai December 2015 (1049 mm/3 days), Hyderabad October 2020 — all exceeded design return periods by 2-5×. Without explicit extreme-event consideration, the response is reactive + chaotic.
NDMA Urban Flooding Guidelines (2010) provide the institutional framework: vulnerability assessment, Early Warning System (EWS), Incident Response System (IRS), post-event learning. Compliance is uneven — Smart Cities + AMRUT 2.0 are forcing the issue.
AMRUT 2.0 storm water master plan is the mandate: 25-30 year horizon, climate-adjusted, GIS-based, hydraulic-model validated. Phase 1 underway for most Class-1 cities in 2026. Without a coherent master plan, ad-hoc projects don't add up to a functioning system.
Early warning systems target ≥ 30 minutes lead time per NDMA. Modern stack: IMD heavy rainfall forecast + city sensor network (rainfall + level + flow) + IoT backbone + dashboard + SMS/social media alerts. Hyderabad, Pune, Bangalore, Surat have active deployments via Smart Cities Mission funding.
Flood depth × velocity > 0.6 m·m/s is the lethal threshold — vehicles + people get swept. Critical underpasses + low points need monitoring + automated traffic interventions (signal + barrier closure on threshold).
Post-event learning is the institutional discipline that separates competent ULBs from incompetent ones. Every major event should trigger forensic review: what failed? what assumptions were wrong? what to upgrade? Mumbai's 2005 + 2017 + 2024 events have systematically driven improvements; many cities lack this discipline.
Citizen reporting apps (e.g., Bengaluru BBMP, Mumbai MCGM) crowdsource flood location data — useful for emergency response + future planning. Insurance industry pricing flood risk into premiums (IRDAI 2018+) is creating financial pressure on ULBs.
Pluvial vs fluvial distinction matters: pluvial = local rainfall exceeds drainage (urban problem); fluvial = river overflows banks (CWC + irrigation problem). Both can occur simultaneously in monsoon. CPHEEO Storm Water Manual addresses pluvial; fluvial handled by CWC flood codes.
Where this chapter sits: this is the chapter that converts technical drainage design into risk management. The drainage design from earlier chapters defines normal-event capacity; this chapter defines what happens when normal isn't enough. The combination is climate-resilient infrastructure + responsive crisis management — what Indian cities increasingly need but rarely have.