N NoBullshit.wiki 中文

Butcher shop equipment technician - cooler failure & power-outage SOP: decide by measured temperature, move stock by value and perishability, never rule "still sellable"

Works with:Claude / GPT-4 classCategories:Butcher ShopLevel:Advanced Updated

You are the equipment technician for a butcher shop. Write an
archivable Cooler Failure & Power Outage Emergency SOP,
covering refrigerated display cases, prep-counter chillers,
and the walk-in. Write it as a document executable the day it
is printed - every step carries a decision condition, and no
step is a principle without a condition.

Structure it in the six sections below.

1. Triage (first 10 minutes after noticing)
- Scope the failure: one unit or a whole circuit - check the
  neighboring case, ask whether the register scale has power
  (isolates a supply problem), check the breaker panel
- Tripped breaker: reset once; if it trips again, stop
  retrying and go to the repair-call flow
- Rule out the false alarm: confirm the unit is not mid-
  defrost (some equipment runs warmer and displays oddly
  during defrost); if it recovers when defrost ends, close
  the incident and log it

2. The decision anchor: measured case temperature
- Every move-or-wait decision reads the thermometer inside
  the case - never a hand, never "it seems okay"
- Inside the acceptable range: move no product; read and log
  the temperature every 30 minutes while awaiting repair
- Climbing: enter the transfer flow in section 3
- The range numbers are mine, from equipment spec and store
  policy - leave blanks in the document; do not pre-fill

3. Transfer priority (by value and perishability, not by
   volume)
- First move: chilled cut meat and ground-meat product -
   most perishable and highest value
- Second: today's stock that must stay chilled to sell
- Last: frozen product - thermal inertia buys it time
- Destinations in priority order: other working units in the
  shop → a neighboring shop's cooler by arrangement →
  insulated boxes with ice packs (a wrapping or bag between
  the pack and bare meat; never direct contact)
- The destination list is written in advance and taped to
  the unit - during the event, execute the list; do not
  improvise one

4. The repair call
- Always have ready: model number, year of purchase, the
  fault picture (power / running / sounds), and whether the
  condenser filter was cleaned recently
- Cooler faults get top priority - what is failing is not
  the machine, it is the case of product inside it

5. After power returns
- Measure recovery on every unit; log how long each took to
  pull back to setpoint
- Any product that went through an excursion is stored
  separately and flagged: keep-or-discard is the QC call
  under food-safety policy - this SOP never issues a "still
  sellable," and that sentence goes in the document
- 48-hour watch on the equipment: log cycling frequency and
  recovery times; anything off goes back to repair

6. The record
- Same day, write the timeline: time noticed / triage
  verdict / repair called / transfer details / power
  restored / temperatures at each point
- The timeline goes into the repair log - it is the input to
  the next repair and the next audit

Constraints:
- No "fine for X hours without power" promises - condition,
  season, load, and door openings all change that; every
  decision reads the thermometer
- No phone-walkthroughs for non-repair staff into
  refrigeration or electrical parts
- Excursion product disposition does not appear in this SOP
  - it belongs to food-safety authority, and the day this
  document carries a "you can still sell it" clause is the
  day someone sells problem meat with the SOP as cover
- Every step is a condition plus an action; strike every
  "remain vigilant" and "ensure safety" sentence that has no
  condition attached

Why it is written this way

The real cost of a cooler failure is decision latency: from "seems a bit warm" to "call the technician" to "should we move the meat," each step waits for someone to volunteer a verdict while the case temperature climbs. Anchoring every decision to one variable - the measured temperature, inside the range or climbing - is what lets whoever is on shift execute the sheet while rattled. Feelings are worthless in an emergency; the thermometer inside the case is the only thing allowed to speak.

Transfer "by value and perishability, not volume" is a butcher-shop-specific ordering. Instinct moves the big items first - full boxes, primal cuts - but frozen product is precisely the most tolerant: thermal inertia means another half hour costs nothing. What must move first is chilled premium cuts and ground product - fastest to spoil, highest price per pound, and ground product tolerates temperature swings far worse than whole muscles. Deciding this ordering in advance is what keeps the first half hour from being spent on frozen boxes.

"Tape the destination list to the unit in advance" reads like filler and is in fact the line between an SOP and a poster. At 11 p.m. with a tripped walk-in, who invents "which neighbor can take my meat"? Nobody does - the sheet gets ignored and the floor goes back to improvising. Executability is prepared in advance or it does not exist.

"Never rule still sellable" is written in from the first draft to draw the boundary between the equipment role and food safety: this SOP owns temperatures and timelines; the product's fate belongs to QC under the food-safety standard. The moment an equipment document carries "excursion under two hours is fine to sell," it is underwriting food safety - and nobody writing an SOP can carry what that sentence costs.

Variables

Variable Notes
Acceptable range Chilled and frozen separately, per equipment spec and store policy; blanks in the document, never pre-filled
Destination list Other units in the shop, neighboring-shop arrangements with contacts, insulated boxes and ice-pack stock - maintained in advance, taped to the unit
Repair contact sheet Repair service, manufacturer line, purchase years and model numbers per unit - read off the sheet, not from memory

cold chainemergency responsepower outage