What it is about
No organisation works in isolation. Customers, employees, suppliers, authorities, owners, banks, insurers and the neighbourhood all expect something, and some of it matters for the management system. Clause 4.2 requires you to know these parties, to understand their relevant expectations and to decide what follows from them.
The core is the decision, not the list. An expectation either becomes a requirement that the system fulfils, or it is deliberately not adopted, and you should be able to justify either. In ISO 14001 the adopted requirements are called compliance obligations and end up in the legal register.
4.2 is a starting point. What is recorded here comes up again later: in the risks and opportunities, in the scope, in the objectives and in the management review. Because the environment changes, the overview is reviewed again and again.
What the auditor checks
“Who apart from your customers expects something from you?”
Whether the environment has been thought through completely. If authorities, insurers, banks or the neighbourhood are missing, the auditor asks whether they are not relevant or have simply been forgotten.
“What does your largest customer expect, and how do you know?”
Whether the expectations are backed up: by contracts, terms of delivery, quality assurance agreements, conversations. Assumptions about customers are not evidence.
“You have not adopted this expectation. Why not?”
Whether there is a deliberate decision and who made it. Marking a party as “not relevant” is allowed, but it needs a reason.
“Where can I see that you meet this requirement?”
The trail into the system: a process, a document, an objective, a risk. A requirement that never turns up anywhere else exists only on paper.
“Does any of your parties expect something regarding the climate?”
Since the 2024 amendment to the management system standards, this question is part of it. Customers asking for CO2 figures per product, banks with sustainability criteria or insurers with conditions against storm damage are typical answers.
“Which party or requirement has been added since the last audit?”
The overview is in real use when a specific new customer, a new law or a new site is named and is actually recorded there. If there is no answer, the list has usually not been touched since the initial certification.
Which evidence convinces
An overview of the parties with their expectations and the decision on each
The standards do not require a specific document for this, but the determination must be traceable in the audit. An overview is the shortest way to get there.
The sources of the expectations
Contracts, customer specifications, permits, official conditions, survey results. They show that the expectations are known and not guessed.
Links to risks, objectives and processes
They prove that something follows from the expectations, and they make the check in the audit quick.
The date of the last review and what changed in it
An overview that has taken in new customers, new laws or a new site is the best proof that it is actually used.
For ISO 14001, the legal register
It contains the compliance obligations that have arisen from the parties’ expectations, and it has to be documented.
Typical nonconformities
Only names, no expectations
The list names “customers, employees, suppliers” but does not say what they expect. That leaves out exactly what 4.2 is about. In the audit this is usually a minor nonconformity.
Expectations with no trail in the system
The requirements have been collected, but no process, no objective and no risk picks them up. In the audit there is no way to show that they are being met.
Everything is relevant
Every conceivable party is on the list, and no decision separates what matters from what does not. This is the counterpart to the list that is too short, and it is just as impossible to manage.
Not looked at since the initial certification
New major customers, new laws, a new site: none of it appears in the overview. ISO 9001 explicitly requires the information about the parties to be monitored and reviewed.
Climate not considered
Since 2024, auditors expect the question about climate change requirements to have been asked, even if the answer for a party is “no”.
Differences by standard
ISO 9001ISO 9001
ISO 9001 requires you to determine the parties and their requirements and to monitor and review the information about them. The 2026 edition additionally asks which of these requirements are addressed through the quality management system. Customers are at the centre, but not on their own.
ISO 14001ISO 14001
ISO 14001 asks which expectations become compliance obligations. Together with laws and permits, they form the legal register (clause 6.1.3). Typical parties here also include authorities, neighbours and environmental groups, and voluntary commitments to customers can become just as binding as a law.
ISO 27001ISO/IEC 27001
ISO/IEC 27001:2022 already requires the decision: which requirements of the parties are addressed through the information security management system. These include legal and contractual obligations, for example from data protection, NIS2 or customers’ security requirements. They feed into the scope and the risk assessment.
How IMScollect covers it
In IMScollect, clause 4.2 has its own page. Each party is listed there with its category and the standard it concerns, with its requirements and with details of how they are met and which companies they apply to. An assessment against fixed criteria shows how important a party is, and the climate question is included for each standard.
The date of the next review becomes a task, and from a party you create a risk or an opportunity with one click. That way the audit can still see where a risk comes from. The AI advisor Conni knows these entries and takes them into account in its suggestions.
Frequently asked questions
Who counts as an interested party?▾
Any person or organisation that can affect the organisation’s decisions, is affected by them or perceives itself to be affected. For the management system, the ones that count are those whose expectations matter for its results: usually customers, employees, suppliers, authorities, owners, banks, insurers and the neighbourhood.
Does clause 4.2 have to be documented?▾
None of the three standards explicitly requires a document for 4.2. In the audit, however, the determination must be traceable, and for ISO 14001 the compliance obligations have to be documented. An overview of parties, expectations and decisions is therefore the usual way.
How are 4.1 and 4.2 connected?▾
4.1 asks about the issues that affect the organisation from inside and outside, such as the market, technology or legislation. 4.2 asks about the people and organisations behind them and their expectations. Together they are the basis for the scope and for the risks and opportunities.
What does climate change have to do with interested parties?▾
With the 2024 amendment, the management system standards contain a note that parties can have requirements related to climate change. This is not a new obligation, but it is a question that gets asked in the audit. If you have answered it once for every relevant party, you are prepared.
Further reading and viewing
- Integrated management system: what ISO 9001, 14001 and 27001 really share
- The auditor asks, episode 1: Interested parties (in German)Watch on YouTube (in German)(opens in a new window)
