ISO 22000 clause 7.4: connect food safety information across the chain

What clause 7.4 requires in practice

Clause 7.4 sets up communication as a managed system rather than a habit. It has three layers. The general requirement requires the organisation to decide which internal and external communications the management system needs, covering what, when, with whom, how and by whom, and to make sure people whose work affects food safety understand why effective communication matters.

The external layer requires sufficient food safety information to flow to interested parties in the food chain, with effective arrangements for providers and contractors, customers and consumers, authorities and any other organisation that affects or is affected by the system. Designated people carry the responsibility and authority for external food safety messages, and evidence is retained.

The internal layer requires an effective system for communicating issues that affect food safety, and in particular for getting changes to the food safety team in time so that the system can be updated.

Information received is also an input for management review and system updating.

Plan the message and its responsibility

Clause 7.4.1 addresses what to communicate, when, with whom, how and who communicates. Consider routine exchanges as well as exceptions. Define the information needed for a decision and the point at which it becomes urgent.

Responsibilities should suit the situation. The person receiving a complaint may need to route it for technical evaluation rather than decide product safety personally. A food safety team member may need authority to obtain information from another department when a process changes.

People whose activities affect food safety need to understand the importance of effective communication. Explain the consequence of a missed or ambiguous message, particularly where one person's assumption becomes another person's operating instruction.

Manage information crossing the organisational boundary

External communication includes relevant providers, customers and consumers, authorities and other organisations affecting or affected by the FSMS. Information may concern products, handling, hazards controlled elsewhere in the chain, orders, feedback and complaints.

Assign defined responsibility and authority for external food safety communication. Retain evidence of that communication as required, and use relevant information in FSMS updating and management review. An incoming message can be important even when it does not initially look like a formal food safety notification.

A communication arrangement must also recognise limits. Confidential commercial information and technical food safety information may need different handling. Determine what is necessary and appropriate rather than assuming that sending every available document is effective communication.

Make internal changes visible to the food safety team

Internal communication should keep the food safety team informed in time about relevant changes. These include materials, processes, equipment, premises, cleaning, distribution, responsibilities, competence, requirements and new knowledge about hazards or controls.

The team needs to use that information when updating the FSMS. Top management also needs relevant information for review. Avoid a system in which departments can demonstrate that they sent messages but nobody can explain what was done with them.

Why communication matters to the business

Food is made and delivered through chains. A hazard controlled by a customer's cooking step, a supplier's changed formulation or a regulator's new expectation only stays controlled if the message gets to the person who can act. Weak communication is a typical root cause behind recalls and complaints, because the knowledge existed somewhere in the chain but never reached the right desk.

Good arrangements also protect commercial relationships. Customers value suppliers who tell them early, ask sensible questions and respond to complaints with technical substance. Internally, the food safety team spends less time reconstructing events after the fact, and management receives the signals it needs for review instead of discovering them from an audit.

How to implement clause 7.4

Begin with the information that changes food safety decisions, then design the routes around it. One way that works for many sites is to treat communication as a small set of defined flows.

1. Map the main flows, such as supplier changes, customer enquiries and complaints, authority contact, internal change notifications and urgent alerts.
2. For each flow, set the content, timing, recipient role, method and sender, and name an alternate for out-of-hours cover.
3. Designate who may speak for the organisation on food safety matters outside it, and brief them on the limits of that authority.
4. Connect each flow to a decision point, so that incoming information is evaluated by someone competent and the outcome is traceable.
5. Explain to staff why timely and accurate messages matter, with examples from your own operation.
6. Test the routes with realistic messages, including an after-hours alert, and correct failures.
7. Feed relevant external and internal information into management review and system updates.

Evidence an auditor expects for clause 7.4

An auditor is likely to follow a real item of information from where it arose to the decision it influenced, rather than inspect a contact list. Expect observations and records of these kinds:

• a supplier or customer message and the evaluation that followed it
• records of complaints and external alerts routed to someone technically competent
• interviews showing designated people understand their authority for external contact
• examples of internal changes that reached the food safety team before implementation
• management review inputs that include communication-related information

Common nonconformities with clause 7.4

Findings in this area usually come from gaps between the arrangement on paper and the route actual messages take. Typical examples include:

• No evidence of external communication with customers or providers on food safety matters.
• Complaints held in a commercial system with no technical evaluation of safety implications.
• No clear authority for who may respond to authorities or the media.
• Changes discovered by the food safety team after implementation.
• Contact details out of date, so urgent messages cannot be delivered.

Illustrative food-manufacturing example

Illustrative catering example

A contract caterer changes a service arrangement at a remote worksite. The preparation kitchen needs accurate information about transport, receipt and service responsibilities. The team defines the handover information and the route for resolving incomplete or conflicting details.

During a trial handover, the receiving supervisor identifies a missing contact outside office hours. The organisation resolves that practical weakness before relying on the arrangement during normal service.

Review effectiveness rather than message volume

Trace a real information item from origin to action. Was it accurate enough, timely enough and sent to someone with the appropriate responsibility? Were significant decisions reflected in current FSMS information? This is usually more revealing than counting emails or meetings.

Frequent failures include unclear escalation authority, contact details that are not maintained, and changes announced after implementation. Another is allowing customer complaints and external alerts to remain in a commercial system without technical consideration. Communication should connect with emergency arrangements where relevant.

Explore each numbered part