hello@sterling-grc.com +1 201 263 4443 New York ISO & GRC consulting in 60+ countries
SterlingInternational Consulting Talk to a consultantTalk to us
Clause 3ISO 22000:2018 · Requirements guide

ISO 22000 clause 3: understand the terms behind food safety decisions

ISO 22000 clause 3 provides the vocabulary used throughout the standard. Understanding the relationships between its terms prevents mistakes in hazard analysis, control plans and management reporting. The explanations below are practical interpretations, not substitutes for the authorised definitions. They group related concepts so teams can apply them to their work.

Part ofISO 22000:2018 requirements guide|Reading time 7 min

What clause 3 requires in practice

Clause 3 supplies the defined vocabulary for the whole standard, and it applies for the purposes of reading it. The consequence is practical: wherever the later clauses use a term such as hazard, control measure, validation or correction, the defined meaning is the one the organisation is expected to apply. Terms are grouped by topic below.

  • Food chain and product terms: food, feed, product, end product, lot, traceability.
  • Hazard terms: food safety hazard, significant food safety hazard, acceptable level, risk, contamination.
  • Control terms: control measure, PRP, OPRP, CCP, critical limit, action criterion.
  • Assurance terms: measurement, monitoring, validation, verification, audit.
  • Response and management terms: correction, corrective action, nonconformity, top management, documented information, update.

Several definitions carry notes that separate easily confused ideas, notably hazard from risk and validation from monitoring from verification.

Describe the food-chain activity clearly

Food is used broadly in this standard, including human food, feed for food-producing animals and animal food for non-food-producing animals. The food chain extends across production, handling and distribution and includes relevant materials and services. A business's role matters when deciding what hazards it can introduce or control.

A product is an output and can include a service. An end product is considered from the organisation's perspective: one producer's finished ingredient may be another manufacturer's raw material. A process connects activities that transform inputs into outputs. A flow diagram represents the sequence and interactions of those steps, rather than merely showing the building layout.

A lot identifies a defined quantity produced, processed or packed under essentially common conditions, using parameters established in advance. Traceability is the ability to follow relevant history and movement. A lot code helps, but the code alone does not preserve the links between materials, rework and dispatches.

ISO 22000 consulting & certification support

Get clause 3 right the first time — with a global leader in ISO 22000 implementation

A Sterling consultant works the requirement through with your team, links it to the rest of the system and carries it to certification readiness. Expert and experienced consultants, 8,100+ client engagements in 60+ countries.

Separate the hazard from the assessment of risk

Food safety concerns preventing adverse health effects when food is prepared or consumed as intended. It is different from food security, which concerns availability and access. Contamination concerns contaminants occurring or being introduced in a product or processing environment.

A food safety hazard is the biological, chemical or physical agent of concern; allergens and radiological substances are included in the standard's treatment. A significant food safety hazard is one that the assessment identifies as needing control measures. Do not classify a hazard as significant merely because its name sounds serious, or dismiss it without the relevant assessment.

Risk concerns uncertainty and its effects. In operational food safety discussions, probability and severity of adverse health effects matter. Organisational FSMS planning under clause 6.1 has a different level of application. Using the word “risk” for every entry should not obscure whether the team is discussing a hazard, its assessment or a management-system weakness.

Connect controls with the right criteria

An acceptable level concerns the relevant hazard level in the end product. A control measure prevents or reduces a significant hazard to that level. A prerequisite programme, or PRP, provides the basic conditions and activities supporting food safety. PRPs are not simply an alternative name for every control selected through hazard analysis.

A critical control point, or CCP, is a process step where control of a significant hazard is managed using defined measurable critical limits and arrangements enabling correction. An operational prerequisite programme, or OPRP, controls significant hazards using an action criterion that may be measurable or observable.

Those labels result from the systematic selection and categorisation process; they are not universal labels attached to particular pieces of equipment. The consequences of a failed critical limit and a failed OPRP action criterion also need the distinctions explained in product and process nonconformities.

Know what each assurance activity establishes

Measurement determines a value. Monitoring follows the status of a process or activity so action can be taken within the necessary time. Validation establishes evidence of a control measure's capability before relying on it, including relevant changes. Verification checks through evidence that specified arrangements have been fulfilled.

An audit is a systematic, objective examination against criteria, with appropriate independence and documented evidence. It can use verification information, but it is not identical to routine monitoring. Calling a daily observation an “audit” does not automatically satisfy the internal audit requirements.

Keep response and improvement terms distinct

A requirement provides the basis for a decision about conformity or nonconformity. A correction addresses the detected problem; corrective action addresses its cause to prevent recurrence. Both can be needed in the same event, but completing the immediate correction does not establish that the cause has been addressed.

Continual improvement is recurring improvement of performance. An update brings current information into use. Maintaining an arrangement keeps it operating; retaining a record keeps it retrievable. These distinctions help explain why changing a review date, preserving an old record and improving a process are different activities.

Use management vocabulary to clarify accountability

An organisation has responsibilities and relationships for achieving its objectives. Its management system connects those objectives with policy and processes. Top management directs the relevant organisation at the highest level, including the relevant part where the system has a defined boundary.

Policy communicates management's direction. Performance concerns results, while effectiveness asks whether planned activities and results were achieved. Competence concerns applying knowledge and skills successfully; it cannot be inferred from attendance alone. Documented information includes controlled operating information and evidence in suitable media.

An interested party, also called a stakeholder, can affect or be affected by decisions. To outsource is to arrange for an external organisation to perform a function or process. The external organisation's status does not automatically remove the outsourced activity from the FSMS's responsibilities.

Why shared vocabulary matters to the business

Food safety work crosses purchasing, production, engineering, quality and customer service, and each group may use everyday words differently. When a manager says a supplier was validated while the technical team means verified, decisions and records drift apart. Confusion between a prerequisite programme and an operational one can lead to controls being monitored the wrong way or not at all. Clear terms shorten training, make audit conversations productive and reduce disputes with customers about what was promised. They also help a multi-site group compare results fairly. The cost of building a common language is small compared with the cost of misclassifying a hazard control.

How to put the defined terms to work

Definitions only help when people use them in real decisions. One workable sequence follows. Treat the exercise as a conversation about your own controls and records, since abstract glossary reading rarely changes behaviour. Keep the defined meaning fixed while allowing plain wording on the floor.

  1. Gather the terms your teams misuse most often by listening to a hazard analysis meeting or reading recent records.
  2. Compare their usage with the defined meaning, paying special attention to the paired terms such as correction and corrective action.
  3. Run a short working session using your own product and process examples to place each control in the correct category.
  4. Agree plain-language equivalents for staff who do not use technical terms, keeping the defined meaning intact.
  5. Check forms, procedures and report headings so that they use the terms consistently.
  6. Add the vocabulary to induction and to the food safety team's competence plan.
  7. Revisit the list after audits or incidents to see whether term confusion contributed.

Evidence an auditor expects for clause 3

There is no record that clause 3 asks the organisation to hold. Auditors look for the effect of understanding, which they observe indirectly while examining other clauses.

  • Interview with a food safety team member explaining the difference between monitoring, validation and verification for one of their own controls.
  • Hazard analysis outputs that categorise controls consistently and can explain why.
  • Event records where correction and corrective action are handled as separate steps.
  • Staff answers that match the terms used in procedures and training.

Common nonconformities with clause 3

Weak command of terms usually surfaces as a finding against an operational clause. Typical patterns are listed below.

  • Daily checks described as verification when they are in fact monitoring, leaving no genuine confirmation activity.
  • A prerequisite programme treated as if it were a control with action criteria, or the reverse.
  • Corrections closed as corrective actions without any cause being examined.
  • A hazard described as a risk, or the reverse, so the assessment method does not fit the question being asked.
  • Defined terms used differently across sites, producing inconsistent records.

Illustrative manufacturing example

A manufacturer installs a revised control measure. Evidence of capability belongs to validation; operational readings belong to monitoring; a later check of implementation contributes to verification. Treating one set of readings as all three would leave important questions unanswered.

Automate™ on Effivity · included in every Sterling engagement

Keep clause 3 alive in Effivity

Record what you decided under clause 3, link it to the records and controls it affects, and let the review date trigger the next look. Effivity is the ISO & GRC software used in 50+ countries — and part of every Sterling ISO 22000 programme.

Illustrative catering example

A caterer corrects an identified instruction error and controls the affected work. Investigation then finds that supplier changes were not reaching the food safety team. Corrective action addresses that communication cause and checks subsequent changes. Replacing the original instruction alone would not establish recurrence prevention.

Frequently asked questions

Is every PRP an OPRP?

No. PRPs provide supporting conditions, while OPRPs are selected to control significant hazards through the hazard-control process.

Can verification replace validation?

No. They establish different things: capability of the control and fulfilment of specified arrangements. Plan the evidence appropriate to each.

Do we need a separate glossary document?

Clause 3 does not prescribe one. Consistent application is the priority; a concise glossary can help where local terminology causes confusion.

Build a shared language before redesigning the plan

Discuss a food safety terminology workshop with Sterling using your own decisions and records. Learning and agreed Effivity ISO & GRC automation software support can accompany implementation. Explore HACCP Awareness and ISO 22000 Food Safety Awareness, then use the requirements hub for the detailed guides.

Source basis and reading note. This is original practical guidance for ISO 22000. Use an authorised copy for definitive requirements. Illustrative examples describe hypothetical situations, not client results. Implementation methods are distinguished from requirements; independent bodies decide management-system certification outcomes. Issuer standard record: iso.org.
Disclaimer. This guide is provided for general information only. It is not the text of the standard, not legal or professional advice, and not a representation of how any certification body will assess your organisation. Sterling International Consulting accepts no liability for any loss arising from reliance on it. Requirements are applied to each organisation's own context through an engagement; contact us to implement ISO 22000 in your organisation.