How Professional Chefs Develop a Restaurant Menu — The 6-Step Kitchen Process

Key takeaways

Menu development is a six-step structured process — not creative brainstorming — that ends with one specific deliverable: a complete set of standardised recipes that any trained Commis can execute consistently without the Head Chef present. This guide covers the process from the professional kitchen side: concept and constraints, shared-base-gravy dish architecture, costing on real yield, capacity testing, standardised recipe documentation, and the chef’s negotiation with the owner. The standardised recipe is the product of the process. Everything else is preparation.

FEATURED SNIPPET — What Is Menu Development for a Professional Kitchen?

Menu development is a 6-step structured process: (1) define concept and constraints, (2) develop dishes on a shared base-preparation architecture, (3) cost every dish on yield-adjusted ingredient rates, (4) test the menu through a simulated kitchen-capacity service, (5) write complete standardised recipes, (6) train the team and run a soft launch. The deliverable is a set of standardised recipes precise enough for any trained chef to produce identical results every service — not a PDF menu card.

The GM walks into the kitchen on a Tuesday and says the restaurant is relaunching in eight weeks and can you put a new menu together. What follows — if done correctly — is not creative brainstorming and plating experiments. It is a structured development process with six stages, each of which produces a specific output. The last output is the only one that matters for running a kitchen: standardised recipes the brigade can execute at volume, without the Head Chef watching.

Written from working-kitchen experience leading brigades across Tamil Nadu and international hotel kitchens.

1. Step 1 — Concept and Constraints: Define Before You Cook

Before a single dish is invented, four things must be defined in writing. A chef who starts trialling dishes before defining the constraints will be reworking half the menu by week three.

Constraint	Questions to answer before development starts
Cuisine / format	Multi-cuisine or regional focus? Live counter? Delivery-viable menu needed?
Guest profile	Corporate, leisure, family, Jain, vegan requirements? Average spend target?
Kitchen capacity	What equipment? What brigade size? How many stations? What service hours?
Food cost target	What % is the target? Is it the same for all sections? Who sets it?
Delivery viability	Does the menu need to survive 30 minutes on Swiggy or Zomato?

*The delivery architecture test:

Before any dish is added to a delivery menu, run it through this 5-question test:

1. Does it travel for 30 minutes without significant quality loss?
2. Can it be packaged without requiring assembly by the delivery person?
3. Does it taste correct at 25°C (room temperature on arrival)?
4. Does the packaging maintain structural integrity — no spillage, no compression damage?
5. Is the food cost viable at the delivery channel’s 18–30% commission?

A dish that fails any one of these five questions should not be on the delivery menu — regardless of how well it sells dine-in.

★ The delivery viability question must be asked in the first conversation, not as an afterthought in week six. A dish that cannot travel 30 minutes without collapsing is not a delivery dish. See [working as a chef in a cloud kitchen](/blog/cloud-kitchen-operations-chef-india/) for the delivery-specific constraints that affect menu architecture from the start.

2. Step 2 — Dish Development: The Shared Base-Preparation Model

This is the section no menu development guide has written specifically for an Indian professional kitchen. A Western recipe-costing model assumes each dish has its own self-contained ingredient list. An Indian menu does not work that way — half your à la carte typically runs off two or three shared base gravies made in bulk every morning.

Base preparation	Dishes that draw from it	Efficiency gained
Makhani (tomato-butter-cream base)	Butter chicken, paneer makhani, dal makhani	One costed batch; three dishes share it
Brown onion-tomato gravy	Mutton rogan josh, lamb curry, rajma	Shared prep time and ingredient buying
White cashew gravy	Korma, shahi paneer, navratan	Premium cashew cost spread across multiple dishes
Chettinad masala base	Chicken, prawn, vegetable variants	One complex masala; proteins are interchangeable

is operational architecture that will break at the first Friday dinner service. Design the base preparations first. The dishes follow from them. For the Chettinad base masala technique, see [Chettinad cuisine for professional chefs](/blog/chettinad-cuisine-professional-chef/).

3. Step 3 — Costing on Yield: The Step Most New Menus Skip

The two formulas that govern every dish cost:

Dish Cost = (Ingredient cost at yield-adjusted rate) + Q-factor (₹5–20 per cover)

Food Cost % = (Dish Cost ÷ Menu Price) × 100

Worked example — Butter Chicken (chicken line at purchase weight; see star note):

Component	Purchase qty	Yield %	Usable qty	Cost/kg ₹	Dish cost ₹
Chicken boneless	200 g	85%	170 g	₹300/kg	60
Makhani base (at ₹200/litre)	180 ml	100%	180 ml	₹200/L	36
Cream finish	30 ml	100%	30 ml	₹220/L	7
Q-factor (oil, salt, garnish, accompaniments)	—	—	—	₹5–20/cover	8
Total dish cost	—	—	—	—	111
Menu price (pre-GST)	—	—	—	—	₹420
Food cost %	—	—	—	—	26.4%

★ Note on the chicken figure: ₹60 is costed at purchase weight (200g × ₹300/kg) for simplicity. To cost at yield-adjusted rate: 170g usable × ₹300/kg = ₹51, giving dish cost ₹102 and food cost % 24.3%. Apply yield adjustment consistently across all protein lines in your real recipe cards — the methodology matters more than the specific number used in this illustration. For the full food cost formula and methodology, see [food cost percentage formula](/blog/food-cost-percentage-formula/).

4. Step 4 — Kitchen-Capacity Testing: Run the Simulated Service

Kitchen-capacity testing means running the proposed menu through a mock service — a controlled test with real brigade and real timing — before committing to launch.

Test question	What to look for	Common Indian kitchen finding
Which station becomes the bottleneck?	Longest ticket times; most simultaneous orders	Hot section overloaded with biryani + multiple dum dishes at peak
Which dishes exceed the 12-minute ticket time?	Anything over 12 min on a busy pass	Live tandoor items competing with curry section simultaneously
Which preparations cannot be made to par in the mise window?	Complex bases needing 3+ hours	Multiple biryani variants requiring separate dum sealing
Which dishes hit multiple stations on the same ticket?	Station pile-ups on one order	Dal tadka + naan + biryani all firing at the same moment

★ Discovering a station bottleneck in the capacity test costs nothing. Discovering it at the first 300-cover Saturday dinner costs the restaurant its reputation. Build the mock service into the development process — not as an optional extra.

5a. Critical Control Points — The Food Safety Layer of Every Recipe

A standardised recipe that lacks critical control points is a food safety risk, not just a quality risk. Every recipe must document the points where temperature, time, or hygiene control is mandatory:

Preparation	Critical control point	Minimum standard	Consequence if missed
Chicken tikka (marinade)	Internal temperature post-tandoor	75°C core temperature	Food safety failure; undercooking risk
Cream-based gravies	Temperature when cream is added	Never above 85°C	Cream splits; dish fails
Biryani (dum)	Dum seal integrity and time	Minimum 25 min on low heat	Undercooked rice bottom layer
Curd-marinated items	Cold-chain from marinade to cook	Under 5°C until cooking begins	Bacterial growth in 2–4 hour window
Deep-fried items	Oil temperature before service	175°C minimum	Oily product; absorption-based food cost error
Raw-to-cooked transfer	Separate boards and knives	No shared equipment	Cross-contamination; FSSAI compliance failure

★ FSSAI inspection checklists include CCP documentation as a compliance item. A standardised recipe with documented CCPs is not just better cooking — it is evidence of a HACCP-compliant kitchen. At Sous Chef level, the ability to write recipes with correct CCPs is what separates a kitchen-ready candidate from a line cook with good technique.

The plating specification standard: A standardised recipe is incomplete without a plating spec. The plating spec is the visual standardised recipe:

Element	What to specify	Example
Bowl / plate type	Material, size, colour	“White 26cm deep plate; not the shallow version”
Protein placement	Clock position and orientation	“Chicken tikka at 2 o’clock, bone inward”
Sauce quantity	Millilitres or ladle size	“80ml gravy — one 80ml ladle; not poured free”
Garnish	Specific herb, quantity, placement	“3 coriander sprigs, stems trimmed, placed at 12 o’clock”
Accompaniment	Type and position	“1 wedge lemon, right side; not a slice”

The plating spec is what makes a dish look the same on a Monday morning Commis as on a Saturday evening CDP. Without it, every chef improvises — and improvisation is how “consistent” restaurants become inconsistent.

5. Step 5 — The Standardised Recipe: The Actual Deliverable

The standardised recipe is the product of the menu development process. Not the menu card. Not the plating photos. The recipe.

Required field	What it contains	Why it matters
Recipe name and version	Full name + version number + date	Tracks which version is live
Ingredient list	Quantities by weight in grams only — no cups, no handfuls	Consistency across any cook
Yield after cooking	Final cooked weight or volume	Portion control and food cost benchmark
Portion spec	Exact serving weight or piece count	The theoretical food cost reference
Method	Step-by-step with timing and temperatures	Reproducibility without supervision
Critical control points	Protein internal temperature; stage when cream is added	Food safety and quality control
Plating notes	Component placement; garnish spec	Visual consistency
Allergen flags	All allergens present	FSSAI compliance and guest safety
Dish cost at writing	Total cost per portion at current rates	Theoretical food cost record

★ The standardised recipe is also the training document. When a new Commis joins or the Sous Chef is absent, the recipe is what keeps the dish consistent. A brilliant dish with a poorly documented recipe degrades within weeks.

5a. Writing a Standardised Recipe That Actually Gets Used — The Common Failures

Most kitchens have standardised recipes. Most standardised recipes are not actually used. The gap between a recipe that exists and a recipe that functions as a kitchen control tool is specific and fixable.

Failure 1: Quantities in non-standard measures

“A handful of curry leaves.” “Two large onions.” “Oil as needed.” These measurements produce different dishes every time they are cooked, because a Commis’s handful and a Head Chef’s handful are not the same quantity. Every ingredient on a standardised recipe must be in grams or millilitres. No exceptions.

The conversion table every recipe writer needs:

Common informal measure	Correct gram/ml equivalent
1 medium onion	120–140g (specify: peeled and rough-chopped weight)
1 teaspoon salt	5g table salt; 6g sea salt
1 tablespoon oil	12ml
A handful of leaves	Weigh 3 actual handfuls; average = that’s your gram weight
“To taste”	Specify the starting point in grams; adjust notes in the critical control section
2 large garlic cloves	10g peeled garlic

Failure 2: No critical control points

A standardised recipe without critical control points is a description, not a control document. Critical control points are the stages where the wrong action produces an unrecoverable result. Every recipe must identify them explicitly.

Examples of critical control points for Indian dishes:

• Makhani base: the moment the tomato-butter-cream emulsion is correct — look for a specific sheen, not just a colour
• Biryani dum: internal temperature of the rice layer at the seal point must be 85°C before sealing — below this the rice steams unevenly
• Curd-based gravies: do not exceed 75°C after adding curd — above this the proteins split
• Deep-frying: oil temperature must recover to 175°C between batches — frying in oil that has dropped below 160°C produces greasy, under-cooked results

Failure 3: No plating specification

The standardised recipe ends with a plating note. “Garnish with coriander” is not a plating specification. A plating specification states:

• Bowl or plate: which one, what size
• Amount of sauce: in millilitres (e.g., 180ml sauce)
• Protein placement: centre, side, or scattered
• Garnish: what, how much (in grams), where on the plate
• Any sauce trail or finishing oil: describe the motion

When a Commis reads the plating specification and can produce the dish without seeing the Head Chef plate it first, the specification is complete.

★ A standardised recipe is the most important document a kitchen produces. It outlasts the Head Chef who wrote it. It trains the Commis who will run the section in three years. It is the institutional memory of the kitchen. A kitchen with no functioning standardised recipes is entirely dependent on the individuals currently present — and entirely vulnerable to any one of them leaving.

5b. The Soft Launch — How to Run It Correctly

A soft launch is not a friends-and-family dinner where nobody complains. It is a controlled test of the new menu under real service conditions. To be useful, it must be run as follows:

3 days before soft launch:

• Full brigade training: every dish demonstrated by the Head Chef, with the standardised recipe open alongside
• Tasting session: every dish tasted by the full team — not just the senior chefs
• FoH briefing: every floor team member receives a one-page dish description card with allergens and two talking points per dish

Soft launch day (60–70% capacity, never full):

• Run the service as a real service — no special accommodations for the test format
• Station observer: one chef (typically the Sous Chef) circulates and notes: ticket time deviations, portion inconsistencies, mise en place gaps
• Guest feedback: collect verbal feedback on every table; the floor manager asks specifically about two or three target dishes

Post-service debrief (same evening, no later):

• Station observer’s notes reviewed with the full brigade
• Every dish with a problem gets a specific fix agreed in the room before anyone leaves
• Standardised recipes updated immediately — not “tomorrow”

The debrief question that matters most: “If we run this menu at 100% capacity this Friday, what will break first?” The answer to that question is the final thing that must be fixed before the full launch.

6. Step 6 — Training and Soft Launch: Before Going Live

A new menu the team has not cooked together is not ready for guests. The sequence:

1. Full-brigade technique demonstration — every dish, with mise-en-place walkthrough, tasting and timing — before any guest sees the menu.
2. Front-of-house briefing — every team member describing the menu needs to know allergens, modifications policy, and the two or three dishes to push.
3. Soft launch — limited covers, controlled service, full post-service debrief.
4. Adjust and lock — fix what the soft launch exposed; lock the standardised recipes.

6b. The Delivery Architecture Test — Five Questions Before Putting a Dish Online

A dish that works in a dine-in kitchen may fail catastrophically on delivery. Before adding any dish to a Swiggy/Zomato menu, run it through this five-question test:

Question	Failure indicator	Fix
1. Does it hold for 30 minutes without quality loss?	Bread soaks; sauce splits; garnish wilts	Restructure packaging; adjust sauce consistency
2. Does the packaging contain the dish safely?	Biryani steams inside box and goes soggy	Switch container type; reduce sauce ratio
3. Can a Commis make it to spec at delivery pace?	Only the CDP can make it correctly	Simplify the recipe or standardise more tightly
4. Is the food cost % modelled on NET revenue (after commission)?	Calculated on gross menu price	Recalculate: 25% Swiggy commission on ₹400 = ₹300 effective revenue
5. Does the name communicate the dish without a server’s explanation?	Guests do not know what they ordered	Rename with clear descriptor

★ The delivery channel and the dine-in channel are different restaurants using the same kitchen. They deserve separate menus, separate costing, and separate quality standards. A kitchen that runs one menu for both will compromise on delivery quality or overprice dine-in.

The Standardised Recipe Format — Every Field a Professional Needs

A standardised recipe is not a home cook’s recipe card. Here is the complete professional template with every required field:

Field	What it contains	Why it matters
Dish name	Exact menu name; no abbreviations	What the Commis calls it; what the server describes it as
Category	Section (hot, cold, starter, main)	Station assignment
Yield	Number of portions + total weight	Tells the Commis how many to prep
Portion size	Exact grams per component	Portion control starts here
Prep time	Minutes; active only	Station scheduling
Cook time	Minutes; total time on heat	Service timing
Mise en place list	Every ingredient prepped before service	The pre-service checklist
Ingredient list	Quantity in grams; AP weight; EP weight; supplier name	Costing and consistency
Method	Step by step; numbered; temperature at every stage	Executable by a Commis
Critical control points	Temperature, time, hygiene checkpoints	Food safety compliance
Food cost per portion	₹ calculated on EP weight	Daily food cost management
Selling price	₹	Factor method or management-set
Food cost %	FC ÷ price × 100	Management visibility
Plating spec	Plate type, sauce quantity (ml), garnish description	Visual consistency
Photo reference	Photograph of a correctly plated portion	What the pass checks against
Allergens	Which of the 14 FSSAI allergen categories are present	Legal compliance
Date created + version	Version 1, V2 etc. with date	Tracks recipe changes

The Tasting Panel Process — How to Run a Professional Menu Trial

Before any dish goes on a live menu, it should pass through a structured tasting process:

Stage	Who is present	What is evaluated
Kitchen team tasting	Chef, Sous Chef, section CDPs	Technique correctness; execution feasibility on the line
Food cost validation	Chef + cost controller	Does the dish hit the target FC%?
Internal management tasting	GM, F&B Manager, Marketing	Price point; positioning; menu description
Soft launch (2–3 table specials)	Live service, selected tables	Service flow; real guest response; timing
Full menu addition	Entire team	Only after all above stages pass

★ A dish that passes kitchen tasting but fails at internal management tasting has a positioning problem, not a cooking problem. A dish that passes all tastings but fails at soft launch has a service or timing problem. Running all five stages before a full menu addition is the professional standard — skipping stages is how restaurants end up pulling dishes after two weeks.

Seasonal Menu Rotation Calendar — Four Changes Per Year

A professional kitchen running seasonal menus needs a structured calendar:

Season	Menu change date	Lead time required	Key ingredient changes
Summer menu	March 15	6 weeks before (Feb 1)	Raw mango, watermelon, tender coconut, fresh peas out; kaidat and summer squash in
Monsoon menu	June 15	6 weeks before (May 1)	Ilish and coastal fish in season; corn; jamun; fresh turmeric
Winter menu	October 15	6 weeks before (Sept 1)	Sarson, methi, gajar, gobi, makki — all in; nolen gur in late November
Festival specials	Ongoing	4 weeks before each festival	Navratri (no-allium), Diwali (mithai), Christmas (Western hybrid), Holi (thandai)

★ The 6-week lead time is the minimum for a menu change done correctly: 2 weeks for recipe development and testing, 1 week for cost and pricing approval, 1 week for supplier lead time, 1 week for team training, and 1 week buffer. A menu change launched with 2 weeks lead time produces half-tested dishes, unprepared staff, and a food cost that will be wrong for the first month.

7. Frequently Asked Questions — Menu Development for Professional Chefs

What is menu development in a restaurant?

Menu development is the structured six-step process of converting a restaurant concept into a set of dishes that are financially viable, operationally executable, and consistently reproducible. It runs from concept and constraints through dish development, yield costing, capacity testing, standardised recipe writing, and team training. The deliverable is a complete set of standardised recipes — not a menu card or a chef’s ideas document.

What is the first step in developing a restaurant menu?

Defining the concept and constraints — the cuisine format, the guest profile, the kitchen’s actual capacity in terms of equipment and brigade size, and the food cost target. Developing dishes before defining these constraints means reworking half the menu when the real constraints surface in week four or five of the development process.

What is a standardised recipe in a professional kitchen?

A standardised recipe contains ingredient quantities by weight in grams (never cups or approximate measures), step-by-step method with timing and temperatures, yield after cooking, portion specification, critical control points for food safety, plating notes, allergen flags, and the dish cost calculated at the time of writing. It is written precisely enough that any trained chef produces an identical result every service, without the Head Chef present.

How does a chef cost a new menu dish correctly?

By costing every ingredient at its effective cost per kilogram after trim and yield loss — not at the raw purchase price. Protein dishes in particular lose 10–20% to trim before cooking. The yield-adjusted ingredient cost, plus a Q-factor of ₹5–20 per cover for oil, salt, condiments and accompaniments, gives the total dish cost. That divided by the target menu price gives the food cost percentage.

What makes a restaurant menu operationally executable?

Shared base preparations that multiple dishes draw from rather than isolated prep per dish; station balance so no one section carries more than 40% of the menu; dishes with ticket times under 12 minutes on a busy pass; and a full set of standardised recipes that any trained Commis can execute. The capacity test identifies which of these conditions are not met before launch.

How long does menu development take?

For a full restaurant launch, six to ten weeks is a realistic professional timeline — allowing for concept definition, dish development trials, yield costing, capacity testing, recipe documentation, and team training. Anything significantly shorter usually means skipping either the capacity test or the standardised recipe documentation, both of which create problems on the floor within the first month.

8. Conclusion

Menu development is not a creative exercise — it is a six-step discipline that ends with standardised recipes the brigade can execute every service without supervision. The creative work is real, but it is the front end of the process. The capacity test and the standardised recipe are the outputs that actually protect the kitchen.

Do these five things before finalising any new menu: (1) Write the concept and constraints document before touching a pan. (2) Design the shared base preparations first — dishes follow from them. (3) Cost every dish on yield-adjusted ingredient rates, not purchase price — run the worked example above for each protein dish. (4) Run a timed mock service with the full brigade before soft launch. (5) Write every dish as a complete standardised recipe — version-numbered and date-stamped — before the menu goes live.

To cost your new menu dishes on real yield and model food cost percentages against your target, use the [ChefAnandhub Recipe Cost Calculator](/calculators/).