Risk Management

Technical risk management has a significant impact on project viability and success. Technical risk is not afforded the attention it requires/ deserves both in terms of risk identification and weighting (probability and impact). The following is not a general criticism, but it is easy for the project and technical/ design team to pay lip service to technical risk "hoping" that the factors of safety etc will be a net for any potential technical risks. How do we ensure technical risks are adequately assessed and weighted and is this the role of the Engineers or Project Manager to facilitate this technical risk discussion?

A starting point might be to identify the types of situations where one needs to quantify a technical risk, recognizing that codes and standards address many technical risks. Situations that come to mind include reassessment of existing structures or implementing a novel material or configuration. What else in the built world?

Technical risk management has a significant impact on project viability and success. Technical risk is not afforded the attention it requires/ deserves both in terms of risk identification and weighting (probability and impact). The following is not a general criticism, but it is easy for the project and technical/ design team to pay lip service to technical risk "hoping" that the factors of safety etc will be a net for any potential technical risks. How do we ensure technical risks are adequately assessed and weighted and is this the role of the Engineers or Project Manager to facilitate this technical risk discussion?

Excellent question, Steve.

One area of technical risk uncertainty is rainfall intensity, duration, and frequency (IDF). I recently reviewed an industrial location design in which the storm drains, detention areas, and pumping systems had to be sized. The designers started with NOAA Atlas14 IDF data for the site, which NOAA recognizes as already outdated by climate change-induced shifts in IDF. An updated set of IDF tables and maps was scheduled to begin publication in 2026, but that effort was paused by the President. It has now resumed but the effect of the pause and reduced NOAA workforce numbers and experience isn't clear to me.

Meanwhile, the design must be done now. The designers added a percentage to the IDF guideline values and then provided for adding pump capacity if the need arises. In this case the impacts of flooding can be easily defined but the probability of flooding has been defined arbitrarily. Is it sufficient? Is it necessary? That's unknown technical risk for that project and many other detention ponds, storm drains, flood channels, dams, and levees.

Bill Mc

A starting point might be to identify the types of situations where one needs to quantify a technical risk, recognizing that codes and standards address many technical risks. Situations that come to mind include reassessment of existing structures or implementing a novel material or configuration. What else in the built world?

Technical risk management has a significant impact on project viability and success. Technical risk is not afforded the attention it requires/ deserves both in terms of risk identification and weighting (probability and impact). The following is not a general criticism, but it is easy for the project and technical/ design team to pay lip service to technical risk "hoping" that the factors of safety etc will be a net for any potential technical risks. How do we ensure technical risks are adequately assessed and weighted and is this the role of the Engineers or Project Manager to facilitate this technical risk discussion?

Excellent question, Steve.

One area of technical risk uncertainty is rainfall intensity, duration, and frequency (IDF). I recently reviewed an industrial location design in which the storm drains, detention areas, and pumping systems had to be sized. The designers started with NOAA Atlas14 IDF data for the site, which NOAA recognizes as already outdated by climate change-induced shifts in IDF. An updated set of IDF tables and maps was scheduled to begin publication in 2026, but that effort was paused by the President. It has now resumed but the effect of the pause and reduced NOAA workforce numbers and experience isn't clear to me.

Meanwhile, the design must be done now. The designers added a percentage to the IDF guideline values and then provided for adding pump capacity if the need arises. In this case the impacts of flooding can be easily defined but the probability of flooding has been defined arbitrarily. Is it sufficient? Is it necessary? That's unknown technical risk for that project and many other detention ponds, storm drains, flood channels, dams, and levees.

Bill Mc

A starting point might be to identify the types of situations where one needs to quantify a technical risk, recognizing that codes and standards address many technical risks. Situations that come to mind include reassessment of existing structures or implementing a novel material or configuration. What else in the built world?

Technical risk management has a significant impact on project viability and success. Technical risk is not afforded the attention it requires/ deserves both in terms of risk identification and weighting (probability and impact). The following is not a general criticism, but it is easy for the project and technical/ design team to pay lip service to technical risk "hoping" that the factors of safety etc will be a net for any potential technical risks. How do we ensure technical risks are adequately assessed and weighted and is this the role of the Engineers or Project Manager to facilitate this technical risk discussion?

A starting point might be to identify the types of situations where one needs to quantify a technical risk, recognizing that codes and standards address many technical risks. Situations that come to mind include reassessment of existing structures or implementing a novel material or configuration. What else in the built world?

Technical risk management has a significant impact on project viability and success. Technical risk is not afforded the attention it requires/ deserves both in terms of risk identification and weighting (probability and impact). The following is not a general criticism, but it is easy for the project and technical/ design team to pay lip service to technical risk "hoping" that the factors of safety etc will be a net for any potential technical risks. How do we ensure technical risks are adequately assessed and weighted and is this the role of the Engineers or Project Manager to facilitate this technical risk discussion?

Technical risk management has a significant impact on project viability and success. Technical risk is not afforded the attention it requires/ deserves both in terms of risk identification and weighting (probability and impact). The following is not a general criticism, but it is easy for the project and technical/ design team to pay lip service to technical risk "hoping" that the factors of safety etc will be a net for any potential technical risks. How do we ensure technical risks are adequately assessed and weighted and is this the role of the Engineers or Project Manager to facilitate this technical risk discussion?

Stephen,

The primer stated that using a standard or design code is a form of risk treatment. The question becomes, if those standards are out of date due to changes in climate, etc., what is the standard of care that an engineer should implement to modify those standards? If they do add a safety factor and it is wrong, are they then liable? I think that is when involving all of the participants in those discussions becomes important. An owner needs to understand the risks of staying with the standards and what might happen in the future. 

I think the design industry needs to develop a standard list of potential technical risks. Research can then be conducted to develop probability of occurrence and methodologies to calculate impacts. This would help firms that don't have the staff and/or sophistication to develop this information themselves.

Technical risk management has a significant impact on project viability and success. Technical risk is not afforded the attention it requires/ deserves both in terms of risk identification and weighting (probability and impact). The following is not a general criticism, but it is easy for the project and technical/ design team to pay lip service to technical risk "hoping" that the factors of safety etc will be a net for any potential technical risks. How do we ensure technical risks are adequately assessed and weighted and is this the role of the Engineers or Project Manager to facilitate this technical risk discussion?

James, thanks and you have made a valid point and a useful suggestion. Which entity would prepare a "standard list of potential risks"? Is this something ASCE could initiate?

Stephen,

The primer stated that using a standard or design code is a form of risk treatment. The question becomes, if those standards are out of date due to changes in climate, etc., what is the standard of care that an engineer should implement to modify those standards? If they do add a safety factor and it is wrong, are they then liable? I think that is when involving all of the participants in those discussions becomes important. An owner needs to understand the risks of staying with the standards and what might happen in the future. 

I think the design industry needs to develop a standard list of potential technical risks. Research can then be conducted to develop probability of occurrence and methodologies to calculate impacts. This would help firms that don't have the staff and/or sophistication to develop this information themselves.

Technical risk management has a significant impact on project viability and success. Technical risk is not afforded the attention it requires/ deserves both in terms of risk identification and weighting (probability and impact). The following is not a general criticism, but it is easy for the project and technical/ design team to pay lip service to technical risk "hoping" that the factors of safety etc will be a net for any potential technical risks. How do we ensure technical risks are adequately assessed and weighted and is this the role of the Engineers or Project Manager to facilitate this technical risk discussion?

Steve, building a list of technical risks is a great idea. The starting place is this community. I can investigate creating a shared document later today. We should include a brief description of the issue at hand.

James, thanks and you have made a valid point and a useful suggestion. Which entity would prepare a "standard list of potential risks"? Is this something ASCE could initiate?

Stephen,

The primer stated that using a standard or design code is a form of risk treatment. The question becomes, if those standards are out of date due to changes in climate, etc., what is the standard of care that an engineer should implement to modify those standards? If they do add a safety factor and it is wrong, are they then liable? I think that is when involving all of the participants in those discussions becomes important. An owner needs to understand the risks of staying with the standards and what might happen in the future. 

I think the design industry needs to develop a standard list of potential technical risks. Research can then be conducted to develop probability of occurrence and methodologies to calculate impacts. This would help firms that don't have the staff and/or sophistication to develop this information themselves.

Technical risk management has a significant impact on project viability and success. Technical risk is not afforded the attention it requires/ deserves both in terms of risk identification and weighting (probability and impact). The following is not a general criticism, but it is easy for the project and technical/ design team to pay lip service to technical risk "hoping" that the factors of safety etc will be a net for any potential technical risks. How do we ensure technical risks are adequately assessed and weighted and is this the role of the Engineers or Project Manager to facilitate this technical risk discussion?

Steve, building a list of technical risks is a great idea. The starting place is this community. I can investigate creating a shared document later today. We should include a brief description of the issue at hand.

James, thanks and you have made a valid point and a useful suggestion. Which entity would prepare a "standard list of potential risks"? Is this something ASCE could initiate?

Stephen,

The primer stated that using a standard or design code is a form of risk treatment. The question becomes, if those standards are out of date due to changes in climate, etc., what is the standard of care that an engineer should implement to modify those standards? If they do add a safety factor and it is wrong, are they then liable? I think that is when involving all of the participants in those discussions becomes important. An owner needs to understand the risks of staying with the standards and what might happen in the future. 

I think the design industry needs to develop a standard list of potential technical risks. Research can then be conducted to develop probability of occurrence and methodologies to calculate impacts. This would help firms that don't have the staff and/or sophistication to develop this information themselves.

Technical risk management has a significant impact on project viability and success. Technical risk is not afforded the attention it requires/ deserves both in terms of risk identification and weighting (probability and impact). The following is not a general criticism, but it is easy for the project and technical/ design team to pay lip service to technical risk "hoping" that the factors of safety etc will be a net for any potential technical risks. How do we ensure technical risks are adequately assessed and weighted and is this the role of the Engineers or Project Manager to facilitate this technical risk discussion?

Steve, building a list of technical risks is a great idea. The starting place is this community. I can investigate creating a shared document later today. We should include a brief description of the issue at hand.

James, thanks and you have made a valid point and a useful suggestion. Which entity would prepare a "standard list of potential risks"? Is this something ASCE could initiate?

Stephen,

The primer stated that using a standard or design code is a form of risk treatment. The question becomes, if those standards are out of date due to changes in climate, etc., what is the standard of care that an engineer should implement to modify those standards? If they do add a safety factor and it is wrong, are they then liable? I think that is when involving all of the participants in those discussions becomes important. An owner needs to understand the risks of staying with the standards and what might happen in the future. 

I think the design industry needs to develop a standard list of potential technical risks. Research can then be conducted to develop probability of occurrence and methodologies to calculate impacts. This would help firms that don't have the staff and/or sophistication to develop this information themselves.

Technical risk management has a significant impact on project viability and success. Technical risk is not afforded the attention it requires/ deserves both in terms of risk identification and weighting (probability and impact). The following is not a general criticism, but it is easy for the project and technical/ design team to pay lip service to technical risk "hoping" that the factors of safety etc will be a net for any potential technical risks. How do we ensure technical risks are adequately assessed and weighted and is this the role of the Engineers or Project Manager to facilitate this technical risk discussion?

I created a draft document. Please have a look, and let me know of any opportunities for improvement. Or better yet, implement your ideas.

Link to Risk Register

Steve, building a list of technical risks is a great idea. The starting place is this community. I can investigate creating a shared document later today. We should include a brief description of the issue at hand.

James, thanks and you have made a valid point and a useful suggestion. Which entity would prepare a "standard list of potential risks"? Is this something ASCE could initiate?

Stephen,

The primer stated that using a standard or design code is a form of risk treatment. The question becomes, if those standards are out of date due to changes in climate, etc., what is the standard of care that an engineer should implement to modify those standards? If they do add a safety factor and it is wrong, are they then liable? I think that is when involving all of the participants in those discussions becomes important. An owner needs to understand the risks of staying with the standards and what might happen in the future. 

I think the design industry needs to develop a standard list of potential technical risks. Research can then be conducted to develop probability of occurrence and methodologies to calculate impacts. This would help firms that don't have the staff and/or sophistication to develop this information themselves.

Technical risk management has a significant impact on project viability and success. Technical risk is not afforded the attention it requires/ deserves both in terms of risk identification and weighting (probability and impact). The following is not a general criticism, but it is easy for the project and technical/ design team to pay lip service to technical risk "hoping" that the factors of safety etc will be a net for any potential technical risks. How do we ensure technical risks are adequately assessed and weighted and is this the role of the Engineers or Project Manager to facilitate this technical risk discussion?

I created a draft document. Please have a look, and let me know of any opportunities for improvement. Or better yet, implement your ideas.

Link to Risk Register

Steve, building a list of technical risks is a great idea. The starting place is this community. I can investigate creating a shared document later today. We should include a brief description of the issue at hand.

James, thanks and you have made a valid point and a useful suggestion. Which entity would prepare a "standard list of potential risks"? Is this something ASCE could initiate?

Stephen,

The primer stated that using a standard or design code is a form of risk treatment. The question becomes, if those standards are out of date due to changes in climate, etc., what is the standard of care that an engineer should implement to modify those standards? If they do add a safety factor and it is wrong, are they then liable? I think that is when involving all of the participants in those discussions becomes important. An owner needs to understand the risks of staying with the standards and what might happen in the future. 

I think the design industry needs to develop a standard list of potential technical risks. Research can then be conducted to develop probability of occurrence and methodologies to calculate impacts. This would help firms that don't have the staff and/or sophistication to develop this information themselves.

Technical risk management has a significant impact on project viability and success. Technical risk is not afforded the attention it requires/ deserves both in terms of risk identification and weighting (probability and impact). The following is not a general criticism, but it is easy for the project and technical/ design team to pay lip service to technical risk "hoping" that the factors of safety etc will be a net for any potential technical risks. How do we ensure technical risks are adequately assessed and weighted and is this the role of the Engineers or Project Manager to facilitate this technical risk discussion?

I created a draft document. Please have a look, and let me know of any opportunities for improvement. Or better yet, implement your ideas.

Link to Risk Register

Steve, building a list of technical risks is a great idea. The starting place is this community. I can investigate creating a shared document later today. We should include a brief description of the issue at hand.

James, thanks and you have made a valid point and a useful suggestion. Which entity would prepare a "standard list of potential risks"? Is this something ASCE could initiate?

Stephen,

The primer stated that using a standard or design code is a form of risk treatment. The question becomes, if those standards are out of date due to changes in climate, etc., what is the standard of care that an engineer should implement to modify those standards? If they do add a safety factor and it is wrong, are they then liable? I think that is when involving all of the participants in those discussions becomes important. An owner needs to understand the risks of staying with the standards and what might happen in the future. 

I think the design industry needs to develop a standard list of potential technical risks. Research can then be conducted to develop probability of occurrence and methodologies to calculate impacts. This would help firms that don't have the staff and/or sophistication to develop this information themselves.

Technical risk management has a significant impact on project viability and success. Technical risk is not afforded the attention it requires/ deserves both in terms of risk identification and weighting (probability and impact). The following is not a general criticism, but it is easy for the project and technical/ design team to pay lip service to technical risk "hoping" that the factors of safety etc will be a net for any potential technical risks. How do we ensure technical risks are adequately assessed and weighted and is this the role of the Engineers or Project Manager to facilitate this technical risk discussion?