ISO 22000 clause 7.4.3: get changes to the food safety team in time

What clause 7.4.3 requires in practice

Clause 7.4.3 asks for an effective system for communicating, inside the organisation, issues that affect food safety. Its core is a list of changes the food safety team must hear about in good time so the management system stays accurate. The list spans products and new products; materials, ingredients and services; production systems and equipment; premises, equipment position and surroundings; cleaning and sanitation arrangements; packaging, storage and distribution; competence and allocation of responsibilities; legal requirements; new knowledge about hazards and controls; customer and sector requirements; enquiries from external parties; complaints and alerts about hazards linked to the end product; and any other condition with an effect on food safety.

The team must then use that information when updating the management system, and top management must ensure the relevant information is an input to management review.

The expected result is a system in which departments know what to pass on and the team acts on it.

Make the change triggers recognisable

Departments need to recognise which changes can affect food safety. Products, ingredients and services are obvious examples, but changes to equipment, premises, equipment location and the surrounding environment can also matter. Cleaning, packaging, storage and distribution arrangements need the same attention.

Changes in competence, responsibilities and authorisations can alter how a control operates even when the process itself is unchanged. New legal, customer or sector requirements and new knowledge about hazards or control measures may also require a response.

Relevant external enquiries, complaints and alerts need an internal route. Do not limit the system to planned engineering projects. An unexpected complaint may reveal an assumption that needs investigation or updating.

Define timely involvement

For planned changes, involve the team while it can still influence the decision. Informing it after a new material has entered production can turn a manageable review into an urgent product evaluation. The precise timing depends on the change and its potential effects.

For unexpected changes or new information, define the escalation route and how interim decisions are made. Staff should not need to prove that a change is dangerous before raising it. Their role may be to identify the changed condition so competent people can assess it.

Use existing purchasing, maintenance, product-development and service processes where practical. Add clear food safety triggers and responsibility rather than creating a separate communication system that nobody consults during ordinary work.

Close the loop through updating and review

The food safety team must use relevant information when updating the FSMS. That can involve preliminary information, hazard analysis, control arrangements, instructions or competence needs. The decision may also conclude that no change is necessary, with an appropriate basis.

Top management must ensure relevant information enters management review. Repeated late notifications may reveal a system weakness requiring management attention rather than another reminder to individual staff. Connect this requirement with planned change and FSMS updating.

Why internal communication of change matters to the business

A hazard analysis is a snapshot. The day after it is approved, purchasing may switch an ingredient, maintenance may move a machine or a customer may change how the product is served. If the food safety team learns about these things only after they happen, the business is relying on controls designed for a situation that no longer exists.

Getting change information early lets the team assess it while options are still open and inexpensive. It also builds trust between departments, because the food safety team is seen as a partner who can help a change succeed rather than a late obstacle. For management, the pattern of late notifications is a useful signal of where processes or priorities need attention.

How to implement clause 7.4.3

Use the standard's list of change types as the starting point, then connect each type to an existing business process so the notification happens as part of normal work.

1. Turn the list of change types into plain questions each department can ask, such as whether a material, machine or instruction is changing.
2. Attach a food safety notification step to the processes that generate change, including purchasing, maintenance, product development, sales and human resources.
3. Decide how early the team must be involved for planned changes, and how quickly it must be told about unplanned ones.
4. Give the team a simple way to log what it receives, decide whether the system needs updating and record the conclusion, including when no change is needed.
5. Carry the outcome into affected documents and make sure the people who apply them hear about it.
6. Summarise significant changes and recurring late notifications for management review.
7. Sample recent changes periodically to see whether the team really heard about them before implementation.

Illustrative food-production example

Illustrative catering example

A catering contract introduces a different meal-service pattern at a construction site. The commercial team routes the proposal to the food safety team because preparation, transport and service timing may change. The team considers the relevant controls and responsibilities before the service arrangement is confirmed.

When the site later requests an unplanned variation, supervisors use the same escalation principle. The original contract review is not treated as approval for every future change.

Evidence and common failures