4 ways to automate food cooling temperature checks

#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. The standard is to cool food from 63°C to 8°C or below within 90 minutes; the longer it sits in the danger zone between those temperatures, the more bacteria grow.

Available on: Basic.

In practice: A single-site carvery cooks a batch of gravy and a tray of rice to cool for tomorrow. The chef logs "Beef gravy", start 70°C, then after blast-chilling logs 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

When to upgrade:

1. Rota staff are logging cooling and don't all know the 90-minute rule
2. Your EHO wants proof, not just typed numbers
3. You run more than one site and want a named sign-off

#2 - With guidance

Who it's for: Kitchens with new starters or rota staff who don't all know the 90-minute rule by heart.

What it is: The simple log with a guidance note added to the box. The note explains the danger zone (8 to 63°C), the target of cooling to 8°C or below within 90 minutes, and practical ways to hit it: shallow trays, ice baths, or a blast chiller rather than leaving a deep pot on the side.

Available on: Standard.

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 previous template:

1. The 90-minute rule and the danger zone are on screen at the moment of logging
2. New staff know the methods that actually cool food fast
3. A failed cooling time is recognised, not missed

Why it works: The guidance sits in the same box as the readings, 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 grouped check (one box per item): food item (text), temperature at start (number), temperature at end (number)
• 1 guidance note in the box (the 90-minute rule and the danger zone)

When to upgrade: When typed numbers are no longer enough and you want photo proof of the probe reading (Cooling #3), or a named sign-off for an audit trail (Cooling #4).

#3 - 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 guided check plus a photo of the probe reading next to the food. 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.

Available on: Standard.

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 previous template:

1. A photo of the probe reading next to the food, captured at the time
2. Proof that holds up to an inspector, not just numbers
3. A visual record that ties the reading to a real item and 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 item and time.

Steps included:

• 1 grouped check (one box per item): food item (text), temperature at start (number), temperature at end (number)
• 1 guidance note in the box (the 90-minute rule and the danger zone)
• 1 photo in the box (the probe reading)

When to upgrade: When the records need a named, dated sign-off so an audit can see who confirmed them (Cooling #4).

#4 - With photo and 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 photo 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.

Available on: Standard.

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

What it adds to the previous template:

1. A signature confirming every item cooled within time
2. Named accountability for each kitchen's cooling records
3. A complete record (readings, photo, signature) an auditor treats as best practice

Why it works: A signature turns a set of readings into a record someone has put their name to. With the photo and the readings, it is the full evidence an EHO or a group auditor wants.

Steps included:

• 1 grouped check (one box per item): food item (text), temperature at start (number), temperature at end (number)
• 1 guidance note in the box (the 90-minute rule and the danger zone)
• 1 photo in the box (the probe reading)
• 1 signature in the box (sign-off)

When to upgrade: When you want Poppi to flag a failed cooling time to the manager on its own, or pull every site's cooling records into one report. Those versions are coming in the next post update.

How to pick the right version

You don't need to know our product to choose. Just answer three questions about how your kitchen runs.

Is it just you logging cooling, or do other people do it too?

If you log it yourself and know the rule cold, a plain record is enough. The moment rota staff do it, the rule needs to be on the screen. If only you check, #1 is fine. If anyone else does, start at #2.

Do you need proof, or is a record enough?

A record tells you numbers were logged. Proof is something you can put in front of an inspector. If numbers are enough, stop at #1 or #2. If you are under scrutiny or cook ahead for vulnerable groups, #3 adds a photo of the reading.

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, #3 is enough. If you run more than one site, #4 adds a signature.

Related reading

• 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

Frequently asked questions

How quickly does cooked food need to cool?

From 63°C to 8°C or below within 90 minutes is the working standard. The danger zone is 8 to 63°C, where bacteria multiply fastest, so the aim is to move food through it quickly. Food cooled too slowly, then chilled and reheated, is one of the most common causes of food poisoning outbreaks.

How do I cool food fast enough?

Split it into shallow trays, use an ice bath, stir it, or use a blast chiller. A deep pot of stew left on the side can take hours to cool through and will fail the 90-minute target. The guidance note in versions #2 onward lists these methods so staff reach for them.

What temperatures should I record?

The temperature when cooling starts and the temperature when it ends. The start reading confirms the food was hot when you began; the end reading proves it reached safe storage temperature in time. Recording both, with the item name, is what makes the record meaningful to an inspector.

What if food doesn't cool in time?

Record the readings and the time, then decide based on how long it sat in the danger zone. Food that cooled slowly but is still within a defensible window can sometimes be used; food that sat warm for hours should be thrown away. The logged readings are what let you make and defend that call rather than guessing.

Where to go next

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. The versions above move from a simple log to a signed photo record, so the proof is there when an inspector asks.

Five more versions are coming in the next refresh that bring AI into the check. Poppi can flag a failed cooling time to the manager, and pull every site's records into one report. Those need more review time and will land separately.

→ Build your own food cooling temperature check on Pilla. The Basic plan unlocks the simple log today.