Logging and Managing General Hazards

Introduction

This guide covers the lifecycle of a General Hazard, from initial logging to final resolution. This form is used for hazards identified directly, not those originating from a Risk Assessment.

Logging a New General Hazard

1. Navigate to the Hazard module.
2. Select 'New Record' (ensure "Hazards" or the general hazard form is selected if a choice is available).

Key Initial Fields

• Accountable*: The person responsible for the hazard's management. This individual typically receives notifications and drives the hazard to resolution.
• Reporting Person*: Defaults to you; change if logging for someone else.
• Date Reported*: Defaults to today; ensure it reflects the actual reporting date (cannot be a future date).
• Brief Description*: A concise summary for lists and notifications.
• Details*: Full description of the hazard.
• Temporary Controls: Any immediate actions taken.
• Type (Hazard Classification): Select from a pre-defined list (e.g., "Fall from Height").
• Stakeholders: Individuals/groups to be notified of progress or comments.
• Treatment Due Date*: Target for resolving the hazard; crucial for 'Overdue' status tracking.
• Initial Risk Rating: Assess risk before controls using the Risk Matrix.

Once completed, Submit the form (or use the equivalent button that moves it to an 'Open' status). Saving as 'Draft' will not yet assign it or trigger notifications.

Analyzing, Controlling, and Updating Status

Once a hazard is 'Open', the Accountable Person takes over.

Key Fields for Analysis and Control

• Control Strategy: Select control types from the hierarchy (e.g., Elimination, Engineering).
• Controls*: Detail the specific permanent controls implemented or planned.
• Residual Risk Rating*: After planning/implementing controls, reassess the risk using the Risk Matrix. This determines if the risk is reduced to an acceptable level (e.g., ALARP).
• Associated Actions: Link or create new actions in the Actions module to manage specific tasks for controlling the hazard. Refer to "Actions Management" documentation for details on managing actions.
• Next Review Date: Set for hazards requiring ongoing monitoring (especially if 'ALARP').

Updating Hazard Status

After analysis and control implementation:

• Save as Eliminated: If the hazard is completely removed.
• Save as ALARP (As Low As Reasonably Practicable): If risk is reduced to the lowest practical level but not eliminated. Ensure 'Next Review Date' is set if ongoing monitoring is required.
• The system may automatically move hazards to 'Overdue' if the 'Treatment Due Date' passes. From 'Overdue', you can then move to 'Eliminated', 'ALARP', or 'Open' (after updating the due date).
• Re-open: If an 'Eliminated' or 'ALARP' hazard needs further attention.

Refer to the "Hazard Module Workflows and Notifications" document for more details on status changes and automated alerts.