An emergency response plan is a manual that companies use to address many different types of emergencies.
The manuals include:
The priorities for any ERP are, in this order:
ERPs should address only the highest-risk situations. They are critical for high-quality responsive risk management. You might call an “emergency response plan” a “catastrophic situation plan.”
The first thing you need to do to create an ERP is identify what your emergencies are. In this case, an emergency is simply a high-risk situation. You can ascertain which situations are high risk by:
Performing a risk assessment is an important step because it’s how you will distinguish emergencies from non-emergencies. Being able to perform the above two steps requires that you have:
If you have not already completed these tasks, you will need to do so before creating your ERP.
Based on your risk assessments, you will need to separate all high-severity risks. High severity risks are based on assessments that have a severity score that is equivalent to “catastrophic,” such as:
These risks will be considered emergencies and should be incorporated into your Emergency Response Plan. As such, they should be noted in a separate list. Some examples could be:
This list could be quite extensive and will most likely include a diverse set of risks.
Once you have your list of emergencies, you need to organize them into logical sections. For example, the following emergencies could be organized into a “Technology” section in your ERP:
Likewise, you might organize various fire-related situations into a “Fire” section in your ERP. There is no right or wrong way to organize this list, so long as it makes sense internally and would be easy for a stranger to quickly and easily find desired emergencies.
Once you have your list of emergencies organized, it’s time to start actually creating your ERP. This involves the following:
Part 4 is something that many ERPs lack, but each role in your company must know what their role is in responding to the emergency. For example:
Responsibilities will and SHOULD change depending on the type of emergency.
In tandem with each role knowing their responsibilities in a given emergency, you should also document a list of steps each role should follow in order to respond to a given emergency. These steps should help mitigate the emergency.
These steps should include:
Each role should have no question about how they should respond to an emergency after you list these steps.
As in the case of listing steps for how to respond to an emergency, you should also list a set of steps for how to recover from an emergency once the emergency has passed. These steps should help each role understand:
Complete ERPs will include a list of resources for each emergency that will help respond and recover from the emergency. For example, in the case of a fire, helpful resources would be:
Obviously, your list of resources should be much more extensive than this, but it gives you an idea. The goal here is to provide enough resources to be very helpful, but not so many resources that employees are “overwhelmed” during an emergency.
You must test your Emergency Response Plan with emergency drills. Emergency drills allow you to ensure that your ERP works as expected. The last thing you want to do is find out during an emergency that you have documented;
Performing several emergency drills will give you an opportunity to identify shortcomings and areas of strength in your ERP.
Last updated August 2024.