BBQ server table-service checkpoint list - eight checkpoints from order read-back to stick counting at checkout, each with "what counts as done" nailed down

You are the trainer at a BBQ restaurant. Generate a table-service checkpoint list for servers covering one table's full journey from seating to send-off. My shop: [stick-count billing yes/no, self-serve dips yes/no, outdoor seating yes/no, checkout method].

Fixed scope, eight checkpoints, no additions or removals:

1. Seating: stick cup, napkins, utensils down; parties with children seated away from the serving aisle and the grill's hot zone
2. Order: full read-back before submitting - items and bunch counts, heat, dip, exclusions, drinks - confirmed, then entered. The read-back is reciting, not asking ("five bunches of lamb, medium, dry dip" - not "what was it you ordered?")
3. Skewers to table: announce each item; stick handles aligned the same way for easy grabbing; warn hot on fresh-off items; keep the meat-then-vegetable sequence (matching what was promised at ordering)
4. Drinks: open bottles at the table - unopened ones can be returned or swapped, opened ones become an argument; draft poured full with no short foam; glassware arrives with the drink
5. Mid-meal sweep: swap the stick cup at two-thirds full (in a stick-count house the sticks are money, and a full cup spills and cross-contaminates tables); clear empties to make room for the next round; top up dips once; ask about add-ons in passing
6. Table safety: wipes or napkins kept stocked (hands with no place to wipe end up on trousers); a word to the adults about keeping children clear of sticks and the grill
7. Pre-checkout: audit what was served against the order - missing, extra - before announcing the number, not by flipping through tickets in front of the guest; in a stick-count house, count sticks in front of the guest and announce meat and vegetable counts plus the total
8. Send-off: remind about belongings (phone in the chair seam, jacket on the back); reset outdoor furniture; do not rush the stick cup - clearing the table before guests stand up reads as eviction

Every item must carry "what counts as done," written as a checkable action, not an adjective:
- Fails: "warm, attentive service"
- Passes: "before submitting, the items, counts, heat, and exclusions are read back in full and the guest nods"

Every item gets one of two levels:
- Every table: a miss causes direct loss or an incident (read-back, opening bottles at the table, counting sticks)
- As-you-can: allowed to slip when slammed, but done the moment it is seen (clearing, topping dips, swapping a two-thirds-full cup)

Output format:
- Table: checkpoint / what / what counts as done / what the miss costs / level
- The "what the miss costs" column must be concrete: money lost, complaint filed, or reputation dented - named, separately
- Follow with the "five-second table scan": the fixed order for checking five points on one table from across the room (stick cup - tabletop - drinks in glasses - dips - people)

Constraints:
- No configurations I did not mention (no self-serve dips, no dip-station items)
- No "smiling service" or "proactive warmth" - nothing uncheckable
- Money and quantity conventions left at [ ]
- Output only the table and the scan; no explanatory prose

Why it is written this way

The "what the miss costs" column is the lever of the whole list. Ordinary service lists state only "what to do," and to the person executing it everything weighs the same - ticks are ticks. "Missed the heat read-back = a torched batch plus a table waiting for round two" and "skipped opening bottles at the table = an unresolvable return dispute" write each checkpoint's failure cost as concrete money, complaints, or reputation - a new server sees the minefield on first read, and the trainer finally has something to point at.

Standards rewritten as checkable actions keep the list from decaying into wall decoration. "Attentive service" cannot be inspected; "before submitting, read back items, counts, heat, and exclusions in full, and enter only after the guest nods" can - a supervisor hears one read-back from across the room and knows. "Swap the cup at two-thirds full" supplies a physical gauge, an order of magnitude more executable than "change cups promptly": in a stick-count house the sticks are money, and a full cup that spills or mixes tables is tomorrow's checkout dispute.

The "five-second table scan" subtracts work from the busiest checkpoint. Mid-meal, one server watches four or five tables; item-by-item inspection is impossible, but a fixed order (cup - tabletop - drinks - dips - people) covers eighty percent of anomalies in five seconds. The order itself is deliberate: objects before people, the cup first because it is money, people last because judging whether to offer an add-on takes the longest. A list's usability is not completeness - it is whether it still gets used during the rush.

"Do not rush the stick cup" is written out explicitly because it is the best-intentioned mistake in the closing sequence: clearing before guests stand signals eviction, and the guest who stays ten more minutes to finish the drink after paying is very often the one who brings friends next time. Table-turn pressure at a skewer house is real, but the pace should be set by the next table waiting, not by a server's tidying reflex.

Variables