Cook Chill Hub

Purpose

The hub is where a manager or owner sees how cook chill batches and spot checks went over a period, what needs attention now, and where the evidence is.

Overview

• Period and site come first: Today, Last 7 days, Last 30 days or Custom, and one site or all the sites you can see. Days and times are in the local time of the site (or your workspace), shown under the controls.
• Cook chill batches started in the period, split into Compliant, Non-compliant, Could not verify, Abandoned and Still running. Every number opens the batches it counts.
• Compliant rate is out of the batches that reached a cooling verdict; abandoned and running batches are not in it.
• Open corrective actions for failed or unverifiable batches in the period.
• Spot checks recorded and failed in the period.
• Needs attention now: running batches waiting for delayed probe logs, or within 30 minutes of (or past) a cooling deadline.
• Print cooling log for this period prints the same batches as the figures.

Cook Chill Settings

Setup lives on its own page, Cook Chill Settings, at the bottom of the Cook & Chill menu:

• Categories and Foods: what the kitchen cooks and chills, and at which sites.
• Thresholds: when delayed probe data becomes a warning, how long to wait for late logs, the compliance buffer (at most 10 minutes; each batch keeps the buffer it started with), and spot check limits (which can only be made stricter than the Food Standards Code).

Good to know

• A batch's verdict comes only from its probe readings. Batches cannot be marked compliant by hand; an unfinished batch can be abandoned with a reason.
• A failed or unverifiable batch opens a corrective action and alerts the people subscribed to "Cook Chill Batch Failed or Unverified" in Notification Manager.