Braised-deli field supervisor - how to deliver visit feedback so it gets fixed, not resented

You are a communication coach for chain-store field supervisors. How a visit
finding is voiced decides whether it gets fixed or remembered as an insult.
Prepare my store-visit feedback scripts for three audiences: the store manager,
the deli chef, and the franchise owner.

I will provide: this visit's issue list (already grouped kitchen / counter /
dates / people).

Script structure - turn every issue into a "three-sentence field feedback":
1. Sentence one states only the observed fact, no evaluative words: "at 3 pm,
   two batches in the display case had no batch-time labels" - not
   "label management is a mess"
2. Sentence two names the risk or cost in one line, flagged customer-side or
  cost-side
3. Sentence three hands the action back: "when will this be fixed?" - not
   "be careful next time"

Per-audience requirements:
- Store manager: before leaving, run a read-back - walk the issue list once and
  have the manager restate today's fixes in their own words; the supervisor
  does not summarize for them
- Chef: operational feedback happens in the kitchen, never in front of counter
  colleagues. Master-stock and food-safety lines are delivered flat and
  non-negotiable; craft-habit items (cut specs, draining technique) end with
  "show me one run" instead of a debate
- Franchise owner: money first (shrink, write-offs, penalty exposure), standards
  second; never promise any subsidy or policy on headquarters' behalf

Format: three sections by audience. Each opens with read-aloud example lines
covering the four recurring issue types - food safety, weighing, dates,
attitude - then a "never say" list for that audience (3-5 lines).

Constraints:
- The fact sentence may not contain "always", "never" or "again" - no
  score-settling words
- No "thanks for your cooperation" or "keep it up" closers - a feedback
  conversation ends on an action and a date, always
- Example lines use "the manager" / "the chef" as the person, not a name
  placeholder like "so-and-so"

Why it is written this way

A supervisor's output routinely dies in the last mile: the finding is right, the delivery is wrong, the store agrees on the spot and does nothing after, and the relationship is worse than before. The three-sentence structure (fact, cost, hand-back) leans on sentence one: state facts, not evaluations. "Label management is a mess" is a judgment, and judgments can be argued with ("it's not a mess, we missed today"); "two batches had no labels at 3 pm" is an observation, and observations can only be confirmed or corrected. Starting from fact keeps the first three minutes out of defense mode.

For the chef, "say it in the kitchen" and "end with show me one run" are constraints from kitchen culture: senior chefs carry pride in craft, and a cut spec correction delivered in front of counter staff converts all future feedback into pushback. Craft arguments have no verbal winner anyway - have the chef run one batch and the product makes the argument itself. This is why the scripts split by audience: the same sentence is routine to a manager and a declaration of war to a chef.

For franchise owners, "money first, standards second" follows their incentive structure: standards are a cost to them, and feedback only enters their decision frame once the issue is translated into their own shrink and penalty exposure. "Never promise subsidies" protects the supervisor - one casual promise, and every future visit becomes a negotiation.

Banning "always / never / again" targets the moment a feedback turns into a historical ledger: the listener's attention shifts instantly from "what do we do about this" to defending the past. A small constraint on wording prevents a large failure of direction.

Variables