Skip to content
Enquire
All posts

ISO 14001:2026 Clause 4.2

Picture of SQMC Technical Faculty   SQMC Technical Faculty  ·  5 minute read

ISO 14001:2026 for Auditors > Clause 4.2

Explained: Understanding Interested Parties.

Clause 4.2 of ISO 14001 asks an organisation to understand which interested parties are relevant to its Environmental Management System, what those parties need or expect, and which of those needs and expectations become compliance obligations.

What is ISO 14001 Clause 4.2 trying to achieve?

Clause 4.2 helps the organisation understand who has an interest in its environmental performance and what they expect from the organisation.

In plain English, the organisation should ask:

  • Who cares about our environmental performance?
  • What do they need or expect from us?
  • Which of those expectations are relevant to our EMS?
  • Which expectations do we legally have to meet?
  • Which expectations have we chosen or agreed to meet?

The aim is not to please everybody. The aim is to identify the interested parties and requirements that matter to the EMS.

Why interested parties matter in an EMS

Environmental management is affected by more than internal operations. Organisations often face expectations from customers, regulators, suppliers, neighbours, employees, investors, insurers, contractors and local communities.

These expectations can shape:

  • environmental policy commitments;
  • compliance obligations;
  • environmental objectives;
  • operational controls;
  • communication arrangements;
  • monitoring and reporting;
  • management review priorities.

A good EMS recognises these expectations and uses them to make better environmental decisions.

What does ISO 14001 expect?

ISO 14001 expects the organisation to determine three things:

  • which interested parties are relevant to the EMS;
  • what relevant needs and expectations those interested parties have;
  • which of those needs and expectations become compliance obligations and will be addressed through the EMS.

The organisation does not need to create a huge stakeholder thesis. It needs a practical understanding of relevant parties, relevant requirements and how those requirements affect the EMS.

What is an interested party?

An interested party is a person, group or organisation that can affect, be affected by, or perceive itself to be affected by the organisation’s environmental decisions or activities.

Common examples include:

  • regulators and enforcement bodies;
  • customers and clients;
  • employees and workers;
  • contractors and external providers;
  • suppliers;
  • neighbours and local communities;
  • landlords or tenants;
  • insurers;
  • investors, funders or parent companies;
  • waste carriers and treatment providers;
  • emergency services;
  • certification bodies.

Relevant needs and expectations

Not every expectation matters to the EMS. The organisation should focus on needs and expectations that are relevant to environmental performance, compliance obligations, environmental risks, operational control or the intended outcomes of the EMS.

Examples include:

  • a regulator requiring compliance with environmental permits;
  • a customer asking for carbon-emissions information;
  • a neighbour expecting noise, odour or dust to be controlled;
  • a landlord requiring waste segregation rules to be followed;
  • an insurer expecting suitable spill prevention and emergency controls;
  • employees expecting clear environmental procedures and safe working arrangements;
  • a parent company requiring sustainability reporting;
  • a supplier code of conduct requiring resource efficiency or waste reduction.

When does an interested party expectation become a compliance obligation?

This is the key point in Clause 4.2.

Some interested party expectations are mandatory because they come from legislation, permits, licences, contracts or binding requirements.

Other expectations become compliance obligations when the organisation chooses or agrees to meet them.

Simple example

A customer asks the organisation to report annual greenhouse gas emissions as part of a supply-chain requirement. If the organisation agrees to this requirement contractually, it becomes something the EMS should recognise and manage as a compliance obligation.

This is why Clause 4.2 links directly to Clause 6.1.3 on compliance obligations.

Environmental conditions and interested parties

Interested party needs and expectations may relate to wider environmental conditions, not just site-level controls.

Examples include expectations around:

  • pollution prevention and control;
  • greenhouse gas emissions;
  • natural resource consumption;
  • water use and water quality;
  • climate-related risks;
  • biodiversity protection;
  • ecosystem health;
  • waste reduction and circularity;
  • local nuisance such as noise, odour, dust or traffic.

The organisation should consider how it affects these environmental conditions, how it is affected by them, and which interested party expectations need to be addressed through the EMS.

Practical implementation guidance

Organisations commonly address Clause 4.2 using an interested parties register or matrix.

A simple register might include:

  • the interested party;
  • why they are relevant to the EMS;
  • their relevant environmental needs or expectations;
  • whether those expectations are legal, contractual, voluntary or internal;
  • whether they become compliance obligations;
  • where they are addressed in the EMS;
  • how they are reviewed and kept up to date.

The register itself is not the main point. The main point is that relevant requirements are understood and acted upon.

What auditors typically look for

Auditors usually look for evidence that the organisation has identified relevant interested parties and has considered their relevant needs and expectations.

Evidence may include:

  • interested party register or stakeholder matrix;
  • compliance obligations register;
  • permits, licences or regulatory correspondence;
  • customer contracts or supplier requirements;
  • complaints or community feedback;
  • environmental reporting requirements;
  • management review minutes;
  • objectives linked to interested party expectations;
  • communication records;
  • interviews with managers and process owners.

Auditor tip

Do not stop at checking whether an interested party list exists. Follow the trail. If customers expect carbon information, where is that requirement captured? Who owns it? How is the information gathered? How is accuracy checked? How is it reviewed?

Common weaknesses in Clause 4.2

  • generic interested party lists copied from templates;
  • interested parties identified, but no needs or expectations recorded;
  • needs and expectations recorded, but not evaluated for relevance;
  • failure to identify which expectations become compliance obligations;
  • customer or contractual environmental requirements missed;
  • neighbour or community concerns ignored;
  • environmental reporting commitments not controlled;
  • registers created once and never reviewed;
  • no link between interested parties and EMS planning.

Weak example

“Interested parties include customers, employees, regulators and suppliers.”

This is weak because it only lists categories. It does not explain what those parties need or expect, which expectations are relevant, or which ones become compliance obligations.

Better example

“Relevant interested parties include regulators, customers, employees, contractors, neighbours and waste service providers. Their needs and expectations include permit compliance, waste transfer documentation, carbon reporting, contractor environmental awareness, spill prevention and control of noise during early deliveries. Legal, contractual and voluntarily adopted requirements are reviewed to determine which become compliance obligations.”

This is stronger because it identifies relevant expectations and shows how they feed into the EMS.

Real-world example: manufacturing company

A manufacturing company identifies several interested parties relevant to its EMS:

  • the environmental regulator expects permit conditions to be met;
  • customers require evidence of waste reduction and carbon reporting;
  • employees need clear instructions for chemical handling and spill response;
  • neighbours expect noise and odour to be controlled;
  • contractors need induction before working near chemical storage areas;
  • the parent company requires quarterly environmental performance reporting.

The organisation decides which of these expectations are legal, contractual, internal or voluntary commitments. Those that become compliance obligations are added to the EMS and considered during planning, operational control, monitoring and management review.

Auditor questions for ISO 14001 Clause 4.2

  • Who are the interested parties relevant to your EMS?
  • How did you decide which interested parties are relevant?
  • What environmental needs and expectations do they have?
  • Which expectations become compliance obligations?
  • How are legal, contractual and voluntary requirements distinguished?
  • How are customer environmental requirements captured?
  • How are neighbour or community concerns reviewed?
  • How do interested party expectations influence EMS planning?
  • How is this information reviewed and kept up to date?
  • Can you show an example of an interested party requirement being addressed through the EMS?

Related ISO 14001 clauses

  • Clause 4.1 — Understanding the organisation and its context
  • Clause 4.3 — Determining the scope of the EMS
  • Clause 4.4 — Environmental Management System
  • Clause 5.2 — Environmental policy
  • Clause 6.1.3 — Compliance obligations
  • Clause 6.1.4 — Risks and opportunities
  • Clause 6.1.5 — Planning actions
  • Clause 7.4 — Communication
  • Clause 9.1.2 — Evaluation of compliance
  • Clause 9.3 — Management review

Continue learning

This page is part of SQMC’s ISO 14001:2026 guidance library for auditors, managers and QHSE professionals.