AS 3745-2010 Planning for Emergencies in Facilities
Section 3: Emergency plan – AS 3745-2010 Planning for Emergencies in Facilities

AS 3745-2010 Planning for Emergencies in Facilities 3.1-3.4: Develop a facility emergency plan from an analysis of the emergencies that could occur

Every facility needs a written emergency plan that is built and kept up to date. It records how the organisation, its systems and its tactics respond to emergencies, and covers prevention, preparedness, mitigation, preparing and preventing activities such as training and maintenance, overall control and coordination (including evacuation strategies for occupants with disability) and the agreed parts played by the wardens' organization and by occupants. Potential emergencies for each facility must be identified and analysed from internal, external and neighbouring sources (for example fire, flood, bomb threat, medical emergency, hazardous substances and severe weather), including the consequences and the vulnerability of people, and the EPC then decides which types need specific procedures; the facility's scale and intricacy, its engineered fire or life safety features, security arrangements, how many people use it and who they are, and when it is occupied must all be weighed. The plan must contain a purpose and scope statement, the committee's structure and purpose, the facilities covered, fire safety and emergency features, organisational arrangements, separate sections for the emergency identification outcomes, response procedures, evacuation diagram and training, a distribution statement and record (including where personal emergency evacuation plans are held), hours of occupancy, the validity period, and an issue or amendment date on every page; if the plan is electronic, one printed copy must be on site.

Maintained by Gerard Blokdyk

Other controls in Section 3: Emergency plan – AS 3745-2010 Planning for Emergencies in Facilities

Query this from an agent

The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.