Most kitchen teams panic over food cost variances, but smart managers see opportunity. While others point fingers and assign blame, successful chefs turn these moments into powerful team learning sessions. The difference transforms your kitchen culture completely.
Why food cost variances are educational
A variance in your food cost means something went differently than planned. That could be purchasing, preparation, portioning, or waste. Instead of assigning blame, you can help your team understand why the numbers matter.
💡 Example:
Your carbonara had 28% food cost last week, this week 35%. The team discovers together:
- Bacon got more expensive (supplier)
- Portions were larger (chef gave more)
- Parmesan was wasted (stored incorrectly)
Result: 3 concrete improvement points without blame
Make it discussable without guilt
Never start with "who did this?". Start with "what can we learn from this?". That way your team becomes curious instead of defensive.
- Show the numbers without judgment
- Ask the team to think along about causes
- Focus on solutions, not mistakes
- Compliment good suggestions right away
⚠️ Heads up:
Always discuss variances within 24 hours. Later, nobody remembers exactly what happened.
Concrete approach per type of variance
With higher ingredient costs:
- Check the purchasing prices from that week together
- Compare with last month
- Discuss if you should try other suppliers
With portions that are too large:
- Measure the standard portion together again
- Let everyone portion once
- Make agreements about scoop sizes
💡 Example team discussion:
"Our steak cost €2 more per portion this week. Why do you think that is?"
- Team discovers: meat was more expensive + portions were 50 grams heavier
- Solution: check new supplier + use portion scale
- Agreement: we'll measure again next week
Make it visual and understandable
Not everyone on your team loves numbers. Make it concrete by showing what a variance means. This is the kind of thing you only learn after closing your first month at a loss – numbers mean nothing until you translate them into real consequences.
- "5% higher food cost = €200 less profit this month"
- "20 grams extra pasta per plate = 1 extra bag per day"
- "This waste costs us €50 per week"
Celebrate improvements
When your team has solved a variance, acknowledge it. Positive feedback makes sure they'll think along faster next time.
💡 Example:
"Last week we had 35% food cost on the carbonara, this week 29%. Great job team!"
This motivates more than just discussing problems.
Build it into your routine
Make food cost discussion part of your weekly team meeting. Not as punishment, but as a normal part of your work.
- Every Monday: food cost of top dishes from last week
- With variance: find cause together
- Make agreements for the coming week
- Next week: discuss results
Modern food cost tracking systems let you see right away where variances are happening, so you have concrete talking points for your team meeting.
How do you turn a variance into a learning moment? (step by step)
Show the numbers without judgment
Show last week's food cost next to this week's. Say: "Here we see a difference, what do you think the cause might be?" That way you make your team curious instead of defensive.
Brainstorm together about possible causes
Let the team think along: more expensive purchasing, larger portions, more waste, different preparation? Write down all ideas without judging them. Often the team knows exactly what went differently.
Choose one concrete action together
Address the most likely cause. Make a clear agreement: "This week we'll pay extra attention to portion size" or "We'll check the new supplier". Discuss the result next week.
✨ Pro tip
Track your team's variance-solving wins for 30 days and celebrate the biggest catch publicly. Nothing motivates cost awareness like recognition from their peers.
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 team isn't interested in food costs?
Make it concrete: "5% higher food cost means €200 less for kitchen improvements this month". Show how it affects their work, then it becomes relevant.
How often should I discuss food cost variances?
Weekly short sessions work better than monthly marathons. With big variances, discuss right away – otherwise everyone forgets what happened that shift.
What if the variance is due to my own decision?
Be honest: "I bought more expensive meat this week, that's why our food cost is higher". Your team appreciates transparency and learns why choices have consequences.
Should I discuss individual mistakes with the whole team?
No, discuss individual mistakes privately. Team meetings are for patterns and systems that affect everyone, not for personal feedback.
How do I prevent the team from seeing food costs as their problem?
Position it as "our shared goal". Say: "If we solve this together, we can invest in better equipment" instead of "you're making mistakes".
What if the same variance keeps happening despite discussions?
Time for hands-on training, not just talking. Shadow that station for 3 shifts and identify the real blockers preventing change.
📚 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.
Automate your daily kitchen controls
Manual controls take time and miss errors. KitchenNmbrs automates temperature logging, inventory management, and HACCP checks. Try it free for 14 days.
Start free trial →