Hotpot restaurant kitchen helper - thawing and water-packed storage SOP: frozen rolls thaw slow and dry, water-goods change water on schedule - two clocks that must be set hours ahead

You are the back-of-house lead at a hotpot restaurant. Write
"frozen-goods thawing" and "water-packed goods storage"
into one archivable standard document for kitchen helpers.
The two goods share one trait: both are clocks, and every
shortcut taken after the moment passes (hot water, extended
soaking) is destructive.

1. Frozen-roll thawing (sliced beef, lamb rolls)

1. The timetable (posted on the freezer door)
- Based on next day's projected usage, move frozen goods
  from freezer to walk-in [T] hours ahead - derive T
  from your own freezer-to-walk-in temperature gap;
  a few logged rounds of testing will pin it down
- Thaw-complete standard: no frozen core, no blood-water
  weeping, roll shape intact
- Rush exception: genuinely out of time - sealed bag
  under cold running water, never longer than [Q]
  minutes; this is an exception, not a method, and
  every use gets noted on the day's log

2. Handling
- Thaw in a lipped container, never bare on a work
  surface (blood water contaminates the board)
- Thawed rolls stored flat in a single layer, never
  stacked (stacking re-bonds them into a block and
  glues the shapes together)

3. Red lines (never clauses)
- NEVER hot or warm water thawing - the outer layer
  cooks grey while the center stays frozen; the plate
  is scrapped
- NEVER refreeze after thawing - a once-refrozen roll
  shows ice-crystal layers when cut and weeps blood
  water at the table; this is the direct source of
  "the meat wasn't fresh" reviews

2. Water-packed goods storage (tripe, duck intestine,
   aorta)

1. Change interval
- All water-goods live in ice water, cold enough that
  a hand notices immediately
- Change the water every [R] hours; turn and rinse with
  long tongs, no prolonged bare-hand soaking
- Log it: each change gets a time note on the item's
  card, initialed by whoever changed it

2. Quality self-check (piggybacked on every change)
- Texture: springy, not tacky; slimy means stop use
  and report to the head chef
- Smell: raw-material smell; sourness or a sharpened
  chemical note means stop use
- Water: if the changed-out water runs obviously cloudy
  or viscous, shorten the next interval

3. End-of-day disposal
- At close, assess: next-day-usable stock goes back to
  fresh ice water per standard, card marked "held over"
- Held-over stock gets used first the next day, with
  the full texture-and-smell check re-run before prep;
  anything two days old never touches the prep table

3. Records and checks (written for the checker)
- Three things land on the day's log: thaw pull times,
  rush exceptions, water-change notes; the team lead
  verifies at close
- Check method: pull one water-packed item at random
  and reconcile its card's change log against the
  actual water temperature

Output format: sectioned document; the timetable and the
red lines in quote blocks or bold; the two "never" clauses
in their own section at the end.

Why it is written this way

Thawing and water-goods belong in one SOP because they share one failure mechanism: destructive shortcuts under time pressure. The thaw isn't ready, so hot water; the water change was missed, so an extra-long soak - each shortcut "solves" the moment, and the bill lands on a table hours later when nobody can trace the review back to that faucet. The SOP's counter is front-loading the clocks: the pull timetable on the freezer door, the change interval on the item card, so "out of time" becomes visible hours before it happens.

The rush exception exists as its own lane because reality gets a vote: peak hours will produce goods that didn't thaw in time, and without a sanctioned fast lane, staff build a dangerous one (hot water). Giving the exception a defined motion (sealed bag, cold water, time-capped, logged) turns the fast lane into data - the day exceptions pile up, the T value is wrong and the timetable needs adjusting, not yelling at.

"Never refreeze" has to explain the consequence, not just prohibit: ice-crystal layers when cut, blood water at the table, a "meat wasn't fresh" review - a helper who can see the causal chain holds the red line; write only "prohibited" with no why, and the rule is the first thing sacrificed in the rush. The who-changes-logs-it design keeps logging under ten seconds for the same reason: anything longer gets skipped at peak, guaranteed.

Variables