erp-emergency-assessment

Emergency Identification and Assessment

You are conducting an emergency identification and analysis for a facility per AS 3745:2010 Clause 3.2. This assessment identifies all foreseeable emergencies — both from facility operations (internal) and from the facility's geographic location and surroundings (external) — and organises them for use in an Emergency Response Plan.

The assessment produces two distinct outputs that serve different purposes:

• Appendix G — a complete register of every individual risk, ungrouped, for reference and completeness
• Grouped emergency types — practical groupings that drive the emergency response procedures in Section 17

Before You Start

1. Load the erp-emergency-library skill — read its SKILL.md to understand the available industry scenario baselines.
2. Load the as-3745 reference skill — you will need Clause 3.2 for the emergency identification methodology.
3. Read references/research-checklist.md — this is your structured checklist for location-based research. You work through every item on this checklist for every assessment.
4. Read references/assessment-output-format.md — this defines the exact table structures for your outputs.

Minimum Required Inputs

Before starting the assessment, confirm you have:

1. Facility address (street address, suburb, state, postcode) — needed for all location-based research
2. Industry/site type — needed to load the correct scenario baseline from the emergency library
3. Basic facility information — hazardous materials present, key processes, plant and equipment, building characteristics

These can come from an intake form JSON, site tool data, or conversational input from the user.

---

Assessment Workflow

Work through these steps in sequence. Each step builds on the previous one.

Step 1 — Load Industry Scenario Baseline

Read the appropriate industry scenario file from the erp-emergency-library skill's scenarios/ directory based on the facility type. Also read scenarios/common-all-facilities.md — these universal emergencies apply to every site.

The scenario files provide a starting list of foreseeable emergencies with pre-written consequence and vulnerability descriptions. These are baselines — you will add to them based on research and facility-specific information.

Step 2 — Research External Hazards

This is the research-driven step. Using the facility address and region, conduct web searches to identify external hazards specific to the location.

Work through every item on references/research-checklist.md. Mark each item as applicable or not applicable with a brief rationale. For applicable items, record your findings.

The research checklist covers:

Natural hazards:

• Flood risk — state flood mapping portals, council flood studies
• Bushfire prone area — state BPA maps, council overlays
• Cyclone zone — BoM cyclone data, building code wind regions
• Earthquake hazard — Geoscience Australia hazard maps
• Severe weather frequency — BoM climatology, historical events
• Storm surge / coastal inundation — coastal hazard maps (coastal facilities only)
• Landslide / subsidence — geological mapping (hilly terrain, mining areas)

External / neighbouring hazards:

• Major hazard facilities nearby — state MHF registers, EPA records
• Dangerous goods transport routes — road, rail, pipeline mapping
• Industrial neighbour profiles — aerial imagery, business directories
• High-voltage transmission proximity — network provider mapping
• Gas main / pipeline proximity — network provider mapping

Research quality rules:

• Source every finding with a URL, publication name, or map reference
• Record the risk level or classification where available (e.g., "1 in 100 year ARI, depth 0.5–1.0 m")
• If data is unavailable for a research item, state this explicitly — do not estimate or fabricate
• Note the date of the data source where possible
• For items not applicable to the region, briefly state why (e.g., "Cyclone zone: Not applicable — facility is in Melbourne, south of the cyclone risk zone")

Step 3 — Identify Internal Hazards

Review the facility data (intake form, site tool data, or user-provided information) to identify internal hazards beyond the industry baseline. The research checklist includes triggers for common site-specific hazards:

Trigger from Intake Data	Emergency to Consider
DG Class 3 chemicals listed	Flammable/combustible liquid fire or spill
Any hazardous chemicals listed	Chemical spill / toxic release
Combustible dust processes	Dust explosion
Compressed gas systems	Compressed gas failure / leak
Confined spaces identified	Confined space emergency
Multi-level or elevated work	Working at height rescue
High-voltage equipment, switchrooms	Electrical incident / arc flash
LPG or natural gas on site	Gas leak, gas fire/explosion
Forklifts or mobile plant	Vehicle/plant incident

Step 4 — Present Combined Hazard List

Compile all identified emergencies from Steps 1–3 into a single list, organised by the three AS 3745 categories:

1. Human-caused — bomb threat, armed intrusion, personal threat, civil disorder, medical emergency, arson, explosion, suspect object, workplace violence
2. Natural — bushfire, cyclone, earthquake, fire and smoke, flood, severe weather, storm surge, heatwave
3. Technological — hazardous substance incidents, industrial/plant incidents, structural instability, transport incidents, toxic emissions, utility failure

Present this list to the user and ask them to:

• Confirm the hazards are appropriate for their site
• Add any hazards you may have missed (site-specific knowledge)
• Remove any hazards that are genuinely not foreseeable for this facility
• Flag any hazards they want to emphasise or de-emphasise

Wait for user confirmation before proceeding.

Step 5 — Consequence and Vulnerability Assessment

For each confirmed emergency, assess:

Column	Description
Source	Internal, External, or Both
Consequences	Potential outcomes for people within the facility
Vulnerability Before	Factors that increase likelihood or severity before the event
Vulnerability During	Factors that affect response capability during the event
Vulnerability After	Factors that affect recovery after the event

Use conservative, factual language. Describe specific, observable consequences — not vague generalities. Draw on the industry scenario library's pre-written descriptions as a starting point, then adapt to the specific facility.

Step 6 — Generate Appendix G

Produce the full emergency identification register. Every individual risk gets its own row — do not group or consolidate at this stage. Number each item sequentially.

Appendix G table format:

No.	Risk	Source	Consequences	Vulnerability Before	Vulnerability During	Vulnerability After

See references/assessment-output-format.md for the complete table structure and example entries.

Step 7 — Propose Risk Groupings

Group the Appendix G items into practical response categories for Section 17 procedures. The grouping logic:

• Emergencies sharing the same primary response actions and evacuation strategy are grouped together
• Each group produces one emergency response procedure
• The Appendix G item numbers cross-reference to the procedure group

Grouping table format:

Procedure Group	Appendix G Items	Colour Code	Primary Strategy

Present the proposed groupings to the user. Explain the rationale: Appendix G lists all individual risks for completeness, while Section 17 uses grouped procedures for usability — workers need practical response steps, not 27 separate procedures.

Wait for user confirmation or adjustments.

Step 8 — Generate Section 16 and Grouping Map

Produce two outputs:

1. Section 16 — Types of Emergencies summary table: Lists the grouped emergency types with colour codes and cross-references to Appendix G item numbers. This goes into the ERP document.

2. Grouping map (internal reference): Links each Appendix G item to its Section 17 procedure group. This is used by the erp-developer skill in Phase 4 when generating procedures — it does not appear in the final document.

---

Output Format

When invoked as part of the full ERP workflow (/erp-develop Phase 3), the outputs feed directly into the ERP document sections.

When invoked standalone (/erp-assess), produce a Word document (.docx) containing:

1. Title page — "Emergency Identification and Assessment Report" with facility name, address, date
2. Research summary — Key findings from location-based research, with source references for every finding
3. Appendix G table — Complete emergency identification register
4. Grouping map — How individual items map to procedure groups
5. Section 16 table — Grouped emergency types
6. Recommendations — Additional considerations for the ERP (e.g., "Site is in a 1:100 ARI flood zone — consider flood-specific evacuation route that avoids low-lying car park")

Save the document to the working folder using the docx skill.

---

Language Requirements

• Australian English spelling throughout
• Conservative, factual language for risk descriptions — no emotive or speculative terms
• Source all external hazard data with verifiable references (URLs, publication names, map references)
• Do not fabricate or estimate risk levels — if data is unavailable, state this explicitly
• Use the three AS 3745 categories (Human, Natural, Technological) consistently