ISO 22000 clause 5.2.1: establish a food safety policy the business can deliver

What clause 5.2.1 requires in practice

Clause 5.2.1 puts the policy in the hands of top management: it sets it up, puts it into effect and keeps it. Six characteristics are listed. The policy suits the organisation's purpose and context. It supplies a frame for setting and reviewing objectives. It carries a promise to meet the food safety requirements that apply, which covers legislation and any terms agreed with customers. It deals with communication, both inside and outside the business. It also carries a promise to keep improving the FSMS. It addresses the need to secure competence in food safety.

The wording is for the organisation to choose. The clause fixes the subjects the policy must touch, not its length or style. The outputs are a policy that has been approved by top management, is current and can be tied to objectives and resources.

Begin with the business and its responsibilities

Review the products, services, intended uses and scope of the FSMS. Consider what customers and other relevant parties need from the organisation. A food-contact packaging producer and a catering operator share a concern for food safety, but their responsibilities and operating decisions differ.

The policy includes commitment to satisfying applicable food safety requirements, including relevant statutory and regulatory requirements and mutually agreed customer requirements. Appropriate specialists need to determine what applies to the actual activities and locations. Do not replace that work with a promise that the organisation meets every rule in every country.

Check commitments against delivery capability. Where a proposed customer promise exceeds current resources or technical capability, resolve the gap before using the policy as evidence of readiness. A policy commitment does not establish that its supporting arrangements already exist.

Include communication, competence and improvement

The policy addresses internal and external communication and the need to ensure food safety competence. These subjects matter because food safety decisions often depend on information held by suppliers, customers or different internal teams. Competence also extends beyond attendance at a general briefing.

Include commitment to continual improvement of the FSMS. This should create space for learning from verification, audit, operating experience and management review. It should not be phrased as a guarantee that incidents or nonconformities can never occur.

Use the policy as a framework for objectives. If management commits to dependable communication, the relevant objective and plan might address an identified handover weakness. The objective should still be selected and evaluated under clause 6.2; a policy paragraph alone does not provide the action plan.

Why the content of the policy matters

A policy written for a tender and filed afterwards creates exposure, because it commits the business to things that nobody has planned. A policy written with the six subjects in mind does the opposite: it becomes a short brief that tells managers what to resource and tells customers what to expect. Competence and communication are the two themes most often left out, yet they are where many food safety failures begin. When top management owns the text, it can also defend the commitments in front of an auditor or a customer. The policy then supports contract negotiations and investment decisions instead of sitting on a wall.

How to establish a policy the business can deliver

Draft from the operation outward, and check every phrase against capability. Write only what management will stand behind, since every sentence is a commitment that customers and auditors may later test. Involve the managers who will need to deliver it before it is approved.

1. Gather the scope, the main customer terms and the legal duties that the policy will need to reflect.
2. Ask top management what it is genuinely prepared to commit to on food safety, competence, communication and improvement.
3. Write the policy in plain language, with one clear statement for each of the six subjects.
4. Test each commitment against current resources and name any gap that needs a plan.
5. Link the policy to at least one objective under clause 6.2 so the direction produces action.
6. Approve it through top management and apply document control, including a review trigger for changes in services or context.
7. Keep detailed limits and criteria in the technical controls, not in the policy.

Illustrative manufacturing example

Illustrative catering example

A caterer starts supplying a service with different intended consumers and delivery arrangements. Its existing policy is reviewed against the changed context. Management confirms the relevant requirements, communication interfaces and competence needed before treating the earlier policy as automatically suitable.

The policy remains concise, while detailed product and process information sits in the appropriate controlled records. This avoids overloading the policy with technical criteria that require more frequent and specialist review.

Evidence and common mistakes