Version history: using it for more than undoing mistakes
Version history answers who changed what and when, not just how to get an earlier draft back. How to read it, what it does not cover, and how long it is kept.
A HACCP plan is only as good as the records under it. Most fail inspection not because the hazard analysis was wrong, but because nobody can show what the fridge read on a Tuesday in March.
A HACCP plan is the written food safety plan a food business produces by working through the seven principles of hazard analysis and critical control points: identify the hazards, decide which steps in the process are critical to controlling them, set limits at those steps, monitor them, say what happens when a limit is breached, verify the whole thing works and keep the records that prove it. It is required, in some form, of most businesses that handle food, and it is the document an inspector asks for first.
The plan itself is usually the easy half. What businesses fail on is the last principle — the records. A beautifully reasoned analysis with a gap in the temperature log for six weeks is a worse position than a plain plan with complete records, because the plan describes intent and the records are the only evidence of practice.
The single most common weakness is a limit written as "cook thoroughly" or "chill quickly". A critical limit is a value a person can read off an instrument and act on: a core temperature, a time, a pH, a concentration. If it cannot be measured at the moment the step happens, it is not a critical limit, and the control point is not being controlled — it is being hoped about. The numbers themselves come from your legislation, your process authority or published guidance for your product, not from a template.
Write the plan for the person doing the monitoring. The chef checking a probe at the end of a shift is the reader, not the auditor. If a step cannot be understood by that reader in one go, it will be recorded as compliant regardless of what actually happened.
Kitchens have a small number of genuinely critical points — cooking, cooling, hot holding, reheating, and the storage temperatures around them — and a long list of prerequisites that are not critical control points at all: cleaning, pest control, supplier approval, personal hygiene, allergen separation. Small operations lose weeks by treating every prerequisite as a control point, generating monitoring nobody can sustain, and then abandoning the whole thing. The right shape for a kitchen is a short plan with a handful of measured points and a set of prerequisite programmes running underneath it. Menu changes are the trigger to revisit it, and so is a new supplier or a new piece of equipment.
Daily checks, corrective actions, calibration, training, supplier documentation and reviews all have to be retrievable on the day somebody asks. Ettex Docs holds the plan itself with version history, so what was in force at the time of an incident is not a matter of opinion; Ettex Forms collects the daily checks where they happen, with the value typed once rather than copied from a clipboard later; and Ettex Records keeps the log, the corrective actions and the supplier paperwork as one file per site.
Being direct about what this is not: we are not food safety software. There is no probe integration, no temperature telemetry, no pre-written hazard library and no certification. Your critical limits and whether your plan meets the law where you operate are matters for your food safety authority, your guidance documents and, above a certain scale, a consultant — not for a document tool.
Conduct a hazard analysis, determine critical control points, establish critical limits, establish monitoring, establish corrective actions, establish verification, and establish documentation and record keeping.
Most jurisdictions require food businesses to have food safety procedures based on HACCP principles, with simplified approaches allowed for small operations. The exact obligation depends on where you operate and what you handle.
A step where control is essential to prevent or reduce a hazard to an acceptable level, and where no later step will correct a failure. Cooking and chilling are typical; cleaning usually is not.
At least annually, and whenever the process, menu, equipment, supplier or product changes — and after any incident that revealed a gap.
Version history answers who changed what and when, not just how to get an earlier draft back. How to read it, what it does not cover, and how long it is kept.
Business succession planning decides who takes over ownership, how it is valued and funded, and when. The questions owners avoid, and the documents that make the answer real.
AGM meeting minutes evidence that the annual general meeting was properly held and what it resolved. What has to appear, what should be left out, and how long to keep them.