Full-service restaurant server - menu-driven table setting checklist - whole fish on tonight's order means serving cutlery and a fish knife; shellfish means finger bowls; the table follows tonight's menu, not habit
You are a shift lead for servers at a full-service restaurant. Write me a "menu-driven table check" checklist. When to run it: after the order is in, [30] minutes before service, table by table - especially private rooms and banquet tables - checked against the actual dishes that will hit that table tonight. Note: this is not the general setting-and-hygiene routine - that is someone else's list; this one checks only the menu-difference items, the things tonight's specific dishes require that are not set by default.
Checklist structure: every line has three columns - what to check (a concrete, tickable item) / why (which dish drives it) / what breaks when it is missing (the on-the-floor consequence). Organize by trigger:
1. Menu-triggered specialty items
- Whole fish or seafood on the order -> serving spoon and fork on the table, fish plate, fish knife and server; shell-in dishes (shrimp, crab, clams) -> add finger bowls (warm water), because without them guests are eating with their hands
- Soup or casseroles -> soup bowls and spoons per cover, a serving ladle, underplates for casseroles
- Plated-service items (per-cover courses, hosted room dinners) -> service flatware counted and staged in the side station, not on the table
- Hand-torn or bone-in centerpieces (roast ribs, shredded chicken) -> serving tongs plus a generous spare-stack of change plates
2. Covers and service type
- Total change plates = covers x (1 + house plate-change count) - full-service tables turn plates more than feels natural; the spares live in the side station, not on the table
- Tea setting and glassware matched to the drinks order (white liquor / wine / beer glasses); corkscrew and ice bucket within reach, not in the storeroom
- Banquet tables: place cards, table number, lazy Susan turning smoothly, menu cards if used
3. Order-note catch-alls (every special note on the ticket, item by item)
- Allergy / restriction flags -> beyond informing the kitchen, the table side keeps serving chopsticks set apart
- Children on the booking -> high chair, child-safe ware, seating away from the Susan's edge
- Cake ceremony / longevity noodles -> timing, ware, and storage location all three confirmed
- Wine brought by the guest -> matching glassware ready, corkage terms already settled with the booker - never negotiated at the table
4. Flow and safety
- Service entrance kept clear: in private rooms the service position is fixed, and hot dishes never pass between the host and the guest of honor
- No chipped or cracked ware on the table - damaged pieces get swapped, not tolerated
Execution basis (printed at the end of the list):
- Who checks: the table's own server; the shift lead spot-checks [2] banquet tables
- When: complete [30] minutes before service, signed and handed in
- When an item is missing: report to the pantry immediately; anything that cannot be restocked in time goes to the shift lead for a fallback - never open the doors on "we'll probably make it"
Forbidden:
- No "table neat and attractive" lines - anything untickable does not belong
- Every line is a concrete item or state, checkable and signable
- This list does not cover general hygiene or default settings - the boundary is stated explicitly
Why it is written this way
The moment a missing item is discovered sets its price: before service it costs a walk to the pantry; during service it costs a sprint in front of a full table. And what gets missed is almost never the default setting (plates and teacups go out daily on muscle memory) - it is the difference items: the serving cutlery tonight's whole fish implies, the high chair this booking's toddler implies. Hence the menu-driven design: run tonight's actual menu per table, not a setting standard that never changes with the seasons.
The "what breaks" column is not decoration - it explains to the person executing why the line exists: a missing finger bowl leaves a guest with shellfish hands and nowhere to put them, and the polish of the whole service zeroes out in that moment. Servers who understand consequences check honestly; hand them a bare item list and within three months someone will tick every box from the pantry.
The plate-change count in the covers section is full-service arithmetic: a hosted dinner changes plates three times, and a side station without spares means the whole table waits with dirty plates after course two - the same experience disaster as slow food. The math (covers x changes) is not obvious mid-shift, so the checklist does it for them.
The order-note section translates "special notes" into objects and actions: a cake ceremony means confirming timing, ware, and storage location - three things, not a note to "remember the cake". Corkage gets settled before doors open because a pricing dispute in front of guests humiliates both sides. The execution basis (who, when, what happens to misses) turns the sheet into a signed record instead of another poster on the wall.
Variables
| Variable | Notes |
|---|---|
| Pre-service timing | How many minutes ahead the check completes - 30 suggested; banquet days run earlier |
| Plate-change count | How many times plates change in this house - the multiplier for spares, tiered by service type (hosted vs family) |
| Specialty ware table | The full dish-to-ware mapping for this menu - confirmed by manager and head chef, refreshed with menu seasons |