Noodle shop lunch-rush service checklist - from 10:30 prep verification to 13:00 wind-down, every slot with a pass line

You are a noodle shop operations consultant. Generate a lunch-rush service
checklist for me - printable, checkable, used from 10:30 to 13:00. Follow the
structure below exactly: do not add or remove time slots or check items;
leave numeric pass lines blank for me to fill.

My inputs (I will provide before you generate):
- Staffing: register, noodle station, topping/pass, delivery packing,
  floater - how many people each at peak
- Yesterday's same-window numbers (11:30-13:00): topping-level sales,
  total bowls
- Delivery: typical same-window order count, average pass-to-courier
  handoff time (if tracked)
- My thresholds: topping low-stock line (portions left before calling
  for a refill), delivery backlog line (tickets waiting before acting)

Checklist structure (strictly these layers):

[10:30 Prep verification] Every item formatted: check / pass line /
immediate fail action
- Topping portions: each topping = same window yesterday x 1.1 (use last
  week's same weekday for Fridays/Sundays); patch shortfalls on the spot;
  what cannot be patched gets a "sold-out plan: at what time the register
  starts steering to what instead"
- Noodle stock: fresh and par-cooked portions by noodle type
- Broth: both pots' temperature and volume; taste against the shop's
  reference bowl standard - never "tastes about right"
- Condiment station: scallions, chili, pickles, utensil-pack count

[10:50 Stations]
- Each station gets: who / where they stand / first task at open
- POS and delivery tablets switched to accepting; receipt rolls replaced

[11:00 Dry run]
- Pass counter cleared; order-number screen / pickup rack numbered
- 86 list confirmed with the kitchen: anything unavailable today comes
  off the register now - not after a customer orders it

[11:30-13:00 Patrol, every 15 minutes] Exactly four items per round:
- Broth: below pass line -> top up / crank the heat
- Topping stock: any topping below my low-stock line -> refill OR 86 it,
  binary; "it'll hold" is not an option
- Delivery backlog: waiting tickets over my threshold -> execute my
  preset action (pause acceptance ten minutes / floater jumps in)
- Pass dwell: any finished bowl sitting past 3 minutes unclaimed or
  unserved -> handle that bowl first, everything else second

[13:00 Wind-down]
- Leftover broth handling rule; record tomorrow's prep figures (today's
  x1.1 experience value feeds tomorrow)

Output format:
- Full checklist as tables: slot / check / pass line / fail action /
  owner / checkbox
- One "anomalies this round" line after each patrol block
- Close with "how to run this sheet": week one ticks every box, from
  week two tick only exceptions

Constraints:
- No unverifiable items like "keep communication smooth" or "watch
  service attitude"
- The patrol stays at exactly four items - a fifth kills the patrol;
  nobody walks a twenty-item list
- Where I gave no threshold, print "TBD - fill from last week's average";
  never invent a number for me

Why it is written this way

"Prep early" fails because it answers none of: how much, how early, and what happens when it runs short. Every quantity pass line here anchors to "same window yesterday x 1.1" - the multiplier is tunable, but the structure is locked: prep derives from the shop's own sales data, never from intuition about "what shops usually prep." The 1.1 multiplier means 10% headroom for variance - better to end the rush with slightly surplus toppings (sellable at dinner) than to 86 mid-rush, because a stockout costs the entire bowl's ticket, not the topping's margin.

The patrol holds at exactly four items because that is what keeps the sheet alive. Checklists die by accretion - everything feels important until the patrol hits twenty items, at which point nobody runs it and the original four die with it. Four items is what one manager can genuinely walk in fifteen minutes during a rush, and each maps to a distinct, common failure: broth, toppings, delivery, pass dwell.

"Pass dwell past three minutes" is its own line because it is the one metric where finished work is actively decaying: every minute a bowl sits, the noodles clump - that bowl is the physical origin of a "noodles arrived stuck together" review. Directing the manager's eyes to the pass before the kitchen puts attention where loss happens fastest.

The 86 confirmation lives in the 11:00 dry run rather than mid-rush because "customer orders it, then finds out" is the most expensive move of the peak - one refund-and-recook costs two tickets' worth of time. Making "what's gone today" the register's first information of the day is the cheapest, highest-return line on this sheet.

Variables