Picture this: your chef creates an amazing new dish that becomes a hit with customers, but three weeks later it tastes completely different and costs twice what you budgeted. This scenario plays out in restaurants everywhere because they lack documented recipe testing procedures. Structured approval protocols prevent these costly surprises and ensure menu consistency.
Why documenting testing procedures matters
Creating new recipes feels exciting, but without clear protocols everything falls apart quickly. Your chef develops an incredible dish but forgets to calculate food costs. Or the recipe exists only in their memory, and after three weeks it tastes completely different.
⚠️ Heads up:
Without documented procedures, you'll develop recipes that destroy your profit margins, can't be executed during rush periods, or suddenly taste different after a month because nobody documented the exact preparation method.
Three essential pillars of recipe testing
1. Calculate costs before anything else
Before you start tasting: figure out what the dish can cost maximum. If you're selling it for €24 and your food cost target is 30%, you've got €5.51 for ingredients (€24 ÷ 1.09 × 0.30).
2. Must work during peak service
A dish requiring 20 minutes of prep per portion won't survive when you're pushing 100 covers nightly. Always test new creations during your busiest service periods.
3. Anyone on your team can execute it
If only your head chef can make the dish, you're in trouble. Every new recipe must be executable by your entire kitchen staff.
💡 Example testing workflow:
New truffle pasta with burrata:
- Step 1: Calculate food cost → €6.20 ingredients
- Step 2: Chef creates test portion
- Step 3: Sous chef replicates dish
- Step 4: Test timing during busy service
- Step 5: Document recipe with precise measurements
- Step 6: Owner gives final approval
Result: Dish ready for menu launch
Approval hierarchy and responsibilities
Chef: Develops dish concept, creates initial version, calculates food costs
Sous chef/second cook: Replicates dish using chef's instructions, tests reproducibility
Owner: Final sign-off on taste, food cost and operational feasibility
Service team: Verifies they can describe the dish to guests and identify all allergens
💡 Example approval timeline:
New fish special development:
- Monday: Chef develops recipe
- Tuesday: Sous chef tests reproducibility
- Wednesday: Test during service (5 portions)
- Thursday: Process feedback, refine recipe
- Friday: Owner final approval
- Saturday: Goes live on menu
Total development time: 1 week from concept to customer
Essential documentation for every new recipe
- Precise ingredient list with quantities per portion
- Food cost breakdown using current purchase prices
- Preparation timing (prep + à la minute)
- Allergen information (all 14 EU-required)
- Portion size and plating instructions
- Shelf life for prep components and finished dish
- Seasonal availability of key ingredients
Digital systems vs. handwritten notebooks
Most kitchens still rely on handwritten recipes in notebooks. It works, but creates problems. A pattern we see repeatedly in restaurant financials is food cost creep from recipes that drift over time because they're poorly documented.
Digital recipe management (using tools like KitchenNmbrs) offers clear advantages:
- Everyone accesses recipes on their phone instantly
- Food costs update automatically when supplier prices change
- Allergen information displays automatically
- Recipes never get lost or damaged
⚠️ Heads up:
Digital systems only work if your entire team actually uses them. Ensure everyone knows how to access and update recipes properly.
Recipe review schedule
New recipes are never perfect immediately. Schedule regular evaluation points:
- After 1 week: Is kitchen execution smooth?
- After 1 month: Are food costs still accurate? Customer satisfaction good?
- Each season: Are ingredients still available and reasonably priced?
- Upon customer complaints: Evaluate and adjust immediately
💡 Example review outcome:
Mushroom risotto after 1 month:
- Food cost jumped from €4.20 to €5.10 (premium mushroom prices)
- Prep time longer than expected (18 min vs 12 min)
- Customers frequently request extra parmesan
Action: Modify recipe or increase menu price to €26
How do you build a testing and approval procedure?
Determine your food cost budget
First calculate what the dish can cost at most. Take your desired selling price, subtract VAT, and multiply by your food cost percentage. For example: €28 menu price becomes €25.69 excl. VAT, at 30% food cost you can spend €7.71 on ingredients.
Make a test version and document everything
Have your chef develop the dish and immediately document: exact quantities, preparation time, allergens, and food cost. Test whether another team member can recreate it based on this documentation.
Test during real service
Make the dish during a busy evening for real guests. Check if it's feasible timing-wise, if you can keep all ingredients in stock, and if guests are satisfied. Adjust where needed.
✨ Pro tip
Establish a 72-hour rule: new recipes must be successfully executed by at least two different kitchen staff members within 72 hours before menu approval. This prevents dishes that only work in your chef's hands from reaching customers.
Calculate this yourself?
In the KitchenNmbrs app you can do this in just a few clicks. 7 days free, no credit card.
Was this article helpful?
Frequently asked questions
How often should I evaluate new recipes?
Review after 1 week (smooth kitchen execution?), after 1 month (accurate food costs and customer satisfaction?), and each season (ingredient availability?). Address customer complaints immediately with recipe evaluation.
Who should approve new recipes in my restaurant?
Chef develops and costs the dish, sous chef tests reproducibility, owner provides final approval on profitability and feasibility. Service team verifies they can explain the dish and identify allergens to guests.
What if a new dish becomes too expensive after launch?
You have three options: substitute cheaper ingredients, reduce portion sizes, or increase the selling price. Sometimes it's better to remove the dish entirely rather than hurt your profit margins.
How do I prevent recipes from getting lost or forgotten?
Document everything digitally in a centralized system everyone can access. Paper recipes get lost, damaged, or become illegible over time. Always maintain backups of your digital recipe database.
Should every kitchen team member be able to make new recipes?
Absolutely - if only your head chef can execute a dish, you're vulnerable when they're absent. Always test whether other kitchen staff can reproduce dishes using your documentation before menu launch.
How long should recipe testing take before menu launch?
Allow 5-7 days minimum for proper testing cycles. This includes initial development, reproducibility testing, busy service trials, and final approval rounds. Rushing leads to expensive mistakes during service.
📚 Sources consulted
- EU Verordening 852/2004 — Levensmiddelenhygiëne (2004) — Official source
- EU Verordening 853/2004 — Hygiënevoorschriften voor levensmiddelen van dierlijke oorsprong (2004) — Official source
- EU Verordening 1169/2011 — Voedselinformatie aan consumenten (2011) — Official source
- NVWA — Hygiënecode voor de horeca (2024) — Official source
- NVWA — Allergenen in voedsel (2024) — Official source
- Codex Alimentarius — International Food Standards (2024) — Official source
- FSA — Safer food, better business (HACCP) (2024) — Official source
- BVL — Lebensmittelhygiene (HACCP) (2024) — Official source
- Warenwetbesluit Bereiding en behandeling van levensmiddelen (2024) — Official source
- WHO — Foodborne diseases estimates (2024) — Official source
Food Standards Agency (FSA) — https://www.food.gov.uk
The HACCP standards shown in this application are for informational purposes only. KitchenNmbrs does not guarantee that displayed values are current or complete. Always consult the FSA or your local authority for the latest regulations.
Written by
Jeffrey Smit
Founder & CEO of KitchenNmbrs
Jeffrey Smit built KitchenNmbrs from 8 years of hands-on experience as kitchen manager at 1NUL8 Group in Rotterdam. His mission: give every restaurant owner control over food cost.
All your recipes in one place, forever
Recipes in heads, on notes, in folders — that doesn't work. KitchenNmbrs centralizes all your recipes with costs, allergens, and portions. Try it free for 14 days.
Start free trial →