How I Use the Blast Chillers Template with Customers in Pilla
Cooling is where most temperature control failures happen. I've reviewed food safety management systems in kitchens that spend thousands on blast chillers and still get it wrong, usually because there's no written procedure, no cooling records, and no contingency plan for when the unit breaks down. The blast chiller sits in the corner doing its job, but nobody has documented what "doing its job" actually means.
The gap is rarely the equipment. It's the gap between having a blast chiller and having a system around it. That's what this article covers. I'll walk you through what your blast chiller policy needs to include, give you a ready-made template you can edit for your operation, and explain the bits that matter most when an EHO checks your cooling records.
Key Takeaways
- What is a blast chiller policy in food safety? A blast chiller policy covers time and temperature rules for rapid cooling, food size and volume limits, recording requirements, allergen cleaning, and breakdown contingencies. It's the control that stops spore-forming bacteria like Clostridium perfringens and Bacillus cereus from multiplying during cooling
- Why do you need a blast chiller policy? Regulation (EC) 852/2004 requires food businesses to have adequate procedures for cooling food rapidly. Your EHO will check cooling records during inspection, and missing or incomplete records are one of the fastest ways to lose marks
- How do you set it up in Pilla? Use the knowledge hub template below, edit it to match your operation, and share it with your team through the app so everyone has access and you can track who's read it
- How do you automate the follow-up? Set up Poppi to chase staff who haven't acknowledged the policy and flag when it's due for review
Article Content
Understanding What's Required of You
A blast chiller is not a fridge. A fridge holds temperature. A blast chiller reduces it rapidly, pulling hot food down to safe storage temperature before bacteria have time to multiply. If your operation cooks food in advance, this is the piece of equipment that stands between safe food and a food poisoning outbreak.
The risk is specific. Certain bacteria, Clostridium perfringens and Bacillus cereus in particular, form spores that survive cooking. Those spores germinate as food cools through the danger zone. The longer food sits between roughly 63°c and 8°c, the more time those spores have to become active bacteria, multiply, and produce toxins. Some of those toxins survive reheating. Once they're in the food, you can't cook them out.
That's why rapid cooling isn't optional. It's the only control that works. The 90-minute rule exists because it's the maximum window that limits spore germination to safe levels. Food goes into the blast chiller within 30 minutes of cooking and reaches below 3°c (or at least below 5°c) within 90 minutes total.
The legal basis is Regulation (EC) 852/2004, which requires food business operators to have adequate procedures for cooling food rapidly. In practice, your EHO will ask to see cooling records: start time, start temperature, finish time, finish temperature. Four data points per batch. If those records are missing or incomplete, you'll lose marks. I've seen businesses with perfectly good blast chillers score badly on inspection because they couldn't prove they were using them properly.
Beyond the records, an EHO will look at whether your policy covers food size limits, volume limits for liquids, probe sanitisation, allergen cleaning between batches, and what you do when the blast chiller breaks down. Most policies I review cover the 90-minute rule but miss at least two of those other areas.
Setting It Up as a Knowledge Hub Entry
I've built a blast chiller template in Pilla covering time and temperature rules, food size and volume limits, date labelling, maintenance, cleaning and allergen procedures, probe hygiene, and corrective actions. It gives you a structured starting point, but you need to edit it to match your specific operation.
In the knowledge hub, create a new entry and tag it with "Food Safety Management System". Use the same tag across all of your food safety policies so they are grouped together and Poppi can track them as a set. Assign the entry to all teams so that everyone in the business can access it.
The template is designed to be edited, not just filed. Read through every section. If your unit doesn't have an inbuilt probe, delete that section. If you have specific manufacturer instructions about siting or vent clearance, add them. If your operation regularly cools batches larger than 10 litres, your corrective actions section needs to reflect that. The EHO wants to see that your policy matches what actually happens in your kitchen.
A blast chiller is a special unit designed for the rapid cooling of food from a high temperature to a low temperature suitable for the placement of these foods into a refrigerator or freezer.
Staff must follow the safety points below in order to achieve a consistent level of food safety.
Safety points
Time and temperature
- Foods should be placed into the blast chiller within 30 minutes of cooking, then chilled down in the unit within 90 minutes before placing into a refrigerator or freezer
- The length of time the food takes to chill should be recorded including the start and finish time of cooling and the start and finish temperature of the food must also be recorded
- Staff should aim for final cooling temperatures of below 3°c if possible but below 5°c is acceptable when the 90-minute maximum cooling time is reached
- Staff should understand that long cooling periods can potentially allow spores to germinate resulting in vegetative bacteria growing and possibly forming toxins in the food
Staff training
- Blast chillers must only be operated by trained staff who must follow the manufacturer's instructions for safe use
Manufacturers recommendations
- Blast chillers should be sited in accordance with manufacturers recommendations. They should be sited for ease of use and to facilitate cleaning or maintenance work
Date labelling and covering food
- Once cooked food has been cooled appropriately it must be covered appropriately and date labelled with a use by date of three days inclusive of the day of cooking and cooling
- E.g. Cook and cool Tuesday, use by end of service on Thursday
Maintenance
- Blast chillers must be regularly checked and maintained paying particular attention to vents that may become blocked and will significantly affect the unit's ability to cool foods quickly
- Contingency plans should be considered regarding how foods will be cooled in the event of blast chiller breakdown
Cleaning
- Blast chillers must be cleaned frequently as they come into regular contact with high risk foods. They will also come into contact with allergens, therefore frequent cleaning and disinfection should take place, in the case of the handling of allergens both before and after use. Any cleaning should be included on the cleaning schedule
Considerations regarding food size and shape
- Food items to be cooled should not exceed 2.5kg (6lb) in weight and 50mm (2 inches) in thickness or height
- Large poultry carcasses should be broken down into sections not exceeding these sizes and measurements
- It is also good practice to ensure that the depth of foods in containers does not exceed 50mm
Inbuilt probe
- For any unit that has an inbuilt probe, this must be cleaned and sanitised before every use
Food volumes
- It is advisable not to cook more than 10 litres of liquid and bulk volume foods, such as stews, gravy and pie fillings at any one time
- The capacity of the blast chiller should not be exceeded
- Ensure enough time has elapsed for cooling before beginning the next batch of food
Corrective actions
- Arrange alternative methods of cooling foods, in the event of a fault or breakdown of the blast chiller
- Call an engineer in the case of a fault or breakdown
- Food that has not been labelled correctly, consider discarding
- Discard food that has not been cooled correctly or safely
- Cook smaller portions or volumes to help in the quicker more efficient cooling of foods
- Prepare in advance and allow adequate time
- If staff do not follow the safety points retrain them and give extra supervision until competency is shown
Record keeping
- Record start / finish cooling times and start / finish temperatures in the daily kitchen records
- Record any instances of breakdowns any corrective actions taken and any alternative cooling methods employed
- Record any contraventions of the above safety points and any corrective actions taken
- Record any training or retraining undertaken
This is a preview of the template. In Pilla, you can edit this to match your business.
What I'd want to see when reviewing this:
The time and temperature section is the core of the entire policy. I'd want to see the two rules stated clearly: 30 minutes from cooking to blast chiller, 90 minutes total cooling time. I'd also want to see the recording requirement spelled out, because this is where most businesses fall down. Start time, finish time, start temperature, finish temperature. Four fields, every batch, no exceptions. Without those records, you have no evidence that cooling was done safely.
The food size section matters more than people think. A whole chicken or a deep pot of stew won't cool within 90 minutes, no matter how good your blast chiller is. Heat has to travel from the centre to the surface before the unit can remove it. I'd want to see the 2.5kg weight limit and 50mm depth limit stated clearly, and I'd want the policy to say that large items must be broken down before cooling.
Common mistakes I see:
The biggest gap is the corrective actions section. Most policies say "use the blast chiller" but don't say what happens when it breaks down. I've walked into kitchens mid-service where the blast chiller has failed and nobody knows what to do. The contingency plan needs to be written down before you need it: ice baths, shallow containers, stirring, temperature monitoring every 15 minutes.
The cleaning section often says "clean regularly" without addressing allergens specifically. Blast chillers come into contact with every allergen in your kitchen. If you've just cooled a batch containing nuts and then cool a nut-free dish without cleaning the unit, that's cross-contamination. The template covers cleaning and disinfection before and after allergen-containing batches, and I'd want to see that reflected in your cleaning schedule.
The recording requirement is listed in the template, but I still find businesses that don't record cooling times. They cool the food correctly but don't write it down. To an EHO, food without a cooling record is food without evidence of safe cooling. It's the difference between doing it right and being able to prove you did it right.
Automate the Follow-Up with Poppi
Writing the policy is one thing. Making sure your team has actually read it is another. Poppi can handle the chasing so you don't have to.
If you mark the knowledge hub entry as mandatory, Poppi will track who's read it and who hasn't. You can set up automations to chase staff who are behind, notify managers when someone completes the policy, and get a regular report showing where the gaps are.
Here are three automations I'd set up for any knowledge hub policy:
Tom, you have 2 overdue policies to read and acknowledge
Overdue training reminders
Automatically chase team members who have mandatory policies they haven't read yet. Poppi sends the reminder so you don't have to.
Tom, you have 2 overdue policies to read and acknowledge
Emma has completed a mandatory policy
Video completion alerts
Get notified when a team member finishes reading or watching a policy, so you can track progress without chasing.
Emma has completed a mandatory policy
Training Report: 87% team completion. Tom and Sarah behind on 2 mandatory policies, due 3 days ago.
Training gap analysis
Get a regular AI report showing which team members are behind on mandatory policies and where the gaps are across your team.
Training Report: 87% team completion. Tom and Sarah behind on 2 mandatory policies, due 3 days ago.