Fast food restaurant kitchen helper - prepped-food sealing and thawing SOP - four label fields, old-in-front stocking, thawing gets labeled too; three moves stop most mix-up incidents

You are a process-writing consultant for a fast food
kitchen. Write the full SOP from sealing prepped items
through thawing. The reader is a first-week kitchen
helper - no industry experience, working from this one
document only.

Six stages (fixed order):
1. Sealing: container requirements, sealing method, and
   the cool-before-refrigerating rule [per store
   policy]
2. Labeling: four mandatory fields - item / prep date
   and time / use-by date (converted per store policy)
   / initials; one label position standardized store-
   wide
3. Stocking: old in front, new behind; old above, new
   below (set by this store's picking side); opened
   and unopened in separate zones
4. Picking: read the label before grabbing - use-by
   first, then item name; same item always picked
   from the pick side
5. Thawing: the cooler thawing position only [written
   per this store's actual equipment]; thawing also
   gets a label (item / thaw start time); food left
   out at room temperature overnight is prohibited,
   no exceptions
6. Thawed leftovers: handle per store policy [ ];
  any case the policy doesn't cover, the action is
  uniformly "ask the head chef - do not improvise"

Writing rules:
- Every step starts with a verb, one action, followed
  by a one-line "why" - a helper who knows what breaks
  when the step is skipped doesn't skip it for
  convenience
- All shelf-life days and temperatures stay [per
  store policy]; you may not write a single concrete
  number
- Each stage ends with a "self-check" line: one thing
  the helper can verify alone (e.g. "after sealing:
  every container labeled, dates facing out")

Two attachments after the SOP:
- Three red lines: violations that must reach the
  head chef the same day, pulled out and placed at
  the very top of the document
- New-hire verification: in week one the helper runs
  the full chain from this document while a senior
  cook observes without prompting; state what counts
  as passing

Constraints:
- No regulation names or clause numbers - every
  standard points to store policy
- No "mind food safety" slogans - every requirement
  lands as an action
- No equipment this store doesn't have (e.g. temp
  alarms) - work from the equipment list I give in
  the variables

Why it is written this way

Setting the reader as "a first-week helper" is not rhetoric, it's the quality bar: every step has to survive someone with no experience and no context working from this document alone. Phrasing a senior cook finds clear ("stock it the usual way") instantly fails that bar. The reader definition forces action-level steps.

Shelf-life days and temperatures stay blank because store policies differ wildly, and an AI-invented number has real food-safety consequences: write a wrong "three days in the cooler" and helpers will execute it faithfully. The SOP owns actions and order - cool before storing, label at thaw - which transfer across stores; the numbers belong to store policy, posted where store policy lives.

"Thawing gets labeled too" is the most counterintuitive and most valuable line in the document. Most stores label at sealing only; the label dies the moment thawing starts, yet mix-ups and overdue-use incidents cluster precisely in the post-thaw window: chicken thawed two days ago and chicken thawed this morning sit side by side with no visual difference. The thaw-start timestamp closes that accident window.

The "ask the head chef, do not improvise" fallback looks lazy and outperforms ten more rules: no SOP covers every edge case, and the costliest calls happen when a helper guesses in one. Giving "I don't know what to do" a legitimate exit is more honest than pretending the rules are complete.

Variables