ISO 22000 clause 4.2: make food safety requirements traceable to action
ISO 22000 clause 4.2 requires the organisation to determine the interested parties relevant to its FSMS and their relevant requirements. Information about these parties and requirements must be identified, reviewed and updated. A list of customers, regulators and suppliers is only a starting point: the organisation needs to understand what matters for its ability to provide food-safe products and services.
What clause 4.2 requires in practice
Clause 4.2 asks the organisation to identify two things: the interested parties relevant to its FSMS, and the requirements those parties have that are relevant. The stated purpose is that the organisation can keep providing products and services that satisfy applicable legal, regulatory and customer expectations on food safety. The information must be identified, reviewed and refreshed, so it has to stay accurate as relationships change.
Interested parties may include customers, regulators, suppliers, certification or scheme owners, staff and food-chain partners. The word relevant matters: not every party or wish becomes a requirement. The organisation distinguishes an obligation, an agreed commitment and a simple preference. Where the 2024 amendment is used, it adds a note that parties can have climate-related requirements, which is a point for examination rather than a new universal duty. The outputs are a justified list of parties and their relevant requirements, kept current, which feed scope, planning and operations.
Translate a stakeholder name into a requirement
A customer may specify an intended use, information to accompany a product or a communication arrangement. A supplier may provide information needed to handle an ingredient safely. Relevant authorities establish obligations whose applicability needs appropriate expertise. Employees also need usable instructions and a route for raising concerns.
Differentiate an applicable obligation, a mutually agreed commitment, a preference and an unsupported assumption. Do not record “all laws” as if that phrase identifies the requirements for a particular site. Equally, do not dismiss an accepted customer condition because it is more demanding than a general practice used elsewhere.
The 2024 amendment adds a note that relevant interested parties can have climate-related requirements. Examine actual relevant commitments and expectations. It does not create a universal customer climate specification or make every sustainability request an operational food safety limit.
Give requirements a route into the FSMS
Identify the source, affected product or service and responsible owner. Decide how the requirement reaches contract review, product information, supplier control, communication or another appropriate process. Some information is commercially sensitive, so a controlled summary can be more suitable for operational users than broad distribution of the entire contract.
When a requirement changes, assess the consequences before simply replacing text in a register. A different intended consumer group, for example, may affect technical decisions as well as labels and customer communication. Keep the relationship with scope and communication clear.
Why interested-party requirements matter to the business
Food businesses sell trust. A single missed customer condition, such as a labelling detail or a communication duty, can lead to a rejected delivery, a complaint or the loss of a contract. A single missed legal duty can stop production. Clause 4.2 gives the organisation a structured way to collect these expectations and see that someone owns each of them. It also prevents effort being wasted on wishes that carry no obligation. For sales and account teams, it creates a clear route to confirm what was promised before operations are asked to deliver it, which protects margins and relationships.
How to make party requirements reach operations
A list of names is only the first step. The aim is that each real requirement has an owner and a route into daily work.
- List the parties that can affect or be affected by your food safety performance, including those inside the business.
- For each, record the actual requirement, its source and whether it is a legal duty, an agreed term or a preference.
- Ask technical and legal advisers to confirm which regulatory duties apply to your products and sites.
- Name an owner for each requirement and decide how it reaches the relevant process, for example contract review or supplier control.
- Share a controlled summary with operations instead of the whole contract where commercial sensitivity applies.
- Set a rule that any customer change goes to the food safety team before it is accepted.
- Test the trail by tracing one important requirement from its source to a record of operation.
Illustrative catering-contract example
A caterer receives a contract revision concerning meals for a defined consumer group and the information supplied at service. The account manager involves the food safety team before promising unchanged arrangements. They examine product information, relevant hazards, staff responsibilities and what the customer needs to communicate.
The resulting evidence links the reviewed commitment to operating instructions and checks at the service point. An email filed only by sales would not show that the people preparing and serving the meals know what is required.
Illustrative food-manufacturing example
A manufacturer supplies an ingredient to several customers whose processing conditions differ. Technical sales clarifies the information and food safety commitments relevant to each application. The team avoids treating a broad product description as proof that every intended use has been assessed.
When a customer reports a changed downstream process, the manufacturer routes the information to competent personnel. The review determines what must change in its own specification, communication or assessment, rather than assuming the customer alone owns every consequence.
Use evidence to check the connection
Select an important requirement and trace it from its source to the responsible process and evidence of operation. Then work backwards from a control to the requirement or hazard it addresses. These two directions expose obligations that have no owner and practices whose purpose has been lost.
A stakeholder matrix is an optional organising method. Clause 4.2 does not prescribe its format. Common failures include recording every party as equally relevant, overlooking updates received by commercial teams and assuming a supplier certificate proves fulfilment of a specific material requirement.
Common nonconformities with clause 4.2
These findings usually show up where a requirement is known to one team and unknown to another.
- A stakeholder list that treats every party as equally relevant and records no actual requirements.
- A customer condition accepted by sales but never passed to production or the food safety team.
- Legal requirements described only as all applicable law, without identifying what applies to the site.
- No review after a customer or authority changed its expectations.
- Reliance on a supplier's certificate as proof that a specific material requirement is met.
Frequently asked questions
Does every preference become a binding food safety requirement?
No. Establish its relevance and basis. Applicable obligations and mutually agreed commitments should be distinguished from suggestions or unaccepted requests.
Who should review customer changes?
Involve the roles able to understand their operational and food safety consequences. Sales receipt alone is not sufficient when technical decisions are affected.
Is one group register enough for multiple sites?
It can be useful if relevant local products, obligations and ownership remain clear. A common format must not erase meaningful site differences.
Find commitments that have not reached operations
Ask Sterling to review a requirement-to-process trail within an agreed FSMS engagement. Documentation, training and suitable use of Effivity ISO & GRC automation software can be considered together. Review ISO 22000 Food Safety Awareness for the wider system; navigate through clause 4 and the hub.