Launch Operations: Putting Your IMS Controls into Action
QHSE operational controls are where an integrated management system stops being paperwork and starts protecting people, product and the environment. Most Australian businesses have a policy, a risk register and a set of procedures. Far fewer can prove that the controls named in those documents are running on site today.
That gap is where incidents, nonconformances and audit findings come from. This post shows how to launch your controls, verify them and keep them alive.
What operational planning and control demands
ISO 9001:2015, ISO 14001:2015 and ISO 45001:2018 each place operational planning and control in Clause 8.1. The organisation must plan, implement and control the processes needed to meet requirements. It must also set criteria for those processes and keep documented information that gives confidence they ran as planned.
ISO 45001 goes further. Clause 8.1.2 requires the hierarchy of controls, and Clause 8.1.3 requires management of change before it creates new risk.
The law lines up with the standards. Section 19 of the Work Health and Safety Act 2011 requires a person conducting a business or undertaking to ensure, so far as is reasonably practicable, the health and safety of workers. Regulation 36 of the WHS Regulations sets the hierarchy of control measures. Regulation 37 requires those measures to be maintained, and regulation 38 requires them to be reviewed. A control that is written down but not maintained does not meet the duty.
Why QHSE operational controls fail after launch
Three patterns appear in almost every business that struggles to keep controls alive.
First, the control has no owner. The procedure says “the supervisor will inspect”, but no named position is accountable, so nobody does. Second, the control has no proof. It may be happening, yet nothing is recorded, so an auditor or regulator cannot see it.
Third, the control drifts. New plant arrives, a subcontractor starts, or a chemical is substituted. As a result, the original control no longer matches the work, and nobody notices until something goes wrong.
Turn your controls into a launch register
A single register is the simplest way to manage QHSE operational controls across quality, safety and environment. It gives one place to see what is running, who owns it and when it was last proven.
Start with your risk register and your legal register. For every significant hazard, environmental aspect or quality risk, list the control, its place in the hierarchy and the document that describes it. Then name the position responsible.
Next, add the two fields most registers miss. These are how the control will be verified and how often. Be specific. A daily plant pre-start, a weekly extinguisher check, a monthly exclusion zone audit and a quarterly spill kit check are all verifiable.
Record a last verified date and a frequency for each one. The next due date then calculates itself, and a simple formula flags every control as Current, Due Soon or Overdue. Therefore overdue controls become visible without anyone chasing a diary.
Where a contractor performs the control, such as annual test and tag or fire equipment servicing, the evidence is the contractor’s report. Attach it to the register. Do not ask your team to retype it.
Prove it works through verification and change control
Launching is only the start. Verification confirms a control exists, while monitoring confirms it works. ISO 14001 and ISO 45001 Clause 9.1 both require monitoring, measurement, analysis and evaluation, so pair each control with a lead indicator. Pre-starts completed on time is a good example.
Then review the lagging results, such as incidents and nonconformances, at management review under Clause 9.3.
Change control closes the loop. Regulation 38 requires a review of control measures before a change likely to create a new or different risk, when consultation raises a concern, and when a health and safety representative asks for one. In practice, new plant, a new site or a new subcontractor should trigger a review of the affected controls before work starts.
Competence matters as much as the register. ISO 9001, ISO 14001 and ISO 45001 Clause 7.2 require people to be competent for the tasks they perform. A control that depends on a worker who has never been trained will fail, however well it is written. Link each control to the training or licence it needs, and check that before the control is launched.
Consultation matters too. Sections 47 to 49 of the WHS Act require you to consult workers when you decide on control measures. Workers know whether a control is practical. Ask them before launch, and ask again when you review it.
Practical Application
Consider an Australian electrical and mechanical contractor with 30 staff working across commercial sites in several states. Its risk register lists 40 significant risks, and each one has a procedure. However, nobody can say which controls were verified last month.
The QHSE Manager builds one register for all QHSE operational controls. Every control gets an owner, a verification method and a frequency. Plant pre-starts are daily, portable RCD testing follows the intervals in AS/NZS 3760, ladder inspections are monthly and first aid kits are checked monthly.
Each Monday, the Operations Manager filters the register for Due Soon and Overdue items. Each item gets an owner and a date before the toolbox talk. After one quarter, overdue controls drop sharply, and the next principal contractor audit takes minutes instead of days because the evidence is already linked.
Conclusion
Policies and risk registers set the intent. QHSE operational controls deliver it. Launch them with an owner, a verification method and a frequency, then let the register flag what is slipping. Review them whenever the work changes, and your IMS will hold up at audit, at inspection and on site.
Ready to act? Contact us today or book a free 45-minute consultation.
Download the Free Template
Download the free Operational Controls Register (.xlsx) and start flagging every overdue control before it becomes an incident.
Recent Comments