What can we help you with?

The Safety Observations Module

Safety Observations are documented to identify safe and unsafe behaviours and potential hazards in the workplace. Reporting safety observations helps prevent accidents in the workplace and helps to ensure compliance.

Documenting Safety Observations – Safety Observation Initial Report (Stage 1)

When initially adding a safety observation, the system requires basic information, such as the type, date, location, and the project. When this information is added, users can fill out the investigation report forms that were applied to the safety observation type.

Users can also fill out safety observation forms by scanning a QR code using their phone's camera. When a code is scanned, a link shows which includes safety observation public forms. This functionality is beneficial as not all users might have instant access to a computer.

QR codes can be accessed using the ‘Public Forms’ functionality in the safety observations module.

Documenting Safety Observations – Safety Observation Investigation (Stage 2)

Filling out investigation forms is an optional step when adding safety observations. Investigation forms are used to add more detailed information about safety observations. An investigation report form can be selected when configuring a safety observation type on the system. This form is then applied when the safety observation type is added to the safety observation. Safety Observation investigation report forms can be configured using the ‘Form Builder’ functionality.

Safety Observation Statuses

Administrators can approve and reject safety observations. This is done to ensure safety observations are fully and accurately documented.

The safety observation statuses that show are:

1. Approved
2. Awaiting Approval
3. Rejected

Safety Observation Quotas

Safety observation quotas are implemented to ensure that a set amount of safe or unsafe actions are observed within a certain time period. Quotas can be implemented daily, weekly, monthly and yearly. This functionality can be found in the Settings menu.

Corrective Actions

Corrective actions are implemented to identify the root cause of unsafe observations and can help prevent incidents from occurring.

Type of Corrective Actions (Immediate/Long Term)

There are two types of corrective actions that can be implemented:

Immediate - steps taken to quickly resolve the issue

Long Term - steps taken to improve overall processes to prevent recurrence

Adding corrective actions includes:

1. Documenting the issue - include the problem description and any relevant details
2. Identifying the root cause - what caused the issue
3. Implementing action(s) that is required to solve the issue

When implementing action(s) to a corrective action, it can be helpful to implement SMART actions:

1. Specific - enter exactly what needs to be done to resolve the issue
2. Measurable - include what is needed to track progress of actions being taken
3. Achievable - set a realistic but effective goal
4. Relevant - make sure the actions align with the objectives
5. Time - Bound - set a time frame to ensure the actions are completed quickly