Guide to standardizing recipes in restaurants

A creamy risotto on Monday, salty on Tuesday, and a small portion on Wednesday is not read as “menu variation.” The customer reads it as inconsistency — and decides whether to return. How to standardize a recipe is, in practice, moving away from relying on a person's memory and shifting to a process that any shift can repeat.

This guide is a numbered SOP for restaurants and cafes in Mexico: spec sheet, costing in MXN, testing, training, and cross-branch control.

SOP: how to standardize a recipe (step-by-step)

1. Choose the priority dish
   Start with what sells the most or has the highest margin (e.g., house latte, daily pasta, bowl). Not the “pretty” dish on the menu.

2. Cook and weigh a reference portion
   Use a scale. Write down grams and milliliters. Eliminate “to taste,” “a splash,” and “eyeballing it.”

3. Separate gross vs net weight
   Record purchase weight, clean weight, and actual yield (e.g., onion: you buy 1 kg, you use 820 g net).

4. Write the procedure in numbered steps
   Each step: action + time/temperature + visible cue (“light golden on the edges,” not “until ready”).

5. Define portion size and presentation
   Target plate weight, plating layout, reference photo, and allergens.

6. Calculate cost in MXN and price
   Direct cost + sub-recipe allocation + indirect costs. Set a target food cost (usually around 25–35%).

7. Scale and validate
   Test 1 → 4 → 12 portions. Tolerate ±5% in weight. If texture fails during scaling, adjust the spec sheet (do not improvise during service).

8. Train with a checklist
   Guided reading → supervised practice → surprise audit.

9. Freeze version and communicate
   Version code, date, person in charge. Same spec sheet in kitchen, purchasing, and POS.

10. Audit across locations
    Same recipe, same scale, same photo. Deviations are corrected with training, not with the “style of the shift chef.”

Operational rule: if it cannot be explained with measurements, steps, and visible criteria, it is not yet an operational recipe.

Printable spec sheet (checklist in the body)

Print or post at the station. Check each box before declaring the recipe “ready.”

Header

• Dish / beverage name

• Internal code (e.g., LT-01)

• Category and version (v1.2 — date)

• Declared allergens

• Printed reference photo / QR code to photo

Ingredients

• Complete list in g / ml (no “to taste”)

• Gross and net quantity per item

• Brand / cut / authorized substitute

• Sub-recipes with their own code (sauce, syrup, stock)

Procedure

• Numbered steps

• Time and temperature for critical steps

• Required equipment (scale, pot, steamer…)

• Observable cue for “ready”

Portion and Service

• Target weight of plate / glass

• Plating / finish (foam height, toppings order)

• Shelf life / preservation

• Allowed modifiers (plant milk, double shot…) with cost

Cost and Control

• Updated cost per portion in MXN

• Food cost % vs target

• Person responsible for shift verification

• Station staff training signature

Costing example in MXN (12 oz latte)

• Target food cost: 30%

• Estimated selling price: $19.54 ÷ 0.30 ≈ $65 MXN

• If the menu price is at $59, you either raise the price, reduce waste/portion, or accept a food cost of ~33% focusing on volume.

Seafood pasta (summarized cost in MXN)

Update when shrimp or tomatoes move by more than 5%; otherwise, the “standard” becomes a fiction.

For detail on the calculation, you can cross-reference with how to calculate the cost of a dish.

Consistency across locations (short and strict)

Standardizing a recipe fails if each location “interprets” it.

1. One master spec sheet (version and date). Branch does not edit by hand; proposes change to central kitchen / manager.

2. Same scale and same units at all stations.

3. Photo + weight as pass criteria (not just the shift lead's taste buds).

4. Monthly cross-audit: a cook from location A prepares food at location B using only the spec sheet.

5. Identical modifiers in the POS (names and costs). If Plaza sells “lactose-free milk” and Centro does not have it costed, the margin and the CRM lie.

6. Simple KPI per location: % of preparations within ±5% of weight in audits; actual vs. theoretical waste.

Consistency also drives loyalty: the customer who orders the same latte at two different locations expects the same cup. When the product is repeatable, recurrence campaigns (points, rewards, “your usual”) actually make sense.

3-stage training (not just a PDF during onboarding)

1. Guided reading of the spec sheet and the photo.

2. Supervised practice with recorded corrections (too much sauce, low temperature, weight out of range).

3. Autonomous execution + surprise audit with the 6-point list: weighing, sequence, time, temperature, presentation, log.

Minimum daily checklist:

1. Weighing of key components

2. Correct sequence

3. Cooking / extraction time

4. Temperature

5. Presentation vs. photo

6. Signature / deviation note

From the spec sheet to the POS and CRM

The standardized recipe must talk to the ticket:

• Kitchen/purchasing: ingredients, yield, cost in MXN

• POS: dish, allergens, modifiers

• CRM: what the customer ordered, at which branch, how often

This way you can see if the “usual” of a segment dropped after a recipe change — and correct it before losing recurrence. Swirvle helps centralize consumption habits, locations, and loyalty campaigns once product quality is already repeatable. For order flow, it is also useful to align restaurant order tickets.

Example of numbered procedure (latte)

1. Grind 18 g of coffee (grind adjustment according to extraction sheet).

2. Extract double shot in 25–30 s; discard if it falls out of range.

3. Steam 250 ml of milk to 60–65 °C; microfoam texture.

4. Pour into 12 oz cup; finish according to photo (heart / simple dot).

5. Weigh finished cup: target 340–355 g. Out of range = does not go to the bar.

6. Record deviation on shift sheet if applicable.

That level of detail is what allows you to train four new baristas without “the morning guy doing it differently.”

What NOT to do

• Leave the spec sheet only in the manager's WhatsApp.

• Use euros or another currency in costing if you operate in Mexico — work in MXN.

• Change the recipe in one branch “because the local supplier is different” without a new version.

• Promise fleet automation or other verticals unrelated to the kitchen: here the focus is recipe, cost, and consistency.

To organize the flow during peak hours without breaking standards, review how to organize the bar and kitchen.

30-day plan

Prioritize: no spec sheet → outdated spec sheet → uncosted modifier → training without verification.

Once the recipe is standardized, the next step is turning that consistency into returning customers. Swirvle centralizes customer data, segments habits, and runs loyalty campaigns with clear dashboards — useful for restaurants and cafes that no longer want to leave quality to shift chance.