Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 18 Next »

 Lead the WASH Emergency Preparedness Plan (ERP)

Form an ERP Task force

This step consists in identifying key WASH stakeholders interested and capable to be involved in the process and create a dedicated group of partners, representative but small enough to be efficient. Engage with other actors and local communities during the process when relevant.

Risks analysis and scenario building

ERP can be defined as a process to manage risk. risk must be listed and prioritized based on their likelihood and planned impact on human life. Basic scenarios should be built to anticipate on the evolution of the context after a disaster, what will be the impact on the humanitarian situation and on the aid operations.

Develop the emergency WASH response strategy

Based on the most likely risks identified and the scenario, propose a strategy to respond to the WASH needs of the affected population.

Assessing core capacities and gaps

To mitigate and respond to the risks and needs identified in the scenarios, an ideal level of capacity is needed from the WASH sector (NGOs, local authorities, local population etc.). The level of capacity of these stakeholders may not be sufficient, and capacity gaps are observed. Assess capacities to identify gaps.

Develop the ERP plan

Capacities and capacity gaps were identified in the previous step. The ERP plan must propose a vision shared by most partners on of how to decrease the gaps identified and strengthen the sector. Actions to be taken are grouped in two categories:
  • Minimum Preparedness Actions (MPA): to be systematically implemented
  • Advanced Preparedness Actions and contingency planning: to be implemented only when risk has become very likely

Monitor and evaluate the ERP plan

WASH coordination platform monitors the implementation of preparedness actions by partners, advocate in case delays or gaps are observed, regularly update the ERP. After an emergency, the ERP must be reviewed to understand what worked and what didn’t, and improve it.

  • No labels