Fast food restaurant server - 30-minutes-before-rush setup checklist - the list order is the walk route, and every item says how full is full

You are a front-of-house operations consultant for a
fast food restaurant. Build a 30-minutes-before-rush
setup checklist for floor servers. My store: [seat
count, whether guests return their own trays, delivery
share of sales, whether sauces and napkins are self-
serve stations, a description of the floor layout].

Three fixed zones:

1. Ordering area:
- Packaging supplies (bags, boxes, cups) restocked
  to [count] per the rush standard
- Register-side stock: receipt paper, coins and small
  bills, straws
- Point-of-sale materials: menu boards and promo
  materials updated, and today's sold-out items
  pulled - leave a sold-out item up, and every single
  order at peak gets an on-the-spot explanation
2. Pickup area:
- Number display or pickup tickets working
- Expo counter wiped, holding-cabinet supplies staged
- Delivery rack cleared and reset: last period's
  leftovers off the rack first
3. Dining room:
- Tables and chairs squared away, tops wiped (pass
  standard: back of the hand on the table, no stick)
- Sauce station refilled; trash liners changed - by
  foot traffic, change the two that fill first
- Restroom quick check: supplies and floor
- Pathway clear: entrance-to-register route free of
  obstructions

Every item states "how full is full": this store's
rush volumes or a concrete state [ ] - "plenty" and
"adequate" are forbidden words.

Route requirements:
- The list's order equals a physical route: out of
  the kitchen, through the pickup area and dining
  room, ending at the ordering counter - no doubling
  back. Sort it from my layout description
- Five minutes before the rush, walk the same list
  once more marking only "enough / not enough"; fix
  or escalate whatever isn't

Output format:
- Table: sequence / zone / item / standard for
  "enough" / first move when short
- One closing line: the "ready" action after all
  three zones pass - report "floor ready" to the
  manager on duty

Constraints:
- No facilities I never mentioned (play area, patio
  seating) may appear
- No time-management philosophy - table only
- All rush volumes stay [ ] - no invented numbers

Why it is written this way

"How full is full" is the checklist's soul. "Stock enough supplies" says nothing - enough is a number you can't decide mid-rush, so decide it once: after that, the daily pre-rush check becomes an executable, handoff-able action with the same result no matter who runs it. This is also why every count stays blank: the number can only come from this store's own rush history and must not be invented.

List order equals the walk route, a design aimed at the most common checklist failure mode. When items are grouped by category (supplies together, cleaning together), the person executing has to thread their own route through the room, and threading is where items drop - "I'll come back for that" becomes never once the rush hits. Making the list itself the route turns sequence numbers into footsteps: walk finished, check finished.

The explicit "ready" report can't be cut. Without a reporting node at the end of prep, "I thought she restocked it" is how rush-hour accidents are born; one sentence - "floor ready" - cleanly closes the prep phase so the manager on duty never has to interrogate item by item.

Sold-out signage holds its own line because it never appears in any "supplies" category, yet it's the counter's biggest hidden time cost at peak: thirty seconds of "we're out of that today" times a lunch rush costs more than two missing napkin packs. Made a fixed pre-rush action, the cost drops to zero.

Variables