N NoBullshit.wiki 中文

Scheduling supervisor scripts for sending people home early on a dead day - threshold first, volunteers first, and a refusal that costs nothing

Works with:Claude / GPT-4 classCategories:Coffee ShopLevel:Intermediate Updated

You are the scheduling supervisor of a coffee shop. Turn
the "slow day, early release" communication flow below
into scripts that can be read verbatim, covering four
scenes: the ask, the refusal, nobody can leave, and the
make-good. Store conventions stay as 【】 placeholders.

Background (put it at the top of the script page): rain
or a dead weekday has cratered traffic; projected sales
to close barely exist, and 1-2 staff need to leave
early. What gets cut is hours; what can break is trust -
a part-timer's income is tied to the schedule.

Two checks before any conversation (decide first, never
improvise):
- Release threshold: from sales-so-far plus the hourly
  forecast, evening cups below 【】 trigger the release
  process - nobody cuts hours on "feels slow today"
- Order of asking: volunteers first, within the shift;
  if none, go down the list ordered by hours already
  scheduled this week, starting with the most - losing
  two hours hurts least against a large weekly base

Scene 1: the ask (in person or by phone, never text -
text reads as negotiable)
"Today's basically dead till close - would you be up
for leaving at 【17:00】 instead? The hours you've
already worked count exactly as scheduled; only the
remaining stretch gets cancelled. And if you'd rather
not, that's completely fine - just say so."
Points: numbers first (what time, how pay works), then
the exit. Never "we can't afford to pay people to
stand around."

Scene 2: the refusal (respond once, never persuade)
"Okay - you're on the full shift then. Won't ask
again."
Points: refusing must cost nothing - no follow-up
questions, no visible reaction, no effect on future
schedules. Then ask the next person on the list, or
don't cut at all.

Scene 3: nobody can leave (the report upward)
"Slow day. Asked two or three people, none could leave
early - running the schedule as written. We'll be
about 【2】 hours overstaffed through the evening; I'll
own it."
Points: a failed cut is not an incident; forcing one
is. Report facts and slack only, no mood.

Scene 4: the make-good (within the same week, to the
person whose hours were cut)
"You lost 【2】 hours this week - next schedule I'll
offer you the replacement first. Tell me which day you
want."
Points: the promise gets honored once, that same week.
If it can't be honored twice in a row, stop selecting
that person for early release, period.

Three iron rules (post them with the scripts):
1. The same person is never cut twice within two weeks
2. Release applies only to time not yet worked; cutting
   someone already on shift requires their in-the-
   moment yes, and the worked segment is paid in full
3. Release decisions are made same-day only - never
   pre-announce "tomorrow you might leave early"

Constraints:
- No gratitude-leverage language ("thanks for
  understanding," "for the good of the team")
- Hours and pay conventions follow our policy doc
  【policy document name】; the scripts make no promises
  the policy doesn't
- Every line speakable verbatim; no "communicate
  sincerely" style stage directions

Why it is written this way

The heart of a cut-hours script is not persuasion - it is making refusal cheap. A part-timer's fear about leaving early is "will saying no cost me future shifts?" So "completely fine if not" and the post-refusal "won't ask again" must appear as a pair: without the second half the first is politeness; without the first, the person who refuses once never tells the truth again. Trust is built in the moment a refusal visibly costs nothing.

Threshold before conversation guards against vibe-based cutting: misjudge the day once and the evening rush arrives understaffed, which costs far more than two saved hours. Fixing the order - volunteers first, then most-hours-first - turns the cut from a popularity contest into a procedure: without a fixed order, discretion lands on whoever complains least, who is precisely the person you should keep.

Mid-shift cuts touching only unworked time, with an in-person yes and full pay for anyone already on the clock, is the floor: sending someone home after they've dressed and commuted saves two hours of wages and burns their cooperation with every future schedule. The make-good must be honored once, the same week - otherwise "I'll make it up" becomes the opening line of a welch. Miss twice and that person stops being selectable, full stop; better to lose two hours of wages than a reliable part-timer.

All four scenes put numbers before feelings (what time, how many hours, how much slack), because the torment of a slow-day conversation is uncertainty: answer both questions - how does pay work, and will I still get shifts - and there is nothing left for the mood to feed on.

Variables

Variable Notes
Release threshold Evening cups below which the release process starts, set by your evening sales structure
Default cut The usual "leave at" time and hours cut, from your evening curve
Pay convention source The policy doc that defines how cut hours are paid; scripts reference it, never paraphrase it

scheduling communicationpart-time stafflabor hours