HACCP without a folder nobody updates

In many kitchens, the food safety plan lives in a thick folder on a high shelf in the office. It was written when the venue opened, perhaps by a consultant, and it describes dishes that left the menu years ago, a walk-in fridge that has since been replaced and a team that has long moved on. Nobody reads it, nobody updates it, and when the inspector asks to see it, someone has to climb on a chair.

HACCP was never meant to be a folder. It is a way of thinking about food safety: where things could go wrong, how you stop them and how you know you have. Done well, it fits on a few pages, its daily part takes minutes, and the team uses it without thinking of it as paperwork at all.

This guide covers the principles of HACCP in plain terms, the four records that matter every day, how to keep them in minutes and how to keep the plan up to date as the menu and the kitchen change. Every venue and figure in it is an example.

HACCP, hazard analysis and critical control points, is a method for keeping food safe by finding the points where it could become unsafe and controlling them. It was developed for food production and is now the basis of food safety law in many countries, including for restaurants.

Its idea is simple. Rather than checking every plate at the end, you identify the few steps where a hazard can be prevented or removed, such as cooking, chilling and storage, and you control those steps carefully, every time.

HACCP ends up in a folder because it is often written once, by someone outside the kitchen, in language the kitchen does not use. The result is long, generic and hard to follow, so the team quietly keeps its own routine and the folder gathers dust.

The fix is to write the plan for your own kitchen, in your own words, and to keep the daily part so short that it becomes part of the routine. A plan the team recognises is a plan the team uses.

HACCP has seven principles. Work out what could go wrong. Decide where you can control it. Set a limit for each control. Check the limits. Decide what to do when a limit is missed. Check that the system works. Keep records.

In kitchen language: know the risks in each dish, know the steps where you stop them, know the numbers that matter, check those numbers, fix things when they go wrong, review it now and then and write down enough to prove it.

The hazards in a kitchen fall into a few groups. Biological hazards, such as bacteria that grow in food left warm. Chemical hazards, such as cleaning products. Physical hazards, such as glass, metal or packaging in food. And allergens, which are harmless to most guests and dangerous to some.

For each dish, or each kind of dish, ask which hazards apply. A cooked chicken dish carries the risk of undercooking and of bacteria growing if it cools slowly. A salad carries the risk of contamination from raw foods. Most dishes share a handful of hazards, which keeps the plan short.

A critical control point is a step where a hazard can be prevented, removed or reduced to a safe level, and where losing control would make the food unsafe. In most restaurants, the critical control points are the same few steps: receiving deliveries, chilled and frozen storage, cooking, cooling, reheating and hot holding.

Everything else, such as handwashing, cleaning and pest control, is essential too, but is usually managed through good everyday practice rather than as a critical control point. Separating the two keeps the plan focused on what matters most.

A critical limit is the number that separates safe from unsafe at each control point: a core temperature reached during cooking, a fridge temperature, a time within which hot food must be cooled. Each control point needs one, stated plainly.

Use the limits set by your local food safety guidance, and write them where the team will see them: on the fridge, by the probe, on the cooling checklist. A limit known only to the person who wrote the plan protects nobody.

Monitoring means checking each limit, at the right moments, and recording the result. Fridge temperatures checked at opening and closing, core temperatures probed when food is cooked, cooling times noted when food goes into the fridge.

The checks should be quick and part of the work itself. A probe by the stove and a sheet beside it make the cooking check a matter of seconds. A check that needs a walk to the office will be skipped on a busy night.

Corrective action is what the team does when a limit is missed: cook the food for longer, move food from a warm fridge to a working one, throw away food that was cooled too slowly, call the engineer. Write down the usual actions in advance, so nobody has to decide under pressure.

Record each corrective action with the reading that triggered it. A record that shows a problem and its fix is more convincing to an inspector than a record that never shows a problem at all.

Verification means checking that the system works. Once a week, a manager or the head chef looks through the records: are they complete, are the readings sensible, were problems dealt with? Once a year, or when something changes, the plan itself is reviewed.

Verification is what keeps the plan alive. A weekly look at the records takes ten minutes and catches gaps before they become a pattern.

Records prove that the system is working. They need to show what was checked, when, the result and who did it, and they need to be kept for a sensible period so an inspector can see the history.

Keep only the records that matter. A system that asks for twenty records a day will produce twenty incomplete records. A system that asks for the four that matter will produce four complete ones.

Four records carry most of the daily weight in a typical restaurant. Opening and closing checks, covering the basics of the kitchen. Fridge and freezer temperatures. Cooking, cooling and reheating temperatures for the dishes that need them. And delivery checks.

Each can be kept in a minute or two. Together, they show an inspector that the critical control points are controlled every day, which is most of what HACCP asks.

Opening and closing checks cover the things that must be right before service starts and after it ends: fridges at temperature, the hand wash basin ready, surfaces clean, food labelled and in date, nothing left out. A short list, ticked and signed each time, does the job.

Keep the list to a dozen items or fewer. Our guide to a kitchen operations checklist for every service covers what belongs on one.

Fridge and freezer temperatures should be checked and recorded at least once a day, usually at opening and closing. Record the reading, the time and the initials of the person who checked.

If a reading is above the limit, check again, move the food if needed and record what you did. Our guide to temperature records that take one minute covers how to keep these checks quick enough that they always happen.

Cooking, cooling and reheating are where most food safety risks lie. Probe large or risky items when they are cooked, and record the core temperature. Note the time hot food goes to cool, and check it is chilled within the limit. Reheat to the right temperature and hold hot food hot.

Not every dish needs a record every time. Many kitchens record a sample each service, plus every batch of the risky items, such as large joints, stocks and rice. Decide which, write it in the plan and keep to it.

Deliveries are the first control point. Check chilled and frozen deliveries as they arrive: the temperature, the condition of the packaging and the dates. Record the temperature of a sample and reject anything that fails.

The check should be quick enough to do while the driver waits. A probe, a clipboard and a habit of checking before signing make it routine.

Batch labelling, marking each batch of food prepared in the kitchen with what it is, when it was made and when it must be used by, links the records to the food itself. A sauce made on one day and used three days later should carry a label that shows both dates.

Labels make it easy to use the oldest food first, to throw away anything past its date and to trace a batch if a problem appears. Keep labels and pens by every fridge, so labelling is part of putting food away.

Allergens belong in the HACCP plan. For each dish, record which allergens it contains, and how the kitchen prevents cross-contact for guests who need it: separate boards, clean utensils, a careful check of the ticket.

Keep the allergen record current every time a recipe or supplier changes. Our guide to build an allergen matrix that stays correct covers how.

The plan is easier to keep when recipes are written down. A standard recipe card records the ingredients, the method and the critical steps, such as the cooking temperature and the cooling time, so the plan and the recipe agree.

When a new dish arrives, its recipe card shows where the hazards are and which control points apply. Our guide to write a standard recipe card your kitchen will use covers the format.

A useful HACCP plan for a typical restaurant fits on a few pages: the hazards, the control points, the limits, the checks, the corrective actions and the records. It does not need a page for every dish, because most dishes share the same steps.

Group dishes by how they are made: cooked and served hot, cooked and chilled, served raw, and so on. Each group shares its control points, so a new dish usually fits an existing group rather than needing a new page.

Some food safety agencies publish ready-made packs for small businesses, built on the principles of HACCP, with the checks and records already laid out. In England, for example, the agency's pack for caterers is widely used and accepted by inspectors.

A pack is a good starting point, as long as it is adapted to your own kitchen. Cross out what does not apply, add what is missing and keep the daily diary pages in use, because a pack that sits on a shelf is just another folder.

Records can be kept on paper or on a screen. Paper is quick, cheap and works with wet hands; a sheet on a clipboard by the fridge is hard to beat for a temperature check. A digital system can remind staff, flag missed checks and keep records tidy.

Choose whichever the team will actually use. A paper system filled in every day is far better than a digital one that nobody opens.

Dishes and ingredients bought in ready-made, such as desserts, sauces, bread or cooked meats, still belong in the plan. Their hazards are mostly handled by the supplier, but the kitchen controls how they are received, stored and served, and it needs to know what they contain.

Keep each supplier's product details, including allergens, and check them when a product or supplier changes. A dessert that switches to a new recipe with nuts in it, unnoticed, is exactly the kind of change a plan exists to catch.

Cleaning supports every control point. Surfaces, boards, utensils and probes that are not properly cleaned spread bacteria from raw food to cooked, and cleaning chemicals used carelessly become a hazard of their own.

The plan should say how surfaces and equipment are cleaned and disinfected, with which products, and how chemicals are stored away from food. The cleaning schedule, signed off as tasks are done, is the record that shows it happens.

A small kitchen with a short menu and two or three cooks needs the same principles and far less paper. One page for the hazards and control points, one sheet for the daily records and a weekly look at them may be all it needs.

What matters is that the plan matches the kitchen. A small café copying a hotel's plan will drown in records it does not need; one with a short plan of its own will keep every record it does.

Update the plan whenever something changes: a new dish with a new hazard, a new piece of equipment, a new supplier, a change to the kitchen layout. Note the change and the date in the plan itself.

Review the whole plan once a year, even if nothing seems to have changed. A short review often finds a dish that left the menu or a check that is no longer needed.

Every member of the kitchen team should know the plan: the control points, the limits for their section, the checks they are responsible for and what to do when something goes wrong. A short briefing for new starters, and a reminder when the plan changes, is usually enough.

Ask questions now and then: what temperature should this fridge be, how long can this cool before it goes in the fridge? Staff who can answer have understood the plan; staff who cannot need a reminder.

Inspectors judge how well a business manages food safety, and a working HACCP plan, with complete records, is the heart of it. A kitchen with a short, current plan and complete daily records gives the inspector confidence; a kitchen with a dusty folder and missing records does not.

Our guide to food hygiene rating: earning the top score covers the inspection itself and the easy losses that cost good kitchens the top score.

When something goes wrong, such as a fridge failing overnight or a guest becoming ill, the plan and its records show what happened. Follow the corrective actions, record what was done and review the plan to see whether anything should change.

Records that show a problem found and fixed are evidence of a system working. Records that show nothing, followed by a problem, suggest the system was not.

An invented bistro has a consultant's HACCP folder of eighty pages that nobody has opened in two years. The head chef rewrites it in four pages: three groups of dishes, five control points, the limits, the checks and the corrective actions. The daily records become four sheets on a clipboard by the walk-in: opening and closing checks, fridge temperatures, a cooking and cooling log and delivery checks.

Batch labels and pens go by every fridge. The manager reviews the clipboard every Monday and files the week's sheets. At the next inspection, the inspector reads the four pages in five minutes, finds the records complete and notes the plan as clear and well kept.

servearound holds no HACCP plan or food safety records: there are no temperature logs, delivery checks, cleaning schedules or batch labels in it, so those stay on the clipboard or in a tool made for them. What it does hold is the allergen information the plan relies on at service. Each dish carries its allergens, from the fourteen statutory groups and many more, its dietary tags and its ingredients, and the guest menu shows them, with filters and a reminder to tell the server about allergies.

Servers can add an allergy to an order or take an ingredient off a dish on the till, and allergies recorded on a guest's profile show on their booking. In the kitchen, the guest's allergies sit at the head of the ticket, removed ingredients show as "No" lines and each dish's allergens turn red when this guest is allergic to one. See point of sale and kitchen.

A method for keeping food safe by finding the steps where it could become unsafe and controlling them.

In many countries, yes: food businesses must have food safety procedures based on its principles.

A few pages for a typical restaurant, grouping dishes by how they are made.

Opening and closing checks, fridge and freezer temperatures, cooking and cooling temperatures and delivery checks.

Whichever the team will actually use every day.

Whenever something changes, and reviewed in full once a year.

Marking each batch of prepared food with what it is, when it was made and when it must be used by.

A manager or head chef, weekly, looking for gaps and problems dealt with.

HACCP is a way of thinking about food safety, not a folder: find the hazards, control the critical steps, set the limits, check them, act when they are missed, review the system and keep enough records to prove it. For a typical restaurant, the plan fits on a few pages, grouped by how dishes are made, and written in the kitchen's own words.

The daily part is four records kept in minutes: opening and closing checks, fridge and freezer temperatures, cooking and cooling, and deliveries, with batch labelling linking the records to the food. Review them weekly, update the plan when anything changes and train the team on their part, and both food safety and the food hygiene rating look after themselves.