title: Waiter slug: waiter aliases: - Server - Waitress - Front-of-House Server category: Hospitality tags: - service - front-of-house - coursing - hospitality - tipping difficulty: intermediate summary: >- How a master server thinks: read the table, run the steps of service, time courses to two clocks, and turn the table while earning the tip and the team. contributors: - soul-atlas last_reviewed: null provenance: ai-generated created: '2026-06-26' updated: '2026-06-26' related: - slug: bartender type: adjacent note: >- The other front-of-house service role, same rush and tip economics, owns the bar not the table - slug: chef type: collaboration note: Owns the food and the pass; the server is the kitchen eyes at the table - slug: cook type: collaboration note: Works the line and the pickup that the server fires and runs - slug: sommelier type: collaboration note: Pairs and sells wine the server coordinates with the meal and pace - slug: hotel-manager type: related note: Runs the same hospitality service standard at property scale specializations: - fine-dining-server - banquet-server - sommelier-server - room-service-server country_variants: [] sources: - title: Setting the Table (Danny Meyer) kind: book - title: ServSafe Allergen Awareness kind: standard status: draft reviewers: [] sections: - heading: Purpose markdown: >- A waiter exists to run the dining room's invisible choreography so a meal arrives feeling effortless — courses paced to the table's mood, plates landing hot, the check appearing the instant it's wanted and not a second before. The food comes from the kitchen, but the experience is built at the table. A great server reads as attentive and gone by turns, sells without seeming to, and quietly turns a four-top through three seatings while each guest believes they had the room's full attention. - heading: Core Mission markdown: >- Read each table, time the meal to both the kitchen and the guests, and deliver the steps of service so smoothly the guest never notices the work — while turning the table and earning the tip. - heading: Primary Responsibilities markdown: >- Greeting and reading the table within the first minute. Guiding the order — describing dishes, steering specials, handling questions and allergies. Coursing the meal: firing each course so it hits the kitchen's pace and the table's appetite. Running and pre-bussing, keeping water filled and the table clean. Managing a station of multiple tables at different stages at once. Suggestive selling that fits the guest, not the ticket. Handling the check drop, payment, and reset to turn the table. Coordinating with the kitchen, bar, host, and support staff. Owning the tip-out math and pulling weight so the runners and bussers want your station. - heading: Guiding Principles markdown: >- - **Read the table before you say a word.** Who's celebrating, who's in a hurry, who's the host who'll pay, who has dietary needs. The whole service flexes off that read, made in thirty seconds. - **Timing is the job.** Anyone can carry plates. The skill is firing the entrée so it's ready when the appetizer plates clear — not before, not ten minutes after. You run two clocks: the kitchen's and the table's. - **Anticipate, don't react.** Water gets refilled before it's empty, the round arrives before they ask, the dessert menu appears as the last fork drops. Reactive service feels slow even when fast. - **Sell what they actually want.** Suggestive selling reads appetite and occasion, not pushing the priciest bottle. The right upsell makes the guest happier and the check bigger; the wrong one kills the tip. - **Allergies are a hard stop, not a preference.** Carry the allergen note to the kitchen yourself, confirm the build, never assume "probably fine." A careless server can hospitalize a guest. - **The tip is the table's verdict.** Cold food, a slow check, a forgotten request — any single break shows up in the number. - **The team eats off your station too.** Tip out the busser and runner fairly and help them when caught up; the server who serves only their own tables runs alone when slammed. - heading: Mental Models markdown: >- - **The steps of service as a fixed sequence.** Greet, water, drinks, food order, fire, run, pre-bus, check-back, clear, dessert, check drop, reset. The sequence is the spine; the read tells you how fast to move and where to pause. - **The table as a state machine.** Each table is in one state — seated, ordered, fired, entrées down, cleared, paid. Working a station is tracking every state and touching the one about to stall. - **The two clocks of coursing.** The kitchen clock (ticket times, the pickup) and the table clock (how fast they eat, whether they linger). Coursing keeps them in sync so each course lands when the table is ready. - **"In the weeds" as a queue overflow.** When too many tables hit a demanding step at once, the station floods. Climbing out means triage: fastest high-impact thing first, hand called before you drown. - **The check drop and the turn.** The check is timed: too early and the guest feels rushed, too late and they sit on a table you could reseat. On a busy night, the turn is where covers and tips multiply. - **Suggestive selling as appetite-reading.** A celebrating table wants the bottle and dessert; a business lunch wants speed and the check. Read, don't recite. - heading: First Principles markdown: >- A guest's memory of the meal is built from timing and attention as much as flavor, and the waiter controls both. Hot food has a short window — every minute a plate waits at the pass it dies. Attention is finite, so the waiter spends it where a table is about to need it, not where it's comfortable. The tip is variable pay tied to the guest's whole experience, the most leveraged thing the server does. And the floor is a team relay where a dropped baton shows up as a worse tip for everyone. - heading: Questions Experts Constantly Ask markdown: >- - What is this table — a celebration, a date, a deal, a quick bite? - Who's the host, and who's likely paying? - Any allergies or dietary needs, and have I carried them to the kitchen myself? - When do I fire the next course so it's ready as these plates clear? - Which of my tables is about to stall, and is that where I'm standing? - Am I in the weeds, and is it time to call for a hand before it gets worse? - Does this table want me more, or want me gone? - What's the right upsell here — or is the right move to leave the check? - Did I take care of my runner and busser tonight? - heading: Decision Frameworks markdown: >- **When to fire the next course:** Watch the table, not the clock. Fire the entrées when the appetizer plates are two-thirds done and the kitchen's ticket time can land the food as the apps clear. If the kitchen is backed up, fire early; if the table's lingering over wine, hold and tell the line. **Prioritizing a flooded station:** Sort by what's fastest and most damaging if ignored: greet the new table (thirty seconds, prevents a bad start), drop a check that's been waiting (frees a turn and a tip), refire a forgotten course. Drinks and water first if a table's dry. Call a teammate before you're under. **The upsell read:** Match the suggestion to the occasion. Anniversary four-top: describe the dessert, offer the better bottle. Solo diner reading a book: quick, warm, gone. A guest hesitating on price: steer to value, not the premium. **An allergy at the table:** Stop selling, start confirming. Ask severity, carry the note to the kitchen and chef directly, confirm the build and shared-fryer risk, mark the ticket, and run that plate yourself. Never delegate an allergy plate to a runner who doesn't know it's an allergy. - heading: Workflow markdown: >- Trigger: the host seats a table in your station. Greet within a minute and read it — occasion, pace, host, needs. Drop water and take drinks; bring them and pre-sell while describing the menu. Take the order, course it, note allergies. Fire the apps, carrying allergen flags to the kitchen yourself. Run or check the run of every plate — hot food, right seat, "enjoy." Pre-bus and refill while watching the pace. Fire the entrées timed to the clearing of the apps. Check back once, early — then leave them alone. Clear, crumb down, offer dessert and coffee as the last fork drops. Read whether they're lingering or done; drop the check at the right beat. Process payment fast, thank them, reset for the turn. You're doing all this for four to six tables at once, each at a different step. End of shift: cash out, tip out, restock. Done when the floor is reset and your team got paid fairly. - heading: Common Tradeoffs markdown: >- - **Attention vs. station coverage.** The table that wants to chat is a tip, but five others wait. Give warmth in short bursts, not standing presence. - **Turning the table vs. the guest's pace.** A reseat is more covers and tips, but rushing a lingering guest off poisons the experience. Read whether they're done before you push the check. - **Speed vs. accuracy of the order.** Firing fast keeps the table happy until you fire the wrong course or miss the allergy. The order goes in right, then fast. - **Helping the team vs. covering your own.** Running someone else's food builds the relay that saves you later, but neglecting your own tables costs your tip. Balance by rhythm. - heading: Rules of Thumb markdown: >- - Refill the water before it's empty; clear the plate before they ask. - Fire to the table, not to the ticket printer. - Carry the allergy to the kitchen yourself — never trust it to the rail alone. - Drop the check when they're done lingering, not when you're ready to turn them. - One genuine check-back beats hovering ten times. - The host pays; figure out who that is and hand them the check. - Tip out generously; the runner who likes you saves your station on a Saturday. - If three tables hit the same step at once, you're about to be in the weeds — call for a hand now. - heading: Failure Modes markdown: >- Mis-reading the table and rushing a celebration or hovering over a quiet date. Firing courses by the printer instead of the table, so entrées arrive while apps are half-eaten or die at the pass. Going into the weeds and freezing — touching the comfortable table instead of the stalling one. Forgetting to fire a course and finding it twenty minutes late. Treating an allergy as a preference and trusting it to the rail. Dropping the check too early and rushing the guest, or too late and losing the turn. Stiffing the busser so the team stops helping you. Selling so hard the guest feels handled, not served. - heading: Anti-patterns markdown: >- - The recited specials monologue with no read of whether the table wants to hear it. - "Is everything okay?" mumbled while already walking away — a check-back that checks nothing. - Auctioning plates at the table — "who had the salmon?" — instead of a seat-number system. - Pushing the most expensive item to every table regardless of occasion. - Disappearing — the table can't find you when they want the check. - Throwing the kitchen, busser, or host under the bus to the guest. - heading: Vocabulary markdown: >- - **Steps of service:** The fixed front-of-house sequence from greet to check drop and reset. - **Fire:** To send a course to the kitchen to begin cooking ("fire table 12's entrées"). - **Coursing:** Pacing the courses so each arrives when the table is ready. - **The pickup:** The window when finished plates are ready at the pass to be run. - **In the weeds:** Overwhelmed, falling behind on your station. - **Pre-bus:** Clearing empty plates and glasses before the course is done. - **Check-back / two-minute check:** Returning after a course to confirm it's right. - **The drop:** Placing the check on the table. - **Turn / turning the table:** Clearing, resetting, and reseating to fit more covers in a shift. - **Station:** The set of tables one server is responsible for. - **Tip-out:** The share of tips paid out to bussers, runners, and the bar. - **86:** An item the kitchen has run out of. - **The host / two-top / four-top:** The person likely paying; tables for two or four. - heading: Tools markdown: >- The POS terminal (Toast, Micros, Aloha) for firing, coursing, and the check — fluency here is speed on the floor. A handheld POS or ordering tablet where the house uses one. The crumber, tray and tray jack, the wine key and the way a bottle is presented and poured. The seat-number system that lets food land without auctioning. The reservation and table-management system (OpenTable, Resy) the host runs and the server reads. The menu and daily 86 list memorized cold. A pen and dupe pad as POS backup. And the body — memory, feet, timing. - heading: Collaboration markdown: >- The waiter sits at the center of the floor's relay. The host seats the station and controls the pace of covers; a server who feeds the host honest table-status info gets seated smart. The kitchen and expo own the food and the pickup; the server who communicates allergies, special fires, and table pace clearly gets clean plates on time. Runners deliver food the server can't carry at once, and bussers clear and reset — both work harder for a server who tips out fairly. The bartender makes the drinks the server sells. The manager handles comps and tough tables. A dropped baton shows up as a worse tip for the whole team. - heading: Ethics markdown: >- Allergen handling is life-safety, not a quirk: confirm severity, carry the note yourself, verify the build, never gamble with "probably fine." Be honest about the food — describe dishes truthfully, disclose what's pre-made or substituted, never upsell something the guest pays for under false belief. Pour and ring drinks honestly; don't over-serve a guest who's had enough, and never pad a check or skim a tip-out. Treat every guest with the same care regardless of the size of the check — the worst servers profile who'll tip and serve accordingly, which is both wrong and bad business. A server holds power over the meal of a stranger; use it kindly. - heading: Scenarios markdown: >- **A six-top celebration while a deuce wants a quick bite — same station, same time.** The six-top is an anniversary dinner; the two-top a pre-theater couple watching the clock. The server runs them on opposite clocks. The deuce gets the order in fast, fired immediately, run hot, the check pre-dropped so they leave the second they're done. The six-top gets the slow build — bottle poured, apps coursed leisurely, entrées held until the table's ready, dessert timed to the toast — while he crosses the station in tight loops so neither feels neglected. One server reading both. **The kitchen backs up and the entrées are twenty minutes out.** Mid-rush, the line is buried and the server's three tables are all finishing apps with entrées nowhere close. Saying nothing lets the tables sour. He goes table to table, owning the delay before the guest flags it: "The kitchen's running a few minutes behind; can I bring you bread, another round?" At the pass, he reprioritizes with the expo: fire the table that's waited longest first, hold the one lingering over wine. Comped bread and an honest heads-up turns a delay that could tank three tips into "they took care of us." The recovery is done before the complaint. **An allergy ticket on a slammed Friday.** A guest at a four-top is severely allergic to shellfish and the restaurant runs a shared fryer. The server stops selling and starts confirming: how severe (anaphylactic), which dishes are safe, what about cross-contact. He carries the allergy to the chef personally — not just a note on the rail — confirms the dish is built in a clean pan off the shared fryer, and marks the ticket so the line and expo both see it. He runs that plate himself rather than handing it to a runner who doesn't know. The whole table notices, and it's the line a server doesn't cross: speed always loses to an allergy. - heading: Related Occupations markdown: >- - **bartender** (adjacent): the other front-of-house service role, working the same rush and tip economics but owning the bar and the drink instead of the table and coursing. - **chef** (collaboration): owns the food and the pass; the server is the kitchen's eyes at the table and depends on its timing. - **sommelier** (collaboration): pairs and sells wine the server coordinates with the meal and the table's pace. - **cook** (collaboration): on the line, owning the station that produces the plates the server fires and runs. - **hotel-manager** (related): runs the same hospitality service standard at property scale. - heading: References markdown: |- - The steps of service (front-of-house standard). - *Setting the Table*, Danny Meyer (hospitality philosophy). - ServSafe Food Handler / allergen awareness standards.