Scheduling supervisor store add-on order scripts - when the phone rings after cutoff, how to open with accept, defer, or decline; every add-on leaves a written confirmation

You are a scheduling supervisor coach for a central
kitchen. Write me a set of scripts for "store add-on
orders after cutoff," three tiers - accept, defer,
decline - readable verbatim.

Scene: the order cutoff has passed. A store manager
calls: "it's busy today, 20 more of X please."
Production is locked, waves are staffed. My stance:
neither pushover nor wall - the surplus decides, and
every add-on leaves a written confirmation.

1. Accept (open your mouth only if both preconditions
hold):
Precondition 1: same-day production surplus for the
item ≥ add-on quantity + safety cushion (I hold the
day's surplus sheet);
Precondition 2: the delivery run still has capacity
and the stop is on the way.
"Sure, 20 of X I can add. I'll text you a
confirmation: item, quantity, delivery time, and whose
approval this runs on - reply 'confirmed.' One more
thing: today came out of surplus. Tomorrow's numbers
still go in before cutoff - once we lock the plan,
accepting more means taking it from someone else's
share."

2. Defer (surplus insufficient, but tomorrow's first
wave has room):
"20 today genuinely won't fit - the item is at full
production and adding more means moving someone else's
volume, and I can't face the other stores with that.
Tomorrow's first wave, delivered by X o'clock - I'll
send that as a written confirmation. For tonight's
crowd, can you borrow a few from the neighboring store?
If that truly won't work, I'll help you think of
something else."

3. Decline (truly impossible - not even the materials):
"This one I can't do today - not refusing to help: the
materials arrived to plan, and there isn't one spare X
in the building. What I can do: one, ask the two
neighboring stores if they can spare any and have them
transfer to you; two, push Y tonight - similar on the
plate, and today's quantity still holds. Send tomorrow's
numbers tonight before cutoff and I'll schedule you
first."

Iron rules (every tier, every time):
- Within 5 minutes of hanging up, send the written
  confirmation: item / quantity / arrival time / who
  approved. A verbal acceptance with no confirmation
  is next month's unreconcilable account
- Any store adding on more than 【3】 times in a week
  gets summarized to the regional manager on Friday
  with each add-on's size and reason - the data talks,
  no confrontation on the phone

Constraints:
- The word "impossible" never appears in a decline -
  every refusal carries an alternative action, and a
  refusal without one goes unsaid
- No unverifiable delivery times - "probably" and
  "should be" are banned from the defer tier; what you
  give is the time backward-computed from the
  production schedule
- No "let the phone ring" tactics - every minute a
  call goes unanswered is a minute off the store's
  rescue window; stalling is the worst of the three
  tiers

Why it is written this way

The accept tier's two preconditions are hard because "the nice person collapses" is the standard arc of add-on handling: accept today on goodwill, and tomorrow a second store hears and calls too, surplus gets eaten by the first asker, and eventually even the planned stores run short. Making "surplus plus delivery capacity" the condition for opening your mouth turns acceptance from a favor into a capacity fact - and when the manager hears "this came out of surplus," they also understand that volume doesn't follow volume of voice.

Defer and decline both must carry alternatives because of one reality: the store calls with the day's business standing at the door, and a bare "can't fit it" solves nothing - they just call the owner next and the pressure routes straight back. Saying "borrow from the neighbor" or "push Y instead" out loud repositions you from "the one who wouldn't send" to "the one working the problem with them" - and those two alternatives are precisely the ones stores don't think of, or don't feel entitled to propose themselves.

The written-confirmation rule is the only non-negotiable line in the set. Three parties remember a verbal acceptance (how many, arriving when, approved by whom) three different ways a month later, and the reconciliation turns into the scheduler's private Rashomon. Send the confirmation within five minutes, get one word back - thirty seconds per call, buying out a full day of month-end dispute. It may be the highest-return line in the whole set.

High-frequency add-on stores get the Friday summary rather than an on-the-spot confrontation because of cadence: confronting solves today's emotion; Friday's data solves next month's schedule. A store that habitually adds on either needs its forecasting fixed or deserves a higher safety stock - both questions data answers. Scripts manage the day; data manages the month; the two rhythms must not blur.

Variables