Scheduling supervisor trough-hours task pool - fill the two slow windows with cleaning, prep, and training, with a milk-waste cap on latte-art practice

You are the scheduling supervisor of a coffee shop. Turn
the trough-hours task pool below into a tickable
scheduling checklist laid into the two slow windows in
half-hour cells, for the shift lead to run. Store
parameters stay as 【】 placeholders.

Background (put it in the checklist header): our traffic
is double-peaked (morning commute + afternoon bump);
10:00-11:30 and 14:00-16:30 are long troughs. Trough
labor is a sunk cost - the pool gives that capacity a
destination, and it always yields to drink orders.

Task pool (each item tagged: estimated duration /
frequency / owning role):
A Deep cleaning - one item per week on rotation, never
  more
- Steam wand deep soak and descale / 20 min / Mondays /
  barista
- Grinder removable parts washed and dried / 30 min /
  Wednesdays / barista
- Freezer defrost and temperature log catch-up / 25
  min / Thursdays / barista
- Patio furniture and window sills / 20 min / weather
  permitting / cashier
B Prep - daily, anchored to a time
- Tomorrow's cold brew beans in and timer set /
  15 min / daily 15:30 / barista
- Syrup decant and bottle-mouth cleanup / 15 min /
  daily 10:30 / barista
- Cup stock replenish and date-check / 15 min /
  daily 14:00 / cashier
C Training - weekly when a trainee is on
- Latte-art practice: milk-waste allowance of 【500】
  ml per session; practice ends when the allowance
  does / 30 min / training barista
- Side-by-side cupping: two cups from today's newly
  opened bag / 20 min / rotating staff
D Customer-asset work - weekly
- Regulars profile refresh (usual orders, taste
  notes) / 20 min / cashier
- Member-community post draft (what and when to post
  is the manager's call) / 25 min / shift lead

Scheduling rules:
- At most one task per half-hour cell; a customer
  stops the task - tick the cells you actually
  finished, no time made up, no rushing
- At most one Category A item per day - the trough
  first protects the bar's ability to re-ramp; too
  much cleaning starves the next peak of hands
- Category C waste allowance is a hard cap: training
  value never gets paid for with an open-ended milk
  bill
- A full grid is not the goal: when rain brings the
  crowd back early, the pool stops wherever it
  stopped, and nobody owes an explanation

Constraints:
- Every item carries a duration and frequency - no
  "flex time" or "miscellaneous tasks" cells that
  can't be ticked
- Pool completion is never used for performance
  review - it is a scheduling tool, not a punch card

Why it is written this way

The trough is the most awkward stretch in coffee-shop scheduling: you can't send people home (the next peak arrives unannounced) and the idleness is visible to everyone. The pool's real job is answering "what is this stretch of wages buying?" - deep cleaning, prep, and training capacity, not phone scrolling. Naming the purpose is what turns trough labor from a cost line into a capacity line.

"Customers interrupt, tick what you finished" is what keeps the pool alive: run it as a rigid quota and the shift lead will shortchange customers to complete cells, so the pool starts damaging the very service it was meant to support. That's why the final constraint states outright that the pool feeds no performance review - the moment it touches a KPI, performative completion replaces real completion within a week.

The milk-waste allowance on latte-art practice closes the most abused loophole in bar training: without a cap, "practice" becomes unlimited milk poured down the drain; with the quota in the checklist, training cost becomes budgetable for the first time - which is exactly what makes a manager willing to approve practice blocks at all. It is the one number in the pool that needs a manager's signature.

Every task carries an owning role rather than "everyone takes turns," because distributed trough ownership means nobody owns it: a cashier who knows cup-stock replenish happens at 14:00 daily is an order of magnitude more reliable than "do it when free." Frequency anchored to a clock time (cold brew at 15:30 daily) gives each task a hook - a frequency without a time is a frequency that doesn't happen.

Variables