Your sous chef is leaving and taking all his knowledge with him. The specials that sell out every evening only exist in his head. Suddenly you're left with a gap in your menu and no idea how those dishes were actually made. This is one of the most expensive mistakes you can make as a restaurant owner.
Why this is so dangerous
If important recipes only exist in someone's head, you're vulnerable. Not just to them leaving, but also to illness, vacation, or simple forgetfulness. A recipe that generates €2,000 per week disappears in one fell swoop from your offerings.
⚠️ Heads up:
Many business owners underestimate how much knowledge disappears when an experienced chef leaves. It's not just about recipes, but also techniques, timing, and quality control.
The hidden costs of knowledge loss
What does it really cost if recipes disappear?
💡 Example:
Your sous chef makes a special that sells 40 times per week for €24.00:
- Revenue per week: 40 × €24.00 = €960
- Revenue per year: €960 × 52 = €49,920
- At 30% margin: €14,976 profit per year
If this recipe disappears, you lose almost €15,000 in profit.
How to prevent this
The solution is simple: document everything before it's too late. But do it systematically so others can use it too.
- Recipes with exact quantities: Not "a pinch of salt", but "5 grams sea salt"
- Cost calculation per recipe: So you know what each dish generates
- Preparation techniques: Temperatures, times, sequence
- Presentation: How should the plate look?
The best way to document recipes
A notebook gets lost. An Excel file on one computer is also vulnerable. You need a system that:
- Is accessible to everyone
- Automatically calculates food costs
- Applies updates to all dishes
- Can't get lost
💡 Example: Digital recipe database
With an app like KitchenNmbrs you document recipes including:
- Exact ingredients and quantities
- Automatic food cost calculation
- Food cost percentage per dish
- Access for your entire team
If ingredient prices rise, you immediately see the impact on all your dishes.
What to do if the damage has already happened
Your sous chef is already gone and you don't have the recipes? Then you need to limit the damage quickly:
- Try to reconstruct the recipe: Ask other cooks to help
- Test different versions: Have guests taste and give feedback
- Document immediately: Once you have the recipe, record it
- Learn from this mistake: Make sure it never happens again
⚠️ Heads up:
Reconstructing a recipe takes time and money. You lose revenue while the dish isn't on the menu, and the first versions are often not perfect.
Recipes as business capital
Good recipes are just as valuable as your kitchen equipment. They generate revenue, have value, and can be stolen or lost. Treat them that way.
💡 Example: Value of a recipe database
A restaurant with 20 dishes that average €2,000 per year in revenue:
- Total annual revenue from recipes: €40,000
- At 30% margin: €12,000 profit
- Value of your recipe database: €12,000+
Would you leave €12,000 worth of equipment unprotected?
How do you build a recipe database? (step by step)
Inventory all existing recipes
Go through all your dishes with your chef and sous chef. Note not just ingredients, but also techniques, temperatures, and presentation. Start with your best-selling dishes.
Calculate the exact food cost per recipe
Add up all ingredients, including oil, spices, and garnish. Calculate your food cost percentage. This gives you immediate insight into which dishes are most profitable.
Choose a digital system for storage
Use an app or cloud system that your team can access. Make sure recipes automatically calculate food costs and that you can apply updates to all dishes at once.
✨ Pro tip
Don't just document recipes, but also the stories behind them. Why is this dish popular? Which seasons does it perform best? That context helps your team understand and sell the dish better.
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 do I prevent my chef from keeping recipes to himself?
Make documenting recipes part of the job. Include in the contract that recipes are the property of the restaurant. Reward staff for helping with documentation.
Do I need to document all recipes or just the important ones?
Start with your 5 best-selling dishes and your specials. That delivers the most value. Then you can expand to the rest of your menu.
What if my chef says cooking can't be documented?
Every successful kitchen works with standards. Explain that documentation helps with consistency and quality. It makes the kitchen more professional, not less creative.
How often should I update recipes?
Check at least every 3 months whether ingredient prices are still accurate. For seasonal dishes or when suppliers change prices, you need to update immediately.
Can I just save recipes in a Word document?
You can, but then you have to calculate food costs manually and apply updates yourself. A digital system that calculates automatically saves a lot of time and prevents errors.
📚 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 →