4 ways to automate cooked food temperature checks

#1 - Simple log

Who it's for: Single-site kitchens where the chef or duty manager runs the check themselves. No second checker, no EHO pressure yet, just a need to record that cooked food reached a safe temperature.

Available on: Basic.

What it is: A cooked food temperature check is a record of the core temperature of each cooked or reheated item, taken with a probe in the thickest part. This version keeps it to the three things that belong to every check: what the item was, whether it was cooked or reheated, and the core temperature. The three sit together in one box, so each item reads as a single check rather than three loose fields. The UK target is 75°C at the core, or 70°C held for two minutes, which is the equivalent the Food Standards Agency accepts. Regulation (EC) 852/2004 is the law behind it: food has to be cooked thoroughly enough to remove the hazard, and 75°C is the number an environmental health officer checks you against.

In practice: A single-site bistro runs this four times across the day, spread over service. The chef probes the thickest chicken breast in the tray, types "Chicken breast", taps "Cooked", and records 78°C. The next item gets its own box. The whole thing takes seconds per item and leaves a record that names the food, the method, and the temperature, which is exactly what an inspector asks for.

Why it works: The three inputs live in one box, so a temperature can never be saved on its own. The item name and the cooked or reheated context are always captured next to it. That is what makes the record traceable later: if a customer reports illness, you can find the exact item and batch instead of guessing from a lone number.

Steps included:

• 1 grouped check (one box per item) holding: food item (text), cooked or reheated (single choice), core temperature (number)
• Duplicate the box for each item checked during the service

When to upgrade:

1. New or rota staff are running the check and don't all know the targets by heart
2. Your EHO starts asking for proof, not just a typed number
3. You run more than one site and want a named sign-off on the day's checks

#2 - With guidance

Who it's for: Kitchens with new starters or a rota of staff who don't all know the safe temperatures by heart, and want the check to teach as it goes.

Available on: Standard.

What it is: The simple log with a guidance note added to the top of the box. The note states the 75°C core target, the 70°C-held-for-two-minutes equivalent, and where to put the probe: the thickest part, not touching bone. Roughly a third of kitchen staff in hospitality have never had formal food safety training beyond a basic certificate, so the target often lives in one person's head. A guidance note on the check puts it in front of whoever is on shift.

In practice: A gastropub with high summer turnover runs this. A new commis chef opens the check, reads the note, and knows before probing that a chicken breast needs 75°C and that resting the probe against the bone gives a false high reading. They probe the flesh, record 76°C, and move on. No one had to stand over them.

What it adds to the previous template:

1. The safe core temperature is on screen at the moment of the check, not in a training folder
2. Probe placement guidance cuts the most common false pass (probe touching bone)
3. New staff run the check the same way as the head chef from day one

Why it works: The guidance sits inside the same box as the reading, so staff see it at the moment they probe, not in a training session they have half forgotten. 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), cooked or reheated (single choice), core temperature (number)
• 1 guidance note inside the box (safe core temperatures and probe placement)

When to upgrade: When a record of the number is no longer enough and you want photo proof of the probe reading (Cooked Temp #3), or a named sign-off for an audit trail (Cooked Temp #4).

#3 - With photo evidence

Who it's for: Kitchens under EHO scrutiny, or supplying vulnerable groups, that want to show proof rather than ask an inspector to trust a typed number.

Available on: Standard.

What it is: The guided check plus a photo of the probe display next to the food. The photo is captured in the box, at the time of the check, alongside the item name and the reading. A number typed into a log can be written from memory or rounded up; a photo of 78°C on the probe screen next to the chicken is contemporaneous proof. For high-risk items (poultry, mince, large joints, reheated dishes), that is the difference between a record and evidence.

In practice: A care-home kitchen cooking for residents runs this on every batch of reheated food. The cook probes the centre of the shepherd's pie, photographs the probe reading against the dish, and records 79°C, reheated. If the CQC or the EHO ever questions a meal, the kitchen can show the exact reading for that exact dish on that day.

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 or an investigation, not just a number
3. A visual record of which item was probed, so a low reading can be traced to a real dish

Why it works: Evidence taken in the moment is far stronger than a number recalled later. The photo ties the temperature to the actual item and the actual time, which is what an inspector or an insurer needs to see.

Steps included:

• 1 grouped check (one box per item): food item (text), cooked or reheated (single choice), core temperature (number)
• 1 guidance note inside the box (safe core temperatures and probe placement)
• 1 photo inside the box (the probe reading next to the food)

When to upgrade: When the check needs a named, dated sign-off as well as a photo, so an audit can see who confirmed the day's checks (Cooked Temp #4).

#4 - With photo and signature

Who it's for: Multi-site groups and larger operations where a chef or duty manager signs off the day's checks and the records have to stand up to an audit across sites.

Available on: Standard.

What it is: The photo check plus a signature at the end. The person running the check signs to confirm every item reached a safe core temperature. The signature turns a set of readings into a named, dated commitment. For a group with a food safety manager overseeing several kitchens, that signature is the line that makes each site accountable for its own checks, captured in the same box as the readings and the photos.

In practice: A 20-site pub group runs this. Each kitchen's duty manager logs the cooked items with photos through the day, then signs off at the end of service. The group's food safety lead can open any site's record and see the items, the temperatures, the photos, and the signature, all timestamped, without driving to the venue.

What it adds to the previous template:

1. A signature confirming every item reached a safe core temperature
2. Named accountability for each site's checks, not just an anonymous log
3. A complete record (item, temperature, photo, signature) an auditor treats as best practice

Why it works: A signature turns a private set of readings into a record someone has put their name to. Nobody can later say the checks were not done or were done by someone else. Together with the photo and the readings, it is the full evidence an EHO or a group auditor wants to see.

Steps included:

• 1 grouped check (one box per item): food item (text), cooked or reheated (single choice), core temperature (number)
• 1 guidance note inside the box (safe core temperatures and probe placement)
• 1 photo inside the box (the probe reading next to the food)
• 1 signature inside the box (sign-off confirming safe temperatures)

When to upgrade: When you want Poppi to brief the chef on the day's high-risk items before service, flag a low reading to the manager on its own, or pull every site's checks 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 actually runs. Each one moves you up a rung.

Is it just you running the check, or do other people run it too?

If you run every check yourself and you know the targets cold, a plain log is enough. The moment new starters or a rota of staff are probing food, the target needs to live on the screen instead of in your head. If only you check, #1 is fine. If anyone else does, start at #2, where the guidance note keeps everyone working to the same temperature.

Do you need proof, or is a record enough?

A record tells you a temperature was logged. Proof is something you can put in front of an inspector. If a written number is enough for now, stop at #1 or #2. If you are under EHO scrutiny, cook for vulnerable groups, or want to defend a single meal, #3 adds a photo of the probe reading captured at the time.

Does someone need to sign off the checks?

In a single kitchen, the records speak for themselves. Across several sites, an auditor wants to know who confirmed each day's checks. If no sign-off is needed, #3 is enough. If you run more than one site or answer to a food safety lead, #4 adds a signature so every site is accountable for its own record.

Related reading

• Fridge temperature check - the storage check that protects food before it is cooked
• Food probe accuracy test - how to prove the probe itself is reading true
• Food cooling temperature check - the check for food going the other way, from hot to cold storage

Frequently asked questions

What temperature should cooked food reach?

The target is 75°C at the core, held for at least two seconds. 70°C held for two minutes is an accepted equivalent. At 75°C the harmful bacteria that cause food poisoning, including Salmonella, Campylobacter, and E. coli O157, are destroyed within seconds. Whole cuts of beef or lamb can be served pink if the surface is properly seared, but minced products, poultry, and reheated food must reach 75°C throughout.

Does it matter whether food was cooked or reheated?

Yes, which is why the check records it. Reheated food has already been through the danger zone once during cooling and storage, so bacteria may have multiplied. Some, like Bacillus cereus in rice, produce toxins that survive reheating. You reheat to 75°C, not just to serving temperature, and food should only be reheated once.

How often should I run cooked food temperature checks?

Most kitchens run the check several times across the day, spread over service periods, rather than once. Record the core temperature of each high-risk item you cook or reheat: all poultry, minced products, large joints, reheated dishes, and anything for vulnerable groups. Records showing 75°C for every item with no variation look as unconvincing to an EHO as no records at all.

Do I need a photo of the probe reading?

Not for a basic compliant record. A documented temperature with the item name and cooked or reheated method (Cooked Temp #1 or #2) meets the requirement. The photo in #3 is a defensive step for kitchens under heavy scrutiny or cooking for vulnerable groups, where you may need to prove a single reading rather than ask an inspector to trust a typed number.

Why probe the thickest part and not touch the bone?

The thickest part is the last to reach temperature, so it tells you the whole item is safe. Bone conducts heat faster than meat, so a probe resting against bone reads higher than the actual flesh and can pass an undercooked item. Insert the probe into the thickest part of the flesh, parallel to the bone, and wait for the display to stop moving before recording.

Where to go next

Cooking is the step that kills the bacteria you cannot wash off, see, or smell, but only if someone checks the core and records it. The gap in most kitchens is rarely the cooking; it is that nobody captured the proof. The versions above move from a simple log to a signed photo record, so the evidence is there when an inspector asks.

Five more versions are coming in the next refresh that bring AI into the check. Poppi can brief the chef on the day's high-risk items, flag a low reading to the manager on its own, and pull every site's checks into one report. Those need more review time and will land separately.

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