Almost every Indian restaurant runs on three departments and four reporting layers, whatever its size. Front of house, kitchen, and the admin desk that sits behind both.
The four layers are ownership, a general manager, department heads, and the floor and kitchen teams under them. A 20-seat cafe collapses several of those into one person. A 200-cover fine dine gives each one its own desk. The shape stays the same either way.
Team size is the part nobody can hand you as a number. It follows your covers, your service style and your menu, so this guide gives you the method to work it out rather than a ratio borrowed from somewhere else.
Key Takeaways
- Three departments run a restaurant: front of house, kitchen, accounts and admin
- They sit in four layers, from owner to general manager to the teams
- Front of house is everyone a guest sees; the kitchen everyone they do not
- Team size follows covers, service style and menu, not a fixed ratio
- Settle reporting lines before POS access, or everyone becomes a manager
What Is a Restaurant Staff Structure?
It is who reports to whom, and who is allowed to decide what. Nothing more complicated than that.
Indian restaurants split into three departments.
Front of house is everyone a guest sees. That is the host, the captain, the servers, the bartender and the busser.
Kitchen is everyone they do not. That runs from the head chef down to the dishwashers.
Accounts and admin sits behind both. It covers the cashier, purchase and store, which in most outlets means the billing screen and the purchase register.
The structure matters most on the days it is tested. A guest complaint at 9pm on a Saturday needs one person who can comp a dish without calling the owner. If nobody holds that authority, the table waits.
What Does a Restaurant Org Chart Look Like?
This is the full shape, with the four layers marked. Most restaurants run a smaller version of it.
Four layers, three departments Owner / Investor Layer 1 General Manager Layer 2 Layers 3 and 4, one block per department Front of House Manager Captain / Supervisor Servers · Host Bartender · Busser Everyone a guest sees Head Chef Sous Chef Chef de Partie · Commis Stewarding Everyone a guest does not see Accounts & Admin Cashier Purchase · Store Sits behind both Smaller outlets merge layers 2 and 3, and often merge the admin roles into one. The four layers most Indian restaurants run on, and the three departments underneath.Read it top down for authority and left to right for departments. The lines matter more than the boxes on a busy night, because they tell a server whose call it is when a table sends food back.
Three things are worth noticing in the chart.
The general manager is the only single point. Everything above is ownership and everything below is departmental. Remove that box and the three department heads start reporting to the owner directly, which works until there are two outlets.
The departments do not talk to each other on the chart. In practice they talk constantly, and the KOT is what carries that conversation. The chart shows authority, not workflow. Confusing the two is why some restaurants make the head chef report to the front of house manager. They should sit level.
Layer four is where the headcount is. Layers one to three are usually three or four people in total, whatever the size of the restaurant. Everything you add as you grow gets added at the bottom.
Most Indian restaurants run a compressed version. In an owner-run outlet, layers one and two are the same person, and the admin column is a laptop at the end of the counter.
Once the roles are named, our salary benchmarking guide gives role-wise ranges across metro and Tier-2 cities, so you can price the chart rather than guess at it.
Which Org Chart Shape Fits Your Restaurant?
The chart above is the hierarchical version, which is what most restaurants use. Two other shapes turn up, and it is worth knowing when they fit.
| Chart shape | How it works | Fits |
|---|---|---|
| Hierarchical | One line of authority from owner down | Almost every single outlet |
| Functional | Grouped by department, with heads at equal level | Kitchens with several strong sections |
| Matrix | Staff report to a department head and an outlet manager | Chains where a central chef sets the menu for all outlets |
The matrix shape is the one that causes arguments. A cluster head chef owns the recipe while the outlet manager owns the shift, so a line cook has two people giving instructions.
It works only if you write down which of the two wins on a given question, before anyone has to ask.
Who Does What in the Front of House?
The front of house carries the guest from the door to the bill. A front of house team usually runs five roles, though a small cafe folds them into two.
- Host. Greets, seats, manages the waitlist and the reservation book.
- Captain or supervisor. Runs a section, takes the difficult table, and holds the authority to fix a complaint on the spot.
- Server. Takes the order, fires the KOT to the kitchen, and closes the bill.
- Bartender. Runs the bar as its own small kitchen, with its own stock.
- Busser. Clears and resets, which is what actually decides how fast you turn a table.
The captain role is the one small outlets skip and then miss. Without it, every judgement call travels to the owner’s phone, and a captain ordering app only helps once somebody actually holds that authority.
Who Does What in the Kitchen?
The kitchen runs on the brigade system, which is a rank order rather than a job list. Each rank knows what it owns and what it is next in line for.
- Head chef or executive chef. Owns the menu, the food cost ratio and the pass.
- Sous chef. Second in command, runs the shift the head chef is not on.
- Chef de partie. Runs one section, such as tandoor, grill or curries, which is also how tickets get routed on a kitchen display system.
- Commis. Works under a chef de partie and learns the section.
- Stewarding. Dishwashing and kitchen cleaning, and the reason the next service can start.
The back of house roles are covered in more depth in our guide to restaurant chef types.
The rank order matters because a commis can see the next step. That visible ladder is one of the few retention tools a kitchen has, and it comes back at the end of this guide.
How Many Staff Does a Restaurant Need?
There is no ratio that survives contact with a real menu, so work it out from your own covers instead of copying a number. Four inputs decide it.
- Seat covers and turns. Eighty seat covers turning twice is a 160-cover night, not an 80-cover one. Size against the busiest service you actually run, not the average.
- Service style. A QSR counter needs a fraction of the floor staff a fine dine does at the same cover count, because the guest does the walking. A 40-seat cafe in Koramangala and a 40-seat fine dine in Lower Parel (an example) size their floors very differently.
- Menu complexity. Every extra kitchen section needs someone standing at it. A menu with tandoor, Chinese and continental sections needs three chefs de partie before it needs a fourth server.
- Opening hours. A restaurant open for both lunch and dinner needs two shifts, which is close to double the headcount, not a longer day from the same people. Daily hour caps make that a legal constraint rather than a preference, and they differ by state, so check yours against the labour codes. Our shift schedule template tracks the weekly hour limit and overtime for you.
Across the outlets we onboard, the pattern that repeats is under-staffing the pass and over-staffing the floor. Orders back up at the kitchen while servers wait, and the fix is usually one more pair of hands in the kitchen rather than two more on the floor.
Work out the number for your peak service, then price it with the staff cost calculator to see it as a share of revenue. If your kitchen metrics show ticket times climbing after 8pm, the structure is short in the kitchen, not on the floor.
How the Structure Changes as You Grow
This section covers what shifts as headcount grows and what does not. The three departments never change; what changes is how many people share each box.
| Stage | Who runs it | What usually breaks first |
|---|---|---|
| Single outlet, owner present | Owner is the general manager | Nothing, until the owner takes a day off |
| Single outlet, owner absent | A general manager is hired | Authority, because nobody knows who can comp a bill |
| Two to five outlets | Department heads per outlet, one owner above | Consistency, since each outlet drifts into its own way of working |
| Chain | Area managers between owner and outlets | Reporting, because the owner loses sight of the floor |
Volume is what forces the brigade to get deeper. A single tandoor at 40 covers a night is one person’s job. The same section at 400 covers needs a chef de partie with two commis under them.
A single outlet in Indiranagar that opens a second in Whitefield (an example) hits this on day one, because the owner can only stand in one of them.
That second move is the one that catches most owners. Handing over daily running means writing down the authority that used to live in your head. That is the point at which a structure has to exist on paper rather than by habit.
Set the Structure Before You Set POS Access
The org chart decides who can do what on the billing screen, so it has to be settled first.
If everyone logs in with the same rights, every discount, void and bill reprint looks the same in the report. You lose the ability to ask who did it, which is the whole point of a hierarchy.
POS user rights should mirror the chart. Servers punch orders, captains approve modifications, managers void bills, and the owner sees the reports.
While talking to restaurant owners using Petpooja, separating those rights is the change they ask for first once they stop working every shift themselves. That is conversation rather than survey data, but it comes up often enough to be worth saying.
The same chart drives the staff schedule, since you can only roster roles you have defined. A restaurant POS that supports role-based logins turns the structure into something enforced rather than something written on a noticeboard.
What the Structure Does for Retention
A structure is also a career path, and that is not a small thing in this industry.
Restaurants are India’s second-largest employer, with 85.5 lakh people directly employed in 2024. The July 2024 NRAI India Food Services Report expects that to rise by over 20% by 2028. That is a lot of people moving between kitchens.
A commis who can see the chef de partie job above them has a reason to stay another year. A server with no captain role above them does not. Most of what we see written about staff retention starts with pay, but the ladder matters just as much, and it costs nothing to draw.
Conclusion
Three departments, four layers. That is the whole structure, and it holds from a 20-seat cafe to a 200-cover fine dine.
Two decisions are worth making deliberately. Where authority sits, so a complaint can be settled on the floor. And how many people you need at peak, rather than on an average Tuesday.
Draw the chart before you hire the next person. Then mirror it in your POS access rights so the hierarchy shows up in your reports, not just on the noticeboard.
Frequently Asked Questions
What are the three departments in a restaurant?
Front of house, kitchen, and accounts and admin. Front of house covers everyone the guest meets, the kitchen covers everyone they do not, and admin handles cash, purchase and store. Every restaurant runs all three, even when one person does two of them.
What is the kitchen brigade system?
A rank order for the kitchen, running head chef, sous chef, chef de partie, commis and stewarding. Each rank owns a defined section and is next in line for the one above. It gives a kitchen both a chain of command and a promotion path.
How many staff does a small restaurant need?
It depends on covers, turns, service style, menu sections and opening hours, so no single number applies. Size the team against your busiest service rather than an average day, and count kitchen sections before you count servers.
Who should be able to void a bill?
A manager or the captain on duty, not every server. Restricting voids and discounts to named roles is what lets you trace an unusual pattern later, and it is set up through role-based logins on the POS.
Does a small cafe need a full hierarchy?
It needs the roles, not the headcount. One person can be owner, general manager and cashier at once. What matters is that someone knows they hold each responsibility, particularly the authority to settle a guest complaint without a phone call.
Thanks. This helps us make the next article better.





