Document control
Versions, approvals and distribution with read receipts.
Software for HACCP
A living HACCP plan: identified hazards, critical control points with limits, and monitoring logged for every batch.
HACCP (Hazard Analysis and Critical Control Points) is a preventive system that has been mandatory in the European Union since Regulation (EC) 852/2004, whose article 5 requires every food business operator to apply procedures based on its principles. Its methodological reference is the Codex Alimentarius, revised in 2020, which organises it into seven principles deployed across twelve application steps.
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.
Critical limits with an owner and monitoring per batch.
From the raw-material batch to the delivered product, in minutes.
Hazards identified by process and product with their risk assessment.
Critical limit deviation with an immediate corrective action logged.
Requirements covered
Standards covered
Templates and records
Which clause of HACCP calls for each record, which fields it needs, a completed example and what the auditor usually flags.
How to document the HACCP preliminary steps: team, product description, intended use, flow diagram and its…
How to fill in the HACCP hazard analysis: biological, chemical, physical and allergen hazards by step…
How to document which steps are critical control points: decision tree, justification of each answer and the…
The chart that summarises the HACCP plan: each CCP with its hazard, critical limit, monitoring, corrective…
What monitoring of a critical control point must record under HACCP: what is measured, how, how often, by…
What to record when a CCP goes outside its limit: deviation, product affected, decision on the batch, cause…
How to document periodic HACCP verification: record review, calibrations, testing, internal audits and…
How to draw up the cleaning and disinfection plan Regulation 852/2004 requires: what, how, with what, how…
How to document the pest control Regulation 852/2004 requires: bait station map, inspections, treatments…
How to document the hygiene training Regulation 852/2004 requires for food handlers: content by role…
What data food traceability requires under Regulation 178/2002: supplier, customer, product, quantity, batch…
Frequently asked questions
The edition in force is Codex Alimentarius CXC 1-1969, 2020 revision. 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 HACCP 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
The ISO food safety standard: prerequisites, a HACCP plan with CCPs and OPRPs, traceability and emergencies…
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…
A free learning path on HACCP: the seven Codex Alimentarius principles explained with practical examples and…
Kimobox is a software for HACCP that digitizes the requirements of the standard: hazard analysis by process and product, ccps with critical limits and an owner, monitoring and verification logged per batch, corrective actions when a critical limit is breached, with full traceability and evidence ready for the auditor.
The platform lets you run an integrated management system that combines HACCP with other ISO standards and sector protocols, sharing the process map, document control, internal audits, non-conformities and KPIs.