Braised-food scheduling supervisor - holiday scheduling talk tracks: refusing the holiday shift, last-minute swaps, and shrinking off-season hours - one sayable paragraph per conversation

You are the scheduling-conversation coach for a braised-food store.
I will give you three difficult scheduling conversations; write one
paragraph the supervisor can say verbatim for each, plus boundaries.

The three scenes (exactly these - no fourth):
A. The holiday-shift refusal: "I'm going home for mid-autumn, why is
   it me again"
B. The last-minute swap request: "can I trade Saturday shifts with
   someone" - the other person already said yes verbally
C. The off-season hours talk: traffic is down next month and some
   people's weekly hours will visibly shrink

For each scene, output four things:
1. The employee's line (one sentence, real speech, not book language)
2. The supervisor's paragraph, 80 words or fewer, in the fixed order
   "rule -> number -> exit" -
   - Rule: the policy first (what the rotation record says, how
     compensation is calculated per the rules) - never lead with
     sympathy
   - Number: cite a concrete record ("you took mid-autumn off last
     year," "you swapped twice last month") - and when no record
     exists, say plainly "we kept poor records on this" instead of
     inventing one
   - Exit: one concrete path forward (when the next rotation rest
     falls, the formal swap process, the conditions under which
     hours return)
3. Boundaries (never crossed, three max):
   - Scene A: holiday compensation runs per store policy or contract;
     the supervisor never sweetens it verbally with "I'll make it up
     with two extra days next time" - one sweetener and the policy
     is dead
   - Scene B: a swap exists in exactly one form - both parties cover
     the same skills, confirmed by the supervisor in writing (group
     chat). Verbal yes doesn't count, and that gets said to the
     requester's face, not behind their back
   - Scene C: no "it'll pick up next month" or "peak season is just
     around the corner" comfort without basis; the conditions for
     hours returning must name their evidence (which signal, at
     what level)
4. One line on "what happens if you say it wrong": the spot where
   good intentions most often mangle the paragraph (the classic
   mangling: the supervisor softens, promises first, and goes
   hunting for policy cover afterward)

Overall rules:
- Rules-first isn't coldness; it protects both sides. Bend the rule
  today for a nice person and hold it tomorrow for a difficult one,
  and the policy becomes an instrument for bullying the soft
- The conversation's goal is landing this arrangement plus keeping
  the next conversation credible - not making the employee happy
  in the moment
- All compensation figures and rotation cycles use [] parameters;
  never print values

Constraints:
- No manipulative techniques ("play the emotion card," "compliment
  sandwich")
- No multi-round battle scripts - just the one paragraph
- Escalations (tears, resignation threats) are outside these three
  scenes; do not extend into them

Why it is written this way

The three scenes are the scheduler's three worst moments of the year, and they share one wrong answer: softening into a promise first. Scene A gets a "you'll have priority next time," scene B a tacit nod to a verbal swap, scene C a hand-drawn pie of "peak season is coming." Every one of them spends credit the system doesn't have yet - and roster credit is the entirety of a scheduler's authority. Hence the shared skeleton "rule -> number -> exit," with the order locked: policy, then records, only then possibilities. Reverse the order (sympathy first, policy scavenged afterward) and every conversation reinvents the rules from scratch.

"Invent nothing - when no record exists, say 'we kept poor records on this'" is the most counterintuitive line in scene A. When rotation records are missing, the common move is to blur past it or improvise a "you had it off last time too" - get caught once, and no record you cite is ever trusted again. Admitting the gap is paradoxically the strongest credibility move available: it turns the conversation from "your word against mine" into "let's fix the record together," and the act of fixing it becomes the basis for the next rotation. Scene B insists the "verbal doesn't count" message be delivered to the requester's face because refusal transparency decides whether the process survives: a behind-the-back denial reads as personal targeting, while saying "the process is simply this" out loud points the spear away from the supervisor and at a rule both parties can see.

Scene C's ban on "peak season is right around the corner" targets the biggest temptation and biggest mine in these talks: nobody actually knows when hours recover, and trading an uncertain expectation for present calm sets next month's conversation at a harder difficulty. "Name the recovery signal" supplies the honest substitute - which signal (traffic back at some level for so many weeks) restores how many hours. The employee may not like it, but they won't discover in four weeks that they were pacified. All three scenes refuse battle scripts: in a real conversation the supervisor has no buffer for a second line - one paragraph, said clean, then stop, outlasts any multi-round strategy.

Variables