InnerWeb
Skip to main content

Group occupational safety standard: step-by-step guide

When a group has several plants, each one usually runs occupational safety in its own way: different checklists, different names for risks, different documentation. A group standard lets the plants start up in the same way and compare their results. Below we describe how a group safety manager can build it in InnerWeb in four steps, from the hierarchy to the comparison of results.

Step 1: agree a shared plant hierarchy

The standard starts with the structure, because every further element is attached to it. The structure of a plant in InnerWeb has levels: plot, view (division), building, line and location. It is worth agreeing what the group calls a division, what it calls a building and what it calls a line, and writing these definitions down before any plant starts entering data.

A level named hall (view) in the data model means a plant division or view, not a single building. Buildings are areas inside it. If the group does not agree on this difference, plants will enter the same concepts at different levels and the later summaries will not be comparable.

Step 2: assign documents and recordings to levels

Documents, audio and video recordings are assigned at each level of the plant hierarchy (hall, area, line), with inheritance down the tree. A document set at the division level applies to all buildings and lines below it, while a document specific to one line appears only there. For a group the rule is simple: shared rules are attached high, and exceptions low.

An example split: the evacuation procedure and rules for moving around the site at the view level, and workstation instructions at the line level. Thanks to inheritance, the same file does not have to be copied to dozens of places.

Sample timeline for building the group standard

Sample timeline for building the group standardBar chart: sample step durations of the group standard in weeks, from 2 to 4 weeks01234weeksHierarchy and definitionsHierarchy and definitions: 2 weeks2Documents and recordingsDocuments and recordings: 3 weeks3Risk catalogueRisk catalogue: 4 weeks4ChecklistsChecklists: 3 weeks3
Source: Sample calculation: planning assumptions for a group of several plants, not client data

Step 3: assign risks to locations and types of work

Risks are assigned to a location at every level of the plant hierarchy and to a type of hazardous work. The group standard should contain a shared catalogue of risks for typical jobs, for example work at height or in confined spaces, and a list of risks specific to selected types of location.

A plant adds local risks but does not change the names or the meaning of the shared risks. This split ensures that a permit for the same job at two plants of the group requires the same preventive measures, and that any differences come from the conditions of the place, not from an oversight.

Step 4: run the same checklist and compare the results

The same BHP checklist can be run at many sites, and the results are comparable between sites and periods. This is the core of the standard: the list is one, the inspectors are many, and the result from a hall in one plant can be set against the result from a hall in another.

Practical advice: start with a few of the most important lists, for example workstation and protective equipment inspections, and expand the set only after a quarter. A standard that tries to cover everything at once rarely takes hold.

How to document the standard for an audit

The evidence for an audit is consistency: the same level definitions, the same checklists and the same risks in the documentation of every plant. It is worth keeping a short register of standard versions, with the date each change was introduced and a list of the plants that adopted it. This makes it possible to show that differences between plants result from decisions and not from neglect.

Checklist

Video

Frequently asked questions

Does a group standard limit the plants?

A plant can add local risks and documents. The shared definitions, names and checklists stay the same, so the results can be compared.

Where do we start when the plants have different documentation?

Start by agreeing a shared hierarchy and names. The documents are then moved to the right levels, using inheritance down the tree.

How many checklists should we cover at the start?

A few of the most important ones, for example inspections of workstations and equipment. The set is extended after the first quarter, once the plants are used to the shared way of working.

Building a BHP standard for a group?

We will show you how to map the hierarchy, risks and checklists of your group in one system and roll them out to the next plants.

Let's talk