August 24, 2026 · by David Gilbert · 3 min read · Emergency Services & Tech
A flood response, by its nature, tends to stretch every single piece of equipment and every backup plan to its genuine practical limit, not just its comfortable theoretical one. One particular flood callout taught me more about real-world redundancy, in a single long, exhausting stretch, than any amount of calm, comfortable planning ever had.
Why Floods Are Uniquely Hard on Equipment and Plans
Unlike a lot of emergencies that resolve in hours, flood responses can run for days, across a genuinely large area, with conditions that actively degrade equipment the entire time — water, mud, constant heavy use, exhausted volunteers running on too little sleep making small mistakes they wouldn't normally make. Redundancy plans built around "this piece of gear might fail" get properly tested by "this piece of gear, and its backup, and possibly its backup's backup, are all under sustained stress simultaneously, for days."
What Held Up, and Why
Equipment with genuinely independent power sources held up best — gear that didn't share a single point of failure with everything else relying on the same generator, the same vehicle, the same charging setup. The lesson reinforced itself constantly: redundancy that shares an underlying dependency with the thing it's meant to back up isn't real redundancy, it's just a second copy of the identical vulnerability, waiting for the same failure to take both out together.
What Didn't Hold Up
A few items we'd assumed were robust enough for sustained, multi-day conditions started showing real wear faster than anyone expected, purely because most equipment testing and assumptions are built around shorter, more contained incidents rather than the genuinely sustained, multi-day grind a serious flood response actually demands. We'd planned reasonably well for "this might fail" and less well for "this might fail after sustained heavy use longer than we typically plan around."
The Human Side of Redundancy
Equipment wasn't the only thing needing backup — people did too. Volunteers genuinely need relief, rotation, and rest built deliberately into a multi-day response, not because anyone's individually weak, but because sustained, high-stress work without planned relief degrades judgement and safety for absolutely everyone eventually, no matter how experienced or committed they are. Treating people as needing the exact same kind of deliberate redundancy planning as equipment was a genuine, important shift in how I think about this.
What I Changed Afterwards
I now think specifically about sustained-use scenarios, not just single-failure scenarios, when assessing equipment and plans for genuinely serious situations — both in emergency services contexts and, just as importantly, in business continuity conversations with clients. A system that survives one bad day is necessarily different from one that survives a genuinely bad week, and a lot of planning, mine included before this, quietly only accounts for the former.
Where This Maps Directly to Business Continuity
A backup generator that runs fine for a few hours during a short outage might behave completely differently across several genuinely sustained days. A staff member covering for a colleague might manage a few days fine and then genuinely burn out covering for weeks. Planning for the short version of a disruption while quietly hoping the long version never happens is a real, common gap, and it's exactly the gap that an extended, genuinely difficult flood callout taught me to actually take seriously.
The Honest Takeaway
Redundancy planning is usually built, understandably, around the scenarios that are easiest to imagine clearly — short, sharp, contained failures. The scenarios that actually do the most damage are often the sustained, grinding ones nobody quite planned for in enough detail, because they're genuinely harder to imagine clearly until you've actually lived through one.
