Butcher shop manager - the end-of-day sell-off SOP: food-safety screen first, value routing second, and who decides how deep the markdown goes

You are the operations process designer for a butcher shop. Write me an
"end-of-day sell-off and markdown SOP." Understand the premise first: fresh
meat is short-dated, and whatever is unsold today loses most of its value
tomorrow - mishandle the order of decisions and you pay twice. Meat that
should have gone to the cooler but got marked down is money handed away;
meat that should have been written off but got marked down is a food-safety
incident. This SOP turns the last hour before close into fixed motions
that require no thinking on the spot.

Follow this structure (the sequence is the thesis - do not reshuffle):

Step zero: the safety screen (before everything)
- Go over every unsold item: off color, tacky surface, off smell, or any
  known break in the cold chain goes straight to write-off
- This judgment must never get crowded out by "but we could discount it" -
  write-off criteria outrank every value judgment, and no one, including
  the owner, can waive them
- Every criterion must be answerable yes/no on the spot - never "looks
  okay"

Step one: count-down (about two hours before close)
- Weigh all unsold meat: weight per cut, split into "cut today" versus
  "carried over from yesterday" - never mixed

Step two: value routing (for what passed the screen; ask from the best
outcome down; each item enters exactly one lane)
- Ask "can it hold?": whole uncut pieces, cut today, cooler up to
  standard - date-label it for the cooler, display first at opening.
  Carried over yesterday and still unmoving by midday? No second carry -
  it drops to the next question
- Ask "can it transform?": cuts with slipping looks but sound quality -
  grind or cube them now, tag "today only," run the markdown before close
- Ask "can it discount?": sellable but slow - discounted sale at a fixed
  time and place, depth per the authority ladder below
- Fails all three - write-off

Step three: markdown authority ladder (structure fixed, the discount
lines are mine to fill)
- Clerk's own authority: down to X% off, no permission needed
- Manager on duty: below X% down to Y%
- Owner: anything deeper, or moving whole pieces to restaurants in bulk
- Never stall waiting for permission beyond your rung - missing the
  evening crowd costs more than any discount depth saves

Step four: the record (five minutes at close)
- Total weight per lane: written off / carried over / transformed /
  sold at markdown
- Track carryover items separately the next day: still unsold at next
  close logs one "carry-over failure" - the most direct ordering signal
  there is; repeated failures mean order less, not discount harder

Format requirements:
- One A4 page, large type, taped to the cooler door
- Every action gets a parenthetical - one line on why, or the trap it
  avoids
- Every criterion written so it can be answered yes/no with eyes closed

Constraints:
- No invented numbers for temperatures or keeping times - they follow
  local regulation and this shop's equipment; a made-up number in an SOP
  is itself an accident waiting to happen
- The phrases "at discretion" and "as circumstances require" are banned -
  every routing decision must be executable without judgment
- The write-off rule carries no "in special cases we may..." escape
  hatch - a red line with a hatch is not a red line

Why it is written this way

The sequence is the whole thesis: the safety screen runs as step zero, and value routing starts from the best outcome. Most shops run it backwards - at close, the first thought is "what discount clears this," and questionable pieces slip through inside that markdown logic, blessed as "looks fine." Lifting write-off judgment above everything else concedes a truth: every sell-off decision gets pushed by the day's performance pressure, and only removing the unsellable first makes the remaining routing rational. Routing asks "can it hold" before "can it discount" because every step down the ladder is real money - what can hold shouldn't be discounted, and what can transform shouldn't wait to be discounted.

"Carry-over gets exactly one carry" cuts off the classic muddle: today's leftover becomes tomorrow's, tomorrow's becomes the day after's, and by day three the meat neither sells nor fits the cooler - it ends as a write-off anyway, while the books showed three days of "normal selling." Forcing midday demotion, plus the "carry-over failure" log line, gives the lane an exit: repeated failures say "order less" more directly than any shrink analysis.

The markdown authority ladder prevents crashes in both directions: clerks with no authority stall waiting for the manager and miss the evening crowd (the markdown's time window is worth more than its depth); clerks with full authority discount erratically and sign favors for regulars. The lines are a variable - tight for busy shops, looser for neighborhood shops - but the three-rung structure is fixed. Fix the structure, loosen the numbers: the general recipe for an SOP that survives contact with a shop floor.

"No discretion" targets how SOPs actually die: not from going unread, but from readers skipping every line that says "as appropriate." Criteria rewritten as yes/no questions let whoever is on duty route the meat by process, not by judgment, during the hardest hour of the day. Likewise the food-safety numbers stay blank for local filling: regulations and equipment differ, and a number invented into the SOP has no owner when things go wrong.

Variables