Noodle shop no-show and last-minute leave scripts - cover the slot first and ask why second, approve shift swaps only within the same skill class, and handle the chronic Friday caller with the record, not an accusation

You are a scheduling supervisor coach for a noodle shop.
Write me a set of scripts for last-minute leave and shift
swaps: four scenarios, each with lines I can read verbatim,
formatted as one note I keep on my phone.

Our shop's context (I will provide before you generate):
- Positions and skill tags: who can pull noodles, who can
  run the register, who can cover whom
- Part-timer roster and their usual free hours
- Existing time-off and swap rules, if any
- My comp authority: what I can promise on the spot
  (comp time, overtime pay) and what needs the owner

Scenario 1: the 7 a.m. "can't come in today"
The first sentence never asks why - it covers the slot:
"Got it. I'll find cover - take care of what you need to."
Then act immediately: list who can cover today by skill
class, and message the best match first:
"[Name], [who] can't make it in today. Can you come in
early and hold the noodle station until [time]? I'll log
it as overtime / comp time. If not, no problem - I'm
asking the next person."
Once the slot is covered, return to the person who called
out - once, no follow-up interrogation:
"Logging today as personal leave or comp time? Whatever
paperwork the shop needs, per the usual rules." - if they
said something happened at home, skip the paperwork line.

Scenario 2: someone asks me to approve a swap
Approve same-skill-class swaps only (dishwashing cannot
swap into the noodle station):
"Fine by me, as long as you two are the same skill class.
Post it in the group in the fixed format: who swaps with
whom, which day, which shift, both of you replying to
confirm - I'll reply 'noted,' and only then does it count.
Anything you only told me verbally doesn't."
When someone tries to route around the format:
"It's not that I don't trust you - it's that an unposted
swap counts as your no-show if the other person doesn't
show. I'd rather never have to have that conversation with
you."

Scenario 3: asking someone to come in early to cover
State the situation, offer the choice, no arm-twisting:
"We're short one noodle cook for the lunch peak. You're
on the afternoon shift - any chance you can come in two
hours early? I'll log overtime / comp time. And if not,
that's fine, I'll ask around."
Never say: "You're the only one who can save us today" or
"If you don't come in, we're done for."

Scenario 4: the same person's third absence this month
Private conversation, on the record, about the facts:
"You've taken [N] days off this month, all Fridays. I'm
not asking why. Two things I do need to say: the Friday
lunch noodle station has come up empty each time, and I've
had to find cover on the spot. The shop rule is [one-line
rule]. Going forward, if you need Fridays off, tell me [X]
days ahead and I'll build it into the schedule; same-day
notices I'll have to log as no-shows."
No naming them in the group chat, no discussing it with
other staff.

Output format: four scenarios, each with "lines to read +
follow-up actions," plus a "what not to say" column for
each.

Prohibitions:
- No "communicate more" or "be understanding" attitude
  lines - everything must be speakable verbatim
- Do not promise comp beyond my stated authority - unfunded
  promises hurt more than having no script at all
- No firing or pay-docking guidance - that is a different
  process; these scripts only keep the schedule standing
- Do not interrogate sick-call details or ask for a
  diagnosis - the script needs exactly two facts: coming
  in today or not, and back when

Why it is written this way

Cover first, ask why second - get this order wrong and everything after it goes wrong. Leading with the reason turns the call-out into an interrogation, puts the supervisor's temper into the conversation, and leaves the slot still empty while the 11 a.m. rush waits for nobody. Covering first is not indifference; it is an admission of priorities, and the cover action itself tells the employee "the shop holds together, don't panic" - which does more for the relationship than any sympathetic phrasing. The alternative, the supervisor silently taking every shift, teaches the staff one lesson: leave requests self-process, and they multiply.

"Same skill class plus fixed format" targets the single biggest source of noodle-shop no-shows: the verbal swap. A says they swapped with B; B says they never agreed; neither shows up; the pass-through window stalls; the records show nothing. The fixed format - posted in the group, both parties confirming, the supervisor acknowledging - turns "we swapped" into a checkable artifact. The "it's not that I don't trust you" line belongs to the supervisor, not the manual: state the stakes (an unposted swap books as your no-show) rather than the distrust, and the rule holds without a grudge attached.

The chronic-absence scenario is built around one translation: converting the attitude charge "you're always off" into the fact statement "three times this month, all Fridays, the lunch noodle station empty each time." Numbers accuse nobody, yet the impact becomes undeniable - that is what "about the situation, not the person" means in practice. Offering the path out (X days' notice) matters because wanting Fridays off is legitimate; the problem was never the day off, it was the same-day notice. A path out plus a bottom line is what makes the rule survive.

The "don't interrogate sick-call details" prohibition stands on its own: a scheduling supervisor is not HR and not a doctor, and "what's wrong with you" both oversteps and never gets the truth. The scripts need exactly two facts - in today or not, back when - and nothing else. The exception in scenario 1 (skip the paperwork question when something happened at home) matters just as much: demanding documentation from someone in a real crisis teaches them that next time they should invent a smoother lie, when what the supervisor actually needs is notice, not a perfect reason.

Variables