Restaurant SOPs: The Eight You Actually Need
A restaurant needs about eight SOPs, not eighty. Each is one page with an owner, the steps, and a number that shows whether it was done.
A restaurant SOP, or standard operating procedure, is a written way of doing a recurring job so it comes out the same whoever does it. Most restaurants need about eight of them. The binders with eighty SOPs, one for folding napkins, are written once, read never, and quietly replaced by "ask Ravi".
This piece covers the eight worth writing, what each one has to contain, and the one feature that separates an SOP your staff follow from one they ignore: a number you can check.
Key takeaways
- An SOP is one page: who owns it, when it runs, the steps, the standard, and what to do when it goes wrong.
- Eight cover almost everything: opening, closing, receiving, storage, cooking and cooling, cleaning, order to bill, and complaints.
- Every SOP needs a checkable standard. "Keep the fridge cold" is a wish. "5°C or below, logged twice a day" is a procedure.
- For the kitchen, FSSAI has already written most of the numbers down.
- The SOPs that hold are the ones your systems enforce, not the ones that depend on memory.
What a restaurant SOP is, and what it isn't
An SOP is not a job description and it is not a training manual. It is the answer to one question: how do we do this particular job here, every time?
Every good one has the same six parts:
- Purpose. One line on why it exists.
- Owner. A role, not "everyone". If everyone owns the gas check, nobody does.
- When. Opening, every delivery, every table, end of day.
- Steps. Short, numbered, in the order they actually happen.
- The standard. A number or a yes/no someone else can verify.
- If it goes wrong. What to do when the fridge reads 9°C, not just what should happen when it reads 4°C.
Keep each to a page. If a procedure needs three pages, it is two procedures.
The eight SOPs worth writing
| SOP | Usual owner | The checkable standard |
|---|---|---|
| 1. Opening | Opening manager | Signed opening checklist, temperatures logged |
| 2. Closing and day close | Closing manager | Cash, card, UPI and online totals match the system |
| 3. Receiving deliveries | Kitchen lead | Chilled at 5°C or below, frozen at -18°C or below, checked against the invoice |
| 4. Storage and stock rotation | Storekeeper or chef | First in, first out; labels with date and time |
| 5. Cooking, cooling and reheating | Head chef | FSSAI core temperatures and cooling times |
| 6. Cleaning and pest control | Kitchen lead | Signed cleaning schedule; pest control on a fixed cycle |
| 7. Order to bill | Floor manager | Every order on a KOT, every bill in sequence, voids approved |
| 8. Complaints and refunds | Duty manager | Logged, resolved, and reviewed weekly |
1 and 2. Opening and closing
These are the two most people already have, usually as a laminated sheet nobody signs. The fix is initials and a time on every line, and a manager signature at the bottom. We built a free opening and closing checklist you can cut down to your venue and print, with the FSSAI figures already on the kitchen lines.
The closing SOP matters more than the opening one, because it is where money is counted. A real close checks each payment type against the system separately, confirms bill numbers ran with no gaps, and looks at voids and discounts by staff member. "The total looks about right" is not a close.
3. Receiving deliveries
The cheapest moment to reject bad stock is at the door, with the driver still there. FSSAI's catering guidance puts chilled high risk food at 5°C or below on receipt and frozen food at -18°C or below. Check temperature, expiry and quantity against the invoice, and write down what you rejected and why. Once a crate is signed for, it is yours. If you buy from Hyperpure or a similar platform, the same rule applies; cold chain is where owners report the most trouble.
4. Storage and stock rotation
First in, first out, with first expired, first out for anything dated. Label everything that goes into a fridge with what it is and when it was made. Most of the value of this SOP shows up later, in food cost and in inventory counts that finally match.
5. Cooking, cooling and reheating
This is where FSSAI's catering guidance is most specific, so borrow its numbers rather than inventing your own:
- Vegetarian food cooked to a core of 60°C for 10 minutes or 65°C for 2 minutes.
- Non-vegetarian food cooked to 65°C for 10 minutes, 70°C for 2 minutes, or 75°C for 15 seconds.
- Hot food held at 65°C or above; chilled food at 5°C or below.
- Cooked food cooled from 60°C to 21°C within 2 hours, then to 5°C within a further 4 hours, and eaten within 24 hours.
- Frying oil discarded once total polar compounds cross 25 percent, per FSSAI's own limit.
A probe thermometer costs less than one bad review. The SOP is useless without one.
6. Cleaning and pest control
Split this into a daily cleaning schedule, signed by whoever did it, and a periodic list: deep cleans, pest control, water testing, and staff health. FSSAI's guidance calls for pest control in stores to be repeated every 15 days, for drinking water to meet IS 10500 and be tested every six months, and for food handlers to have a medical examination by a registered practitioner once a year. Those are dates to put in a calendar, not habits to hope for.
7. Order to bill
This is the SOP most restaurants never write down, and the one that leaks the most money. It covers how an order is taken, how it reaches the kitchen, how the bill is made, and who can change it afterwards.
The standard has three parts. Nothing is cooked without a KOT. Bills run in a single unbroken sequence, because a GST invoice number must be consecutive and unique for the financial year. And no bill is voided or discounted without a named manager approving it. Our bill format generator sets out the invoice rules if you want to check yours.
8. Complaints and refunds
Who can offer a replacement dish, who can waive an item, and where it gets written down. Log every complaint with the dish and the reason, and read the log weekly. A dish that draws three complaints in a week is a recipe problem, not a service one. What ends up online is a separate matter, and Google has firm rules on how you may ask for reviews.
Why SOPs stop being followed
Almost never because staff are lazy. SOPs fail because they rely on someone remembering to do something extra on a busy night.
The ones that survive are enforced by the way the work flows. A bill number assigned by the system at payment cannot be skipped. A dish marked unavailable in one place and switched off everywhere cannot be ordered by mistake. A void that needs a manager's approval in the software doesn't depend on the manager being watchful.
Before you write a procedure, ask whether a system could make the right way the only way. Where it can, you need a setting, not an SOP. Where it can't, write the page and put a number on it.
FAQ
What is an SOP in a restaurant?
A standard operating procedure is a written, step-by-step way of doing a recurring job, such as opening, receiving deliveries or closing the till, so it is done the same way whoever is on shift. A good one fits on a page and names an owner, the steps, and a checkable standard.
How many SOPs does a restaurant need?
About eight cover most restaurants: opening, closing and day close, receiving deliveries, storage and stock rotation, cooking and cooling, cleaning and pest control, order to bill, and complaints. Bars add stock and pour control. Start with these before writing anything more detailed.
How do I write a restaurant SOP?
Use six parts: purpose, owner, when it runs, numbered steps, a checkable standard, and what to do when it goes wrong. Write it with the person who does the job, test it on a real shift, and keep it to one page. If it runs longer, split it into two.
Are restaurant SOPs mandatory in India?
No law requires a document called an SOP. But FSSAI's hygiene requirements under Schedule 4 expect controls on temperature, cleaning, pest control and staff health, plus records. Written SOPs with signed logs are the practical way to show you actually meet them.
What is the difference between an SOP and a checklist?
An SOP explains how a job is done and why. A checklist is the short record that proves it was done on a given shift. Your opening SOP might run to a page, while the opening checklist is the sheet staff initial each morning.
What to do next
Start with the two you already half have. Open the free opening and closing checklist, untick everything that doesn't apply to your restaurant, and print it for tomorrow with a line for the manager's signature. Then write the order-to-bill SOP, because it is the one tied most directly to cash.
If you want the order, the KOT and the bill in one unbroken sequence, with voids needing a manager's approval, book a short dineomAI demo and see it run on your own menu.
See it on a real table
A 15-minute demo: watch dineomAI take an order, speak five Indian languages, and upsell the right pairing. No hard pitch.
Book a 15-minute demo →