Headcount Optimisation
Labour is typically the second largest cost in any restaurant after food, often sitting between 25% and 35% of total revenue. Unlike food cost, which scales naturally with covers, labour cost is far stickier. You pay your staff whether the restaurant is full or empty, and getting the balance wrong in either direction is expensive: overstaff a slow Tuesday, and you burn through payroll unnecessarily; understaff a busy Saturday, and you lose covers, damage the guest experience, and burn out the team.
Headcount Optimisation is the discipline of getting that balance right, consistently, across every shift.
What is Headcount Optimisation?
Headcount Optimisation is the process of determining exactly how many staff members you need on each shift, in each role, based on actual and forecasted guest demand rather than habit, guesswork, or the schedule that has always existed.
It uses historical sales data, covers, seasonal patterns, and day-of-week trends to build staffing levels that match the real rhythm of your restaurant rather than a fixed template that applies the same headcount to a quiet Monday as to a packed Friday.
Why Most Restaurants Get This Wrong
Most restaurant staffing schedules are built on habit rather than data. The same number of servers show up on Wednesday as on Saturday because that is how it has always been done. The kitchen runs the same number of line cooks during a festival week as during a regular one because no one has systematically looked at whether the numbers actually match the demand.
The result is a labour cost that does not flex with revenue, which means your labour percentage shoots up during slow periods and squeezes your margins precisely when revenue is already under pressure.
The opposite problem is equally damaging. Being chronically understaffed during peak periods because the schedule was built conservatively leads to longer wait times, table errors, overwhelmed staff, and guests who leave without returning.
A Real Example
A 70-cover casual dining restaurant in Chennai runs a consistent team of 6 servers and 4 kitchen staff across all evening shifts, seven days a week. After pulling three months of cover data, the owner identifies the following pattern:
Monday to Wednesday evenings average 28 covers. Thursday to Sunday evenings average 61 covers. Friday and Saturday evenings between 7 PM and 10 PM average 74 covers with a 20-minute wait during peak hour.
They restructure the schedule so that Monday to Wednesday evenings run with 3 servers and 3 kitchen staff, saving approximately Rs. 12,000 per month in labour cost. Thursday gets 4 servers. Friday and Saturday get 7 servers, including one dedicated runner, and the kitchen adds a part-time prep support on those two evenings specifically.
Service quality on weekends improves because the team is appropriately staffed for the volume. Labour cost as a percentage of revenue drops from 31% to 26% within two months, entirely through schedule restructuring rather than pay cuts or redundancies.
The Key Metrics for Headcount Optimisation
- Covers per labour hour: Total covers served divided by total staff hours worked in the same period. Tracking this across different shifts tells you where your team is working efficiently and where they are overstaffed relative to demand.
- Labour cost percentage: Total labour cost divided by total revenue for the same period. Industry benchmark for most restaurant formats sits between 25% and 32%. Consistently above 35% usually indicates a scheduling problem rather than a pay rate problem.
- Revenue per available staff hour: Total revenue divided by total staff hours. This helps you identify which shifts are genuinely productive and which are absorbing payroll without generating proportionate revenue.
How to Optimise Headcount at Your Restaurant
- Pull at least 3 months of cover and revenue data broken down by day of week and shift, to identify your genuine demand pattern before changing any schedule
- Build shift templates based on cover tiers rather than fixed headcounts, for example: under 30 covers requires this team configuration, 30 to 50 covers requires this one, above 50 requires this one
- Use a rolling 4-week forecast informed by historical data, local events, weather, and known bookings to project covers and set staffing accordingly each week
- Cross-train staff across roles so that a server who is not needed on the floor during a slow lunch shift can support prep or hosting without being sent home or sitting idle
- Track labour cost percentage weekly rather than monthly so that scheduling problems are visible and correctable before they compound into a significant margin issue
- Account for ramp-up time by scheduling one additional staff member at the beginning of peak shifts to handle the transition from slow to busy without the service gap that occurs when the team is already stretched before reinforcements arrive
How Headcount Optimisation Connects to Guest Experience
Staffing optimisation is not just a cost exercise. The right number of staff on the right shift is also what makes excellent service consistently deliverable. A server covering too many tables during a peak shift cannot provide the attentiveness, upselling, and personalised interaction that drives higher average check size and guest satisfaction scores.
Getting headcount right means your team can do their jobs well, which means guests have better experiences, leave better reviews, and come back more often. The profitability benefit and the hospitality benefit point in exactly the same direction.
Quick Recap
- Headcount Optimisation aligns staffing levels with actual guest demand across different shifts, days, and seasons.
- The most common mistake is using fixed headcounts across all shifts regardless of demand variation.
- Covers per labour hour and labour cost percentage are the two most useful metrics for diagnosing scheduling inefficiencies.
- Getting headcount right improves both profitability and guest experience simultaneously, making it one of the highest-impact operational improvements available to any restaurant owner.