QC failed-result communication scripts - one fact base feeding three versions for the owner, the stores, and the production floor; no unconfirmed cause enters any of them

You are a QC specialist at a central kitchen. A third-party
lab report has come back with a failing indicator. Prepare
three communication versions: for the owner, for the
stores, and for the production team. All three share one
fact base and must all go out within 【4】 hours of
receiving the report.

The fact base (list it separately; all three versions may
draw only from it):
- The indicator detected, its value, and the limit
- Item and batch involved
- Report number, lab, and report date
- Actions already completed: is the batch isolated, is
  the retention sample intact
- What is not yet confirmed: how far the cause analysis
  has gotten

Boundaries of each version (they differ; do not write one
draft and blast it three places):

1. To the owner or management (written, under 200 words):
   - Fact base plus actions taken, plus the one decision
     the owner must make: whether to suspend shipment of
     this item
   - Supply the decision inputs: how many stores the
     batch covers, whether a substitute supply exists.
     Do not decide for the owner, and do not rule out
     risk for them either

2. To the stores (group notice, under 100 words):
   - Actions only: hold which batch, stop selling and
     using it, await replenishment instructions
   - No test values, no indicator names, no reassurances
     like "does not affect safety" - the authority to
     explain numbers sits with headquarters' official
     notice, and screenshots travel uncontrollably in
     store group chats

3. To the production team (spoken at shift briefing, 3
   minutes):
   - The facts in one sentence; spend the time on
     rechecks: tied to the indicator, list the checks for
     the next few days - cleaning and sanitation records,
     temperature logs per zone, staff hand-injury logs,
     equipment reassembly after maintenance
   - No names, no blame tone - the cause is not settled;
     investigate first, settle accounts later

Constraints:
- All three versions are barred from unconfirmed cause
  speculation ("probably a transport issue") - before the
  cause is established, speculation enters no
  communication
- No "basically safe" or "not a big problem" hedges
- The store version contains no "sorry for the
  inconvenience" - a hold is an operational instruction,
  not an apology letter; mixed tone means soft execution
- The three versions may not contradict each other on
  facts - wording may differ, facts must share one source

Why it is written this way

The fact base comes first because communications blow up over divergent facts, never over wording: "one indicator marginally exceeded" told to the owner, "routine sampling found an anomaly" told to the stores, "should be fine" told to production - three days later the versions meet in a conference room and QC's credibility zeroes out in one sitting. Listing the base separately and requiring all three versions to draw from it means there is only ever one version of the facts; differences in wording are differences in granularity, nothing more.

Keeping values and indicator names out of the store notice is communication management, not concealment: store group chats are screenshot country, and "colony count exceeded by X times" plus a cashier's own commentary reaches consumers within half a day. Stores need an instruction to execute, not data; data has exactly one correct channel (the official notice), and pulling the numbers out of the group removes the raw material of rumor.

Stopping the owner's version at "decision inputs" without a recommendation is QC's first rule of self-preservation: the classic way QC takes the blame is saying "no need to suspend" for the owner - then the same item blows up two weeks later and that reassurance becomes personal liability. Giving coverage counts and substitute options, and letting the owner make the call, positions QC as the professional input provider, not the risk absorber.

The production version focuses on rechecks instead of blame, and not out of softness: micro failures usually have causes scattered across cleaning, temperature, people, and equipment. Name someone at the briefing and the next three days are spent self-exonerating while nobody investigates. Locking the script to "which records to pull" keeps accountability where it belongs - after the cause is actually known, when that conversation can land.

Variables