ISO 45001 clause 4.2: understand workers and other interested parties
ISO 45001:2018 clause 4.2 requires the organisation to determine relevant interested parties in addition to workers, their relevant needs and expectations, and which needs are or could become legal and other requirements. The 2024 amendment adds a note that relevant parties can have climate-related requirements. The task is to understand actual requirements and their status, not simply create a list of stakeholder names.
What clause 4.2 requires in practice
Clause 4.2 sets out three determinations. The organisation identifies which interested parties, beyond its own workers, are relevant to the OH&S system. It then establishes the relevant needs and expectations of workers and those other parties, which the standard calls requirements. Finally it decides which of those needs and expectations already are, or may turn into, legal or other requirements.
The third step is the one that gives the clause its force. Some needs are mandatory because of law or a collective arrangement, others become binding through a contract or a voluntary commitment, and some remain preferences. The organisation has to know which is which, and those that qualify feed the process in clause 6.1.3. Worker needs are named explicitly, which links the clause to consultation under 5.4. No format is prescribed, and Amendment 1:2024 adds a note that relevant parties may have climate-related requirements, to be assessed on their actual status.
Start with workers and the work relationship
Workers may have different employment or contractual arrangements, and their experience can differ across shifts, sites and roles. Consider relevant needs connected with the work and the management system. Other parties may include authorities, clients, contractors, neighbours, owners or representatives, depending on the organisation’s context.
Identify specific expectations rather than broad labels. A client’s site-access conditions, a worker-representation arrangement or a contractor’s need for coordination can affect implementation. Distinguish the source, relevance and status of each requirement so that operating teams understand what applies.
Determine what becomes a requirement
Some requirements are legally binding; others arise from collective arrangements, contracts or commitments the organisation chooses to fulfil. The organisation needs to determine which are or could become legal and other requirements and connect them with clause 6.1.3. Not every expressed preference automatically becomes an obligation.
The climate-related note prompts attention to relevant party requirements associated with climate change. It does not mean every stakeholder preference becomes mandatory. Assess the actual requirement and its relevance to the OH&S system, just as with other needs and expectations.
Why knowing what others expect matters to the business
A promise made in a sales meeting, a clause in a client contract or a union agreement can each create duties that operational staff never hear about. When that happens, the organisation is exposed to breach, disputes and loss of a customer, and workers experience controls as arbitrary. Workers themselves are often the best source of information about what makes work safer, so their needs deserve the same attention as any external party. Distinguishing real obligations from mere preferences also prevents overcommitment, because a business that treats every expectation as binding will spend effort on the wrong things. Clear requirements make planning, communication and supplier selection more efficient.
How to implement clause 4.2
The clause leaves the method open. The approach below is one that Sterling teams find workable across sites and contracts, and it assumes worker involvement from the start. Keep each entry short, naming the party, the need and the status, because the test is whether the information changes a decision.
- List the parties connected with each activity and location, separating regular employees from agency, contractor and visiting workers.
- Ask each group what they need from the organisation in respect of health and safety, using direct conversations rather than assumptions.
- Classify every need by source: law, collective agreement, contract, voluntary commitment or preference, and seek competent advice where legal interpretation is uncertain.
- Send the items that qualify as legal or other requirements to the person running the process under clause 6.1.3.
- Tell sales, procurement and contract managers that commitments about OH&S arrangements must be checked with operations before acceptance.
- Keep the picture current by reviewing it when a new client, site, contractor or agreement appears.
Two illustrative requirement assessments
A construction contractor works on a client-controlled site with several employers. It identifies the client’s coordination requirements, workers’ need for understandable information and the responsibilities arising from applicable arrangements. The team clarifies who communicates changes and how concerns are escalated. A signed access agreement does not by itself establish that those interfaces work.
A BPO business changes shift patterns to support a new service. Workers raise concerns about workload and the practical effect of the proposed arrangement. Management considers their views before decisions, checks relevant legal and other requirements and identifies the implications for planning. It does not treat consultation as a vote that can waive an applicable duty.
Connect the findings with the system
Relevant needs inform scope, policy, planning, communication and evaluation. Where the organisation accepts a new commitment, make sure the people responsible for implementation know what it means. Sales, procurement and contract teams should understand that a promise about OH&S arrangements can create work for operational owners.
Use suitable local or specialist advice where legal interpretation is needed. A requirement may differ across countries or workplaces. Avoid copying an obligation from one site into another without assessing applicability.
Evidence and common mistakes
Clause 4.2 does not prescribe a stakeholder register or survey method. A concise record of parties, relevant needs and requirement decisions can help demonstrate understanding, while contracts, consultation records and operational arrangements provide supporting evidence.
Common weaknesses include overlooking agency or contractor workers, listing parties without specific needs and treating all expectations as legally binding. Another is keeping accepted requirements in a commercial file where the people managing work never see them. The practical test is whether relevant information changes decisions.
Frequently asked questions
Are workers just one optional stakeholder group?
No. The clause expressly addresses workers as well as other relevant interested parties, and worker involvement is developed further in clause 5.4.
Must every expectation be accepted?
No. Determine relevance and which needs are or could become legal and other requirements. Applicable duties cannot simply be declined.
Does the climate note create a universal new workplace rule?
No. Identify relevant party requirements and their actual status in the organisation’s context.
Clarify requirements at a working interface
Ask Sterling to review worker and interested-party requirements for a site, contract or service change. The ISO 45001 Awareness course supports shared understanding. Effivity ISO & GRC automation software can be scoped around agreed processes and evidence. See context and the directory.