ISO 22000 clause 7: equip people to operate the food safety system

What clause 7 requires in practice

Clause 7 covers the support a working FSMS depends on. Clause 7.1 deals with resources: determining and providing what the system needs, competent people with agreements for any outside experts, infrastructure, work environment, externally developed elements of the system, and control over any process, product or service that comes from an outside provider. Clause 7.2 asks the organisation to define competence, make sure people have it, act where they do not and keep evidence. Clause 7.3 asks that relevant people are aware of the policy, the objectives that touch their work and their own contribution. Clause 7.4 covers communication in general, outward and inward. Clause 7.5 covers documented information: what the system includes, how it is created and updated, and how it is controlled.

The outputs are resources that are provided in practice, competent and aware people, working information channels and controlled information.

7.1: provide resources suitable for the work

Clause 7.1.1 asks the organisation to determine and provide resources, considering internal capabilities and constraints and the need for external support. Under 7.1.2, the people necessary to operate and maintain an effective FSMS need competence. Where external experts assist, retain agreements defining their competence, responsibilities and authority.

Infrastructure under 7.1.3 can include facilities, equipment, utilities, transport and information technology. The work environment under 7.1.4 includes relevant human and physical conditions. A suitable procedure cannot compensate indefinitely for equipment that cannot be cleaned effectively or staffing arrangements that leave essential tasks without a competent owner.

When externally developed elements such as a PRP or hazard-control framework are used, 7.1.5 requires their suitability and adaptation to the actual sites, processes and products by the food safety team. They need implementation, maintenance and updating. Buying a package does not establish that its assumptions match the operation.

Clause 7.1.6 addresses evaluation, selection, monitoring and re-evaluation of external providers, communication of requirements and retained evidence. The organisation needs confidence that external provision does not undermine its ability to meet FSMS requirements. Explore the focused external-provider guide for examples and decisions.

7.2: establish and demonstrate competence

Determine the competence needed for people doing work under the organisation's control that affects food safety performance and FSMS effectiveness, including relevant external providers. Education, training and experience can contribute. Take necessary development action and evaluate whether it worked, retaining appropriate evidence.

The food safety team needs a combination of relevant knowledge and experience covering the organisation's products, processes, equipment and hazards. General awareness learning alone cannot qualify someone to validate a specialised control. Match development and assessment to the decisions the person will make.

7.3: connect awareness with individual responsibility

Relevant people need awareness of the policy, objectives relevant to their tasks, their contribution and the implications of failing to follow the system. Use practical examples from their work. An employee should know when and how to report a concern, not merely recognise the ISO number.

Course completion supports a learning record. It is distinct from organisational certification and from demonstrated competence for a particular technical task. Observe application, discuss scenarios and provide supervised practice where appropriate to the role.

7.4: ensure important information reaches the right people

Under 7.4.1, determine the subject, timing, audience, method and owner of relevant communications. External communication in 7.4.2 includes providers, customers or consumers, authorities and other organisations affecting the FSMS. Relevant information about products, hazards requiring control elsewhere, contractual changes and feedback needs an effective route.

Designated people need authority for external food safety communications, and evidence is retained. Relevant information informs management review and system updating. Avoid relying on personal inboxes when a change must reach several operational owners.

Internal communication under 7.4.3 keeps the food safety team informed of relevant changes, including materials, products, equipment, premises, cleaning, distribution, competence, requirements and hazard knowledge. Complaints and alerts can also matter. The team uses this information to update the FSMS, and relevant information reaches management review.

7.5: keep information usable and trustworthy

The FSMS includes information required by the standard, needed for effectiveness and required by authorities or customers. Creation and updating need suitable identification and format, with review and approval. Control covers availability, protection, access, storage, changes, retention and disposition, including necessary external information.

Protect retained evidence from unintended alteration. A revised instruction and a historical monitoring record serve different purposes; changing one should not rewrite the other. The standard does not mandate a paper manual or a particular software platform.

Why support arrangements matter to the business

A technically sound hazard control plan fails if the equipment cannot be cleaned, the person responsible lacks training, the supplier change never reaches the team, or two versions of an instruction sit at the same workstation. Clause 7 deals with these ordinary but decisive conditions. For a business, getting support right means fewer repeated failures, more predictable audits and less dependence on individual heroics. It also governs how external help is used: consultants, contractors and templates can speed progress, but the organisation remains accountable for the result. Treating support as part of food safety, not an administrative extra, is what separates a system that works from one that merely exists.

How to build the support behind the system

Work through the five support topics by asking what the actual work needs and testing whether it is there. Keep the work proportionate and use existing routines where they already carry the necessary content, since parallel arrangements tend to be neglected.

1. List the recurring FSMS tasks and ask the people doing them what they lack in time, access, equipment or information.
2. Define the competence for food safety team roles and operating roles, and compare it with what people can demonstrate.
3. Plan awareness so that each role understands the policy and how its own work contributes.
4. Map the main information flows, including supplier and customer changes, and name an owner for each.
5. Decide what information the system needs, who approves it, where people find the current version and how records are protected.
6. For outside experts, templates and providers, define the expected role, authority and checks before work begins.
7. Review the whole picture after any change to products, sites or people.

Illustrative example: food manufacturing maintenance cover

Illustrative example: a catering ingredient substitution

A hypothetical workplace caterer receives notice that a supplier has changed an ingredient. Purchasing sends the relevant information to the food safety team before the substitute is used. The team reviews the implications for its system and communicates any necessary changes to preparation and service staff.

If the notice remains in a buyer's inbox, a controlled recipe document may still describe obsolete information. This shows why communication and document control must connect with actual decisions; it does not prescribe a technical conclusion about the ingredient.

Evidence and common weaknesses

Explore each numbered part