Fresh supermarket manager - same-day call-out coverage SOP, with a swap matrix that has no blank cells

You are a grocery operations consultant. Write me an archivable SOP for
"same-day call-out coverage." Scenario: an employee phones in before
open; the manager has 15 minutes to set the day's plan.

First ask me for these inputs (anything I can't supply, write as a
placeholder rule):
- The store's role list and headcount per role (cashier / stocker /
  fresh prep / receiver / scale desk)
- Who has cross-training on record (who can run the scale, who is
  register-trained, who holds a food-handler card)
- Peak windows (typically morning and evening; fill in mine)

The SOP must contain five parts:

1. Entry point (a decision tree, two questions): which role is missing x
   is the gap in a peak or an off-peak window. The two answers index
   straight into the action table - no "use judgment" step between
   question and action

2. The cross-cover matrix (the core deliverable): a role-by-role grid
   where every cell is exactly one of: can cover / can cover after
   training / cannot cover. Every cell must hold a verdict - no "TBD."
   A TBD cell is a decision you have silently postponed back to the
   worst fifteen minutes of the day. "Cannot cover" cells must cite
   their reason (credential, food safety, system permission) - e.g. no
   food-handler card, no fresh prep; no register permissions, no
   cashiering. That is a permissions fact, not an attitude judgment

3. Task triage for the stripped role (priorities written down, not
   principles): the role that lost its person runs the day in three
   buckets:
   - keep: anything food-safety-adjacent (temperature checks, date
     rotation) and customer-facing service
   - defer: deep replenishment and display resets, pushed to tomorrow
   - drop: admin (labeling paperwork, backroom organizing), not today
   List each role's concrete tasks by bucket so I can literally strike
   through them

4. Escalation triggers (when to stop absorbing): two or more people
   out; cashier and receiver both out; promo day or holiday. Any
   trigger fires -> call the area manager or coordinate a loan from a
   sister store; the SOP names where that contact info lives

5. The after-section: where the day's coverage moves get logged in the
   shift book, and the one review question for tomorrow - did anything
   deferred today cascade (e.g. no evening replenishment -> empty
   shelves this morning)

Do not:
- Write "arrange flexibly" or "as the situation requires" - that is
  the thing this SOP exists to eliminate
- Leave any matrix cell blank or TBD
- Base a red line on "the supervisor doesn't think it's a good fit" -
  red lines cite credentials and safety only
- Exceed one page; it has to be usable start-to-finish inside those
  15 minutes

Why it is written this way

The hard part of a call-out is not thinking of a plan - it is that there is no time to think on the day. A manager making staffing decisions during the busiest fifteen minutes of the morning is deciding on adrenaline and memory. The SOP's entire value is moving those decisions to a quiet afternoon when nothing is on fire.

The matrix with no blank cells is the skeleton. Real coverage chaos lives in the hesitation - "can he actually cover register?" - and five minutes of hesitation eats the peak. A "TBD" cell is more damaging than a missing SOP: it hands the manager a legitimate-looking excuse to postpone the decision right back to the morning. Every cell gets a verdict, even when the verdict is "cannot cover."

The keep/defer/drop triage exists because a stripped role will not downgrade itself: the covering person tries to run both jobs at 80% each, and the food-safety items are exactly what gets squeezed out in the scramble. Deciding in advance which tasks simply will not happen today beats "do everything well" every time.

Red lines live in their own section and cite credentials only, to guard against "everyone chips in" heroics: the food-handler card for prep, register permissions for the till. These are compliance facts, not proficiency levels, and they are precisely what busyness loves to sacrifice.

Variables