OPERATOR PLAYBOOK · 2026 14 min read Updated August 2026

Restaurant Weekly Staffing India 2026 — The Labour Model That Keeps You at 22-25%

Labour is the second-largest controllable cost in an Indian restaurant after food. Get it right and you sit at 22-25% of revenue — healthy, sustainable, room to reinvest. Get it wrong and you drift to 30-35% within two quarters, usually because the roster is over-staffed Monday to Wednesday and under-staffed Friday to Sunday. This is the Sunday-morning ritual, the staffing formula, the shift patterns, the PF and ESI math, and the weekly roster template every operator should run — every single week, without exception.

In this playbook

  1. Why the weekly roster is your #2 profit lever
  2. Step 1 — Forecast next week's revenue by daypart
  3. Step 2 — The staffing formula (labour hours from revenue)
  4. Step 3 — The 5 shift patterns that work in India
  5. The 30-minute Sunday ritual
  6. The PF, ESI and statutory reality
  7. Full-time vs part-time vs gig — the real ₹/hour
  8. The 3 metrics to review every Monday
  9. Warning signs your model is broken
  10. The weekly roster template
  11. FAQ

Why the weekly roster is your #2 profit lever

Food cost you audit invoice-by-invoice. Rent is a fixed number you cannot move. Aggregator commission is what it is. That leaves labour — the largest cost you actually control week-to-week. A well-run restaurant staffing model india keeps labour at 22-25% of revenue. A poorly-run one drifts to 30-35% and quietly eats your entire operating margin.

The 8-point difference between 22% and 30% on a ₹18 lakh monthly revenue outlet is ₹1.44 lakh — every month. That is the head chef's salary. That is your marketing budget. That is your next outlet's deposit. It hides in plain sight because nobody looks at labour weekly. They look monthly, by which time the pattern is baked in.

The pattern that repeats in most Indian restaurants: the owner hires slightly more than needed "just to be safe" during opening months. Nobody trims the roster once the outlet stabilises. Six months later, Monday lunch has 8 people serving 22 covers and Saturday dinner has the same 8 people serving 90 covers — same labour bill, wildly different revenue per hour, and the whole operation feels either sleepy or on fire depending on the day.

What the weekly discipline gets you

Step 1 — Forecast next week's revenue by daypart

You cannot staff without a demand signal. The demand signal is a simple 7-day × 2-or-3 daypart matrix — lunch, dinner, and late-night if you run one.

The trailing 4-week baseline

Pull last 4 weeks of daypart revenue from your POS. Take the average per cell. That is your starting point. Never staff on one week's data alone — a rainy Wednesday or a cricket final Saturday will distort the number.

DayLunch (12-4 PM)Dinner (7-11 PM)Total
Monday₹12,000₹22,000₹34,000
Tuesday₹11,500₹24,000₹35,500
Wednesday₹13,000₹27,000₹40,000
Thursday₹14,000₹32,000₹46,000
Friday₹18,000₹48,000₹66,000
Saturday₹22,000₹58,000₹80,000
Sunday₹28,000₹42,000₹70,000

The 4 adjustments that matter

Write the adjusted forecast in the same matrix. This is your weekly staffing restaurant demand signal.

Step 2 — The staffing formula (labour hours from revenue)

The formula is simple. Everyone forgets it because it feels too simple to be right.

Labour hours needed per daypart = forecast daypart revenue ÷ revenue-per-labour-hour benchmark.

The revenue-per-labour-hour benchmark for Indian casual dining is ₹800-1,000. So if Friday dinner is forecast at ₹48,000, you need 48-60 labour hours across the 4-hour dinner service — meaning 12-15 people on the floor and in the kitchen combined during peak.

Adjusting the benchmark to your outlet

FormatTicket sizeRev/labour hour
QSR / cloud kitchen₹150-300₹600-800
Casual dining₹400-800₹800-1,000
Premium casual₹800-1,500₹1,000-1,300
Fine dining₹1,500+₹1,200-1,500

QSRs run lower because throughput compensates — cheaper covers, more of them, fewer touchpoints per order. Fine dining runs higher because the ticket carries the labour. If your outlet consistently underperforms these benchmarks, your restaurant labour cost india is going to sit above 28% no matter what shift patterns you use.

Splitting labour hours between kitchen and floor

The rule of thumb is 55-60% kitchen, 40-45% floor for Indian casual dining. Higher kitchen weight for menus with a lot of tandoor/chinese/dessert stations. Higher floor weight for restaurants with heavy service ritual or bar service.

Step 3 — The 5 shift patterns that work in India

Ninety-five percent of Indian restaurant scheduling is one of five patterns. Pick the mix that fits your format, don't invent new ones.

PatternHoursBest for
Split shift11 AM-3 PM, 7-11 PM (8 paid, 4 break)Full-time floor staff who work both lunch and dinner
Full shift11 AM-11 PM (9 paid, 3 break)Kitchen staff needing continuous presence and prep time
Evening-only5-11 PM (6 hours)Part-timers, college students, weekend supplementary floor
Weekend-onlyFri-Sun peak daypartsSupplemental floor and dishwash during predictable peaks
Utility floaterVariable 4-8 hour on-demandAll-rounder filling absences and unexpected peaks

The split shift is the workhorse of Indian casual dining because our meal periods are so cleanly separated by the 3-6 PM lull. Kitchens don't take it because prep continues through the lull — that's why kitchen defaults to the full shift with a proper break room.

What breaks: forcing floor staff onto the kitchen's full shift or kitchen staff onto the floor's split. You will get attrition inside 90 days. Match the pattern to the role, not to owner convenience.

The 30-minute Sunday ritual

This is the whole discipline in one paragraph. Every Sunday morning, before the outlet opens, you run these five steps. Non-negotiable, no exceptions, even when you're on holiday — you delegate it, you don't skip it. This is the how to schedule restaurant staff answer that everyone else avoids.

  1. Pull last week's daypart revenue from the POS (5 minutes). Save the matrix. You are looking at what actually happened, not what you hoped.
  2. Forecast next week with the 4 adjustments (10 minutes). Trailing 4-week average per cell, then plus/minus for festival, weather, event, aggregator promo. Write the adjusted matrix.
  3. Calculate labour hours per daypart (5 minutes). Forecast revenue ÷ benchmark = labour hours. Split 55/45 kitchen/floor.
  4. Assign specific people to specific shifts (10 minutes). Use the template in Section 10. Rotate the weekend load fairly. Note holidays, half-days, planned leave.
  5. Publish the roster to the WhatsApp group by 6 PM Sunday (5 minutes). PDF or image, pinned message. This is the contract for the week.

The reason 6 PM Sunday matters: your staff have a life. They plan Monday around Sunday evening. A roster published Tuesday morning tells them you don't respect their time — and they'll show you the same by calling in sick.

The PF, ESI and statutory reality

Your headline salary is not your true labour cost. Every Indian operator learns this the hard way when the accountant sends the first quarterly reconciliation.

The layers on top of gross pay

The real cost of an ₹18,000 captain

ComponentAmount
Gross salary₹18,000
PF (12% on basic ₹9,000)₹1,080
ESI (3.25% on gross)₹585
Gratuity accrual (4.81% on basic)₹433
Staff meals (₹50 × 26 days)₹1,300
Bonus accrual (8.33% on basic)₹750
True monthly cost to restaurant₹22,148

Add 12-15% to every headline salary when you're modelling labour cost percentage restaurant india. If you're budgeting on gross alone, your actual labour cost is going to land 2-3 percentage points higher than your model says. That is the difference between hitting 25% and hitting 28%.

Full-time vs part-time vs gig — the real ₹/hour

Not every role should be full-time. The best restaurant staff scheduling india uses a deliberate mix — full-time for the core, part-time for predictable peaks, gig for surge.

Role classEmploymentAll-in ₹/hour
Head chef, sous chefFull-time salaried₹250-450
Chef de partie, captainFull-time salaried₹120-180
Commis, floor serverFull-time or part-time₹80-120
Weekend floor top-upPart-time hourly₹100-140
Dishwash, utilityFull-time or part-time₹60-90
Chef Kart / gig chefGig platform₹200-350
Event staffing agencyAgency contract₹150-250

Gig is more expensive per hour but saves you PF, ESI, gratuity, staff meals and — critically — the cost of paying a full-time salary during weeks you don't need the person. For a 45-cover casual dining outlet, a 60-25-15 split (full-time-part-time-gig) is typical. Weekend-heavy formats push part-time to 30-35%.

The trap: operators either go 100% full-time (safe, but 30%+ labour cost) or 100% gig (cheap on paper, but zero continuity, unrecognisable service quality, and gig platforms hit surge pricing on the exact nights you need them). The mix is the answer.

The 3 metrics to review every Monday

Sunday you plan. Monday you review. Same 3 numbers, every week, no exceptions.

1. Labour cost percentage — target 22-25%

Total all-in labour cost (gross + PF + ESI + gratuity + staff meals) divided by total revenue. If you're at 27-28% for two weeks running, your roster has drift — usually mid-week over-staffing. If you're above 30%, restructure the roster before doing anything else.

2. Revenue per labour hour — target ₹800-1,000

Total revenue divided by total paid labour hours (including breaks that were paid). Below ₹600 means either you're over-staffed or your menu isn't priced right for the labour it requires. Above ₹1,200 for a casual dining outlet usually means you're under-staffed — service quality is quietly slipping.

3. Overtime hours — target zero for salaried, under 10% for hourly

Salaried overtime is a red flag not a saving — you're paying nothing extra for the hour but you're burning the person out. Their exit costs you ₹15,000-30,000 in replacement and training. Hourly overtime above 10% is chronic understaffing dressed up as flexibility.

Warning signs your model is broken

Three patterns you cannot afford to ignore. Each one on its own is a "fix within 2 weeks" issue.

Same person doing 4 consecutive 12-hour shifts

Burnout risk is real and measurable. In our sample of Indian casual dining outlets, staff on 4+ consecutive 12-hour shifts have a 3x higher exit probability within 6 weeks. Rotate hard days. Use the utility floater to break the pattern.

Wednesday overstaffed while Saturday dinner is short

Classic broken forecast. Someone built the roster from headcount, not from demand. Redo it with the forecast-first method in Section 2. If Wednesday is genuinely over-staffed every week, some staff need to move to weekend-only or part-time.

Overtime above 10% of total hours

You are understaffed and paying the premium to hide it. Cheaper to hire one more part-timer. Every hour of overtime at 1.5x is money you would have spent hiring — but without the burnout, without the resentment, without the exit risk.

The weekly roster template

Same template every week. Same 6 roles down the side. Same 7 days across the top. Fill in hours per person per day, total hours, and cost.

WEEKLY ROSTER — [Outlet name] — Week of ___/___/2026 to ___/___/2026 Prepared by: ___________________ Published to WhatsApp: Sun 6 PM +------------------+------+------+------+------+------+------+------+-------+ | Role / person | Mon | Tue | Wed | Thu | Fri | Sat | Sun | Total | +------------------+------+------+------+------+------+------+------+-------+ | Head chef | 10 | 10 | 10 | 10 | 10 | 10 | OFF | 60 | | Sous chef | OFF | 10 | 10 | 10 | 10 | 10 | 10 | 60 | | CDP tandoor | 8 | 8 | 8 | 8 | 10 | 10 | 10 | 62 | | CDP curry | 8 | 8 | 8 | 8 | 10 | 10 | 10 | 62 | | Commis x 2 | 12 | 12 | 12 | 16 | 20 | 20 | 16 | 108 | | Dishwash x 2 | 12 | 12 | 12 | 14 | 18 | 18 | 16 | 102 | | Captain | 8 | 8 | 8 | 8 | 10 | 10 | 10 | 62 | | Steward x 3 | 18 | 18 | 18 | 22 | 28 | 30 | 24 | 158 | | Weekend part-t. | - | - | - | - | 6 | 8 | 6 | 20 | | Utility floater | 4 | 4 | 4 | 6 | 8 | 8 | 6 | 40 | +------------------+------+------+------+------+------+------+------+-------+ | DAILY HOURS | 80 | 90 | 90 | 102 | 130 | 134 | 108 | 734 | | FORECAST ₹ | 34K | 36K | 40K | 46K | 66K | 80K | 70K | 372K | | ₹/hour | 425 | 400 | 444 | 451 | 508 | 597 | 648 | 507 | +------------------+------+------+------+------+------+------+------+-------+ All-in labour cost this week (est): ₹92,000 Labour cost % of forecast revenue: 24.7% ← TARGET 22-25% ✓ Overtime hours planned: 0 Notes: Fri-Sun peaks staffed for +15% Swiggy promo running Sat-Sun. Utility floater breaks up commis burnout risk on Thu-Sat sequence.

Anybody in the outlet should be able to look at this and know exactly where they need to be, for how long, on any day of the week. That is what a restaurant roster planning discipline actually produces — not paperwork, but clarity.

Get the daypart revenue reports that make forecasting a 5-minute job

Online eMenu Ordering Suite reports break revenue down by day, daypart and channel — the exact demand signal you need for Sunday's roster. ₹199/month, no lock-in, live in 48 hours.

See pricing

Frequently Asked Questions

What is a healthy labour cost percentage for a restaurant in India?

22-28% all-in for casual dining including PF, ESI, staff meals and gratuity. QSRs 18-22%. Fine dining 28-32%. Anything above 30% for casual dining is a broken model.

What is the restaurant staffing formula?

Labour hours needed = forecast daypart revenue ÷ revenue-per-labour-hour benchmark. Benchmark is ₹800-1,000 for Indian casual dining.

How do I forecast next week's restaurant revenue for staffing?

Trailing 4-week average per day-and-daypart cell, then adjust for festival, weather, local event, aggregator promo.

What shift patterns work best for Indian restaurants?

Split shift, full shift, evening-only, weekend-only, utility floater. Match the pattern to the role, not to owner convenience.

How much do PF and ESI add to labour cost?

12% PF on basic + 3.25% ESI on gross + 4.81% gratuity + staff meals + bonus accrual. Layers 12-15% on top of headline pay.

How long should the Sunday staffing ritual take?

30 minutes with a template. 2-3 hours if you rebuild from scratch every week.

Full-time vs part-time vs gig?

Full-time for kitchen and senior floor. Part-time for weekend peaks. Gig for surge and one-off events. Typical mix 60-25-15 for a 45-cover outlet.

What are the 3 Monday metrics?

Labour cost % (target 22-25%), revenue per labour hour (target ₹800-1,000), overtime hours (target zero salaried, under 10% hourly).

Warning signs of a broken model?

Same person doing 4 back-to-back 12-hour shifts, Wednesday overstaffed while Saturday is short, overtime above 10% of total hours.

Does Online eMenu help with staffing decisions?

Yes — Ordering Suite reports give you the daypart demand signal for the Sunday forecast. You still build the roster in Sheets or a scheduling tool. ₹199/month.

O

Online eMenu Editorial Team

INWIZARDS SOFTWARE TECHNOLOGIES L.L.C · Dubai · Engineering in Indore · Published 2026-08-08