Digital HACCP cooling log template

A cooling log is the record that a batch which was hot moved through the temperature danger zone in the time your food safety program allows, and that somebody was accountable for watching it. It is not a souvenir of the shift. When an auditor, a customer, or your own manager asks what happened to yesterday’s curry, the log is the answer.

The fields below are a template you can lift into paper or into software. They match the checkpoints the HACCP assistant on this site is built to store: batch identity, start temperature, stage timing, end temperature, a pass / fail / deviation flag, and the operator. Your approved HACCP plan and your state rules win if they ask for something different. Do not replace a plan your auditor has already signed with a template from a website.

The public reference implementation is the E_HACCP repository, built around FD Catering’s HACCP records. The name and the repository stay on the tool page because that is a real system, not a mock brand. Use it as a concrete example of the fields, not as a claim that every kitchen should run that exact stack.

Identity comes first. A batch or cook ID, the product name, the date, and the equipment or vessel stop two batches of the same soup from being written on one line. If you rework a batch, give the rework its own line that points back at the original ID. Overwriting the first line deletes the story.

Temperatures need a start, the points your plan calls critical, and an end. For many cooked foods the familiar two-stage cooling reference is 60°C down to 21°C, then 21°C down to 5°C, inside the times in the plan. The assistant’s demo uses a stage-one limit of 120 minutes from 60°C toward 21°C and a total of 360 minutes to get under 5°C. Those numbers are the rules configured for that demo. Confirm the limits in your own program before you copy them into a form.

Time should be captured as clock times, not only as a duration somebody calculates later. Duration can be derived. A missing clock time cannot. Record the operator, and leave a field for corrective action: what was done when the limit was missed, who decided, and whether the food was chilled further, reheated, or discarded. A blank corrective-action box next to a fail is the finding.

Paper logs fail in ordinary ways. The sheet is on a clipboard in the cook line and the batch is in a blast chiller. Times get filled in at the end of the shift in handwriting that is one pen for six batches. A temperature that was never taken is written as a tidy number because the column looked empty. None of that requires bad intent. It requires a form that asks for memory.

The other failure is filing. A pass and a fail live in the same folder, and the fail is visible only if someone reads every page before the audit. Digital does not fix this if it is a spreadsheet with no status and no filter. A useful record can be listed by date, product, and failed status without opening each row’s story.

Corrective actions get lost on paper because they are written in a margin and then photocopied away. Give them a field that is part of the row, so a deviation cannot be marked closed while the action is empty.

A screen is not an improvement if the record can be edited with no trace, or if the only copy sits on one laptop. For a cooling log, the useful properties are ordinary: who entered it, when it was entered, what changed later, and a backup that is not the same device as the kitchen tablet. The E_HACCP notes describe an audit trail for that reason. You do not need that product to insist on those properties.

Calculated fields should be calculated. If stage duration is typed by hand, the log has the same memory problem as paper, with better fonts. Store the clock times and let the system show the minutes. When the minutes cross the limit, raise the status. Do not rely on a conditional format somebody can turn off.

Keep the demo data clearly fake if you show a system to a customer or an auditor. The assistant page uses sample batches so the screen can be read. Sample rows are not production records and should not be exported into an evidence pack.

Start with one product that you cool every day, not with every SOP in the plant. Run the template beside the existing paper for a week. Compare missing fields, late entries, and any batch the paper called a pass while the times said otherwise. Then retire the paper for that product, not before.

The HACCP assistant page shows the cooling-log screen and links the public repository. If you want the same shape fitted to your plan’s limits and your product names, use the contact page and send the current paper form. The limits should come from your program. The template only makes them hard to skip.