ISO 22000 clause 4.4: make the FSMS work across process boundaries

What clause 4.4 requires in practice

Clause 4.4 is the short clause that turns the FSMS into a working whole. The organisation needs to set up, put into operation, keep going, refresh and keep improving a system, and that system has to include the processes it needs and the ways they interact. All of this is done in line with the rest of the standard.

Each verb carries a different expectation. Establishing and implementing mean the arrangements exist and are in use. Maintaining means they continue to operate as people, suppliers and products change. Updating means they reflect current information. Continual improvement means the organisation looks for ways to make the system stronger.

The outputs are processes with identified inputs, outputs and owners, plus evidence that information flows between them. The clause does not insist on a manual, a process map or a given structure, and an existing business workflow can form part of the system when it carries the food safety requirements.

Follow a decision through the system

Choose a meaningful starting event, such as a new ingredient, changed recipe or new distribution arrangement. Identify who receives the information, who assesses its significance and who authorises the affected work. Follow the result into specifications, hazard analysis, control arrangements, training and verification where relevant.

This reveals the interaction between processes. Purchasing can complete its commercial approval while the food safety team remains unaware of a material change. Production can follow an instruction correctly while using information based on an earlier product. Local completion does not necessarily produce a reliable whole system.

A process map can make these relationships visible, but the clause does not prescribe one drawing style or a separate FSMS manual. Use arrangements people can apply. An existing business workflow can form part of the FSMS if it incorporates the relevant requirements and preserves necessary evidence.

Keep the system operating after initial implementation

Maintenance involves continuing the agreed arrangements as personnel, suppliers and work change. Updating addresses information and decisions that no longer reflect the operation. Continual improvement considers how the system's suitability, adequacy and effectiveness can become stronger. These activities connect; they are not satisfied by changing a document's review date.

Define ownership where processes meet. The sender needs to know what information to provide, and the receiver needs to know what decision or check follows. Where a handover is incomplete, there should be a usable route to resolve it before unsupported assumptions become normal practice.

Why connected processes matter to the business

A food safety system rarely breaks inside a single task. It breaks at the point where one team hands information to another: a purchasing change that never reaches the technical team, a recipe update that does not arrive at the line, a customer request that stays in an inbox. Clause 4.4 is the requirement that makes those handovers visible and owned. Businesses that manage them well see fewer repeat incidents, shorter investigations and calmer audits. It also reduces dependence on one coordinator who patches gaps from memory. For management, it offers a practical way to judge whether the system is alive or only documented.

How to make the FSMS work across boundaries

The test of this clause is flow. Start with real events and follow them through the organisation. Prefer simple, tested handovers over elaborate diagrams, and judge success by whether information arrives where a decision is made.

1. List the processes that matter to food safety, such as purchasing, receiving, production, cleaning, dispatch, complaints and management review.
2. For each, note what it needs from other processes and what it passes on.
3. Choose a recent change, such as a new ingredient, and trace who learned about it, who judged it and who changed instructions.
4. Fix any break by naming a sender, a receiver and the decision expected at that point.
5. Use existing workflows and systems where they can carry the food safety content, rather than building parallel ones.
6. Review outputs from monitoring and verification to see whether they lead to updates.
7. Repeat the trace with another event after improvements to confirm the connections hold.

Illustrative food-manufacturing example

Illustrative catering example

A caterer transfers responsibility for a satellite service point to a different supervisor. The menu is unchanged, but the new supervisor needs the relevant control arrangements, authority and reporting contacts. The organisation links the personnel change to competence, communication and operational checks.

A later sample confirms that the supervisor can recognise a concern and reach someone with the right authority. The test examines an operating handover, rather than assuming that adding a name to an organisation chart establishes a functioning process.

Evidence and common weaknesses