Reviewing and Updating Your Food Safety Program

Review your food safety program at least once a year, and again whenever something material changes, such as a new menu item, new equipment, a new supplier, a process change, or a recurring problem or complaint. A review checks that every hazard, control, monitoring step and record still matches how you actually operate. Keep dated versions so you can prove the program is current and controlled. Confirm any documented review frequency with your state or territory regulator and local council. Key takeaways: Review the whole program at least annually, and again whenever a material change happens.. Common triggers: new menu items, new equipment, new suppliers, process changes, complaints, recalls, or a failed audit.. A review confirms that hazards, controls, critical limits, monitoring and records still match how you really operate.. Use version control: date every version, note what changed and why, and keep superseded copies.. Retrain staff on any changes and record that the retraining happened.. Review triggers at a glance: Trigger, What to review. Annual date reached — Full program, all sections and supporting programs. New or changed menu item — Hazards, controls, critical limits, monitoring, allergens. New or replaced equipment — Control capability, calibration, cleaning, monitoring points. New supplier or ingredient — Supplier approval, receiving controls, storage, allergens. Process or layout change — Process flow, cross-contamination controls, monitoring. Complaint, illness, recall or failed audit — The failed control, root cause, corrective actions. Why a food safety program has to be a living document A food safety program (sometimes built on HACCP principles) is only useful if it describes what your business actually does today. Menus change, equipment is replaced, suppliers come and go, and staff turn over. If the document still describes last year's operation, the controls on paper stop protecting the food coming out of your kitchen, and an auditor or environmental health officer can quickly see the gap. Under the Australia New Zealand Food Standards Code, businesses that are required to keep a food safety program are generally expected to keep it current and effective. Treat the program as a living document that is reviewed on a schedule and refreshed whenever the operation shifts, rather than a folder that is written once and forgotten. How often to review: the annual baseline Set a fixed, recurring date for a full review of the whole program so it never slips. An annual full review is a sensible baseline for most food businesses, but your required frequency and the specific rules for your business type can vary by state and territory and by the class of food business you operate. Some regulators or standards specify a minimum review frequency or require review after particular events. Confirm the exact requirement with your state or territory regulator and local council. A full review means working through every section, not just skimming: process steps, identified hazards, control measures, critical limits, monitoring, corrective actions, verification, records and supporting programs such as cleaning, pest control and supplier approval. Diarise the annual review so it happens on the same date each year.. Review the entire program, including supporting prerequisite programs.. Check that monitoring records from the past year actually match the controls described.. Confirm your minimum review frequency with your regulator and council.. Change triggers: when to review before the annual date You should not wait for the annual date if something material changes. Any change that could introduce a new hazard, remove or weaken a control, or change how food flows through your business is a trigger for an out-of-cycle review of the affected part of the program. Update the relevant section, check whether other sections are affected, and retrain staff on the change. The most common triggers are new or changed menu items, new or replaced equipment, new suppliers or ingredients, changes to your process or layout, changes to who your customers are, and problems that reveal a control is not working. New or changed menu items, especially raw, high-risk, or allergen-containing dishes.. New or replaced equipment, such as a different fridge, blast chiller, vacuum sealer, or cook line.. New suppliers, new ingredients, or a change in how food is delivered or stored.. A change in process, workflow, or premises layout.. Serving a new vulnerable customer group (for example, a shift toward aged care, childcare, or hospital catering).. A recurring complaint, a customer illness report, a product recall, a failed audit, or a repeated corrective action.. New menu items and new equipment: worked examples A new menu item can change your whole hazard picture. Adding a raw or lightly cooked dish, a cook-chill item, sous vide, a house-made sauce, or a new allergen means new hazards, new critical limits, and possibly new monitoring. For example, introducing a cook-chill process means you now need controls for cooking (a core temperature such as 75°C, or an equivalent time-temperature combination), rapid cooling, cold storage at 5°C or below, and clear use-by dating. Document those controls before the dish goes on the menu, not after. New equipment can change how you meet an existing control. A replacement fridge, a new probe thermometer, or a different oven may need recalibration, new cleaning instructions, and updated monitoring points. Where a piece of equipment is central to a control, confirm it can reliably hit and hold the target temperatures and reflect that in the program. Map the new item or equipment against your existing process flow.. Identify any new hazards and add the controls, critical limits and monitoring needed.. Update cleaning, calibration and record templates to match.. Trial and verify the new control before relying on it in service.. What a review actually checks A meaningful review is more than a signature on the front page. Work through the program and confirm each element is still accurate, still adequate, and actually being followed. Check that the process description matches what happens on the floor, that all significant hazards are captured, that control measures and critical limits are current and based on established figures, and that monitoring and corrective-action records show the controls are working in practice. Look for drift: places where staff have quietly changed how they do something without the document catching up. Also confirm your supporting programs, contact details, supplier list and staff training records are up to date. Does the written process match the real process, step by step?. Are all significant hazards identified, with suitable controls and critical limits?. Do monitoring records exist, and do they show controls being met?. Were corrective actions taken and recorded when limits were breached?. Are cleaning, pest control, calibration and supplier-approval programs current?. Are staff trained on the current version, with training recorded?. Version control: proving the program is current Version control is what turns a pile of edits into a controlled, defensible document. Every version of the program should carry a version number or date, the date of the last review, the name of the person who reviewed or approved it, and a short summary of what changed and why. Keep superseded versions rather than overwriting them, so you can show the history if an auditor asks. Make sure only the current version is in use on the floor and that old printouts are removed. Whether you keep the program on paper or in a digital system, the same principles apply: one clear current version, a visible review date, and a traceable change history. Give each version a number or date and show the last-reviewed date on the front.. Record who reviewed or approved each version.. Keep a change log: what changed, why, and when.. Archive superseded versions; remove old copies from the workplace.. Make sure staff can only access the current, approved version.. Closing the loop: retraining and verification A change to the program only protects food once the people doing the work understand it. After any update, brief or retrain the affected staff, and record that the retraining happened and who attended. Then verify, after a short period, that the new control is actually being followed and is working, by checking records and observing the task. This closes the loop between changing the document, changing behaviour, and confirming the change is effective. The food safety supervisor typically drives this process, but responsibility for keeping the program current sits with the business. Checklist: Annual review date is diarised and the last review actually happened on time.. Written process flow matches what staff do on the floor.. All significant hazards have current controls and critical limits.. Monitoring and corrective-action records exist and show controls being met.. Supporting programs (cleaning, pest control, calibration, supplier approval) are current.. Every version has a version number, review date, approver and change summary.. Only the current version is in use; superseded versions are archived.. Staff are trained on the current version, and training is recorded.. New controls have been verified as effective after implementation.. Common mistakes: Signing off a review without actually walking the process and checking records.. Updating the menu or equipment but leaving the program describing the old operation.. Overwriting the program so there is no history of what changed or when.. Leaving old printed versions on the floor alongside the new one.. Changing the document but never briefing or retraining the staff who do the work.. Copying generic temperatures or controls that do not match your actual process..