Key Takeaways
An SCDF-approved Emergency Response Plan (ERP) for a P&FM facility must connect regulatory duties with practical decisions made under pressure. The plan should be site-specific, tested through operations, and kept current for audits and renewal.
- Define the facility’s P&FM activities, approval conditions, and ERP boundaries.
- Base the hazard assessment on actual inventories, layouts, processes, and access constraints.
- Make command, alarms, evacuation, communications, and handover procedures easy to follow.
- Set clear CERT competencies, equipment needs, training requirements, and intervention limits.
- Treat drills, records, corrective actions, and management reviews as part of renewal readiness.
Establish the regulatory and operational basis for the ERP
A useful ERP begins with the facility as it actually operates, not with a generic emergency template. The document should connect P&FM activities, licence conditions, site constraints, and response expectations in one coherent framework. Early coordination between engineering, operations, and regulatory stakeholders prevents gaps that are difficult to correct later. For projects requiring coordinated design and regulatory work, Stellar Structures provides engineering, architectural, and interior design solutions alongside regulatory submissions and approvals.
Define the facility’s P&FM activities and approval conditions
Start by describing what the site receives, stores, processes, transfers, and dispatches. Record operating hours, occupancy, contractors, delivery movements, maintenance activities, and any temporary arrangements that could affect an emergency. Approval conditions should be read alongside operating procedures so the ERP reflects actual responsibilities rather than merely repeating licence language.
The scope should identify the buildings, rooms, tanks, warehouses, loading areas, utilities, and external yards covered by the plan. It should also state which activities are excluded and where another emergency procedure applies. That clarity helps the incident controller decide whether the ERP has been activated for a local event or a wider site emergency.
Identify applicable SCDF requirements, codes, and licence obligations
The regulatory review should identify the SCDF requirements, fire safety provisions, storage controls, licence obligations, and internal standards relevant to the facility. Keep a register showing the source, requirement, responsible owner, evidence location, and review date. This makes the ERP easier to defend during inspection and easier to revise when conditions change.
Avoid treating approval as a one-time administrative event. A change in inventory, process, layout, occupancy, or emergency equipment may affect the assumptions on which the approved arrangement was based. The plan owner should therefore confirm the approval pathway before implementing material changes.
Set ERP objectives, scope, assumptions, and activation criteria
The ERP should state what it is intended to achieve: protect life, raise the alarm, control escalation where safe, support evacuation or shelter, protect responders, and provide accurate information to SCDF and other agencies. It should define credible assumptions, including unavailable equipment, blocked access, power loss, reduced staffing, and poor visibility.
Activation criteria need to be observable. Examples include a confirmed fire, uncontrolled flammable vapour, a significant chemical release, a casualty, an alarm that cannot be verified promptly, or an event that crosses the site boundary. Clear criteria reduce hesitation and stop teams from waiting for perfect information.
Assign the plan owner and interfaces with external responders
Name the ERP owner, deputy, document controller, operations representative, and senior decision-maker. Their roles should remain clear across normal hours, nights, weekends, and contractor-heavy periods. The plan should also identify how information is passed to SCDF, police, medical services, landlords, neighbouring occupiers, and utility providers when relevant.
External interfaces should be practical rather than ceremonial. Confirm who meets responding agencies, who provides site plans and hazardous-material information, who controls access, and who records decisions. A short responsibility matrix can be more useful than several pages of broad statements.
Build a site-specific hazard and risk assessment
The hazard assessment is the working logic behind the ERP. It should show where an incident can begin, how it might spread, what people may be exposed to, and which controls can change the outcome. Site observations, current drawings, inventory data, and conversations with operators are more reliable than assumptions carried forward from an old project.
Map storage areas, process zones, utilities, and access routes
Prepare a current site plan showing P&FM storage, process equipment, transfer points, drains, electrical rooms, fire protection systems, isolation points, muster areas, access gates, hydrants, and emergency equipment. Mark routes for SCDF appliances and identify obstructions such as parked vehicles, security barriers, temporary works, or narrow turning areas.
The map should work in daylight and poor visibility. Use consistent symbols, provide a legend, and ensure the displayed information matches the physical site. Separate versions may be needed for responders, employees, contractors, and management if each group requires a different level of detail.
Assess fire, explosion, toxic release, and spill scenarios
Scenario assessment should consider initiating events, escalation paths, exposure zones, detection, ignition sources, drainage, weather, occupancy, and available controls. A small spill in a contained process area may require a different response from a release that reaches a drain or crosses a property boundary.
Write each scenario in operational terms. State what people may see or smell, which alarm may activate, who makes the first notification, what immediate actions are allowed, and what conditions require withdrawal. This turns risk analysis into instructions that can be used during a stressful event.
Account for inventories, incompatibilities, and credible worst cases
Inventory information must be current enough to support decisions. Record quantities, container types, storage locations, transfer arrangements, safety data, and incompatibilities. Consider mixed inventories and maintenance conditions, not only the largest individual container.
A credible worst case is not necessarily the most dramatic imaginable event. It is a severe event that could reasonably occur given the site’s equipment, staffing, processes, and safeguards. The assessment should explain the reasoning so that controls and response priorities can be reviewed later.
Translate risk findings into emergency controls and response priorities
Each significant scenario should lead to a defined control: isolation, ignition-source management, exclusion, evacuation, shelter, spill containment, fire protection, medical support, or early notification. Priorities should be ordered around life safety first, followed by preventing escalation and supporting responders.
A practical risk register can connect the hazard to the action without overwhelming the user. Keep the response column specific enough for a trained person to act, while reserving technical intervention for personnel with the required competence.
| Scenario | Immediate priority | Key information | Escalation trigger |
|---|---|---|---|
| Fire or explosion | Raise alarm and withdraw from danger | Location, material, persons exposed | Fire spread, blast damage, or casualties |
| Flammable vapour release | Remove ignition sources if safe and isolate area | Release source, wind, affected zones | Vapour migration or uncontrolled release |
| Toxic release | Protect people and move or shelter as directed | Substance, symptoms, wind direction | Exposure beyond controlled area |
| Chemical spill | Stop source if safe and prevent spread | Quantity, compatibility, drainage path | Entry into drains or off-site migration |
The register should sit beside, not replace, the full procedures. Operators need enough context to understand when a listed action is unsafe or when the incident must be handed to SCDF.
Structure the ERP for fast decision-making
An ERP is read during noise, uncertainty, and interruption. Its structure should help a person find the next decision quickly, even if that person is not the usual supervisor. Use consistent terminology, short action statements, clear diagrams, and controlled document versions. The design should support both immediate response and later reconstruction of what happened.
Create the incident command structure and reporting lines
Define the incident controller and the functions supporting that role, such as operations, evacuation, communications, first aid, access control, utilities, and logistics. Show who assumes command if the nominated person is absent. Reporting lines should distinguish decisions from updates so that the controller is not buried in unnecessary detail.
The structure should work with contractors and shift teams. A contractor supervisor may control workers within a task area, but the ERP must state how that supervisor reports into the site command structure. This avoids parallel instructions during evacuation or isolation.
Define alarm levels, escalation thresholds, and notification procedures
Alarm levels should correspond to clear conditions and actions. Describe who can initiate an alarm, how it is acknowledged, when the incident controller is notified, and when external agencies are called. Include arrangements for alarm failure, false alarms, and events discovered by a person rather than an automatic system.
Notification messages should contain the facility name, precise location, substance involved, known hazards, casualties, access point, and callback details. A prepared script can reduce omissions, but staff must also know how to communicate when information is incomplete.
Document evacuation, shelter-in-place, and accountability arrangements
The plan should state when evacuation is preferred and when shelter-in-place may be safer. Show primary and alternate routes, muster points, refuge areas, mobility assistance, visitor control, and arrangements for people working alone. Accountability should use current personnel and visitor information rather than an assumed headcount.
Supervisors should report missing, injured, or unaccounted persons promptly. No one should re-enter to search unless authorised and properly equipped. The ERP must make that boundary unmistakable.
Include site plans, equipment locations, and emergency contact details
Insert readable plans close to the procedures that use them. Identify fire extinguishers, hose reels, hydrants, spill kits, first-aid equipment, emergency showers, eye-wash stations, isolation points, gas shutoffs, electrical controls, and access gates. Contact details need owners and review dates, not just names copied from an old directory.
Keep critical information available if the normal network or power supply fails. Printed copies, controlled electronic copies, and responder packs should be checked for consistency during document reviews.
Specify communication protocols during degraded or high-stress conditions
Noise, smoke, damaged equipment, language differences, and overloaded telephone networks can all distort messages. Set primary and backup channels, call signs where useful, message confirmation rules, and a method for logging major decisions. Avoid long codes that staff cannot recall under pressure.
Communication should also address rumours and unauthorised updates. One designated information function can coordinate internal notices, while the incident controller retains authority over operational instructions. This separation keeps messages concise without compromising command.
Develop response procedures for P&FM emergencies
Response procedures should guide safe early actions while recognising that many P&FM incidents quickly exceed site capability. They should not encourage improvised firefighting, entry into contaminated areas, or isolation work by unqualified personnel. Each procedure needs a clear point at which people withdraw, escalate, and wait for specialist responders.
Respond to fires, explosions, and flammable vapour releases
For fire or explosion, the first actions are alarm, notification, withdrawal, accountability, and protection of access for responders. The procedure should identify when trained personnel may use installed or portable firefighting equipment and when they must not approach. Flammable vapour releases require attention to ignition sources, wind direction, exclusion zones, and the possibility of delayed ignition.
Do not assume that visible flames define the full hazard area. Vapour movement, damaged containers, heat exposure, and compromised structures may create risks beyond the original location. The ERP should direct staff to provide observations to SCDF without sending people back into danger.
Control chemical spills, leaks, and incompatible-material incidents
Spill procedures should distinguish between a minor, controlled release and an incident requiring immediate isolation and external response. State how to raise the alarm, keep people away, protect drains when safe, consult chemical information, and select suitable containment equipment. Compatibility must be considered before combining absorbents, transferring material, or applying water.
The person discovering a leak should not be expected to identify every chemical from memory. Container labels, inventory records, safety data, and information provided to responders should support the decision. If the substance, quantity, or reaction is uncertain, the procedure should default to withdrawal and escalation.
Manage isolation of equipment, utilities, and P&FM sources
Isolation steps should be written for each relevant system, with the control location, responsible role, verification method, and restrictions clearly stated. Include process equipment, pumps, valves, electrical supplies, gas systems, ventilation, and transfer connections where they affect the hazard. Isolation should never be attempted from an unsafe position.
The ERP should distinguish emergency shutdown from full de-energisation and explain who may authorise each action. A record of the isolation status helps prevent conflicting work and gives responding agencies a clearer picture when they arrive.
Coordinate first aid, casualty handling, and medical evacuation
First-aid arrangements should cover burns, inhalation, eye exposure, chemical contact, trauma, and contamination concerns as relevant to the inventory. State where casualties are moved, who provides initial care, how contaminated clothing is handled, and when medical services are called. The plan should also protect first-aiders from secondary exposure.
A casualty count and basic condition report should be passed to the incident controller and medical responders. Do not delay evacuation while trying to complete a perfect assessment; provide the best available information and update it as facts are confirmed.
Establish handover procedures for SCDF and other responding agencies
When SCDF or another agency takes operational control, the site team should provide a concise briefing: what happened, what materials are present, what actions have been taken, who is missing or injured, which systems are isolated, and what hazards remain. Assign one knowledgeable liaison to support questions and site access.
The handover should be recorded, but documentation must not distract from the response. After the immediate danger has passed, preserve relevant logs, access records, photographs, samples where authorised, and equipment status for investigation and recovery.
Design and implement the CERT setup
A CERT arrangement should be matched to the facility’s hazards, operating pattern, and available manpower. It is not simply a list of volunteers or a collection of equipment. The setup must show what the team can do safely before SCDF arrives, what it cannot do, and how it remains available across shifts and leave periods.
Determine CERT roles, competencies, and minimum manpower needs
Define roles such as team leader, fire response, spill control, first aid, rescue support, communications, and accountability support according to the site’s risk profile. Each role should have a competency statement rather than a vague expectation to “assist.” Minimum manpower should account for simultaneous tasks, rest, supervision, and the possibility that some members are unavailable.
Competency requirements should reflect the materials and equipment actually present. A person trained for general awareness should not be treated as qualified for a higher-risk intervention. The ERP should show how competence is confirmed and recorded.
Define team organisation, appointment criteria, and duty coverage
Set appointment criteria covering fitness for the role, training completion, reliability, communication ability, and willingness to follow withdrawal instructions. Identify team leaders and deputies for each shift. Contractors may support the arrangement, but responsibilities and supervision must remain clear.
A duty roster should show coverage during normal operations, overtime, shutdowns, public holidays, and contractor activities. If minimum coverage is unavailable, the site should know which operations must be restricted or which compensating controls apply.
Select PPE, firefighting, spill-control, rescue, and communications equipment
Equipment selection should follow the hazard assessment and the manufacturer’s instructions. Check suitability for chemical exposure, heat, vapour, visibility, respiratory risk, and rescue conditions. Locate equipment so it is accessible without requiring personnel to pass through the hazard area.
Inspection and replacement arrangements matter as much as procurement. Record the custodian, inspection frequency, expiry dates, charging requirements, and defects. Equipment that cannot be found, opened, or safely used should not be counted as an effective control.
Set training, competency assessment, and refresher requirements
The training programme should combine instruction, practical exercises, scenario decisions, equipment use, communications, and post-incident learning. Assess people against defined tasks, not merely attendance. Refresher intervals should reflect regulatory requirements, operational changes, and observed performance.
Keep records of attendance, assessment results, expiry dates, restrictions, and remedial actions. Training records become especially useful when staffing changes or a renewal review requires evidence that the CERT remains capable.
Establish CERT limits to prevent unsafe intervention
The ERP must state when CERT members withdraw and wait for SCDF or other specialists. Triggers may include escalating fire, unknown substances, suspected structural damage, toxic atmosphere, loss of communications, inadequate PPE, or conditions beyond the team’s training. The team leader should have authority to stop an intervention.
A strong CERT is not measured by how often members enter danger. It is measured by disciplined alarm raising, early control where safe, effective evacuation support, accurate information, and a timely handover. Those limits should be reinforced in every drill.
Validate the ERP through drills and site operations
A plan becomes credible when people can use it during realistic site conditions. Drills should test decisions and coordination, not just whether an alarm sounds. Include shift workers, contractors, security personnel, supervisors, and managers where their actions affect the outcome.
Build drill scenarios from the facility’s highest-consequence risks
Choose scenarios from the hazard assessment rather than repeating a convenient exercise. Vary the location, time, staffing, access route, weather assumptions, and initial information. Scenarios may involve a delayed discovery, an unavailable supervisor, a blocked route, a missing contractor, or a simultaneous equipment fault.
The scenario should have defined objectives and safety controls. Participants can be tested without exposing anyone to actual hazardous material or uncontrolled conditions. Observers should understand the expected actions before the exercise starts.
Test alarm activation, evacuation, communications, and accountability
Test the full chain from discovery to alarm, notification, movement, muster, headcount, and escalation. Measure whether people hear the alarm, understand it, use the correct route, and report accountability information. Include visitors and contractors rather than assuming they will follow employee routines.
After the exercise, compare actual performance with the ERP. A slow headcount may reveal an outdated roster, while unclear instructions may point to a document or signage problem rather than an individual failure.
Exercise CERT deployment and coordination with contractors
CERT drills should examine mobilisation, role allocation, equipment retrieval, communications, exclusion zones, and coordination with contractors. Observers should note whether the team stays within its limits and whether the incident controller receives useful information quickly.
Contractors should know who gives them instructions and how their own supervisors fit into the site command structure. This is particularly important during maintenance, construction, tank cleaning, and other periods when the normal organisation may be disrupted.
Record observations, response times, and corrective actions
Use a structured observation record covering alarm time, notification time, mobilisation, evacuation, accountability, isolation, communications, and handover. Record facts rather than general impressions. Each finding should identify an owner, due date, risk priority, and evidence needed for closeout.
A review of operations audit priorities can provide a useful general lens for sorting process, people, technology, data, and control weaknesses, although the ERP findings must remain specific to the P&FM facility. The value lies in turning observations into assigned work.
Protect business continuity while maintaining emergency controls
Emergency preparedness should not be tested by creating avoidable operational risk. Coordinate drills with production, deliveries, maintenance, neighbours, and security, and define stop criteria for changing weather, real incidents, or unsafe conditions. Where a full exercise is impractical, use focused tabletop sessions alongside physical tests.
Business continuity arrangements should identify essential functions, safe restart conditions, delegated authority, and records that must be preserved. Continuity never overrides evacuation, isolation, responder access, or other immediate emergency controls.
Manage audits, revisions, and ERP renewal readiness
Site Operations, Audits, & Renewal should be treated as one continuing management cycle. Audits reveal whether the ERP exists in practice, while operations expose weaknesses that paperwork may miss. Renewal readiness is therefore built through ordinary inspections, training, drills, change control, and timely corrective action—not a last-minute document rewrite.
Maintain inspection, maintenance, training, and drill records
Keep a controlled record set for fire protection systems, alarms, emergency lighting, spill equipment, PPE, isolation devices, first-aid supplies, training, competency assessments, drills, and incidents. Each record should show the date, asset or activity, person responsible, result, defect, and follow-up.
Records should be legible, retrievable, and linked to the relevant procedure. The financial and performance audits page illustrates how formal review processes may connect evidence with performance and renewal considerations, though P&FM facilities must apply the requirements relevant to their own approvals and operations.
Prepare evidence for SCDF inspections and internal audits
Prepare an evidence index so an inspector or auditor can move from an ERP statement to the supporting record. Include current plans, approvals, licences, inventories, training records, equipment inspections, drill reports, incident logs, and corrective-action closeouts. Do not rely on a single person’s memory to explain how the system works.
Internal audits should sample actual conditions. Walk the routes, open the cabinets, check the equipment, speak with shift staff, and compare posted information with controlled documents. Published audit findings and recommendations also demonstrate the value of documenting what was reviewed and what action followed, even though that material concerns a different operating context.
Track corrective actions, ownership, deadlines, and closeout evidence
Every finding should have a clear owner and a realistic deadline. High-risk issues may require immediate compensating controls, restricted operations, or management escalation while a permanent fix is arranged. Closeout should include evidence such as a revised drawing, maintenance record, training assessment, photograph, test result, or approval correspondence.
A corrective-action register is most useful when it distinguishes overdue work from accepted residual risk. Management should be able to see recurring findings, weak controls, and actions that depend on capital work or external approvals.
Update the ERP after process, inventory, staffing, or layout changes
Use formal change control to review the ERP whenever materials, quantities, processes, equipment, staffing, contractors, building layout, access routes, fire systems, or operating hours change. Reassess the hazard, update drawings and contacts, brief affected personnel, and determine whether regulatory notification or approval is required.
Document the reason for each revision and identify the sections changed. A plan that still names departed staff or shows a removed storage area can fail at precisely the moment it is needed.
Schedule management reviews and plan ahead for renewal submissions
Set a review calendar tied to inspections, drills, incidents, changes, audit findings, and renewal dates. Management review should consider whether the ERP remains suitable, whether CERT coverage is adequate, whether actions are closed, and whether site conditions still match approvals.
Begin renewal preparation early enough to resolve evidence gaps, obtain updated drawings, confirm responsible personnel, and coordinate required submissions. Stellar Structures can support clients through its integrated engineering, architectural, and regulatory submission work when project changes require coordinated design and approval input. A disciplined review cycle leaves the facility prepared rather than rushed.
Conclusion
An SCDF-approved ERP for a P&FM facility should be a living operating document: grounded in the site, usable under pressure, tested with the people who must act, and supported by records that withstand inspection. When hazards, command arrangements, CERT limits, drills, corrective actions, and renewal planning are managed together, the plan becomes a practical control for both emergency response and responsible site operations.
Frequently Asked Questions
What is an ERP for a P&FM facility?
It is a documented emergency arrangement covering hazards, alarms, command, evacuation or shelter, response actions, communications, casualty management, and coordination with SCDF and other responding agencies.
What should be included in a site-specific hazard assessment?
It should address actual inventories, incompatibilities, storage and process areas, utilities, access routes, ignition sources, drainage, occupancy, credible scenarios, safeguards, escalation paths, and response priorities.
When should an ERP be activated?
Activation should follow defined, observable criteria such as fire, explosion, uncontrolled vapour or chemical release, casualty, alarm uncertainty, or an event that may affect people or areas beyond the immediate work zone.
What is the purpose of a CERT?
A CERT provides trained site personnel who can raise alarms, support evacuation and accountability, perform defined early controls where safe, provide information, and coordinate a disciplined handover to responding agencies.
How often should an ERP be reviewed?
Review it on a planned schedule and after drills, incidents, audits, regulatory changes, process or inventory changes, staffing changes, layout changes, and changes to emergency equipment or access.
What records support ERP audits and renewal?
Useful evidence includes approvals, licences, current plans, inventories, inspection and maintenance records, training and competency records, drill reports, incident logs, corrective-action records, and management reviews.
Can business continuity take priority during an emergency?
No. Life safety, evacuation, isolation, responder access, and safe emergency controls take priority. Continuity planning should address safe restart and recovery only after immediate hazards are controlled.