On this page
The short version
- DS/EN ISO 22000:2018 implements Plan-Do-Check-Act cycles across organisational strategy and operational hazard control.
- Organisational planning under Clauses 4 to 7 establishes context, leadership commitment, resources, and high-level risk management.
- Operational control under Clause 8 applies HACCP principles, prerequisite programmes, and control measures at process level.
Structural Background, Systemic Rationale, and Affected Roles
Under DS/EN ISO 22000:2018, food safety management systems operate through a structural architecture built upon two distinct Plan-Do-Check-Act (PDCA) cycles. Quality managers, compliance leads, and internal auditors must understand how Clause 0.3.2 integrates high-level organisational governance with technical food safety operations. Auditing only operational hazard controls or only administrative policy creates a disconnected management system that fails during external certification assessments.
The systemic rationale for this dual structure is to ensure that strategic decisions made by top management directly inform operational controls on the production floor. Conversely, operational data gathered during routine monitoring and verification must flow back into strategic management review processes. Internal auditors must evaluate whether organisational objectives in Clauses 4 to 7 effectively drive operational execution in Clause 8, and whether operational findings inform continual improvement in Clauses 9 and 10.
Organisational Strategy versus Operational Control
The first level of the PDCA cycle governs the overall Food Safety Management System (FSMS). The Plan stage encompasses context determination in Clause 4, leadership commitment and food safety policy in Clause 5, and organisational risk planning in Clause 6. The Do stage relies on support functions in Clause 7, including resource allocation, competence, awareness, and communication. The Check stage evaluates system performance under Clause 9 through internal audits and management review, while the Act stage drives continual improvement and system updating under Clause 10.
The second level operates entirely within Clause 8 to manage operational planning and control. Here, the Plan stage involves collecting preliminary information, establishing prerequisite programmes (PRPs), performing hazard analysis under Clause 8.5.2, validating control measures under Clause 8.5.3, and establishing the hazard control plan under Clause 8.5.4. The Do stage executes operational controls, monitoring measuring equipment under Clause 8.7, and controlling nonconformities under Clause 8.9. The Check stage conducts verification activities under Clause 8.8, while the Act stage updates PRPs and hazard control plans under Clause 8.6.
| PDCA Stage | System-Level FSMS Cycle (Clauses 4–7, 9–10) | Operational Food Safety Cycle (Clause 8) |
|---|---|---|
| Plan | Context (Clause 4), Leadership (Clause 5), Organisational Risk Planning (Clause 6) | Preliminary Steps (Clause 8.5.1), Hazard Analysis (Clause 8.5.2), Hazard Control Plan (Clause 8.5.4) |
| Do | Support Resources, Competence, Awareness, Communication (Clause 7) | Implementation of Hazard Control Plan (Clause 8.5.4.5), Nonconformity Control (Clause 8.9) |
| Check | Monitoring, Performance Evaluation, Management Review (Clause 9) | Verification Activities (Clause 8.8.1), Verification Result Analysis (Clause 8.8.2) |
| Act | Nonconformity Corrective Actions, Continual System Improvement (Clause 10) | Updating Preliminary Information, PRPs, and Hazard Control Plan (Clause 8.6) |
Auditing the Communication Bridge and Systemic Feedback Loops
Internal auditors must verify that interactive communication functions as an active bridge between organisational governance and operational execution. Clause 7.4.2 and Clause 7.4.3 mandate structured external and internal communication channels. When operational changes occur—such as introducing new raw materials, altering equipment layouts, or modifying cleaning programmes—Clause 7.4.3 requires timely communication to the food safety team. Auditors must check whether operational shifts trigger necessary updates to the hazard control plan under Clause 8.6 and organisational risk assessments under Clause 6.1.
Auditors must also trace how operational data from Clause 8 feeds back into performance evaluation under Clause 9. Under Clause 8.8.2, the food safety team must analyse verification results, including prerequisite programme checks and hazard control plan evaluations. This analysis serves as mandatory input for performance evaluation under Clause 9.1.2 and management review under Clause 9.3.2. If management review outputs in Clause 9.3.3 fail to allocate necessary resources or update the food safety policy in Clause 5.2, the two-level PDCA cycle is broken. Auditors must document these disconnects as systemic nonconformities.
What to do now
- Audit the alignment between organisational risks identified under Clause 6.1 and operational hazards assessed under Clause 8.5.2.
- Verify that internal communication procedures under Clause 7.4.3 automatically notify the food safety team of operational or equipment changes.
- Ensure that verification analysis outputs from Clause 8.8.2 are formally presented during management review meetings under Clause 9.3.2.
- Check that management review outputs under Clause 9.3.3 result in documented resource allocation or system updates implemented under Clause 10.3.
- Train internal audit teams to evaluate both the strategic FSMS cycle and the operational HACCP cycle during routine internal audits.
Reference documents
- DS/EN ISO 22000:2018 Food safety management systems – Requirements for any organization in the food chain
- DS/ISO 22003-1:2022 Food safety – Part 1: Requirements for bodies providing audit and certification of food safety management systems
- DS/ISO 22003-2:2022 Food safety – Part 2: Requirements for bodies providing evaluation and certification of products, processes and services, including an audit of the food safety system
Manage this work in 4Auditee
Keep audit plans, problems, corrective actions and document versions in one place. See the records behind each change and decision.
Book a demo