Picture this: your head chef calls in sick during your busiest weekend, and nobody can replicate his signature sauce because all the measurements are scribbled in his personal notebook at home. Employees clinging to their own notebooks create serious vulnerabilities for your operation. You need everyone working from one shared system.
Why employees stick to their own system
Most chefs have been scribbling notes for years. It feels personal and familiar. They assume it's quicker than logging into an app or updating a digital system. But this illusion of control drains your business of money and institutional knowledge.
⚠️ Watch out:
A notebook gets misplaced, stays home in a jacket pocket, or walks out the door with a departing employee. Your operational knowledge shouldn't be anyone's private property.
The real cost of notebooks
What happens if your sous chef quits and takes his notebook?
- Recipes vanish - you're back to guessing measurements
- Portions become inconsistent - food costs balloon
- New hires make costly mistakes - customers taste the difference
- You're retraining from scratch - burning time and payroll
💡 Example:
Your sous chef carries 15 years of recipes in his head. He quits suddenly:
- 2 weeks recreating lost recipes
- €500 wasted on failed test batches
- 3 customer complaints about taste changes
- 20 hours training replacement chef
Total damage: €2000+ plus reputation hits
Making the transition without conflict
Forcing compliance backfires. Staff will just use their notebooks secretly. You need gradual change built on respect.
Week 1-2: Enter data together
Stand beside your chef during prep and input recipes together into the system. Don't frame this as mandatory training - make it collaborative. Say: "Help me document this for the team." Position it as partnership.
Week 3-4: Let them control input
Ask: "Could you add this recipe to the system? That way everyone can access it." Hand them control over data entry. They'll feel ownership over the information.
💡 Example:
Chef Michel clutches his notebook. Your approach:
- Day 1: "Michel, walk me through your carbonara recipe"
- Day 3: "Mind adding that new salad recipe too?"
- Week 2: "Could you verify this recipe looks right in the system?"
- Week 3: Michel inputs recipes independently
Result: Full buy-in without confrontation
Make the system more attractive than the notebook
Your digital system must deliver advantages notebooks can't match:
- Automatic cost calculation - no more manual arithmetic
- Always accessible - even from home or other locations
- Nothing disappears - everything backed up in the cloud
- Team sharing - everyone follows identical recipes
Demonstrate capabilities their notebook lacks. For instance: "See how the system recalculates your food cost automatically if salmon prices jump?"
Be consistent without being heavy-handed
Establish clear expectations, but explain the reasoning:
- "All recipes go in the system for consistency"
- "New dishes get documented digitally before cooking"
- "Recipe changes happen through the system, not on paper"
⚠️ Watch out:
Model the behavior yourself. If you're still managing purchasing through Excel, you can't expect your team to embrace the recipe system.
What if someone refuses to cooperate
Some employees will dig in their heels. That's the kind of thing you only learn after closing your first month at a loss - you can't let individual preferences hold your operation hostage. Then you must clarify consequences:
- Explain that operational knowledge belongs to the business
- Clarify this isn't personal criticism
- Provide reasonable transition timeline
- If resistance continues: reassign duties or part ways
It sounds harsh, but employees who hoard critical knowledge create unacceptable risk.
💡 Example:
Conversation with resistant employee:
- "I really value your expertise and recipes"
- "For operational continuity they need digital documentation"
- "I'll support you through this transition - perfection isn't expected"
- "In 2 weeks I need your core recipes in the system"
Emphasize: partnership, not forced compliance
Maintaining the system
Once everyone's on board, keep the system current:
- Weekly check: are new recipes being added?
- Monthly review: do prices reflect current costs?
- Real-time updates: changes get entered immediately
- New hires: start with the system from day one
Tools like KitchenNmbrs let you manage recipes centrally so everyone accesses the latest version. This prevents staff from reverting to personal notes.
How do you get employees on board with the system? (step by step)
Start by entering data together
Stand next to your chef while he's cooking and enter the recipe together in the system. Don't make it a training, but a collaboration. Say: 'Help me out, I want to record this for the business.'
Give them control
Ask after a week if they want to enter recipes themselves. Say: 'Can you enter this recipe in the system? That way we'll have it available for everyone.' They'll feel like they own the information.
Show the benefits
Show what the system can do that a notebook can't: automatic cost calculation, always available, nothing gets lost. For example: 'Look, when salmon gets more expensive, the system automatically adjusts your food cost.'
Set clear rules
Make agreements: all recipes in the system, new dishes entered first then cooked, changes only through the system. Explain why this matters for consistency and business continuity.
✨ Pro tip
Give your most resistant chef exactly 3 weeks to digitize their top 8 recipes, then check progress every Friday afternoon. The weekly accountability creates urgency without daily micromanagement.
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 says the system is too slow?
Sit down together and time the actual process. Often people imagine more complexity than exists. Entering one recipe takes 5 minutes but saves hours explaining procedures to new staff.
Can I force employees to hand in their notebook?
That approach backfires spectacularly and breeds resentment. Let them keep their notebooks while establishing the system as the official source. After a few weeks they'll abandon their notebooks naturally.
How do I prevent people from falling back on old habits?
Keep the system accessible (tablet in the kitchen) and update it consistently. Once people see the digital version is more current than their handwritten notes, they'll switch automatically.
What if an employee refuses to cooperate?
Explain that operational knowledge belongs to the business, not individuals. Provide a reasonable timeline (2-3 weeks) with transition support. If they continue resisting, consider reassignment or termination.
⚠️ EU Regulation 1169/2011 — Allergen Information — https://eur-lex.europa.eu/eli/reg/2011/1169/oj
The allergen information on this page is based on EU Regulation 1169/2011. Recipes and ingredients may vary by supplier. Always verify current allergen information with your supplier and communicate this correctly to your guests. KitchenNmbrs is not liable for allergic reactions.
In the UK, the FSA enforces allergen regulations under the Food Information Regulations 2014.
📚 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.
Give your team insight into the numbers
When your team understands what dishes cost, their behavior changes. KitchenNmbrs makes food cost visible to everyone in the kitchen. Start your free trial.
Start free trial →