How many people you actually need, by role and by shift — and the scheduling habit that keeps labor cost from quietly eating your margin.
Front of house (FOH) is everyone the guest interacts with directly: hosts, servers, bartenders, bussers, and often an expo person calling out tickets at the pass. Back of house (BOH) is the kitchen: line cooks, prep cooks, dishwashers, and whoever is running the pass when that role isn't split out separately. The split matters because the two teams scale on different drivers. FOH scales with covers, meaning how many guests you are seating and turning through the dining room in a given period. BOH scales more with menu complexity and volume together, meaning how much of the menu is made from scratch and how many of those items are moving through the kitchen at once.
Priya opens a 60 seat New American restaurant with a six item entree list, most of it built from a handful of proteins and a rotating vegetable side. Her BOH is lean: two line cooks and one prep cook can run a full Friday night. Two miles away, a 45 seat brunch spot with a 20 item menu of scratch made hollandaise, pastries baked in house, and a dozen egg preparations needs three line cooks and two prep cooks to hit that same 60 covers, because the kitchen's workload is set by the menu, not the seat count. Both restaurants need roughly the same FOH headcount for that many covers, because a table is a table no matter what's coming out of the kitchen. This distinction earns its keep the moment you sit down to build a labor budget or write a job posting. Treating "restaurant staff" as one undifferentiated line item hides where the money is actually going and makes it hard to answer a simple question: is this Friday's overtime a FOH problem or a BOH problem. It also shapes how you think about cross training. A server picking up bussing shifts is a small stretch. A server picking up prep cook shifts is a different job entirely, and scheduling as if it isn't sets someone up to fail.
Rough starting ratios (adjust for your actual menu and layout)
| Typical ratio | Scales with | |
|---|---|---|
| Servers | 1 per 3 to 5 tables (casual) or 1 per 2 to 3 (full service) | Number of tables/covers, not total sales |
| Line cooks | 1 per station (grill, saute, fry, etc.) | Menu complexity and number of active stations |
| Prep cooks | Scaled to how much made-from-scratch prep the menu requires | Menu complexity, not covers |
| Dishwashers | 1 per shift minimum, even at low volume | Covers and how much is plated vs. to-go |
These are starting points, not rules. A scratch kitchen with a long prep list needs more BOH labor than a menu built around a few high quality proteins with simple sides, even at identical covers. Track how long your actual team takes to prep for a normal night, and let that set your real ratios.
Put numbers on it. An 80 seat full service Italian concept with a wood fired oven typically runs four line stations (grill, saute, pasta, pizza) plus two prep cooks and a dishwasher on a Friday night. A 40 seat fast casual sandwich shop covering that same 80 guests over a lunch rush can run on one line cook and one prep cook, because there is only one real station and most of the menu is assembled rather than cooked to order. Same covers, very different kitchens.
The single biggest scheduling mistake in restaurants is treating every day like it has the same demand curve. It doesn't. Most restaurants have a small number of shifts that generate a disproportionate share of weekly revenue, and a schedule that doesn't flex around that guarantees a bad labor percentage on the slow shifts.
A simple starting method
Pull your last 8 to 12 weeks of hourly sales data (most POS systems report this). Schedule staff hours as a percentage of that hour's historical sales share, not as a flat headcount per shift. A Tuesday lunch that historically does 40% of a Saturday lunch's sales should be staffed at roughly 40% of the Saturday lunch crew, not the same crew.
Marisol runs a 50 seat Mexican restaurant and pulls ten weeks of hourly POS data before building her next schedule. Tuesday lunch averages $850 in sales across that window. Saturday lunch averages $2,150. Tuesday is running at about 40 percent of Saturday's volume, so instead of scheduling the same five servers on both shifts out of habit, she schedules two servers and a food runner on Tuesday and keeps the full five person crew for Saturday. Her Tuesday labor cost as a percentage of sales drops from an uncomfortable 38 percent to a much healthier 24 percent, without cutting a single shift she actually needed.
Redo this exercise every few months, not once and never again. A slow Tuesday lunch that turns into a busy one after a new office building opens down the street will punish a schedule built on outdated historical data just as surely as one built on no data at all.
Everything above assumes you already have weeks of sales history to schedule against. A lot of real decisions happen before that data exists: a new restaurant's first month, a new shift you've never run before, or a concept that simply doesn't have eight clean weeks of numbers yet. Use the branches below to find a reasonable starting point, then correct it against real sales as soon as you have any.
Where do I start staffing?
Do you have at least 8 to 12 weeks of hourly sales data for this shift from your POS system?
Most of the labor problems above show up as one of a small handful of recurring mistakes. None of them are exotic. They're habits that feel reasonable in the moment and only look wrong once you compare them to what the sales data or the schedule itself is actually saying.
Worth checking against your own schedule
0/4What varies by state and city
Scheduling touches more state and local labor law than most new operators expect, and the specifics vary too much by state, and sometimes by city, to summarize safely here. This is general orientation, not legal advice. The categories below are things to check for your specific location before finalizing a scheduling policy, not settled facts you can rely on as written.
What varies by state
Key Terms
Check your understanding
Two restaurants each serve 80 covers on a Friday night. One has a six item menu built around a rotisserie and simple sides. The other has a 20 item scratch menu with several made-to-order sauces and house baked bread. Which team most likely needs more BOH labor for that same 80 covers?
A restaurant's Wednesday lunch historically runs at about 30 percent of Saturday lunch's sales, and Saturday lunch is staffed with 6 servers. Using the historical sales share method, roughly how many servers should Wednesday lunch be staffed with?
A kitchen manager closes the restaurant at 11pm after a busy Friday, then is scheduled to open the kitchen again at 6am Saturday for prep. What is the main practical risk this creates, beyond the manager's fatigue?
A restaurant has been open for nine days and does not yet have reliable sales history. Which approach fits that situation best?
Ask a question about this lesson or share your take.
Loading…
Sanity check the ratios against labor cost percentage
Once you've built a schedule from ratios like these, check what percentage of that shift's projected sales the scheduled labor hours would cost. Most full service restaurants target a total labor cost percentage in the low to mid thirties, and most quick or fast casual concepts target the low to mid twenties, since their labor is lighter relative to their price points. If a ratio-based schedule prices out well outside that range for your concept, recheck the ratios against your actual sales rather than trusting the rule of thumb on its own.
Check your state department of labor's website for statewide rules, and separately check whether your city has its own fair workweek or predictive scheduling ordinance, since many of these are municipal rather than statewide.