Community supermarket field supervisor - walk-finding triage and deadline SOP; food-safety items fixed on the spot, execution items in three days, improvement items checked next visit. Who verifies, who gets the escalation, and what counts as closed - all fixed

You are a field-supervision advisor for a
community supermarket. Write an archivable,
trainable Walk-Finding Triage and Deadline
SOP for me and my backup supervisors.
Context: I cover [store count] stores on
roughly a [visit frequency] rhythm. Today
every finding lands in one running log,
nothing distinguishes severity, and stores
cannot tell which line requires movement
today.

1. Triage criteria (sort first, deadlines
   second)
- Red - food safety & compliance: hygiene
  and temperature control of ready-to-eat
  goods, expired stock on the shelf, raw
  and cooked mixed, blocked fire aisles,
  price tags overcharging versus system -
  signature: customers or regulators could
  hold the store accountable today
- Yellow - operational execution: FIFO
  skipped, write-off process off-spec,
  handover logs missing, out-of-stock
  cards absent - signature: internal
  control holes; a week won't kill, but
  they grow
- Blue - improvement: facing fullness,
  traffic flow, display quality, script
  fluency - signature: bonus if done, no
  deduction if not

2. Deadlines and owners (fixed per tier)
- Red: fixed on the spot - the supervisor
  stands there until it is done; written
  escalation to the district the same day
  (fixed template: finding / photos /
  actions taken / recheck plan); the store
  gets no "review it" step and no
  extension option
- Yellow: [yellow deadline] days; the
  store replies with photos (date-stamped);
  the supervisor closes on photo review.
  One extension maximum for stated cause,
  up to [extension cap] days, and the
  request must say exactly where it is
  stuck
- Blue: reviewed next visit, no standalone
  clock; a blue item unchanged across two
  consecutive visits promotes to yellow -
  what promotes is the behavior ("asked
  twice, nothing moved"), not the item
  itself

3. Acceptance criteria (what "closed"
   means)
- Photo acceptance, three elements: the
  fixed scene / a date stamp / a view
  matching the described finding's
  location - missing any one means not
  closed
- Spot recheck: [spot-check ratio] of
  photo-closed yellow items get a physical
  recheck on the next visit; a mismatch
  between photo and floor reopens the item
  one tier higher
- Recurrence clause: the same problem at
  the same store reappearing inside the
  [recurrence window] is not a new finding
  - the original item reopens one tier up;
  recurrence at red adds a manager
  conversation

4. Overdue and escalation (what happens
   when it drags)
- Yellow overdue with no reply: on day
  [overdue reminder] the supervisor calls
  to find the blocker - a resource problem
  gets help, an attitude problem gets
  logged
- Still open past day [escalation line]:
  escalate to the district manager with
  the full trail and the store's replies
  (or their absence) - escalation is a
  process step, not a punishment, and the
  SOP says plainly that escalating is not
  tattling
- The same store producing red findings
  [consecutive reds] times in a row: start
  a store-level diagnostic (attribution
  analysis) instead of another single-item
  corrective

5. Records
- One file per store: findings logged by
  tier per visit, closures ticked, file
  updated with spot-recheck results
- Monthly rollup: three numbers per store -
  tier counts, closure rate, recurrence
  rate. Three numbers only, no commentary

Forbidden:
- No "handle flexibly as circumstances
  require" - triage and deadlines are all
  fixed; when in doubt between tiers,
  sort up, never down
- No "stores may appeal the tier" process
  - tiering is the supervisor's job;
  disputes go in the file for the district
  to settle
- Two pages max; all five sections carry
  numbers; no purpose statements

Why it is written this way

Triage's first job is not managing stores - it is allocating the supervisor's own attention. With everything in one running log, the supervisor's memory races the store's wishful thinking: the store bets you won't remember which line mattered, and the log genuinely does not say. The three deadlines (on the spot / three days / next visit) map to three kinds of time sensitivity: red is "customers or regulators could hold the store accountable today," written as a consequence signature rather than a category list, because safety failures come in endless shapes and the test must be the consequence, not the appearance - something a supervisor can apply standing on the floor.

"Photos missing any of three elements don't close" is the acceptance clause's teeth: the most common fake fix is a stock photo of nobody knows when. Date stamp plus a view that matches the described location raises the cost of staging above the cost of actually fixing. Add the spot recheck - a share of photo-closed items physically verified next visit, mismatches reopening one tier up - and acceptance moves from "trust the photo" to "photo plus sample," after which stores discover that honest fixing is the cheapest option available.

The recurrence clause is the linchpin of the whole SOP: the same problem back at the same store inside the window is not a new finding - the original item reopens, one tier higher. Without it, corrective work becomes an infinite loop of fresh memos: every recurrence earns a brand-new ticket with the clock reset, and what the store learns is not fixing but the rhythm of digesting memos. With it, recurrence itself becomes the punished behavior - punished for "told and didn't move" - which is the actual disease triage exists to treat.

Writing "escalation is a process step, not tattling" into the escalation section is authorization for the supervisor: a triage system whose supervisor daren't escalate has no teeth - out of face-saving, the escalatable items rot in their inbox until the red one detonates. Hard-coding escalation as a mechanical step (which day, with which attachments) means the supervisor executes it carrying the SOP, not a personal grudge. And the monthly rollup reporting exactly three numbers (counts, closure rate, recurrence rate) hands store performance to the numbers - zero room for supervisor commentary; numbers hold no grudges and grant no favors.

Variables