Different tools and documents mean your team isn't on the same page. One employee works in Excel, another has their own notes, and nobody knows which information is most current. This leads to mistakes, frustration, and loss of valuable time.
The problem of fragmented information
When everyone uses their own system, chaos ensues. Your chef has his recipes in a notebook, your sous-chef works with Excel, and you're trying to keep track of everything in different apps.
💡 Example:
You have 5 employees who all work differently:
- Chef: handwritten recipes in notebook
- Sous-chef: Excel sheet on personal laptop
- Intern: photos of recipes on phone
- Owner: prices in old Word document
- Part-time cook: asks everything again
Result: nobody knows what's correct
Why teams resist new systems
People stick with what they know. Your chef has worked with his notebook for 10 years and doesn't see why that should change. Change feels like extra work, especially if they think their current way is 'good enough'.
- Habit: Old routines are comfortable
- Time pressure: Learning takes time you don't have
- Tech anxiety: Not everyone is digitally savvy
- No urgency: It seems to work as is
The real cost of different systems
What seems like 'no problem' actually costs you a lot of money. Mistakes, duplicate work, and miscommunication add up.
⚠️ Watch out:
A wrong recipe can cost you €50-100 per day in wasted ingredients. Over 300 working days, that's €15,000-30,000 per year.
Concrete problems in practice
These situations happen daily in kitchens where everyone has their own system:
- Wrong portions: New cook doesn't know how much meat per plate
- Outdated prices: Cost calculation is no longer accurate
- Duplicate orders: Nobody knows what's already been ordered
- Allergens forgotten: Information is in different documents
- Lost recipes: Chef is sick, nobody knows how the dish should be made
💡 Example:
Saturday night, fully booked, your chef gets sick:
- Sous-chef searches for 20 minutes for the risotto recipe
- Finds it, but the portion size isn't listed
- Guesses the amount, makes 30% larger portions
- By end of evening: €180 in extra costs
Per month: €720 loss from one missing recipe
How to get your team on board
Change only works if your team sees the benefit. Start small and show concrete results.
- Start with one thing: For example, just the 5 most popular recipes
- Show what it delivers: Fewer mistakes, less stress
- Give time to adjust: Don't force everything at once
- Celebrate small wins: Acknowledge when someone uses the new system
The advantage of one system
With one central place for all information, most problems disappear on their own. Everyone works with the same, up-to-date data.
An app like KitchenNmbrs ensures all recipes, prices, and procedures are in one place. Your team can look up the right information from any phone or tablet, without searching through different documents.
💡 Example:
After 2 months with one system:
- Recipe errors: 80% fewer
- Time searching for information: from 15 to 2 minutes
- Onboarding new staff: 50% faster
- Cost calculations: always current
Result: more time, less stress, better margins
How do you get your team to move to one system?
Start with the biggest pain points
Identify what frustrates your team the most. Often it's searching for recipes or getting ingredient quantities wrong. Start there.
Let one person lead by example
Choose someone who's open to change. Let them use the new system and experience the benefits. Others will naturally see what it delivers.
Make the transition gradual
Don't stop using old systems abruptly. Let both exist side by side for a while, so people can adjust without stress.
Train during quiet moments
Explain new workflows when it's not busy. During lunch break or before service starts, not during the evening rush.
Measure and celebrate results
Keep track of how much time you save and how many mistakes you prevent. Share this with your team so they see the change really works.
✨ Pro tip
Start with one recipe that often goes wrong due to unclear instructions. When your team sees this problem disappear, they'll naturally want to digitize more recipes.
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
What if my chef refuses to work digitally?
Start with small steps. Let them keep their notebook, but make sure someone else also records the recipes digitally. After a while, they'll naturally see the benefits.
How long does it take for everyone to use the new system?
Plan on 2-3 months for full adoption. The first few weeks people use both systems, then they increasingly choose the new system because it's easier.
What if we're too busy to train everyone?
Train one person per week, during quiet moments. That person can then help others. This way knowledge spreads gradually without disrupting service.
Do we need to transfer all old information to the new system?
Start with your 10 most popular dishes. You can add the rest gradually as you need them. Getting started is more important than perfection.
What if the new system goes down during service?
Keep your old backups handy for the first month. Most digital systems are more reliable than paper documents, but having a safety net gives peace of mind.
📚 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.
Discover what KitchenNmbrs can do for you
From recipe calculation to allergen registration, from inventory management to menu engineering. One platform for complete control of your kitchen. Try it free for 14 days.
Start free trial →