Fresh supervisor - cooler temperature check list, three times a day, with bands, buffer tier and a save-the-product-first chain

You are a cold-chain consultant for a fresh-food supermarket. Build me
a cooler and freezer temperature checklist that gets run three times a
day (morning, midday, close). Use case: the fresh supervisor or duty
lead walks the floor with the sheet, no more than a minute per case.

Input I will give you:
- Case list: case number / location / category (chilled produce case,
  freezer, dairy case, seafood case, etc.)
- The acceptable band per case type (I fill from equipment spec and
  company policy - set the column up empty for me)
- Defrost windows from the equipment manual

Checklist structure:
- One row per case: case number / reading / verdict / action
- Three-tier verdict:
  1. Normal: inside the band, nothing to do
  2. Drifting but inside: hovering at a boundary - recheck in 1 hour;
     a normal recheck closes it out; two consecutive drifts escalate
     to out-of-range
  3. Out of range: run the action chain immediately
- The out-of-range chain (fixed order - never call service before
  moving product):
  a. One question first: heavy door traffic or mid-defrost? If yes,
     recheck after the window passes
  b. If not, product first: the sheet pre-assigns consolidation pairs
     (which cases can merge into which, what must go to the back
     cooler); move product per the preassignment, then deal with the
     equipment
  c. Call service while product is moving; tag the case "out of
     service"
  d. Log: out-of-range start/end times, actions taken, product
     affected - that temperature record is what supplier claims and
     insurance will ask for later

Tail sections:
- The thermometer itself: is its calibration date current? An
  out-of-calibration probe is worse than no probe
- The defrost exemption, written down: does a short spike during a
  scheduled defrost count as an excursion? Follow the equipment
  manual - no "probably fine" rulings on the floor
- Power-outage drill: after an outage, how long product stays put
  vs. when it must move (variable, by category)

Do not:
- Include a "temperature OK" column without the band column that
  justifies it - no band, no verdict
- Let the out-of-range action stop at "call maintenance" - what
  happens to the product must be in the same line; the product is
  worth more than the case
- Let the sheet exceed 15 rows; each full round must fit in 10 minutes
- Collapse the verdict to two tiers (normal/abnormal) - real cases
  wander inside their band all day; a two-tier sheet alarms daily and
  gets ignored daily. The buffer tier is what keeps "out of range"
  rare enough to be taken seriously

Why it is written this way

The most common failure of temperature rounds is copying numbers without rendering a verdict: a tidy column of readings that nobody has answered "so is that good?" about. A verdict requires a band hanging on every case - filled by each store from its own equipment specs and local requirements. The checklist only enforces the structure: no band, no verdict, that row is not done.

The "drifting but inside" tier exists because reality is fuzzy: case temps move with door openings, defrost cycles and deliveries. A two-tier sheet produces daily "abnormal" flags, and within two weeks daily alarms become wallpaper. Give drifts a buffer (recheck, then close), and out-of-range stays rare - which is what keeps it alarming.

"Save the product before the service call" is a paid-for ordering: the supervisor's first instinct on a bad reading is to phone the technician, and the product sits in a failing case through the whole response time. Pre-assigning consolidation (who merges into whom, what goes to the back cooler) means the worst ten minutes run on a script instead of improvisation.

The logging line is not decorative: supplier cold-chain claims, equipment warranty disputes and insurance filings all rest on a continuous temperature record - this sheet is the only original evidence the store will have.

Variables