How Many Employees Should I Schedule Each Shift at My Vegan Restaurant in 2026?

The Tuesday I paid eight people to watch each other

The first schedule I ever wrote for a plant-based restaurant had eight names on it for every single shift, seven days a week. Not because I had modeled anything — because eight felt like a restaurant. Two on the line, one on cold prep, one on the juice and smoothie station, a dishwasher, two servers, a host. It looked balanced on paper and it looked like a staffing brochure. What it actually was, in practice, was a fixed cost stapled to a wildly variable revenue line.

Tuesday would do roughly $750 in gross profit across lunch and dinner. Friday would do $1,625. The schedule did not move. So on Tuesday I had eight people producing about $94 each in gross profit, standing in each other's way, wiping down already-clean prep tables at 2:40 in the afternoon, and quietly resenting me for cutting nobody. On Friday those same eight people were producing $203 each, tickets were hanging, the cashew queso ran out at 7:15, and the dining room got a version of service I would not have paid for myself.

Both days were broken by the same mistake, which is worth naming precisely: I had chosen a headcount and then hoped the revenue would show up to justify it. Every restaurant that bleeds labor dollars does some version of that. The count comes from habit — from what the last owner ran, from what the schedule template defaulted to, from what feels safe on a Saturday — and the money is asked to catch up afterward.

The specific way this bites a vegan restaurant is worth spelling out, because the generic advice does not account for it. The check averages are lower. A steakhouse selling a $45 entrée covers a big slice of hourly labor in three covers. A fast-casual plant-based concept selling an $18 bowl needs closer to five or six covers to reach the same place. That means the same absolute staffing error costs you more covers to dig out of. Meanwhile the prep burden runs the other direction: soaking cashews, pressing and marinating tofu, building every sauce from scratch because there is no shortcut jar of the vegan version, breaking down whole vegetables that a conventional kitchen would buy portioned. Higher prep hours, lower ticket. That is the squeeze, and a flat eight-person Schedule does absolutely nothing about it.

What fixed it was not a better feeling. It was a divisor. Once the count came off arithmetic instead of instinct, Tuesday shrank, Friday grew, labor percentage fell into a range I could defend to a lender, and the arguments about who got cut stopped — because nobody was being cut by a person anymore. They were being scheduled by the day's own revenue.

How the gross-profit divisor actually produces a headcount

The mechanism has three moving parts, and it fails when you skip any of them.

Part one: agree on a per-employee daily gross-profit floor. Sit down with your kitchen lead and your front-of-house lead and settle on a single number — the gross profit one average employee should produce working an average shift on an average day. In my restaurant that number was $125. It matters enormously that this is a floor and not a ceiling. You say it out loud to the whole team: show up, take care of a normal load of covers, give normal service, and you produce no less than $125 in gross profit. The people who want to make real money do not coast to $125 and clock out; they hit it on average work and then turn another table, sell another round of house kombucha, upsell the dessert. What the number buys you is one shared yardstick — the same one used by the owner, the general manager, the line cook, and the server — so scheduling stops being a personality contest.

Set that floor from your own numbers, not mine. Take your trailing gross profit for a period, divide by the labor hours you actually ran during it, and multiply by an average shift length. If that arithmetic tells you your crew currently produces $96 per person per day, then $125 is a target you build toward over a quarter, not a stick you hit people with next Monday.

Part two: pull gross profit by day of week. Average your gross profit for each weekday over a trailing three to six months. Three months is the minimum that smooths out a bad weather week; six is better if your neighborhood has any seasonality. Use gross profit — sales minus cost of goods — rather than gross sales, because a plant-based menu's food cost varies enormously between a $6 side of roasted vegetables and a $17 bowl carrying avocado, cashew cream, and hearts of palm. Two days with identical sales can leave you very different money to pay people with.

Part three: divide, then place. Monday averages $750; $750 ÷ $125 = 6 Employees. Friday averages $1,625; $1,625 ÷ $125 = 13. Now the count is settled and the only remaining question is *when*, which is a different data pull: hourly sales, so you can see when tickets actually fire. A concept with a brunch wave and a dinner rush staffs a heavy open, thins hard through the afternoon lull, and staffs a heavy close. A dinner-only concept front-loads prep and stacks the back half of the evening.

Notice the loop back to the top. The floor is not set once. After a month of scheduling this way you compare what each day actually produced per employee against the $125 and adjust — if Wednesdays consistently return $160 per person, you were understaffed and losing covers; if Saturdays return $98, you overstaffed the gap hours.

One clarification that trips people up: the divisor gives you employee-days, not simultaneous bodies. Thirteen on a Friday does not mean thirteen people standing on the line at 7 p.m. It means thirteen shifts across the operating day — a prep cook in at 8, three lunch bodies, a single afternoon gap body, then the dinner block. Peak concurrency on that Friday might be eight or nine. Confusing the two is how people look at a thirteen and decide the math is broken.

Real numbers: covers, labor hours, and what each day should cost

Here is the benchmark set I actually use, with the reasoning attached so you can adjust it to your own concept rather than copying it blind.

Labor percentage target: 28–33% of gross sales, including management. Mainstream full-service guidance usually lands at 25–30%. A plant-based kitchen sits a few points higher for structural reasons: more scratch prep hours per dollar of revenue, and a lower average check spreading fixed labor across fewer dollars. If you are consistently above 35%, you are overstaffed or under-priced. If you are running under 25% at a scratch vegan concept, look hard at whether service quality and prep depth are quietly degrading — that number is often a symptom rather than a win.

Covers per labor hour: roughly 8–12. This is the single most useful operating ratio, and it varies with menu complexity. A counter-service bowl-and-wrap concept with three sauces and a simple build can run at the top of that band or above it. A full-service restaurant doing fermented components, house-made seitan, plated desserts, and a cocktail program runs at the bottom. Compute yours weekly: total covers ÷ total labor hours worked. Track it as a trend line, not as a single week.

Break-even covers per hour. Take your fully loaded labor cost per hour — wages plus payroll taxes plus workers' comp plus any benefits, which typically runs 15–25% above base wage — and divide by your gross profit per cover. If you are carrying $200 per hour in fully loaded labor and your $18 average check yields roughly $12 in gross profit after food cost, you need about 17 covers an hour to cover labor alone. Run that number for your own concept and write it on the wall of the office. It is the fastest sanity check on any proposed Shift.

Worked example, a full week. Take a fast-casual vegan Restaurant with the following trailing weekday gross-profit averages: Monday $750, Tuesday $760, Wednesday $900, Thursday $1,100, Friday $1,625, Saturday $1,750, Sunday $1,250. At a $125 floor: 6, 6, 7, 9, 13, 14, 10 — 65 employee-shifts across the week. Under the old flat-eight schedule that same week ran 56 shifts, but distributed catastrophically wrong: eight on a Monday that justified six, eight on a Saturday that justified fourteen. The flat schedule was simultaneously overstaffed and understaffed, which is why it felt like nothing ever worked.

What the fix is worth in dollars. Moving four people off a dead three-hour Saturday afternoon block at $16 an hour saves $192 in direct wages before payroll taxes — call it about $230 fully loaded. Do that every Saturday and it is roughly $12,000 a year in a business where the entire net margin might be a few points. On the other side, the Friday that went from eight to thirteen recovered covers I had simply been turning away: tables that walked because the wait was quoted at fifty minutes with an empty four-top visible from the door.

The prep overlap, priced out. Most generic scheduling templates assume 15–20 minutes of prep per hour of service. A scratch vegan kitchen frequently needs double that. Cashew cream needs a soak and then real blender time. Tofu needs pressing and marinating hours ahead. Nut-based cheeses need culture time measured in days, not minutes. So carve out a dedicated prep shift that arrives roughly 90 minutes before service and leaves as service ramps. At $18 an hour that body costs you about $27 in wages per day, or $150–200 a week fully loaded across the week. What it returns is line cooks who start service with their mise ready instead of blending sauce between tickets — routinely a few points of labor percentage, because the expensive hours during rush stop being spent on work that could have been done at 8 a.m. by one person.

Staffing bands by day type, for a mid-size room. A weekday lunch doing 40 covers: two to three total bodies on the clock at once. A weekday dinner doing 55: three to four. A weekend lunch doing 60 in a two-hour compressed window: four to five, because compression matters more than volume. A weekend dinner doing 90–120: six to eight concurrent, plus the prep and gap shifts that push the employee-day count into the low teens. These are concurrency bands; the divisor still governs the total.

Trade-offs: three-shift splits, flat schedules, and what each costs

Once the count is right you still have to choose a shape, and the shapes have real costs.

The flat two-shift day. Open crew, close crew, same headcount straight through. Its only virtue is simplicity — the schedule takes ten minutes to write and nobody has to think about a gap. Its cost is the dead window. A vegan Restaurant with a strong Saturday lunch (say 60 covers between 11:30 and 1:30) and a strong Saturday dinner (90 covers after 5) often has a genuinely empty 2:00–4:00 stretch. Keeping four people at $16 through that window burns roughly $190 in wages for takeout volume one person could handle.

The three-shift split. Prep-and-lunch crew from 8 to 2, a single-body gap crew from 2 to 4 handling takeout, restock, and reset, then a dinner crew from 4 to close. On a 180-cover Saturday this typically lands labor in the $1,100 range instead of the $1,450 the flat approach costs, moving labor percentage from the mid-thirties into the high twenties. The trade-off is real and you should not pretend otherwise: split shifts are harder on staff, harder to fill, and in some jurisdictions carry split-shift premium pay or reporting-time pay obligations. Check your state and city rules before you build the schedule around it — the savings evaporate fast if you owe a premium on every split.

Cross-training as the alternative to the split. If splits are legally expensive or your crew hates them, buy flexibility instead of cutting hours. A cook who can run cold prep, the hot line, and the smoothie station lets you carry fewer bodies at any given moment without the coverage cliff. This costs money up front — training hours, a slightly higher wage for the flexible people — and it is the better trade in tight labor markets where a split-shift schedule loses you your best line cook to the restaurant down the street.

Salaried coverage versus more hourly bodies. A working chef or a working GM absorbs peaks without a marginal hourly cost, which is genuinely useful. It is also how owners burn out their best people. If your Friday thirteen is really twelve plus a chef pulling a fourteen-hour day every week, you have not solved the staffing problem — you have moved it somewhere the P&L cannot see it, and you will pay for it later at replacement cost.

On-call and cut-or-keep. The cheapest insurance against a surprise Friday is one person scheduled with an explicit early-cut agreement — they come in, and if covers do not materialize by a set time they go home. This is only fair if it is stated in advance and if the same people are not always the ones cut. Some jurisdictions with predictive-scheduling laws restrict or compensate on-call practices; know your local rules before making it routine.

The pitfalls that break this and how to stay out of them

Confusing employee-days with concurrent bodies. Covered above but it is the number one reason people abandon the method on day one. Thirteen is a day's worth of shifts, not thirteen aprons at 7 p.m.

Using gross sales instead of gross profit. Sales-based staffing quietly overstaffs your high-food-cost days. A day heavy on avocado, nuts, and specialty produce can post strong sales while leaving materially less money to pay labor. Divide the money you actually keep.

Setting the floor at a number nobody believes. If you announce $125 when the crew has been producing $95, you have not set a target — you have announced a layoff, and everyone hears it that way. Set the floor where the business actually is, publish the arithmetic, and move it in increments with the reasons attached.

Ignoring prep in the count. The dedicated prep body is not overhead you trim first when the number looks high. It is the cheapest hour in the building. Cutting it converts $18-an-hour prep work into $22-an-hour line-cook work performed badly during a rush, which is how you run out of a sauce at 11:30 on a Monday brunch that only did 55 covers.

Letting the manager schedule friends. The whole point of a divisor is that it removes discretion from the headcount. If Friday needs thirteen and the schedule says fifteen because two people asked nicely, the method is decorative. Publish the day's gross-profit average next to the day's count on the schedule itself so the arithmetic is visible to everyone reading it.

Refreshing the averages too rarely — or too often. Recompute weekday gross-profit averages monthly on a rolling three-to-six-month window. Weekly recomputation chases noise; annual recomputation means you are staffing last year's restaurant. Between recomputes, adjust for the specific and knowable: a street festival, a holiday, a nearby venue's event calendar, a stretch of weather that reliably moves your patio.

Forgetting compliance mechanics. Overtime thresholds, mandated breaks, minor-labor restrictions, and predictive-scheduling ordinances in some cities all constrain the schedule the math produces. A thirteen-shift Friday built from four people at eleven hours each is a very different cost than one built from six people at seven. Check hours before you publish, not after payroll.

Never asking why the average moved. If Tuesday's gross-profit average climbs from $750 to $900 over two months, the divisor dutifully adds a body — but the interesting question is why. A new office building? A menu change that lifted margin? A competitor closing? The schedule reacts to the number; you should be reacting to the cause.

Treating tools as the method. Scheduling software distributes and publishes; it does not decide. Restaurant-specific platforms will tie a schedule to POS sales and show labor as a percentage in real time, and demand-based schedulers will suggest coverage against projected sales — all useful. None of them will set your per-employee floor or tell you that Friday needs thirteen. You bring the arithmetic; the software handles logistics, swaps, and getting the published schedule onto everyone's phone. Confirm current pricing and features directly with any vendor before you commit — plans change constantly.

Related questions

What if my restaurant has no sales history yet?

Use projected covers instead of gross profit for the first eight to twelve weeks. Estimate 40–70% of seating capacity for lunch and 60–90% for dinner, staff to 8–12 covers per labor hour, and switch to the gross-profit divisor as soon as you have a trailing month of real data.

Does the divisor work for a counter-service concept?

Yes — the method is identical, but the floor is usually higher because counter service turns more covers per labor hour. Recompute your own floor from trailing gross profit divided by labor hours; do not import a full-service number into a fast-casual room.

How far ahead should I publish the schedule?

Ten to fourteen days is the practical standard, and some cities legally require advance notice with penalty pay for late changes. Publishing further out costs you accuracy on the averages; publishing closer in costs you your staff's goodwill and, in some jurisdictions, actual money.

Should managers count toward the headcount?

Count them if they work a station or a section, exclude them if they are purely supervisory — but always include their full cost in your labor percentage. Hiding a working chef outside the count is the most common way an understaffed schedule looks healthy on paper.

How do I handle a seasonal swing?

Compare against the same month in the prior year rather than last month, and adjust the day's gross-profit average up or down before dividing. Known busy stretches — holidays, local festivals, January resolution traffic at plant-based concepts — justify a 10–20% bump above the trailing average.

FAQ

What is the simplest starting rule if I have no data at all?

Roughly one front-of-house employee per 10–15 expected guests per hour, and one back-of-house body per 20–25 covers, plus a dedicated prep shift ahead of service. It is a placeholder, not a system — replace it with the gross-profit divisor the moment you have four weeks of real numbers.

How do I know how many customers to expect on a given shift?

Pull point-of-sale data for the same weekday over the trailing month, then adjust for weather, local events, and holidays. New restaurants without history should start from capacity-based estimates and correct weekly, since the first two months of a new concept rarely resemble the third.

Should weekdays really be staffed that differently from weekends?

Yes. It is common for a weekday to justify 30–50% fewer shifts than a weekend, particularly at lunch. A Tuesday lunch may need two or three total bodies where a Saturday dinner needs six to eight concurrent plus prep and gap coverage — the divisor produces that spread automatically.

What labor percentage should a vegan restaurant target?

Total labor including management typically belongs in the 28–33% band, a few points above the mainstream 25–30% guidance because of heavier scratch prep against a lower average check. Consistently above 35% signals overstaffing or under-pricing; well below 25% at a scratch kitchen usually signals service or prep quality slipping.

How often should I rewrite the schedule shape?

Review weekly against the prior week's actual sales and labor, making small corrections. Recompute the underlying weekday gross-profit averages monthly on a rolling three-to-six-month window, and rethink the whole shift shape quarterly as seasons and neighborhood traffic patterns move.

Why does the math sometimes produce a number that feels too high?

Almost always because employee-days are being read as concurrent bodies. Thirteen Friday shifts might be one prep cook, three at lunch, one through the gap, and eight across dinner — peak concurrency of eight or nine. If concurrency truly exceeds what the room can hold, your per-employee floor is set too low and needs raising.

Sources

• https://www.bls.gov/iag/tgs/iag722.htm — Bureau of Labor Statistics industry data on food services employment and wages.
• https://restaurant.org/ — National Restaurant Association operations and workforce management resources.
• https://pos.toasttab.com/blog — Toast POS blog covering restaurant labor cost and scheduling practices.
• https://www.dol.gov/agencies/whd/flsa — U.S. Department of Labor guidance on FLSA overtime and hours-worked rules.
• https://www.sba.gov/business-guide/manage-your-business/hire-manage-employees — Small Business Administration guidance on hiring and managing employees.
• https://hbr.org/ — Harvard Business Review research on scheduling practices and service-industry productivity.
• https://www.7shifts.com/blog — 7shifts restaurant scheduling and labor-management blog.
• https://www.sba.gov/business-guide/plan-your-business/calculate-your-startup-costs — SBA guidance on cost planning for new food-service businesses.

Related on PULSE

• How Many Employees Should I Schedule Each Shift at My Mediterranean Restaurant?
• How Many Employees Should I Schedule Each Shift at My Thai Restaurant?
• How Many Employees Should I Schedule Each Shift at My Indian Restaurant?
• How Many Employees Should I Schedule Each Shift at My Korean BBQ Restaurant?
• How Many Employees Should I Schedule Each Shift at My Hot Pot Restaurant?
• How Many Employees Should I Schedule Each Shift at My Seafood Restaurant?