Most restaurant owners scramble to solve problems after they've already hit. Your head chef quits without notice, energy costs spike overnight, or your main supplier suddenly shuts down. But what if you could respond to these crises in hours instead of weeks?
Why scenario planning matters for your bottom line
Your restaurant's humming along perfectly. Staff's solid, suppliers reliable, customers happy. Then boom - your sous chef takes a job across town, your produce guy jacks up prices 30%, or another lockdown hits. Without preparation, each crisis costs you weeks of lost revenue and frantic problem-solving.
⚠️ Note:
Scenario planning isn't about being pessimistic. It's about staying ready, not constantly stressed. You map out possible situations so you can act fast if they occur.
The weekly framework: 3 scenarios in 15 minutes
Keep it simple. Every week, run through three scenarios with your team:
- Operational scenario: What happens if your line cook calls out?
- Financial scenario: What if your food costs jump 20%?
- External scenario: What if the market shifts around you?
💡 Example scenario discussion:
Monday morning, 15 minutes:
- What if our pastry chef gets food poisoning on Saturday?
- What if chicken prices rise 40% next month?
- What if that new gastropub opens two blocks away?
For each: what's our move? Who handles what? How fast can we pivot?
Turn scenarios into actionable responses
Talking through problems isn't enough. You need concrete steps ready to execute. For every scenario, build a quick response plan:
- Who owns the response?
- What are your first 3 moves?
- When do you need to act?
- What resources do you need on standby?
💡 Example action plan:
Scenario: Primary supplier stops delivering immediately
- Who: Manager calls 3 backup suppliers within 1 hour
- Step 1: Audit current inventory - how many service days remain?
- Step 2: Contact backup suppliers (contact sheet posted in office)
- Step 3: Modify menu offerings for next 48 hours if needed
Timeline: Execute within 2 hours of notification
Financial scenarios require real numbers
Something most kitchen managers discover too late: financial scenarios need actual calculations, not rough guesses. How much will it really cost? Where's the money coming from? Can you adjust pricing without losing customers?
- Energy costs jump 50%: What's your monthly hit?
- Minimum wage increases: How much extra annually?
- Key ingredient rises 25%: Which dishes lose profitability?
A food cost calculator helps you quickly model what price increases mean for your margins and which menu changes make sense.
💡 Example calculation:
Salmon jumps from €28/kg to €35/kg (+25%)
- Salmon dish (180g): €1.26 extra per plate
- Weekly sales: 35 salmon dishes
- Added costs: €44/week = €2,288/year
Response: Bump menu price from €29 to €32, or swap to 160g portions
Get your team thinking like problem-solvers
Scenario planning flops if your team just nods along. They spot risks you miss. Your prep cook knows which distributor delivers fastest. Your server hears customer complaints about portion sizes first.
- Ask for their input: what problems do they see coming?
- Let them brainstorm solutions
- Assign everyone roles in your response plans
- Run practice drills occasionally (what if the head chef's out sick?)
Document everything and keep it current
Write your action plans down. Don't file them away - post them where everyone can see or store them in your team app. Update monthly:
- Are contact numbers still working?
- Do the costs and quantities match reality?
- What new scenarios should you add?
- Which scenarios actually played out? What did you learn?
⚠️ Note:
Scenario planning dies without consistency. Discussing it once then forgetting won't help you. Make it a weekly habit, especially during good times.
Build momentum gradually
Begin with scenarios that could happen tomorrow. What's likely to go sideways this week? Next month? As your team gets comfortable, layer in more complex situations.
You're not trying to plan for everything - you're training your team to adapt faster when the unexpected hits.
How do you make scenario planning part of your weekly routine?
Schedule a fixed time
Choose a fixed time each week, for example Monday morning at 10:00. Put it in your calendar as a recurring appointment. Keep it short: maximum 15 minutes.
Determine 3 scenarios per week
Choose 3 different scenarios each week: one operational (staff, equipment), one financial (costs, revenue) and one external (competition, regulations). Alternate between likely and unlikely events.
Create concrete action plans
For each scenario, determine: who takes the lead, what are the first 3 steps, how quickly do you need to act, and what do you need. Write this down and make sure everyone knows where to find it.
Actively involve your team
Let team members bring up scenarios and think along about solutions. They often see risks you miss. Give everyone a role in the action plans so they know what's expected of them.
Update and evaluate monthly
Check every month whether your action plans still hold up. Are contact details current? Are the amounts still correct? What new scenarios have become relevant? Learn from scenarios that actually happened.
✨ Pro tip
Every Tuesday morning, spend exactly 12 minutes walking through one 'what-if' scenario with whoever's on shift. Pick scenarios based on what almost went wrong the previous week - this keeps your planning grounded in reality.
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 much time does scenario planning take per week?
Start with 15 minutes weekly for 3 scenarios. Add 30 minutes monthly to update your action plans. You'll save hours when something actually goes wrong.
Which scenarios should I discuss first?
Focus on the most probable ones: key staff calling out, supplier price hikes, equipment failures. Nearly every restaurant faces these. Build complexity from there.
What if my team thinks scenario planning is pointless?
Start with a real example from another restaurant: 'Place downtown had no backup when their chef quit mid-service. How would we handle that?' Make it concrete, not theoretical.
Do I need written plans for every scenario?
For critical scenarios, yes. One page with contacts, steps, and who does what. For minor scenarios, having discussed the approach is enough.
How often do these scenarios actually happen?
More than you'd expect. Staff absences, supplier issues, equipment breakdowns happen regularly. You're not predicting the future - you're preparing to respond faster.
Can I do scenario planning without involving my team?
You can, but it's less effective. Your staff sees risks you don't and offers practical solutions. If you're flying solo, at least bounce ideas off suppliers or other restaurant owners.
What's the biggest mistake restaurants make with scenario planning?
They only do it during crises, then abandon it during good times. The best time to plan scenarios is when you don't need them yet.
📚 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.
Make better decisions with real numbers
Should you change your menu? Raise prices? Test a new concept? KitchenNmbrs simulates scenarios with your own data. Try it free for 14 days.
Start free trial →