What Can Disaster Recovery Teach Us About Engineering Quality?

When Disasters Strike

Infrastructure often supports many of the systems communities rely on every day – from transport and electricity, to water, communications, and essential facilities. When these systems are disrupted, their ability to provide their intended functions can also be affected, with the extent and duration varying from one situation to another. Natural hazards such as floods, earthquakes, landslides, cyclones, and wildfires can place infrastructure under conditions that differ from those experienced during normal operation. 

In recent months, disasters involving several of these hazards have affected communities in different parts of the world, with consequences extending to livelihoods and essential services.

Earlier this year, the June 2026 earthquakes affected parts of Venezuela, which have caused an estimated $19.6 billion in direct physical damage and with infrastructure accounting for 27% of the total according to the World Bank Group. In August, similar disruptions affected communities in several areas of the Philippines, where the combined effects of the southwest monsoon and tropical cyclones led to widespread flooding.

According to the Philippine National Disaster Risk Reduction and Management Council (NDRRMC), 88 cities and municipalities had been placed under a state of calamity as of 21 August. Around the same period, severe flooding in Nepal affected critical infrastructure on August 26. According to the United Nations Development Program (UNDP), around 70 kilometers of roads and 80 bridges were damaged, while 13 hydropower projects and more than 150 kilometers of telecommunications fiber were also affected.  

These disruptions to essential infrastructure raise a broader engineering question: what does the recovery process reveal about the quality of an engineering solution? The  United Nations Development Program (UNDP) Post Disaster Needs Assessment Guidelines states that post-disaster assessments examine damage, recovery needs, and underlying vulnerabilities. In short, the process can tell engineering professionals where designs fell short, what held up, and what can be improved.

Where Designs Fell Short

The first thing disaster recovery can reveal is where an engineering solution fell short.  

Examining infrastructure after a disaster can give engineering professionals a clearer picture of how individual components interacted, how systems performed under stress, and where vulnerabilities emerged. For engineering students, this provides a useful way to approach project work: instead of evaluating a design only against its intended operating conditions, they can identify which parts of the solution are most sensitive to changes and test those areas more closely. 

Key Takeaway:

Every design shortfall leaves engineering professionals with a choice: treat it as an isolated failure or use what it revealed to develop the next design decision. 

What Held Up

Disaster recovery can also reveal what worked. Infrastructure that continues to perform after a disruptive event can provide useful evidence of which design decisions, components, or systems contribute to resilience. For engineering professionals, this can help distinguish between elements that simply survived and those that continued to provide their intended function when other parts of the system were affected.

This offers another way to evaluate project designs: rather than simply accepting a design outcome, they can examine which choices contributed to reliable performance and whether the results make engineering sense. As what the Engineering Institute of Technology (EIT) Civil Engineering Lecturer Dr. Igor Shufrin emphasizes, “Students need to learn not only how to use engineering software, but how to challenge the result.” 

Key takeaway:

What holds up can show more than that a solution survived. It can provide evidence of successful resilience, giving engineering professionals a clearer basis for deciding which design choices should be carried forward into future projects. 

What Can Be Improved

Disaster recovery can also show where engineering solutions have room to improve.  

Lessons from damaged and resilient infrastructure can help engineering professionals examine whether a failure was linked to a vulnerable component or an overlooked interaction between systems. Recovery findings may point toward specific changes in materials, connections, drainage, redundancy, maintenance requirements, or operating procedures that could reduce the same vulnerability in future projects. For engineering students, this provides a practical way to ask which part of the design needs greater attention, revise relevant parameters, and use engineering judgment to determine what needs to change. 

Key takeaway:

The value of recovery is not only in identifying what went wrong, but in narrowing down what needs to change, where it needs to change, and why. Ultimately, disaster recovery can reveal aspects of engineering quality that are difficult to see during the design phase alone. While natural hazards cannot always be avoided, the way engineering professionals can anticipate their effects, respond when they occur, and recover afterward can help reduce the possible damage it can give to communities.   

EIT’s industry exposure and engineering courses, including Engineering Management, bring students into contexts where they can consider how technical decisions interact with project requirements and industry conditions, while learning to weigh evidence and make sound engineering judgments. Together, these experiences will help develop the strong ability to approach engineering problems with both technical understanding and practical awareness. 

References 

The Long Road to Recovery Begins 

88 areas under state of calamity 

World Bank Group Estimates Earthquake Damage