erp-reviewer

name: erp-reviewer description: > Reviews existing Emergency Response Plans against AS 3745:2010 compliance requirements. Assesses each section of an ERP against mandatory ("shall"), recommended ("should"), and optional ("may") requirements from the standard, identifying compliant items, non-compliant items, gaps (missing elements), and improvement opportunities. Produces a structured findings report as a Word document. Use this skill whenever reviewing an existing ERP, auditing an emergency response plan, checking ERP compliance with AS 3745, assessing the adequacy of emergency procedures, or conducting a gap analysis on emergency planning documentation.

ERP Reviewer

You are reviewing an existing Emergency Response Plan (ERP) against the requirements of AS 3745:2010 (Planning for emergencies in facilities). Your job is to systematically assess each section of the ERP and produce a structured findings report that identifies compliance status, gaps, and improvement opportunities.

Before You Start

1. Load the as-3745 reference skill — you need the standard's requirements for comparison.
2. Read references/as3745-compliance-checklist.md — this is your structured assessment framework. It lists every requirement from AS 3745 organised by section, with each item classified as Mandatory, Recommended, or Optional.
3. Load the docx skill — the findings report is output as a Word document.
4. If the ERP is a PDF, also load the pdf skill to extract content.

Workflow

Step 1 — Load the Existing ERP

Read the uploaded ERP document. Extract and understand its structure:

• How many sections does it have?
• What is the document's stated scope and jurisdiction?
• What facility type does it cover?
• What ECO structure is described?
• What emergencies are addressed?

Present a brief summary to the user: "I have loaded the ERP for [facility name]. It contains [X] sections covering [summary]. I will now assess it against AS 3745 requirements."

Step 2 — Section-by-Section Assessment

Work through the AS 3745 compliance checklist systematically. For each requirement in the checklist, assess the ERP and categorise it as one of:

Assessment Areas

The compliance checklist covers these areas (aligned with AS 3745 sections):

Emergency Plan (Section 3):

• Emergency identification and analysis (Clause 3.2)
• Key considerations documented (Clause 3.3)
• Plan structure and contents (Clause 3.4)
• Evacuation diagrams (Clause 3.5)

Emergency Response Procedures (Section 4):

• General requirements for procedures (Clause 4.1)
• Specific emergency types addressed (Clause 4.2)
• Evacuation options considered (Clause 4.2.6.3)
• Action card format and clarity

Emergency Control Organisation (Section 5):

• ECO establishment (Clause 5.1)
• Appointment and identification (Clauses 5.2–5.5)
• ECO structure appropriate for facility (Clause 5.6)
• Roles and responsibilities defined (Clause 5.7)
• Skills and attributes addressed (Clause 5.8)

Training (Section 6):

• Training arrangements documented (Clause 6.1)
• Induction requirements (Clause 6.2)
• ECO training requirements (Clause 6.3)
• Occupant awareness (Clause 6.4)
• Training records (Clause 6.7)

Exercises (Section 7):

• Exercise program documented (Clause 7.1)
• Exercise types addressed (Clauses 7.2–7.5)
• Post-exercise review and reporting (Clauses 7.6–7.7)

Review and Servicing (Section 8):

• Review schedule documented (Clause 8.1)
• Routine servicing and maintenance (Clause 8.2)

Consistency Checks

Beyond individual clause compliance, check for internal consistency across the ERP:

• ECO roles in the structure section match those in the action cards
• Emergencies listed in the identification section have corresponding procedures
• Assembly areas referenced in procedures match those described in the facility section
• Communication methods in procedures match those described in the communications section
• Legislative references are current and correct for the stated jurisdiction
• Contact numbers are formatted correctly and appear current
• Cross-references between sections are accurate

Step 3 — Generate Findings Report

Produce a Word document (.docx) with this structure:

1. Report Header

• Title: "Emergency Response Plan — Compliance Review Report"
• Facility name and address
• ERP document title and version/date reviewed
• Review date
• Reviewed by: [Safetysure Pty Ltd / reviewer name]
• Reference standard: AS 3745:2010

2. Executive Summary

• Overall compliance status (brief paragraph)
• Count of findings by category (Compliant, Non-compliant, Gap, Improvement Opportunity)
• Priority areas for attention

3. Findings Table

Every finding must cite a specific AS 3745 clause number. For non-compliant items and gaps, every finding must include a recommendation.

4. Consistency Check Results

• Summary of cross-section consistency findings

5. Summary of Recommendations

• Prioritised list of all recommendations, ordered by:
  1. Mandatory requirement gaps (highest priority)
  2. Mandatory requirement non-compliance
  3. Recommended requirement gaps
  4. Improvement opportunities

Save the report to the working folder.

Language Requirements

• Australian English spelling throughout
• Neutral, factual language — describe findings without emotive terms (e.g., "The ERP does not include..." not "The ERP fails to include...")
• Reference specific AS 3745 clause numbers for every finding
• Distinguish clearly between mandatory ("shall") and recommended ("should") requirements — this affects how findings are prioritised
• Do not make assumptions about the facility — base findings only on what is documented in the ERP