Document control
Versions, approvals and distribution with read receipts.
Software for ISO 22000
The ISO food safety standard: prerequisites, a HACCP plan with CCPs and OPRPs, traceability and emergencies in a certifiable, audited system.
ISO 22000 is the certifiable international standard setting out the requirements for a food safety management system for any business in the food chain, from feed producers to distributors: it combines the HACCP principles of the Codex Alimentarius with prerequisite programmes and with the management structure shared by ISO 9001 and ISO 14001. The current edition is the 2018 one, amended in 2024 to cover climate change, and it is the foundation of FSSC 22000, the scheme that adds the ISO 22002 series prerequisites and requirements of its own and which, unlike the standard on its own, is recognised by GFSI.
Versions, approvals and distribution with read receipts.
Publish and version documents by connecting to OneDrive, Google Drive or SharePoint, without duplicating folders.
Annual program, checklists per standard, findings linked to actions.
Root cause, action, owner, deadline and effectiveness check.
Process objectives fed with real operating data.
A register of legal and other requirements, with validity and compliance evaluation per standard.
Root cause, action, owner, deadline and effectiveness check, all linked to the nonconformity.
Improvement opportunities with an owner and tracking, beyond just fixing what already failed.
A pre-built report with indicators, audits and nonconformities, ready for the meeting.
Hazards by raw material and step, with their acceptable level and the category of each control measure.
Critical limits and action criteria with recorded monitoring and a correction opened as soon as there is a deviation.
From the raw material batch to the customer who received it, with the mock recall and its response time.
Evaluation criteria, performance monitoring and re-evaluation of every external provider.
Requirements covered
Standards covered
Templates and records
Which clause of ISO 22000 calls for each record, which fields it needs, a completed example and what the auditor usually flags.
How to document ISO 22000 prerequisite programmes: selection, responsibilities, monitoring and verification…
How to carry out the ISO 22000 hazard analysis: identification by step, acceptable level, significance…
How to document validation of ISO 22000 control measures before applying them: method, evidence, outcome and…
What the ISO 22000 hazard control plan must include for each CCP and OPRP: limits, action criteria…
What the ISO 22000 record for each CCP and OPRP must capture: batch, reading, actual time, signature and…
How to plan and record verification of PRPs and the HACCP/OPRP plan under ISO 22000 (8.8): activities…
How to record product leaving an out-of-control CCP or OPRP under ISO 22000: holding, evaluation for release…
How to run and record a traceability and mock recall exercise under ISO 22000 (8.3 and 8.9.5): batch, time…
How to prepare the ISO 22000 emergency plan: scenarios that affect food safety, response, communication…
How to evaluate, select and re-evaluate suppliers under ISO 22000 (7.1.6): criteria, data sheets…
How to record nonconformities and corrective actions under ISO 22000 (8.9.3 and 10.1): correction, root…
Vocabulary
Frequently asked questions
The edition in force is ISO 22000:2018 (2nd edition), with Amd 1:2024; the 3rd edition is at draft stage (ISO/DIS 22000). When the issuing body publishes a new one, a transition period opens; once it closes, certificates issued against the previous edition stop being valid.
Yes. Your existing system — processes, documents, records, audit history — is loaded in and kept alive from day one. Nothing needs redesigning and the certification cycle does not restart.
Yes, provided they are traceable, controlled and able to show who did what and when. No standard requires paper; every standard requires reliable evidence, and a properly controlled electronic record provides it better than a folder.
Yes, and that is the sensible route. The common Annex SL structure lets a single integrated system share the process map, document control, internal audits, nonconformities and indicators between ISO 22000 and the rest, leaving only the standard-specific parts separate.
It depends on the starting point. An organisation already working with written procedures is usually ready in two or three months; one starting from scratch needs longer. The bottleneck is rarely the tool — it is the availability of the people who know the processes.
It is migrated. Existing procedures, forms and records are loaded with their version and approver, so the history is not lost and the system starts with the memory the organisation already had.
Yes. They are given read-only access with a defined scope and an expiry date. It is more comfortable for both sides than preparing a folder of screenshots and exports.
A major one compromises the system's ability to meet a requirement — a required process missing altogether, systematic failure, or a failure affecting the product — and usually blocks certification until it is closed. A minor one is a specific lapse resolved with an action plan.
Yes, from the data the processes themselves generate. That is the difference between a dashboard that reflects what is happening and a spreadsheet somebody fills in the week before the management review.
Yes. The model is multi-company and multi-site: what makes sense to share is shared, and what belongs to each location stays separate — including the certificate scope where it differs.
We'll show you the module running with data similar to yours.
Keep exploring
Free guide to ISO 22000:2018: prerequisites, hazard analysis, the HACCP/OPRP plan, traceability and…
HACCP is mandatory under Regulation (EC) 852/2004; FSSC 22000 is a voluntary certification built on ISO…
ISO 22000 plus sector prerequisites and additional scheme requirements, in a single structure.
A living HACCP plan: identified hazards, critical control points with limits, and monitoring logged for…
Sources
References to the official text in force. If a standard is revised, this page is updated and the review date says so.
Kimobox is a software for ISO 22000 that digitizes the requirements of the standard: hazard analysis with acceptable levels and categorisation as ccp or oprp, hazard control plan with critical limits and action criteria, prerequisite programmes based on the iso 22002 part for your sector, traceability tested with mock recalls, and documented product withdrawal, with full traceability and evidence ready for the auditor.
The platform lets you run an integrated management system that combines ISO 22000 with other ISO standards and sector protocols, sharing the process map, document control, internal audits, non-conformities and KPIs.