Field supervisor store execution audit for semi-finished items - thaw, reheat, date code, discard: four checks, three states, same-hour response for Class A violations

You are a field supervisor for a central kitchen covering a
chain of stores. During store visits I collect execution
data on our semi-finished items using a fixed four-check
format. Audit my record: mark each item compliant /
violation / not provided, and produce the same-hour
response script.

The four checks (only these four - the other thirty items
on the visit form do not enter this audit):
1. Thawing: done under refrigeration or under running
   water per SOP; any overnight room-temperature thawing;
   any refreezing after thaw
2. Reheating: sampled core temperature of reheated items
   reached [target value] and held for [duration]; does
   the store's logged reading match my measured reading
3. Date codes: was the shelf-life label re-applied after
   thawing; any expired product still displayed; can the
   pack date be reconciled with the central kitchen's
   outbound date
4. Discards: were today's discards logged (item /
   quantity / reason / photo); did discarded product go
   straight into the discard bin rather than back onto
   the shelf

Three states:
- Compliant: there is a record or a measurement, and it
  meets the standard
- Violation: a measurement fails, or the record
  contradicts what I observed
- Not provided: the store cannot produce the record.
  Note: "not provided" is neither compliant nor a
  violation - list it separately, in neither bucket

Violation classes:
- Class A (direct food safety risk): overnight room-
  temperature thawing, selling items reheated below core
  temperature, using expired product, discarded product
  back on the shelf
- Class B (record and label defects): date label not
  re-applied, discards unlogged, logged temperature
  disagreeing with measurement but with no consequence

Output:
- Table 1: the four checks line by line / state /
  evidence (the records and measurements I supplied) /
  violation class
- Table 2: the same-hour response script for each Class A
  violation, one script per incident, written for the
  store manager to execute - stop selling the item,
  quarantine and preserve evidence for the affected
  batch, get the manager's signature; three actions
  listed separately
- Table 3: this store versus the other stores visited in
  this round - list only the items where it scores below
  the majority; omit everything else

Constraints:
- If something is not provided, say so. Do not invent a
  reason for the store, and do not assume "they probably
  did it"
- No "overall the store is in good shape with a few areas
  to strengthen" summary - this audit's output is
  item-by-item conclusions, not an overall impression
- The response script covers only what is within a
  supervisor's authority; fines and personnel actions
  belong to the operations manager - do not promise
  beyond that

Why it is written this way

Checking only four items is the antidote to the "generally compliant" report. Supervisor checklists inherit from food safety ledgers and are padded with items that always pass - uniforms, lighting - while the four items that have actually caused incidents (thaw, reheat, date code, discard) shrink into four cells among dozens. Cut everything else, and there is finally room to specify the evidence each check requires - measured values, records, physical product. Fewer checks, deeper checks.

"Not provided" gets its own state because its correct response differs from both other states. A missing record might mean "not done" (dangerous) or "done but not logged" (a management problem) - a supervisor standing in the store cannot tell which, and can only report what is observable. Fold it into "compliant" and a store with no records scores the same as a disciplined one; fold it into "violation" and you overstate what was actually confirmed. Its own bucket forces the next visit to treat record discipline as its own problem.

The A/B classes run on two different clocks. All four Class A items connect directly to food safety - their response cannot wait for the supervisor to drive back and write a report, which is why Table 2 is written at "one script per incident, manager executes on the spot" granularity. Class B items are management defects; erupting over them on the spot burns the manager's cooperation for nothing. Same-day fix with next-day recheck is the right tempo. Mix both classes into one corrective list and Class A slows to Class B's pace.

The ban on an overall verdict guards against the reflexive closing line. Once "generally good" appears, every violation above it loses half its weight - store staff read the ending, not the table. An audit's output ends at item-by-item conclusions; the overall impression was never this document's job to give.

Variables