The requirement that applies today
The fifth Codex principle, at step 10, is to establish the corrective action to take when monitoring shows a CCP is out of control. The current edition maps it to the hazard control plan, corrections and corrective actions.
ISO/DIS 22000:2026, Annex A 9, Codex principle 5 and step 10: establish corrective action.
What the draft does
Mapped in the current Annex A to 8.5.4, 8.9.2 and 8.9.3; the 2026 table is sold by ISO and not held here: The 2026 contents keep all three clause titles. For this row the inferred 2026 destination is 8.5.4.4, 8.9.2, 8.9.3; that reading comes from the clause titles, not from the published 2026 table.
Source: public contents and foreword at A.9, retrieved 2026-10-19.
Why this clause matters
The distinction between a correction and a corrective action is the difference between fixing the batch and fixing the system. The clause requires both, and the record has to show the product decision and the cause. The 2026 contents keep all three destinations.
Suggested evidence to discuss with your auditor
For A.9, these are the artefacts we suggest discussing with your auditor. The standard publishes no evidence list, so this is our reading, not a requirement.
- A correction and corrective action protocol for each CCP
- A worked deviation showing the hold, the evaluation and the release
- Evidence that the cause was addressed
Where systems usually fall short
- A correction recorded with no cause
- A release by someone without the stated authority
How to prepare
Take the last deviation and separate the correction from the corrective action on paper. An empty second column is the gap.
Dates
Cross-references
Source
Annex A, A.9. Current edition: ISO 22000:2018. Draft: ISO/DIS 22000:2026. Retrieved 2026-10-19. The full DIS text for A.9 is sold by ISO and not held here; the sources page lists what is.
Not legal advice; does not certify; our words, not the standard's, and the planning date is an estimate.