Read first
What happens at 9 pm on a Saturday?
Forty covers walk in within fifteen minutes. Tickets stack up on the printer. The tandoor cook has no marinade ready, the curry cook is waiting on a gravy and the captain keeps asking 'how long?' A kitchen at peak is not cooking harder: it is running a system. Everything in this page is about making that system run without the owner standing in the middle of it.
Peak is where a restaurant earns. Casual dining makes 70–80% of sales at weekends, and tables turn Casual 1.5-2.5; fine dining 0.8-1.2; QSR 3.5-6, so every minute lost at the pass is a table not turned.
How should the stations be organised?
A station is a place with one cook, the equipment, the ingredients and the tickets for one kind of dish. Typical Indian stations are the tandoor and grill, the curry or gravy line, the Chinese or wok line, the bread and rice station, the cold station for starters and salads, and the dessert and beverage point. Staffing depends on size: the research puts kitchen staff for 60 to 100 covers at 12–15 kitchen staff, and the kitchen at 40 to 45% of total headcount. See how many staff.
- Match stations to your top dishes, not the whole menu. A station that serves five dishes people actually order beats one that serves twenty.
- Give each station a written par for its mise en place, and a person who owns it.
- Keep each station self-sufficient: its own cold well, spoons, cloths, and handwash within reach.
- Put the slowest dish closest to the pass. The pass decides the time to the table.
How does a KOT flow?
A KOT is a kitchen order ticket: the captain takes the order, the POS prints it in the right kitchen, and the cook reads it. The flow has a few rules that keep a rush from turning into chaos:
- Tickets print by station, or one master ticket is called out by one person (the expediter or head chef) who reads each item to its station.
- One person calls the pass. Someone says 'two butter chicken, one dal, one naan: fire' and tracks which tables are waiting. Without a caller, every cook decides for himself.
- Fire courses together. The captain tells the kitchen which dishes go out together so one table's food does not sit under a lamp for ten minutes.
- Clear the ticket when the plate leaves the pass, not when the dish is cooked.
- Say 'dish off' loudly when you run out, and update the POS so the captains stop selling it.
- Handle changes by voice and ticket. A change by shouting alone gets lost.
Printers, tablets and QR ordering are the tools; see KOT printers and QR ordering. The flow matters more than the tool.
What is mise en place and why does it matter?
Mise en place is having everything cut, measured, marinated and in reach before service starts. A rush is lost in the first hour, not the busiest one: if the base gravies are ready, the marinades are in the chiller and the garnish is cut, a ticket takes minutes. If they are not, you cook from scratch at the peak. Prep to par (daily prep) and build the prep sheet from the day's expected covers.
- Cook the bases (gravies, marinades) ahead and finish to order.
- Pre-portion proteins, breads and sides in labelled containers.
- Put backups for the top five dishes in the chiller at a level that covers the first hour of the rush.
- Restock between waves: a runner refills stations at the lull, not in the middle.
How do I keep a Saturday under control?
- Run a shorter menu on busy nights. Drop the dishes that need a unique ingredient or long cook time. A menu the kitchen can deliver beats a long one; see a menu the kitchen can deliver.
- Add a pair of hands at the stations that bottleneck: a helper on the tandoor, a runner on the pass.
- Watch the longest-waiting ticket, not the newest. Tell the captain early when a table will wait, and offer water or a starter.
- Clean as you go. A dirty station slows a cook and breaks the hygiene rules; see kitchen hygiene rules.
- Keep the owner out of the line. The owner stands where the tickets can be seen and clears blocks.
- Have a plan for a rush of dine-in plus delivery. Switch off or throttle app orders when the room is full; see delivery apps.
How long a table should wait, and what to say when the kitchen is slow, is in how long a table waits.
What do I review after a bad night?
Look at the tickets, not the story. Which dish was slowest? Which station was stuck, and why: no mise en place, a missing ingredient, a broken burner, too few hands? How many covers did you do, and how many walked out? Fix one thing a day. Over a month this is worth more than a new menu. Record the day's covers against the roster so you can adjust staffing next time; the relief factor for weekly offs and leave is about 1.26 times on payroll.
What usually goes wrong
- No one calling the pass.
- A menu too long for the stations that exist.
- Mise en place for an average Tuesday on a Saturday night.
- The owner cooking on the line, so nobody is running the room.
- An ingredient out and the POS still selling it.
- Staff who never rehearse a rush, so the first big night is the first test.
Apply it to your own case
Sit at the pass on your busiest night with a stopwatch and a notebook. Note the five slowest tickets and the cause of each. Fix the cause with one change, then repeat the next weekend. Tell us your type, menu size and the line you run and we can suggest where owners usually find the bottleneck.
Questions people ask
What is a KOT in a restaurant?
A kitchen order ticket: the order printed or displayed in the kitchen so each cook knows what to make. A caller on the pass keeps the flow in order.
How do I stop the kitchen getting slow on weekends?
Prepare mise en place to a weekend par, run a shorter menu on busy nights, add hands at bottleneck stations and have one person call the pass.
How many kitchen staff for 60 to 100 covers?
The research puts it at 12–15 kitchen staff; see staffing.
What is mise en place?
Having ingredients cut, portioned and in reach before service, so dishes are finished to order in minutes.
Where these numbers come from
- Table turns a day: Casual 1.5-2.5; fine dining 0.8-1.2; QSR 3.5-6 (India; software vendor tool page. A 2023 brokerage table gives an industry average of about 1.3). Reported: RestaurantDaily, table turnover tool, checked 14 November 2026.
- Kitchen staff for 60 to 100 covers: 12–15 kitchen staff (India). Reported: ProKitchens, commercial kitchen staffing structure in India (24 March 2026), checked 14 November 2026.
- Payroll multiplier for one weekly off and 8% leave: 1.26 times (India). Ballpark 7 ÷ (7 − 1) × 1.08 = 1.26: to staff a post seven days, pay for 1.26 people.
Fees, rates and rents change. Check the official source before you pay or sign anything.
Operations · Restaurant
More on operations for a restaurant
13 pages on this. You are on number 5.
- What does a restaurant buy every week, and roughly how much?
- How do I find reliable vegetable, meat, seafood and dairy suppliers for a restaurant?
- How do I run a restaurant kitchen at peak: KOT, stations and mise en place?
- How much cold storage and dry store does a restaurant need, and how should it be organised?
- My restaurant supplier delivers late or short. What do I do?
- What a commercial LPG cylinder costs a restaurant, city by city
- What do I do when there is a power cut, a breakdown or no water during restaurant service?
- How do I stop stock, cash and discount theft in a restaurant?
Reading about it is one thing; doing it in your restaurant is another. If you'd like a hand running it smoothly day to day, tell us where you are and a person will reply, free.
Get help with this ↓What now?
Where are you?
One tap, and we point you to the right next step.
What to read next
Related questions
Where this fits in your journey
- Step 8 of 8Should I buy a restaurant franchise, and how to choose one: Open and run the outlet→
- Step 6 of 8Should you rebrand your restaurant, and how to do it well: Train the team and trial the new menu before the switch→
- Step 3 of 9How to run a restaurant well, day to day: Run the kitchen at peak→
- Step 4 of 8How to get a restaurant job in India and grow from there: Make the first three months count→