Picture this: you've got stunning reports packed with charts and percentages, but your team stares at them like they're written in ancient hieroglyphics. Numbers only create value when your people understand and act on them. Most staff won't take action based on financial data they can't decode, and that's where profit opportunities slip away.
Why reports often don't work
Most POS systems and accounting software generate complex overviews stuffed with percentages, ratios and financial jargon. For a chef or server without financial training, it's completely meaningless.
⚠️ Watch out:
When your team can't interpret the numbers, they'll default to gut feeling and old habits - and that's exactly where money bleeds out.
Translate financial terms into kitchen language
Swap 'food cost percentage' for 'how much of every euro goes to ingredients'. Replace 'gross margin' with 'what we keep after buying food'.
💡 Example:
Confusing report: 'Food cost Q3: 34.2% (target: 30%)'
Clear report: 'Out of every €10 we earn, €3.42 goes to ingredients. We're spending €0.42 too much.'
The second version clicks instantly.
Focus on action, not on numbers
Every report must spell out what needs to happen next. Don't just describe the situation - outline the solution.
- Wrong: 'Carbonara has 38% food cost'
- Right: 'Carbonara costs us too much. Solution: reduce portions or bump price from €16 to €18'
- Even better: 'Carbonara: drop from 250g to 220g pasta = save €0.80 per plate'
Use comparisons everyone understands
Frame numbers using familiar references: covers served, days of revenue, or actual euro amounts. This is a pattern we see repeatedly in restaurant financials - abstract percentages confuse people, but concrete comparisons motivate action.
💡 Example:
Instead of: 'Waste 2.3% of purchases'
Try: 'This week €127 worth of food got tossed. That's like cooking 8 meals for free.'
Now the impact hits home.
Make it visual and simple
Fancy charts look impressive, but a basic table with 3 columns often delivers better results: What, Why, Action.
- What: Steak food cost too high
- Why: Meat price increased, menu price stayed same
- Action: Increase price from €28 to €32 or source different supplier
Timing: when do you discuss numbers
Share financial data when your team can actually focus on it. Skip the dinner rush - use staff briefings or weekly meetings instead.
⚠️ Watch out:
Don't overwhelm your team with data dumps. Choose 1-2 crucial points each week and explain them thoroughly. Two things everyone grasps beats ten things nobody remembers.
Involve your team in solutions
Once your chef grasps that the steak is eating profits, ask: 'How do we fix this?' He might suggest different cuts, suppliers or preparation methods.
💡 Example:
Situation: Salad food cost 42% (way too high)
Ask your team: 'How do we cut costs on this salad without sacrificing quality?'
Possible solutions:
- Switch to cheaper nuts, add more vegetables
- Use seasonal produce
- Reduce portion slightly, serve extra bread
This creates collaboration instead of top-down mandates.
How do you make reports understandable? (step by step)
Translate jargon into plain language
Replace 'food cost 35%' with 'out of every €10 revenue, €3.50 goes to ingredients'. Use concrete amounts of money instead of percentages where possible.
Add context and action
Don't just say what is, but also why it matters and what the next step is. For example: 'Food cost too high → Plan: raise price or reduce portion'.
Discuss at the right time
Schedule 15 minutes weekly to discuss numbers during a quiet moment. Focus on 1-2 important points and ask for input from your team.
✨ Pro tip
Create visual cost breakdowns using actual kitchen portions - show your team that out of every €10 plate, €3.20 covers ingredients by physically separating that amount in cash. Do this monthly for your top 3 dishes.
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 discuss numbers with my team?
Weekly works well for most restaurants. Pick a calm moment and focus on 1-2 key issues. Quality beats quantity - better to explain a few things clearly than confuse everyone with information overload.
What if my chef shows zero interest in numbers?
Connect the data to his daily work. Show how food costs impact his kitchen budget and ingredient quality, then ask for his input on solutions. Make him part of the decision-making process.
Should I share all financial details with staff?
No, only share what's relevant to their specific roles. A chef needs to understand dish profitability, but doesn't need access to your complete P&L statement.
How do I explain why we need to remove certain dishes?
Show the revenue difference and present alternatives. For example: 'This pasta generates €3 profit per plate, while that one makes €7. Which one should we promote more heavily?' Let them see the logic behind menu decisions.
📚 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 →