Hotpot restaurant scheduling supervisor - slow-season hour-cut scripts: you are cutting shifts, not people, and four kinds of staff get four different conversations

You are the scheduling supervisor of a hotpot restaurant. The summer
slow season requires cutting hours. Write a script set for the hour-cut
conversations, covering four audiences, each entry in three fixed
blocks: Script (speakable verbatim) / Paired action / Never say.

Opening ground rules (all four audiences):
- Structure before numbers: what gets cut is the "shift structure" -
  a compressed dinner service, rotating Mondays and Tuesdays off - not
  headcount. Make this separation first, or the listener decides it's
  layoffs on their own, and once decided it cannot be unsaid
- Recovery gets a basis, not a date: "rebuilding on last September's
  rhythm" is sayable; "definitely back by September" is not - a date
  spoken aloud is a promise, and the season keeps no promises
- Paper on the spot: end every conversation by handing over a personal
  slow-season shift preview. A verbal reassurance, to an employee's
  ear, never happened

Audience 1: veteran full-timers (monthly income drops directly)
- Script: "Slow season is here and shifts change: dinner compresses,
  Mondays and Tuesdays rotate off - you're looking at about [shift
  count] fewer this month. I won't sugarcoat the pay impact. Your
  guaranteed floor is [guaranteed-shift policy], and the comp time we
  all owe each other from the peak gets repaid this summer."
- Paired action: one-on-one only; never announce anyone's numbers in
  a group
- Never: "We all need to pull together through this" - dressing one
  person's concrete loss as collective duty is the line veterans
  resent most

Audience 2: part-timers (hours cut)
- Script: "Hours contract store-wide in the slow season, so part-time
  scheduling moves to [monthly hour range] for now. The early-bird
  rule stands - [part-timer priority policy]."
- Paired action: walk them through next month's bookable hour range,
  face to face
- Never: "I'll get you more shifts next month" - an off-schedule
  promise that doesn't materialize is exactly how peak-season
  hiring dries up

Audience 3: peak-season newcomers (came to save money)
- Script: "You joined during the rush, so you haven't seen our summer
  - this is hotpot, every year the same loop: lines in winter,
  minding the fort in summer. People who stay through the slow months
  get [peak-season scheduling policy for those who stayed] when the
  rush returns - I will honor that on the schedule."
- Paired action: talk separately; never in the same room as the
  veterans - newcomers will read one veteran's sigh as confirmation
  the store is finished
- Never: "I won't stop you if you leave" - a bitter-handed farewell
  pushes out someone who could have stayed

Audience 4: the employee who asks "is the store failing"
- Script: "Fair question. Here's the data: at peak we were doing
  [peak traffic figure]. Hotpot runs one loop a year like this.
  The business questions I can't answer myself - let me sit you down
  with the manager."
- Paired action: this question deserves a real answer - book time
  and sit down; don't dispatch it standing in a hallway
- Never: "You're overthinking it" - a dismissive reply confirms the
  suspicion it's trying to shut down

Output format: one ground-rules section plus four audience sections,
scripts as quote blocks; each section ends with an "escalation line" -
when this conversation cannot resolve things and the manager takes
over (questions about closure or business data, compensation demands,
visible distress).

Overall discipline:
- Scripts conversational and speakable; [ ] items filled by the house;
  no invented compensation standards
- No script longer than four sentences
- No "other chains are laying people off" contrast as comfort -
  stability frightened into people isn't stability

Why it is written this way

The real risk in hour-cut conversations is not blowing up in the room - it's talking people out the door in the slow season and rehiring in the busy one. A hotpot peak runs on practiced hands; one full turnover of staff resets service quality for the holiday rush, and the cost of recruiting and training exceeds the cost of retention every time. The employee doesn't run this math; the scheduling supervisor must.

"Give a basis, not a date" is the spine of the set. A scheduling supervisor has no control over the season, and promising "back by September" mortgages something unownable. "Last year's rhythm" is a verifiable frame - it costs nothing to say and doesn't count as broken faith if the season drifts. Employee trust in promises has a credit limit, and the schedule itself should be what spends it.

Talking to newcomers separately is structural, not etiquette: people hired in the peak have never lived a full slow-fast cycle, and "nobody eats hotpot in summer" isn't common sense to them - it's news. Put them in the same room as veterans and one sigh gets read as confirmation. Information tiering matters more than the information.

"No off-schedule hour promises" counters the people-pleasing reflex: saying "I'll get you more shifts next month" feels kind in the moment, and when the schedule can't deliver it, what's spent is the store's hiring credit for the entire next peak.

Variables