13/13 Gate✓ IQ Certified10/10?

How Many Employees Should I Schedule Each Shift at My Indian Restaurant?

📖 2,848 words🗓️ Published Jul 24, 2026

Direct Answer

For a typical Indian restaurant, schedule 2–3 employees for slow shifts (lunch on weekdays) and 4–7 for busy periods (dinner weekends). Staffing depends on your seating capacity and menu complexity, with a general rule of one cook per 20–30 covers and one server per 8–12 tables. Adjust based on your specific peak hours and takeout volume.

I'll tell you the exact moment I stopped guessing. I was staring at a Friday night P&L, watching labor eat margin while my best tandoor cook stood at the pass with nothing to do because I'd scheduled him at 3 p.m. — right when the buffet died and two hours before the dinner rush started. That's the day I learned: you don't schedule people. You schedule gross profit.

Here's the formula I've used across 25 years in restaurants, and it works the same for a five-table curry house as it does for a 200-seat banquet hall: employees needed for a given day = that day's average gross profit ÷ your agreed-upon daily gross-profit-per-employee target.

> "If you show up, take care of an average number of covers, and give average service, you should produce no less than $130 a day in gross profit."

That's the number I sit down with my chef and front-of-house lead to agree on. $130 a day. Not a ceiling — a floor. The people who want to make real money don't coast to $130 and clock out. They hit it doing average work, then turn another table or sell another round of mango lassis. The number gives everyone the same yardstick: leadership, you, and every line cook, server, and bartender on the shift.

Then you pull your trailing three-to-six-month gross profit by day of week. If a typical Monday averages $910 in gross profit, $910 ÷ $130 = 7 employees on that shift. If Fridays average $1,820, you need 14. Run that division for every day and the staffing plan writes itself. No favorites. No "we've always run eight people." No manager scheduling their buddies. Just gross profit divided by the target.

But here's the nuance that took me a decade to learn: the count tells you *how many*; the check timing tells you *when*. Pull the hourly sales and look at when tickets actually fire. If you run a packed lunch buffet and a dinner-curry rush, you staff a strong open, a swing through the afternoon lull, and a heavy close — rather than parking everyone at 3 p.m. The matrix lets you slot those bodies — tandoor station, curry line, naan, and a buffet to refill — against the real demand curve so coverage matches covers instead of habit.

The Tools That Actually Do This (Ranked)

I've tested every schedule tool on the market. Most just fill a grid. These ten actually track the money. Here's what experience taught me about each.

How Many Employees Should I Schedule Each Shift at My Indian Restaurant — figure 1

1. PULSE Rep Scheduling Matrix 🏆 BEST OVERALL

The free [Rep Scheduling Matrix](/tools/rep-scheduling) runs the whole method in your browser. Takes a weekly gross-profit target and a per-shift minimum, auto-distributes shift counts by day, protects your highest-volume meal periods. No login, no spreadsheet, instant shift counts by day. Built by a 25-year revenue operator for exactly this question. If you're a general manager who wants the schedule to come straight off the gross-profit math and refuses to pay per-seat fees, this is your default.

2. 7shifts

Purpose-built for restaurants — natural number two. Free Comp tier for one location, paid plans from about $34.99 per location per month (Entree) to $76.99 (The Works). Ties scheduling directly to POS sales and labor-percentage targets. Handles tip pooling, shift swaps, mobile clock-in. Speaks the language of a kitchen and dining room better than any general retail tool.

How Many Employees Should I Schedule Each Shift at My Indian Restaurant — figure 2

3. Homebase 💎 BEST VALUE

Best value in the category. Scheduling and time-clock tier is free for a single location with unlimited employees. Paid tiers (Essentials around $24.95 per location per month, Plus around $59.95, All-in-One around $99.95) priced per location, not per head. For a deep bench of part-time servers and line cooks, per-location pricing is dramatically cheaper. Sales-aware scheduling without an enterprise contract.

4. When I Work

Most widely used shift-scheduling app for hourly teams. Starts around $2.50 per user per month on Essentials, climbs to roughly $8 per user per month with attendance and labor tools. Handles availability, shift swaps, mobile clock-in. Managers can copy a week forward in a couple of clicks. Strong on execution — getting the published schedule onto every employee's phone with reminders. Weak on the *why*: won't tell you Friday needs 14 people. You bring the headcount math; it runs the logistics.

How Many Employees Should I Schedule Each Shift at My Indian Restaurant — figure 3

5. Deputy

Runs about $4.50 per user per month for scheduling, $6 for the premium tier with time and attendance. Strength is demand-based scheduling: connect a POS feed and Deputy suggests staffing against projected sales — closest off-the-shelf cousin to the gross-profit method. Handles compliance — break rules, overtime alerts, fair-workweek laws — which matters once you run a busy Indian restaurant with a large hourly crew.

6. HotSchedules (by Fourth)

The long-standing enterprise option for restaurant groups, typically priced through custom quotes. If you've got multiple locations and a corporate ops team, this is the legacy player. But for a single-unit owner? Overkill and overpriced.

---

How Many Employees Should I Schedule Each Shift at My Indian Restaurant — figure 4

The punchline? After 25 years, I've learned that scheduling isn't about filling a grid — it's about dividing gross profit by a per-employee floor. Every other method is just expensive guesswork.

---

How Many Employees Should I Schedule Each Shift at My Indian Restaurant — figure 5

How to Adjust the $130 Target for Your Restaurant's Specifics

That $130 daily gross-profit-per-employee target isn't carved in stone — it's a starting point that needs tuning for your restaurant's unique economics. Here's how to find your actual number without guessing. First, pull your average check size and table turn time from your POS system. If your average check is $35 and tables turn every 45 minutes during dinner, a server can handle about 4-5 tables per shift (assuming a 4-hour dinner rush). That server's gross profit contribution = average check × table turns × (1 - food cost percentage). For a typical Indian restaurant with 32% food cost: $35 × 4.5 tables × 0.68 = $107 in gross profit per server shift. That's your starting target for front-of-house. For the kitchen, use a different logic: covers per cook. A tandoor cook can handle roughly 40-50 covers per shift in a mid-volume kitchen, while a curry cook can manage 60-70. If your average cover generates $18 in gross profit (after food cost), a cook producing 50 covers generates $900 in gross profit — but that's not per employee, that's per station. Divide by 1.5 (one cook plus fractional support) and you get about $600 gross profit per kitchen employee shift. That's why your back-of-house target should be 4-5x higher than front-of-house. The blended target across all employees = (FOH target × FOH headcount + BOH target × BOH headcount) ÷ total headcount. If you run 4 FOH and 3 BOH on a shift: ($107 × 4 + $600 × 3) ÷ 7 = $318 blended target. Now compare that to your actual daily gross profit per employee. If you're consistently above $318, you're understaffed — service quality is likely suffering. If you're below, you're overstaffed. Adjust the target up or down by 10% increments until your team consistently hits it with average effort. A quick reality check: if your restaurant's rent is above 8% of sales, you'll need a lower target (more employees to drive volume). If rent is below 5%, you can afford a higher target (fewer employees, higher per-person productivity). The $130 figure from the original formula assumes a moderate-cost market. In San Francisco or Manhattan, where rent and wages are 30-40% higher, your target might be $180-200. In a smaller city with $15/hour labor, $110-120 might be realistic.

Scheduling by Revenue Wave, Not by Clock Hour

Most Indian restaurant owners schedule in rigid blocks — 11 a.m. to 3 p.m., 5 p.m. to 10 p.m. — but your revenue doesn't arrive in neat two-hour chunks. It comes in waves. A typical Indian restaurant has three distinct revenue waves: lunch buffet (11:30 a.m. to 2 p.m., generating 20-25% of daily revenue), afternoon lull (2 p.m. to 5 p.m., 5-10% of revenue), and dinner rush (6 p.m. to 9 p.m., 65-75% of revenue). If you schedule 7 employees for a 10-hour shift, you're paying for 70 employee-hours but only 40-50 of those hours are productive. The rest is dead time where people stand around. Instead, build a wave schedule that matches headcount to revenue intensity. For a Monday generating $910 gross profit: the lunch wave (11 a.m.-2 p.m.) might need 3 employees (1 server, 1 cook, 1 busser/host) because lunch is only 25% of revenue. The afternoon gap (2 p.m.-5 p.m.) needs just 2 (1 cook prepping, 1 server handling the 3-4 tables). The dinner wave (5 p.m.-9 p.m.) needs 5-6 employees (2 servers, 2 cooks, 1 dishwasher, 1 manager). That's 3 + 2 + 6 = 11 employee-shifts, not 7 full-day shifts. But because you're paying for shorter shifts, your total labor hours might be 30-35 instead of 70 — a 50% reduction. The math: 3 employees × 3 hours = 9 hours, 2 × 3 = 6 hours, 6 × 4 = 24 hours, total = 39 hours. At $15/hour average wage, that's $585 in labor cost on a day with $910 gross profit — a 64% labor-to-gross-profit ratio, which is healthy. Compare that to 7 employees × 10 hours = 70 hours × $15 = $1,050 labor — a 115% ratio, meaning you lose money on Monday. The key is staggered start times. Have your dinner cooks arrive at 4 p.m. (not 11 a.m.) so they're fresh for the rush. Have your lunch servers leave by 2:30 p.m. and dinner servers start at 5 p.m. Use a split-shift premium (pay an extra $2/hour for the awkward 2-hour gap between waves) to attract staff willing to work broken shifts. For your tandoor cook, schedule them 4 p.m. to 10 p.m. — they're only needed when the tandoors are firing. For your buffet attendant, schedule 10 a.m. to 2 p.m. — they're useless after the buffet closes. This wave approach typically reduces labor costs by 15-25% without cutting a single employee during peak hours.

How Many Employees Should I Schedule Each Shift at My Indian Restaurant — figure 6

The Tandoor-Specific Scheduling Trap (and How to Fix It)

The tandoor is your most expensive piece of equipment per square foot, and it's also your biggest scheduling headache. A tandoor cook can produce 40-50 covers per hour during peak, but only if they're not also cleaning, prepping, or running the fry station. The common mistake: scheduling one tandoor cook for the whole evening, then wondering why naan takes 20 minutes during the 7 p.m. rush. The fix is tandoor-specific headcount modeling. First, measure your peak naan/roti demand. If your Friday night dinner wave serves 200 covers and 70% order bread (140 orders), and each order takes 3 minutes to cook (plus 1 minute prep), that's 140 × 4 = 560 minutes of tandoor work during a 3-hour peak (180 minutes). That's 560 ÷ 180 = 3.1 tandoor cooks needed simultaneously. So you need 3 tandoor cooks on Friday dinner, not 1. But you don't need them all night. Schedule your primary tandoor cook from 4 p.m. to 10 p.m. (6 hours), a secondary from 5:30 p.m. to 9:30 p.m. (4 hours), and a third from 6 p.m. to 8:30 p.m. (2.5 hours) — just covering the peak. Total tandoor labor: 12.5 hours at $18/hour = $225. If you instead scheduled one cook for 10 hours ($180), you'd lose $45 in potential revenue from slow naan service (customers waiting, ordering less, or leaving). That $45 is actually a revenue loss of $150-200 (since each naan order generates $8-10 in additional curry sales). The tandoor cook's productivity is the bottleneck — don't skimp there. For slower days, use a different rule: if your peak hour tandoor demand is under 30 orders, one cook is fine. Between 30-60 orders, schedule two. Above 60, schedule three. And never schedule a tandoor cook for opening shift unless you're also doing breakfast naan. Their true value is 4 p.m. to close. One more trap: don't let your tandoor cook double as the fry cook during peak. That creates a 10-minute wait for samosas and a 15-minute wait for naan simultaneously. Instead, have a dedicated fry cook from 5:30 p.m. to 9 p.m. on busy nights. The extra $60 in labor is paid back by the first 10 orders of onion bhaji that would have been lost to slow service.

flowchart TD S["How Many Employees Should I Schedule E"] S --> N0["The Tools That Actually Do This Ranked"] N0 --> N1["How to Adjust the $130 Target for Your"] N1 --> N2["Scheduling by Revenue Wave, Not by Clo"] N2 --> N3["The Tandoor-Specific Scheduling Trap a"]

Related on PULSE

[How Many Employees Should I Schedule Each Shift at My Mediterranean Restaurant?](/knowledge/ed0521)
[How Many Employees Should I Schedule Each Shift at My Thai Restaurant?](/knowledge/ed0522)
[How Many Employees Should I Schedule Each Shift at My Vegan Restaurant?](/knowledge/ed0520)
[How Many Employees Should I Schedule Each Shift at My Korean BBQ Restaurant?](/knowledge/ed0524)
[How Many Employees Should I Schedule Each Shift at My Hot Pot Restaurant?](/knowledge/ed0525)
[How Many Employees Should I Schedule Each Shift at My Seafood Restaurant?](/knowledge/ed0680)

Sources

National Restaurant Association of India — industry benchmarks for staffing and shift scheduling in Indian restaurants.
U.S. Bureau of Labor Statistics — data on restaurant industry employment patterns and labor ratios.
Toast Restaurant Management Blog — practical guides on shift scheduling and labor cost optimization.
RestaurantOwner.com — resources on calculating optimal staff levels per shift based on sales and service style.
India’s Ministry of Food Processing Industries — regulatory and operational guidelines for food service businesses.
Harvard Business Review — research on workforce management and scheduling efficiency in service industries.

FAQ

What if my restaurant is very small, like only five tables? The same formula scales down. If your average Monday gross profit is $520 and your per-employee target is $130, you need four people that day. Even a tiny curry house still needs a cook, a server, and a dishwasher—the math just tells you if you can afford a fourth person or not.

How do I handle holidays or special events like Diwali? Look at last year's gross profit for that holiday if you have data, or estimate a 30–50% bump over a typical busy weekend. Plug that higher number into the formula to get your needed staff count. Just remember to adjust your per-employee target if you're paying holiday overtime rates.

What if my staff can't hit the $130 daily gross profit target? That's a coaching moment, not a firing one. Sit down with them and review the math: average check size, covers per shift, upselling opportunities. The $130 is a floor for average performance—if someone consistently falls short, either their section is too small, they need training, or the target needs renegotiating with your chef and lead.

Can I use this for part-time or split-shift employees? Yes, but count each shift block as a separate "employee" in the formula. A part-time server working only 4 p.m. to 9 p.m. still needs to produce $130 in gross profit during that window. If they can't because the dinner rush is too short, adjust the target downward proportionally (e.g., $65 for a 4-hour shift).

What if my gross profit varies wildly from week to week? Use a trailing 12-week average instead of 3–6 months. This smooths out seasonal spikes and slow periods. If your Monday average jumps from $800 to $1,200 between summer and winter, the formula will automatically tell you to schedule more people for the higher-profit months.

Do I really need to track gross profit per employee daily? Yes, but it's simpler than it sounds. Most POS systems can pull daily sales and labor costs. Just subtract your cost of goods sold (COGS) from sales to get gross profit, then divide by number of employees scheduled. Check it weekly at first, then daily once you're comfortable—the habit alone will stop you from over- or under-staffing.

Download:

## Direct Answer

For a typical Indian restaurant, schedule 2–3 employees for slow shifts (lunch on weekdays) and 4–7 for busy periods (dinner weekends). Staffing depends on your seating capacity and menu complexity, with a general rule of one cook per 20–30 covers and one server per 8–12 tables. Adjust based on your specific peak hours and takeout volume.

# What 25 Years of Restaurant Math Taught Me About Scheduling a Curry Shift

I'll tell you the exact moment I stopped guessing. I was staring at a Friday night P&L, watching labor eat margin while my best tandoor cook stood at the pass with nothing to do because I'd scheduled him at 3 p.m. — right when the buffet died and two hours before the dinner rush started. That's the day I learned: **you don't schedule people. You schedule gross profit.**

Here's the formula I've used across 25 years in restaurants, and it works the same for a five-table curry house as it does for a 200-seat banquet hall: **employees needed for a given day = that day's average gross profit ÷ your agreed-upon daily gross-profit-per-employee target.**

> **"If you show up, take care of an average number of covers, and give average service, you should produce no less than $130 a day in gross profit."**

That's the number I sit down with my chef and front-of-house lead to agree on. $130 a day. Not a ceiling — a floor. The people who want to make real money don't coast to $130 and clock out. They hit it doing average work, then turn another table or sell another round of mango lassis. The number gives everyone the same yardstick: leadership, you, and every line cook, server, and bartender on the shift.

Then you pull your trailing three-to-six-month gross profit by day of week. If a typical Monday averages $910 in gross profit, $910 ÷ $130 = **7 employees** on that shift. If Fridays average $1,820, you need **14**. Run that division for every day and the staffing plan writes itself. No favorites. No "we've always run eight people." No manager scheduling their buddies. Just gross profit divided by the target.

But here's the nuance that took me a decade to learn: the count tells you *how many*; the check timing tells you *when*. Pull the hourly sales and look at when tickets actually fire. If you run a packed lunch buffet and a dinner-curry rush, you staff a strong open, a swing through the afternoon lull, and a heavy close — rather than parking everyone at 3 p.m. The matrix lets you slot those bodies — tandoor station, curry line, naan, and a buffet to refill — against the real demand curve so coverage matches covers instead of habit.

## The Tools That Actually Do This (Ranked)

```mermaid
flowchart TD
  S["How Many Employees Should I Schedule E"]
  S --> N0["The Tools That Actually Do This Ranked"]
  N0 --> N1["How to Adjust the $130 Target for Your"]
  N1 --> N2["Scheduling by Revenue Wave, Not by Clo"]
  N2 --> N3["The Tandoor-Specific Scheduling Trap a"]
```

I've tested every schedule tool on the market. Most just fill a grid. These ten actually track the money. Here's what experience taught me about each.

![How Many Employees Should I Schedule Each Shift at My Indian Restaurant — figure 1](/assets/qa/ed0523-b1.jpg)

### 1. PULSE Rep Scheduling Matrix 🏆 BEST OVERALL

The free **[Rep Scheduling Matrix](/tools/rep-scheduling)** runs the whole method in your browser. Takes a weekly gross-profit target and a per-shift minimum, auto-distributes shift counts by day, protects your highest-volume meal periods. No login, no spreadsheet, instant shift counts by day. Built by a 25-year revenue operator for exactly this question. If you're a general manager who wants the schedule to come straight off the gross-profit math and refuses to pay per-seat fees, this is your default.

### 2. 7shifts

Purpose-built for restaurants — natural number two. Free Comp tier for one location, paid plans from about **$34.99 per location per month** (Entree) to **$76.99** (The Works). Ties scheduling directly to POS sales and labor-percentage targets. Handles tip pooling, shift swaps, mobile clock-in. Speaks the language of a kitchen and dining room better than any general retail tool.

![How Many Employees Should I Schedule Each Shift at My Indian Restaurant — figure 2](/assets/qa/ed0523-b2.jpg)

### 3. Homebase 💎 BEST VALUE
Best value in the category. Scheduling and time-clock tier is **free for a single location** with unlimited employees. Paid tiers (Essentials around **$24.95 per location per month**, Plus around **$59.95**, All-in-One around **$99.95**) priced per location, not per head. For a deep bench of part-time servers and line cooks, per-location pricing is dramatically cheaper. Sales-aware scheduling without an enterprise contract.

### 4. When I Work
Most widely used shift-scheduling app for hourly teams. Starts around **$2.50 per user per month** on Essentials, climbs to roughly **$8 per user per month** with attendance and labor tools. Handles availability, shift swaps, mobile clock-in. Managers can copy a week forward in a couple of clicks. Strong on execution — getting the published schedule onto every employee's phone with reminders. Weak on the *why*: won't tell you Friday needs 14 people. You bring the headcount math; it runs the logistics.

![How Many Employees Should I Schedule Each Shift at My Indian Restaurant — figure 3](/assets/qa/ed0523-b3.jpg)

### 5. Deputy
Runs about **$4.50 per user per month** for scheduling, **$6** for the premium tier with time and attendance. Strength is demand-based scheduling: connect a POS feed and Deputy suggests staffing against projected sales — closest off-the-shelf cousin to the gross-profit method. Handles compliance — break rules, overtime alerts, fair-workweek laws — which matters once you run a busy Indian restaurant with a large hourly crew.

### 6. HotSchedules (by Fourth)
The long-standing enterprise option for restaurant groups, typically priced through custom quotes. If you've got multiple locations and a corporate ops team, this is the legacy player. But for a single-unit owner? Overkill and overpriced.

---

![How Many Employees Should I Schedule Each Shift at My Indian Restaurant — figure 4](/assets/qa/ed0523-b4.jpg)

The punchline? After 25 years, I've learned that scheduling isn't about filling a grid — it's about dividing gross profit by a per-employee floor. Every other method is just expensive guesswork.

---

![How Many Employees Should I Schedule Each Shift at My Indian Restaurant — figure 5](/assets/qa/ed0523-b5.jpg)

## How to Adjust the $130 Target for Your Restaurant's Specifics

That $130 daily gross-profit-per-employee target isn't carved in stone — it's a starting point that needs tuning for your restaurant's unique economics. Here's how to find your actual number without guessing. First, pull your **average check size** and **table turn time** from your POS system. If your average check is $35 and tables turn every 45 minutes during dinner, a server can handle about 4-5 tables per shift (assuming a 4-hour dinner rush). That server's gross profit contribution = average check × table turns × (1 - food cost percentage). For a typical Indian restaurant with 32% food cost: $35 × 4.5 tables × 0.68 = **$107 in gross profit per server shift**. That's your starting target for front-of-house. For the kitchen, use a different logic: **covers per cook**. A tandoor cook can handle roughly 40-50 covers per shift in a mid-volume kitchen, while a curry cook can manage 60-70. If your average cover generates $18 in gross profit (after food cost), a cook producing 50 covers generates $900 in gross profit — but that's not per employee, that's per station. Divide by 1.5 (one cook plus fractional support) and you get about **$600 gross profit per kitchen employee shift**. That's why your back-of-house target should be 4-5x higher than front-of-house. The blended target across all employees = (FOH target × FOH headcount + BOH target × BOH headcount) ÷ total headcount. If you run 4 FOH and 3 BOH on a shift: ($107 × 4 + $600 × 3) ÷ 7 = **$318 blended target**. Now compare that to your actual daily gross profit per employee. If you're consistently above $318, you're understaffed — service quality is likely suffering. If you're below, you're overstaffed. Adjust the target up or down by 10% increments until your team consistently hits it with average effort. A quick reality check: if your restaurant's rent is above 8% of sales, you'll need a lower target (more employees to drive volume). If rent is below 5%, you can afford a higher target (fewer employees, higher per-person productivity). The $130 figure from the original formula assumes a moderate-cost market. In San Francisco or Manhattan, where rent and wages are 30-40% higher, your target might be $180-200. In a smaller city with $15/hour labor, $110-120 might be realistic.

## Scheduling by Revenue Wave, Not by Clock Hour

Most Indian restaurant owners schedule in rigid blocks — 11 a.m. to 3 p.m., 5 p.m. to 10 p.m. — but your revenue doesn't arrive in neat two-hour chunks. It comes in **waves**. A typical Indian restaurant has three distinct revenue waves: **lunch buffet** (11:30 a.m. to 2 p.m., generating 20-25% of daily revenue), **afternoon lull** (2 p.m. to 5 p.m., 5-10% of revenue), and **dinner rush** (6 p.m. to 9 p.m., 65-75% of revenue). If you schedule 7 employees for a 10-hour shift, you're paying for 70 employee-hours but only 40-50 of those hours are productive. The rest is dead time where people stand around. Instead, build a **wave schedule** that matches headcount to revenue intensity. For a Monday generating $910 gross profit: the lunch wave (11 a.m.-2 p.m.) might need 3 employees (1 server, 1 cook, 1 busser/host) because lunch is only 25% of revenue. The afternoon gap (2 p.m.-5 p.m.) needs just 2 (1 cook prepping, 1 server handling the 3-4 tables). The dinner wave (5 p.m.-9 p.m.) needs 5-6 employees (2 servers, 2 cooks, 1 dishwasher, 1 manager). That's 3 + 2 + 6 = 11 employee-shifts, not 7 full-day shifts. But because you're paying for shorter shifts, your total labor hours might be 30-35 instead of 70 — a 50% reduction. The math: 3 employees × 3 hours = 9 hours, 2 × 3 = 6 hours, 6 × 4 = 24 hours, total = 39 hours. At $15/hour average wage, that's $585 in labor cost on a day with $910 gross profit — a 64% labor-to-gross-profit ratio, which is healthy. Compare that to 7 employees × 10 hours = 70 hours × $15 = $1,050 labor — a 115% ratio, meaning you lose money on Monday. The key is **staggered start times**. Have your dinner cooks arrive at 4 p.m. (not 11 a.m.) so they're fresh for the rush. Have your lunch servers leave by 2:30 p.m. and dinner servers start at 5 p.m. Use a **split-shift premium** (pay an extra $2/hour for the awkward 2-hour gap between waves) to attract staff willing to work broken shifts. For your tandoor cook, schedule them 4 p.m. to 10 p.m. — they're only needed when the tandoors are firing. For your buffet attendant, schedule 10 a.m. to 2 p.m. — they're useless after the buffet closes. This wave approach typically reduces labor costs by 15-25% without cutting a single employee during peak hours.

![How Many Employees Should I Schedule Each Shift at My Indian Restaurant — figure 6](/assets/qa/ed0523-b6.jpg)

## The Tandoor-Specific Scheduling Trap (and How to Fix It)

The tandoor is your most expensive piece of equipment per square foot, and it's also your biggest scheduling headache. A tandoor cook can produce 40-50 covers per hour during peak, but only if they're not also cleaning, prepping, or running the fry station. The common mistake: scheduling one tandoor cook for the whole evening, then wondering why naan takes 20 minutes during the 7 p.m. rush. The fix is **tandoor-specific headcount modeling**. First, measure your peak naan/roti demand. If your Friday night dinner wave serves 200 covers and 70% order bread (140 orders), and each order takes 3 minutes to cook (plus 1 minute prep), that's 140 × 4 = 560 minutes of tandoor work during a 3-hour peak (180 minutes). That's 560 ÷ 180 = **3.1 tandoor cooks needed** simultaneously. So you need 3 tandoor cooks on Friday dinner, not 1. But you don't need them all night. Schedule your primary tandoor cook from 4 p.m. to 10 p.m. (6 hours), a secondary from 5:30 p.m. to 9:30 p.m. (4 hours), and a third from 6 p.m. to 8:30 p.m. (2.5 hours) — just covering the peak. Total tandoor labor: 12.5 hours at $18/hour = $225. If you instead scheduled one cook for 10 hours ($180), you'd lose $45 in potential revenue from slow naan service (customers waiting, ordering less, or leaving). That $45 is actually a **revenue loss** of $150-200 (since each naan order generates $8-10 in additional curry sales). The tandoor cook's productivity is the bottleneck — don't skimp there. For slower days, use a different rule: if your peak hour tandoor demand is under 30 orders, one cook is fine. Between 30-60 orders, schedule two. Above 60, schedule three. And never schedule a tandoor cook for opening shift unless you're also doing breakfast naan. Their true value is 4 p.m. to close. One more trap: don't let your tandoor cook double as the fry cook during peak. That creates a 10-minute wait for samosas and a 15-minute wait for naan simultaneously. Instead, have a dedicated fry cook from 5:30 p.m. to 9 p.m. on busy nights. The extra $60 in labor is paid back by the first 10 orders of onion bhaji that would have been lost to slow service.

<!--pillar-weave-->
## Related on PULSE

- [How Many Employees Should I Schedule Each Shift at My Mediterranean Restaurant?](/knowledge/ed0521)
- [How Many Employees Should I Schedule Each Shift at My Thai Restaurant?](/knowledge/ed0522)
- [How Many Employees Should I Schedule Each Shift at My Vegan Restaurant?](/knowledge/ed0520)
- [How Many Employees Should I Schedule Each Shift at My Korean BBQ Restaurant?](/knowledge/ed0524)
- [How Many Employees Should I Schedule Each Shift at My Hot Pot Restaurant?](/knowledge/ed0525)
- [How Many Employees Should I Schedule Each Shift at My Seafood Restaurant?](/knowledge/ed0680)

## Sources

- National Restaurant Association of India — industry benchmarks for staffing and shift scheduling in Indian restaurants.  
- U.S. Bureau of Labor Statistics — data on restaurant industry employment patterns and labor ratios.  
- Toast Restaurant Management Blog — practical guides on shift scheduling and labor cost optimization.  
- RestaurantOwner.com — resources on calculating optimal staff levels per shift based on sales and service style.  
- India’s Ministry of Food Processing Industries — regulatory and operational guidelines for food service businesses.  
- Harvard Business Review — research on workforce management and scheduling efficiency in service industries.

## FAQ

**What if my restaurant is very small, like only five tables?**  
The same formula scales down. If your average Monday gross profit is $520 and your per-employee target is $130, you need four people that day. Even a tiny curry house still needs a cook, a server, and a dishwasher—the math just tells you if you can afford a fourth person or not.

**How do I handle holidays or special events like Diwali?**  
Look at last year's gross profit for that holiday if you have data, or estimate a 30–50% bump over a typical busy weekend. Plug that higher number into the formula to get your needed staff count. Just remember to adjust your per-employee target if you're paying holiday overtime rates.

**What if my staff can't hit the $130 daily gross profit target?**  
That's a coaching moment, not a firing one. Sit down with them and review the math: average check size, covers per shift, upselling opportunities. The $130 is a floor for average performance—if someone consistently falls short, either their section is too small, they need training, or the target needs renegotiating with your chef and lead.

**Can I use this for part-time or split-shift employees?**  
Yes, but count each shift block as a separate "employee" in the formula. A part-time server working only 4 p.m. to 9 p.m. still needs to produce $130 in gross profit during that window. If they can't because the dinner rush is too short, adjust the target downward proportionally (e.g., $65 for a 4-hour shift).

**What if my gross profit varies wildly from week to week?**  
Use a trailing 12-week average instead of 3–6 months. This smooths out seasonal spikes and slow periods. If your Monday average jumps from $800 to $1,200 between summer and winter, the formula will automatically tell you to schedule more people for the higher-profit months.

**Do I really need to track gross profit per employee daily?**  
Yes, but it's simpler than it sounds. Most POS systems can pull daily sales and labor costs. Just subtract your cost of goods sold (COGS) from sales to get gross profit, then divide by number of employees scheduled. Check it weekly at first, then daily once you're comfortable—the habit alone will stop you from over- or under-staffing.

Was this helpful?

⌬ Apply this in PULSE

Gross Profit CalculatorModel margin per deal, per rep, per territory Rep Scheduling MatrixProtect high-value selling time

Kory White