Fresh-market holiday scheduling SOP - a 30-day countdown in four sheets - leave lock, written asks, floater shifts, pre-booked comp time

You are a scheduling consultant for a fresh-food supermarket. Build
our holiday rush (the 7-10 days before Lunar New Year are the annual
peak; National Day and Mid-Autumn follow the same pattern) into a
countdown SOP - from 30 days out to a week after - with time /
action / owner / deliverable for each block. Anchor on the two ways
we've been burned: through the holiday on goodwill, with someone
working 12 straight days and then out half a month; and the week
after, when everyone took comp time at once and the open store ran
on half a crew.

Organize by countdown timeline:

[T-30 days: labor inventory and leave lock]
- Availability census: who is present the whole holiday, who travels
  (and returns when), who can only work halves - person to day
- Issue the leave lock: X days around the holiday (default: 7 before
  through 3 after) approve no leave in principle; exceptions go
  through the store manager, in writing
- Deliverable: the available-labor pool list

[T-21 days: asks and supplemental hiring]
- Overtime interest survey, in writing: people volunteer their
  available extra windows. Nobody is defaulted in, and no hints of
  "whoever doesn't come is taking responsibility"
- Gap math: peak demand from last year's sales-by-band (or the
  manager's estimate) against the pool
- Temps fill the gap: new hires work low-skill posts only
  (stocking, replenishment, scale assistance); skilled posts
  (cutting, end-of-day register) run double-covered, and no one
  works unsupervised and untrained
- Deliverable: gap sheet + temp requisition

[T-14 days: the holiday roster]
- Principles: everyone on deck for peak days; shifts stretch at
  both ends - openers arrive 2 hours pre-open for delivery and
  stocking, closers stay past close for replenishment and review
- One floater per day: no fixed post, exists to absorb "someone
  didn't show / someone went down." The floater rotates to whoever
  is freshest that day - never parked on one person
- Deliverable: the holiday roster with floaters marked - **and the
  post-holiday comp-time roster booked in the same version**, not
  improvised after

[T-7 days: confirmations and contingency]
- Call every temp individually to confirm start date - do not trust
  the group chat
- Confirm double coverage on every skilled post: every critical
  skill, at least 2 people per day
- Illness contingency: roll call is the first act of every day;
  anyone missing triggers the floater plus the neighbor-store
  borrow (borrow contacts live in the SOP appendix)

[During the holiday: daily]
- Pre-open roll call and floater assignment; a 10-minute post-close
  huddle: does tomorrow's staffing change?
- Deliverable: daily one-line labor snapshot - date / present /
  floater used / gap disposition

[Week after: comp time and the comedown]
- Comp time follows "most overtime first, in batches," and daily
  on-duty headcount never falls below the comedown minimum - sales
  drop after the holiday, the crew can be smaller, but skill
  coverage may not break
- Week two after: a review answering exactly three questions - which
  band was shortest, how many times the floater fired, which temps
  are worth keeping
- Deliverable: comp-time execution sheet + the three-question review

Do not:
- Write "rally team spirit" or "do the motivational work" - every
  block is an executable action with a checkable deliverable
- Cite labor-law clauses - we set our own hour-cap parameter and
  say so plainly; compliance follows the store's local rules (I
  don't supply them, and you don't invent them)
- Expand "temp training" into a training program - "no unsupervised
  untrained work" is the entire policy

Why it is written this way

The opening line's two failures are the SOP's two spines: the war roster plus floater treats mid-holiday burnout, and booking comp time at T-14 treats the post-holiday ghost town. Pre-booking comp time is counterintuitive but load-bearing - leave it until after, and everyone's case for resting first is airtight, the scheduler becomes the store's enemy, and the collisions are guaranteed. The pre-booked sheet is insurance for that week, and the premium is one table filled out two weeks early.

The floater is the only defense against unplanned absence: every holiday includes a sudden illness and a family emergency, and any roster, however full, is paper until the day happens. A standing floater gives the day somewhere to flex; rotating the assignment keeps it from calcifying into a permanent tax on the one person who never says no.

The written, voluntary overtime ask exists because goodwill-powered holidays send the bill later: clustered comp time, resignations, and nobody willing next year. Making the ask an action rather than a vibe also closes the "whoever doesn't come owns it" guilt trip - once that sentence is spoken, the survey becomes a loyalty test.

No legal citations, self-set parameters: hour rules vary by jurisdiction, and one hard-coded clause will eventually detonate somewhere in a multi-region chain. The cap goes into the variables table; compliance follows local rules. That is what makes the document reusable across stores - and what keeps it honest about what it doesn't know.

Variables