ISO 45001:2018 builds a structural dependency between three clauses that most implementations treat as separate deliverables. Clause 4.2 generates inputs. Clause 5.4 transmits them through worker consultation. Clause 6.2 consumes them when setting OH&S objectives. When the first link is static, the entire chain produces objectives disconnected from the workforce the system is supposed to protect.<\/p>\n\n\n\n
What ISO 45001 Clause 4.2 Actually Requires<\/h2>\n\n\n\n
Clause 4.2 of ISO 45001:2018 requires the organisation to determine the relevant interested parties \u2014 workers are named first \u2014 and their relevant needs and expectations. The verb is “determine” \u2014 present tense, open-ended. Under the Annex SL structure, context clauses (4.1 through 4.4) are ongoing inputs to planning, not one-time deliverables. Organisations familiar with the parallel Clause 4 structure in ISO 9001<\/a> will recognise this pattern \u2014 but ISO 45001 adds a critical participative dimension.<\/p>\n\n\n\n But Clause 4.2 does not operate alone. Clause 5.4(d)(1) specifies that non-managerial workers must be consulted on “determining the needs and expectations of interested parties.” Read that again: the determination itself \u2014 the act of working out what workers need \u2014 is a participative activity. Management cannot populate the register unilaterally and call it done.<\/p>\n\n\n\n This is where most implementations go wrong. The OH&S manager or consultant drafts the register, management signs it off, and it gets filed. Nobody asked the workers what their needs actually are. The 4.2 output was never worker-informed \u2014 it was management’s assumption documented in a template.<\/p>\n\n\n\n The dependency runs like this:<\/p>\n\n\n\n Clause 4.2 outputs specific worker needs and expectations. Clause 5.4(d)(1) requires workers to be consulted on those outputs. Clause 5.4(d)(5) separately requires workers to be consulted on establishing OH&S objectives \u2014 the Clause 6.2 process. Clause 6.2.1 requires objectives to “take into account applicable requirements,” which includes the needs and expectations identified under 4.2.<\/p>\n\n\n\n Three clauses. Three separable evidence items an auditor can request:<\/p>\n\n\n\n First, 4.2 outputs specific enough to act on \u2014 not “safe environment” but needs you can trace to a hazard report, an incident log, or a documented worker conversation.<\/p>\n\n\n\n Second, a 5.4 consultation record showing those 4.2 outputs were discussed with non-managerial workers during the objective-setting process \u2014 not after objectives were decided.<\/p>\n\n\n\n Third, 6.2 objectives with documented rationale showing which 4.2 inputs were considered, which influenced the objective, and which were set aside and why.<\/p>\n\n\n\n When the 4.2 register is static, the second and third evidence items do not exist. The 5.4 consultation process runs \u2014 toolbox talks happen, safety committees meet \u2014 but it transmits no 4.2 content into the 6.2 process. Objectives come from management risk assessments and last quarter’s incident numbers. Internally consistent. Not demonstrably worker-influenced.<\/p>\n\n\n\n Experienced ISO 45001 auditors do not stop at confirming the register exists. Their audit trail follows a traceability logic:<\/p>\n\n\n\n The auditor requests the 4.2 register, then the 6.2 objectives, then asks the auditee to show which specific 4.2-identified need influenced which specific objective. If the auditee cannot make that trace, the auditor has grounds for a nonconformity against Clause 6.2.1 \u2014 objectives not demonstrably shaped by applicable requirements \u2014 or against Clause 5.4, where the consultation process did not produce the documented outputs the standard expects.<\/p>\n\n\n\n CB sources back this up. Poor worker participation keeps showing up as a primary first-audit failure driver \u2014 and auditors are looking for operational evidence, not procedure manuals. The distinction that catches people: auditors assess whether feedback was acted upon, not whether a consultation meeting happened.<\/p>\n\n\n\n No publicly available certification body guidance document specifies the precise mechanism by which Clause 4.2 outputs must demonstrably influence Clause 6.2 objectives. The phrase “taking into account” in Clause 6.2.1 is not operationally defined in any accessible CB interpretation. This is a live coverage gap \u2014 the standard creates the obligation, but the audit criterion for “documented that consultation occurred” versus “demonstrably influenced the objective” remains inconsistently applied across certification bodies.<\/p>\n\n\n\n Fixing this requires six steps \u2014 none of them complex, all of them requiring procedural discipline:<\/p>\n\n\n\n First, audit the existing register for specificity. Replace generic entries (“safe environment”) with operationally testable needs derived from hazard logs, incident data, and worker feedback. Segment workers by group \u2014 production floor, remote, contractor, agency \u2014 because their needs differ. Organisations that have not assessed hazard identification scope gaps across contractor categories<\/a> will find this segmentation exposes the same blind spots.<\/p>\n\n\n\n Second, build a worker-input channel for the 4.2 determination. Not a suggestion box. A periodic, documented process \u2014 run as a Clause 5.4(d)(1) consultation activity \u2014 where non-managerial workers contribute to or validate the needs recorded against them. This is the step most implementations skip entirely.<\/p>\n\n\n\n Third, define update triggers. Identify what forces a 4.2 review: new work processes, organisational restructuring, new legal requirements, significant incidents, near-miss patterns, or worker-raised concerns. Document the triggers. This converts the register from a static document to a living input.<\/p>\n\n\n\n Fourth, insert a mandatory 5.4 consultation step into objective-setting. Before OH&S objectives are finalised under Clause 6.2, table the current 4.2 outputs with non-managerial worker representatives per Clause 5.4(d)(5). Record which inputs were considered, which were incorporated, and which were not \u2014 with rationale. The “why not” documentation is your audit defence for “taking into account.”<\/p>\n\n\n\n Fifth, build a traceability matrix linking 4.2 inputs to 6.2 objectives. A cross-reference document mapping each OH&S objective to the 4.2 needs it addresses, the 5.4 consultation event where it was discussed, and the risk assessment result (Clause 6.1) it responds to. This single document is the primary audit evidence for the entire chain.<\/p>\n\n\n\n Sixth, schedule the 4.2 review upstream of objective-setting in management review. Place the register review as a standing agenda item before the objective review under Clause 9.3, so the register review feeds directly into the objective discussion \u2014 mirroring the clause chain in your meeting structure. A gap assessment<\/a> can identify where this sequencing is misaligned before the next surveillance visit.<\/p>\n\n\n\n ISO\/TC 283 published a second committee draft of the revised ISO 45001 in January 2026. The expected publication date is around 2027, with a transition period to follow. The revision expands into worker wellbeing and remote working models \u2014 and it shifts the audit emphasis from documentation conformity to demonstrated effectiveness.<\/p>\n\n\n\n That shift is the one that matters. Organisations fulfilling Clause 4.2 through a static register are meeting a documentation test that the 2027 revision is designed to tighten. The structural deficit is not just a current-edition audit risk \u2014 it is a pre-transition gap that will not close with a register update when the new edition takes force.<\/p>\n\n\n\n Clause 4.2 does not ask for a register. It asks for a determination process \u2014 ongoing, worker-informed, and wired into every OH&S objective your organisation sets. The register is a by-product of that process, not the deliverable. When auditors trace the chain from 4.2 through 5.4 to 6.2 and find no documented influence, the nonconformity is not about missing paperwork. It is about an OH&S management system that governs workers without ever incorporating what they actually need.<\/p>\n\n\n\n Clause references reflect mapped standard requirements verified through certification body interpretation sources. Verify against the current edition of ISO 45001:2018 before audit use.<\/p>\n\n\n\n About AEC International<\/strong><\/p>\n\n\n\n AEC International provides ISO certification, training<\/a>, and consultancy services at the intersection of occupational health and safety, management system design, and workforce governance. We support organisations across industries in achieving and maintaining ISO 45001 certification<\/a> \u2014 from gap analysis<\/a> and implementation through audit preparation and continual improvement.<\/p>\n\n\n\n Learn more: www.aec.llc<\/p>\n\n\n\n <\/p>\n","protected":false},"excerpt":{"rendered":" Most ISO 45001 Clause 4.2 registers list workers and generic needs but never feed into objectives. This article traces the structural dependency from Clause 4.2 through worker consultation under 5.4 to objective-setting under 6.2 \u2014 and shows how to close the gap before auditors do. <\/p>\n","protected":false},"author":1,"featured_media":121,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4],"tags":[38,36,13,12],"class_list":["post-116","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-audit-preparation","tag-competence-training","tag-corrective-action","tag-internal-audit","tag-risk-management"],"reading_time":"6 min read","_links":{"self":[{"href":"https:\/\/aec.llc\/blog\/wp-json\/wp\/v2\/posts\/116","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/aec.llc\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/aec.llc\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/aec.llc\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/aec.llc\/blog\/wp-json\/wp\/v2\/comments?post=116"}],"version-history":[{"count":2,"href":"https:\/\/aec.llc\/blog\/wp-json\/wp\/v2\/posts\/116\/revisions"}],"predecessor-version":[{"id":122,"href":"https:\/\/aec.llc\/blog\/wp-json\/wp\/v2\/posts\/116\/revisions\/122"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/aec.llc\/blog\/wp-json\/wp\/v2\/media\/121"}],"wp:attachment":[{"href":"https:\/\/aec.llc\/blog\/wp-json\/wp\/v2\/media?parent=116"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/aec.llc\/blog\/wp-json\/wp\/v2\/categories?post=116"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/aec.llc\/blog\/wp-json\/wp\/v2\/tags?post=116"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}![\"Auditor](\"https:\/\/aec.llc\/blog\/wp-content\/uploads\/2026\/04\/ChatGPT-Image-Apr-8-2026-09_07_47-PM-1024x683.png\")
<\/figure>\n\n\n\nThe Chain That Breaks: Clause 4.2 \u2192 5.4 \u2192 6.2<\/h2>\n\n\n\n
![\"Dependency](\"https:\/\/aec.llc\/blog\/wp-content\/uploads\/2026\/04\/ChatGPT-Image-Apr-8-2026-09_07_43-PM-1024x576.png\")
<\/figure>\n\n\n\nWhat Auditors Test in the Interested Parties Register<\/h2>\n\n\n\n
Converting the Register Into a Worker-Informed Mechanism<\/h2>\n\n\n\n
![\"Non-managerial](\"https:\/\/aec.llc\/blog\/wp-content\/uploads\/2026\/04\/ChatGPT-Image-Apr-8-2026-09_07_51-PM-1024x683.png\")
<\/figure>\n\n\n\nWhy This Matters Before the ISO 45001 Revision<\/h2>\n\n\n\n
Key Takeaway<\/h2>\n\n\n\n