SOP Development

An SOP is not a binder for the shelf. It is the answer to a simple question: if the person who knows how to do this leaves tomorrow, can the next person do it to the same standard by Friday?

In most Indian restaurants the answer is no, and the cost shows up as inconsistent food, unpredictable ticket times, and a rating that slides every time the roster changes.

What we write

Kitchen SOPs cover prep quantities, station setup, cooking method, plating and closing. Service SOPs cover the first thirty seconds at a table, order taking, timing between courses, and what a server is allowed to do when a guest is unhappy without calling a manager.

Hygiene SOPs are written against FSSAI requirements, because the audit will come and it is cheaper to pass it than to argue with it.

Written for the people who use them

A checklist on the wall beats a paragraph in a manual. Photographs beat descriptions. The plating guide is a photo of the correct plate, taken in your kitchen, under your lights, with your crockery — not a stock image of someone else’s food.

Rolling them out

We train the team on the SOPs rather than emailing a PDF and hoping. Then the owner or manager gets an audit checklist: fifteen items, five minutes, once a week. Standards hold when someone checks them.

Where this sits in the framework

SOPs are the Develop stage. They are also the single biggest reason a second outlet opens smoothly — you cannot copy a restaurant that only exists in one chef’s head.