Community supermarket scheduling supervisor - shift-swap approval SOP; same-skill swaps only, cross-skill needs the cover person verified as trained, one day's notice, frozen before holidays and promos, verbal yes does not count. Archivable, a new supervisor can run it as written

You are a scheduling advisor for a community
supermarket. Write an archivable, trainable
Shift-Swap Approval SOP for the scheduling
supervisor and all staff. Store context:
[store headcount] total staff across checkout,
scale station, stocking, and fresh prep, plus
[part-timer count] part-timers, and rota
tooling [has a system or not] (if not: paper
rota plus a staff group chat).

1. What counts as a swap (definitions fixed)
- Swap: two staff exchange their own shifts;
  total hours unchanged
- Transfer: one staff member hands a shift to
  another to cover; hours move
- Both go through the same approval; transfers
  additionally check the hours cap
- Not a swap, no approval needed: swapping
  meal breaks within a shift, trading stations
  within the same time block

2. Eligibility (who may swap with whom)
- Same-skill swaps: direct - checkout with
  checkout, stocking with stocking
- Cross-skill: the cover person must already
  be verified as able to work that station -
  "verified" means a training record or the
  store manager's on-record sign-off, noted
  in the swap request
- Scale station and evening-markdown shifts:
  never swapped to anyone who has not worked
  them solo - errors on these two are money
  and complaints, immediately
- Part-timers cover part-time windows only;
  full-time/part-time exchanges follow company
  policy, and where policy is silent, the
  answer is no

3. Applying and approving
- Lead time: [lead time] on ordinary days,
  one full day for weekends
- Form: written - a system request, or a group
  chat message the supervisor replies
  "approved" to. A verbal yes does not count;
  whoever claims it keeps the chat record
- Chain: the two staff settle it between
  themselves first, then file with the
  supervisor; cross-skill or over-cap swaps
  add the store manager
- The supervisor checks exactly three things:
  whether either person's weekly hours break
  the cap, whether the slot still has someone
  who can run each skill after the swap, and
  whether anyone reaches more than
  [consecutive-day cap] days in a row

4. Freeze windows (approval refused, fixed)
- The [freeze days] before a holiday and the
  holiday itself: staffing is already at the
  line
- Count week: count teams do not move
- The night before a promo changeover: the
  changeover roster is locked once set
- Genuine emergencies inside a freeze go
  through absence-cover, never through swaps

5. Records and accountability
- Every swap enters the swap log: date / two
  names / shifts / approver / note
- Errors after a swap belong to whoever worked
  the shift - "that shift was originally his"
  moves nothing
- The monthly swap log is archived with the
  rota

Forbidden:
- No soft lines like "accommodate reasonable
  swap requests where possible" - the
  approvable/refusable boundary is written
  hard
- No "special cases handled case by case"
  loophole; special cases go through the
  absence process, never the swap process
- The whole SOP stays within two pages, every
  line executable and tickable, with no
  paragraphs about purpose or significance

Why it is written this way

The entire difficulty of managing swaps is that staff naturally settle it between themselves first and come to the supervisor for paperwork after. An SOP that reverses that order (apply first, then find your partner) simply stops being followed and everything goes underground. So this SOP follows reality: the two staff settle it, then file; the supervisor's job is not "approving the deal" but checking the three things staff cannot see from inside it - the hours cap, skill coverage, and consecutive days. Those three are precisely the entire source of swap disasters.

Scale station and evening markdown get their own hard line in eligibility because their errors are money, immediately: one wrong PLU at the scale or one row missed at markdown close-out means complaints or lost margin that same day, and the investigation never traces it back to the swap - the cover person doesn't even know where they went wrong. The bar for "able to work it" is set at a training record or the manager's sign-off rather than the person saying "I can," because everyone says they can; when the standard sits in a record, accountability sits in the open when something breaks.

The freeze windows get their own section with hard day counts because that is where swap SOPs get worn down: someone always has an emergency right before the holiday, the supervisor relents once, and by the next day everyone has a "special case." Redirecting emergencies to the absence-cover process hands the supervisor a step that doesn't require breaking the rule - absence has its own rules and its own cover assignments, and never touches the swap gate. A gate left open once cannot be closed again.

"Verbal yes does not count" plus the swap log look like they police staff, but they actually protect the supervisor: the most common swap dispute is one employee saying "she approved it" against a supervisor's "I never did," with no evidence on either side. Written confirmation (even one "approved" in the group chat) plus the log makes every swap traceable. Once archived, a new scheduling supervisor inherits the log format and the rules without renegotiating either.

Variables