Food cooling temperature check: 6 ways to automate

What this is

This page covers food cooling temperature check as editable playground workflow templates on Pilla’s canvas. Open a version, tweak the steps, and try it with your team. You are choosing how much you need around the same cooling check: guidance, evidence, sign-off, or follow-up.

#1 - Simple log

Who it's for: Single-site kitchens where the chef logs cooling themselves. No second checker, just a need to prove hot food was chilled down fast enough.

What it is: A food cooling temperature check is a record of an item's temperature at the start and end of cooling. This version keeps it to the three things that belong to one check: what the item is, its temperature when cooling started, and its temperature when cooling ended. The three sit together in one box so each item reads as one check. Cool food as quickly as possible, then refrigerate at 8°C or below, using a method you've proved with a probe; the longer it sits in the danger zone, the more bacteria grow. Where cooling is a critical control point in your HACCP plan, this check is the monitoring record for it.

In practice: You cool a batch of gravy and a tray of rice for tomorrow in a single-site carvery. Log "Beef gravy", start 70°C, then after blast-chilling log end 6°C. One box per item, a clear record that each one cooled in time.

Why it works: The item name and both readings live in one box, so a cooling record can never be saved without saying what cooled and how far. That is what makes it traceable if a dish is later linked to illness.

Steps included:

• 1 grouped check (one box per item) holding: food item (text), temperature at start (number), temperature at end (number)
• Duplicate the box for each item cooled

#2 - With guidance

Who it's for: Kitchens with new starters or rota staff who don't all know by heart to cool as quickly as possible, then refrigerate at 8°C or below.

What it is: The basic check with a guidance note at the top. The note explains the danger zone (8 to 63°C), the rule to cool food as quickly as possible, then refrigerate at 8°C or below, using a method you've proved with a probe, and practical ways to do it: shallow trays, ice baths, or a blast chiller rather than leaving a deep pot on the side.

In practice: A busy event caterer runs this. A new commis sees the note, splits a deep tray of chilli into shallow ones to cool faster, logs start 60°C and end 7°C, and the record shows the cooling worked rather than guessing.

What it adds to the basic check:

1. The rule to cool as quickly as possible, then refrigerate at 8°C or below, and the danger zone are on screen at the moment of logging
2. New staff know the methods that cool food fast
3. A failed cooling time is recognised, not missed

Why it works: The guidance sits with the check, so staff see it as they log. It turns the head chef's standard into a prompt that is always on screen.

Steps included:

• 1 guidance note (cool as quickly as possible, then refrigerate at 8°C or below; the danger zone)
• 1 grouped check (one box per item): food item (text), temperature at start (number), temperature at end (number)

#3 - With a signature

Who it's for: Multi-site groups and production kitchens where someone signs off the day's cooling records and they have to stand up across sites.

What it is: The basic check plus a signature. The person logging signs to confirm every item cooled within time. For a cook-chill operation supplying several sites, that signature makes each kitchen accountable for its own cooling.

In practice: A cook-chill kitchen supplying 25 care homes logs every batch with start and end readings, then the head chef signs off the day. The food safety lead reviews any batch remotely, with the readings and signature both timestamped.

What it adds to the basic check:

1. A signature confirming every item cooled within time
2. Named accountability for each kitchen's cooling records
3. A record someone has put their name to

Why it works: A signature turns a set of readings into a record someone has committed to. With the readings, it is the evidence an auditor wants.

Steps included:

• 1 grouped check (one box per item): food item (text), temperature at start (number), temperature at end (number)
• 1 signature (sign-off)

#4 - With photo evidence

Who it's for: Kitchens under EHO scrutiny, or cooking ahead for vulnerable groups, that want to show proof rather than ask an inspector to trust the numbers.

What it is: The basic check plus a photo of each batch's probe reading. The end reading is the one that matters most, since it proves the food reached safe storage temperature in time; a photo of 6°C on the probe next to the chilled tray is proof, not a recollection.

In practice: A central production kitchen cooking for several care homes photographs the end-of-cooling reading on every batch. When a CQC inspector asked how they knew cook-chill food was safe, the photos answered it.

What it adds to the basic check:

1. A photo of each batch's probe reading, captured at the time
2. Proof that holds up to an inspector because the probe reading is in the photo
3. A visual record that ties each reading to a real batch

Why it works: Evidence taken in the moment is far stronger than numbers recalled later. The photo ties the cooling record to the actual batch and time.

Steps included:

• 1 grouped check (one box per item): food item (text), temperature at start (number), temperature at end (number)
• 1 photo of each batch's probe reading

#5 - With Pilla checking the photo

Who it's for: Kitchens where the probe photo gets taken but nobody looks at it. Multi-site groups where head office can't review every site's photos.

What it is: A photo-checked cooling record is the basic check plus a photo of each batch's probe reading that Pilla reviews the moment it's saved. Pilla answers one question about that photo, set by you: does the photo show the batch cooled to 8°C or below? A single named spot gives an AI something clear to judge. If the answer is no, Pilla posts what it spotted to the team chat, so the problem gets fixed before everyone leaves.

In practice: A three-site catering group closes at 6pm. A cook takes a photo of the probe reading for each chilled batch as always. Pilla reads the photos: clear 6°C reading on the beef, clear 5°C on the rice. Verdict yes, and nothing changes. On a rushed Friday, one photo shows 11°C on the pork. Pilla answers no and posts the reason to the team chat ("The photo shows the batch at 11°C, above the 8°C target"). The cook re-chills it and retakes the photo while still in the kitchen.

What it adds to the basic check:

1. A photo of each batch's probe reading that gets checked the moment it's saved, so problems are caught before anyone leaves
2. A team chat message with Pilla's reason the moment a photo fails the check
3. The manager stops being the only person who ever looks at the photos

Why it works: The check happens in the seconds between the photo being taken and the cook leaving. That is the only moment the problem is still cheap to fix. Reviewing photos the next morning only records that cooling failed; catching a gravy tray still warm at 6pm gets it fixed by the time everyone leaves.

Steps included:

• 1 grouped check (one box per item): food item (text), temperature at start (number), temperature at end (number)
• 1 photo of each batch's probe reading
• 1 Pilla decision (judges the photo against your question)
• 1 Pilla action (posts to the team chat if the photo fails the check)

#6 - With a team alert if checks are missed

Who it's for: Cook-chill kitchens with a target time for signing off daily cooling records. Groups where the records sometimes slip to the next day and you want same-day accountability.

What it is: A same-day alert is the basic check plus a Pilla action set to the workflow's end time. If the cooling records aren't signed off by the end of the shift, Pilla posts a message in the Pilla team chat so the outstanding records get completed that night rather than left for the morning. It watches the end time, so it catches the check that quietly got forgotten, and a half-finished round raises its own alert.

In practice: A central production kitchen supplies 15 care homes and cooks in batches across the day. Each batch needs a cooling record with start-and-end temperatures. The head chef is meant to sign off all cooling records by 5pm. On a busy Tuesday, three batches cooled in the morning but the records are still unsigned at 5pm because the chef is focused on evening prep. Without this version, the records sit unsigned until the next morning and overnight food safety records are incomplete. With it, Pilla posts at 5pm so the chef knows to catch the three unsigned records before leaving.

What it adds to the basic check:

1. A message in the team chat if the cooling records aren't signed off by end of shift
2. A catch for the records that got forgotten mid-shift, and a half-finished round raises its own alert.
3. A record of when the sign-off should have happened, next to when it was done
4. The manager finds out that evening, not from the next morning's incomplete trail

Why it works: The alert is tied to the shift end time, so an unsigned record raises its own hand. Nobody has to spot that the records are missing; the deadline does.

Steps included:

• 1 grouped check (one box per item): food item (text), temperature at start (number), temperature at end (number)
• 1 Pilla action (posts to the team chat if the cooling records aren't signed off by end of shift)

How to pick the right version

You don't need to know our product to choose. Every version here is the basic check plus one addition. Pick the additions your team needs, and skip the rest.

Do other people log cooling, or do you do it yourself?

If you log it yourself and know the rule cold, a plain record is enough: #1. The moment anyone else does it, put the rule on the screen: #2.

Does someone need to sign off the records?

In one kitchen, the record speaks for itself. Across sites, an auditor wants to know who confirmed each day's cooling. If no sign-off is needed, skip this one. If you run more than one site, #3 adds a signature.

Do you need photo proof?

A record says the work was done; a photo shows it. If you want visual proof, #4 adds a photo of each batch's probe reading.

Does anyone look at the photos?

If a manager reviews every photo, #4's record is enough. If photos get taken and filed unseen, #5 has Pilla check each one as it's saved, and tell the team chat when something's wrong.

Do the records need to be signed off by a set time, and do they sometimes slip to the next day?

If your kitchen has a target time for sign-off and the records sometimes get left unsigned overnight, #6 posts a message to the team chat if the records aren't completed by your deadline. If the records always get signed off on time, #1 to #5 are enough.

Need more than one addition? Open the version with the addition that matters most in the playground and add the others as steps.

Related workflows

• Cooked food temperature check - proving food reached a safe temperature when cooked
• Fridge temperature check - where cooled food goes once it's safe
• Food probe accuracy test - making sure the probe you check with reads true

Conclusion

Slow cooling is invisible at the time and dangerous later. A record of the start and end temperatures is the only way to prove food moved through the danger zone fast enough. Every version above is the same simple log plus one addition: guidance, a signature, a photo, an AI check on the photo, or a deadline alert. Pick the ones you need and combine them in the playground.

More additions are coming in future refreshes, like flagging a failed cooling time to the manager by name and pulling every kitchen's records into one daily report. Those need more review time and will land separately.