ISO 45001 clause 4.4: connect the processes that manage OH&S
ISO 45001:2018 clause 4.4 requires the organisation to establish, implement, maintain and continually improve an OH&S management system, including the necessary processes and their interactions, in accordance with the standard. The practical challenge is to make decisions connect across functions so that hazards and requirements influence the work people actually perform.
What clause 4.4 requires in practice
Clause 4.4 is the clause that turns the earlier determinations into a working system. The organisation has to establish, implement, maintain and continually improve its OH&S management system, including the processes it needs and the way they interact, in line with the standard's requirements. Four verbs matter. Establish means design it; implement means make it operate; maintain means keep it fit as things change; continually improve means use evidence to strengthen it.
The emphasis on interaction means the system is judged by how processes connect, not by whether each exists in isolation. A hazard report that never reaches someone able to act is a broken interaction. The clause does not require a manual, a particular process map or a separate system from other management systems. It requires that the arrangements cover what the standard requires and achieve the intended outcomes, with processes that people actually use.
Build the system around real workflows
Identify how the organisation plans work, purchases products and services, introduces change, develops competence, communicates, checks performance and learns from incidents. Worker consultation and participation need to connect with those processes, rather than sit in a separate meeting with no influence over decisions.
Trace the information moving between processes. A hazard identified during work may require a control decision, purchasing change, revised instruction and effectiveness check. If it stops in a reporting system without reaching someone who can act, the interaction is incomplete.
Integrate without losing OH&S requirements
Existing business processes can carry OH&S arrangements. Procurement can include relevant selection criteria; project planning can address work interfaces; management review can allocate resources. Integration is useful when it makes requirements part of normal decisions, not when it hides them inside a broad process that no one can explain.
Clarify ownership, inputs, outputs and escalation at important interfaces. Different functions may own different parts of the same workflow. The OH&S coordinator supports the system, but operational managers still need authority and responsibility for the work they control.
Why connected processes matter to the business
Many organisations have good policies and a competent safety specialist yet still suffer repeated problems, because information stops moving between departments. Purchasing does not know what the risk assessment found, operations change a schedule without telling the person who assessed it, and worker concerns sit in a file. Making interactions work reduces repeat incidents, avoids duplicated effort and allows the OH&S requirements to be built into everyday decisions rather than layered on top. It also helps organisations with several management systems to share processes sensibly, which reduces administration while keeping each discipline visible. Auditors and customers gain confidence from seeing the system operate, not merely be described.
How to implement clause 4.4
No fixed structure is prescribed. The route below is one that Sterling teams use to build a system around existing work, and it works best when operational managers lead it. Keep the map simple and revisit it after any significant change in how work is organised.
- List the core workflows, such as planning work, buying, managing change, building competence, communicating, checking performance and learning from incidents.
- For each, identify where OH&S information enters, who decides, and where the outcome goes next.
- Name one owner for every important interface, and make sure the owner has authority to act or a clear route to escalate.
- Decide which existing business processes can carry OH&S requirements and which need their own arrangements.
- Test the system by following one recent change or incident from start to finish, comparing what people say with what the records and conditions show.
- Set a rhythm for reviewing gaps and feeding the lessons into improvement.
Two illustrative system connections
A manufacturer plans a maintenance task involving contractor workers. Procurement establishes relevant requirements, operations and the contractor coordinate the work, competent people assess hazards and controls, and workers receive appropriate information. After the task, the organisation reviews relevant findings. The system works through these connected decisions, not merely through a contractor file approved months earlier.
A BPO business changes its service model and staffing pattern. Workers contribute information about workload and handovers, managers assess the implications and HR supports the agreed changes. Monitoring and feedback then examine whether the arrangement works. A consultation record with no connection to the staffing decision would demonstrate only part of the process.
Test whether the system operates as designed
Use a recent change, incident or work package to examine the interfaces. Can people explain what information they received, what decision they made and what happened next? Compare the explanation with actual records and conditions. This reveals gaps that a process diagram alone may miss.
Maintenance of the system includes keeping it suitable as people, activities and circumstances change. Continual improvement uses evidence to strengthen processes and OH&S performance. Neither is achieved simply by keeping a policy in a current folder.
Evidence and common mistakes
Clause 4.4 does not prescribe an OH&S manual or a specific process-map format. The system still needs the documented information required elsewhere in the standard and information the organisation determines necessary. A concise map can help if it explains interfaces; it is an optional method.
Common weaknesses include assigning every task to a safety specialist, separating worker feedback from management decisions and building approvals that operational teams routinely bypass. Another is assuming that software creates a management system by itself. Processes, authority, competence and actual use remain necessary.
Frequently asked questions
Must the OH&S system be separate from other systems?
No. It can share processes with quality or environmental management if its own requirements and intended outcomes remain adequately addressed.
Is a process map compulsory?
No particular format is required. The organisation needs functioning processes and clear interactions.
How can we test integration?
Follow a real work decision across functions and check whether OH&S information influenced the action and its evaluation.
Trace one work process end to end
Ask Sterling to map an OH&S workflow with your team, including documentation and audit evidence. The ISO 45001 Awareness course supports shared understanding. Consider Effivity ISO & GRC automation software within the agreed process scope. See context and the full directory.