Every restaurant owner faces the same challenge: making quick, profitable decisions under pressure. Should you raise your steak price? Hire another cook? Switch suppliers? Most operators rely on instinct, but successful restaurants use written decision frameworks they can apply consistently.
Why decision frameworks save money and time
Decision frameworks are step-by-step processes you follow for specific situations. They eliminate guesswork, speed up choices, and keep your responses consistent across similar scenarios.
💡 Example:
Your beef supplier hikes prices 15%. Now what?
- Option 1: Increase menu prices
- Option 2: Reduce portion sizes
- Option 3: Switch to different protein
- Option 4: Remove dish temporarily
A written framework tells you exactly which steps lead to the right choice.
Which scenarios deserve written frameworks?
Target situations that happen frequently and affect your bottom line significantly. Food costs, staffing, and supplier issues offer the biggest returns on your time investment.
- Supplier price jumps: Response plan for 10%+ ingredient cost increases
- Food cost blowouts: Actions for dishes exceeding 35% food cost
- Staffing gaps: Coverage strategies for chef absences or departures
- Seasonal availability: Menu adjustments for out-of-season ingredients
- Underperforming dishes: Criteria for menu removal decisions
⚠️ Note:
Don't document everything. Limit yourself to 5-7 high-impact scenarios. Too many frameworks become overwhelming and unused.
Building frameworks that actually work
Effective frameworks have three components: triggers (what activates them), options (possible responses), and decision criteria (how you choose).
💡 Framework example: Supplier price increases
Trigger: 10%+ price increase on core ingredients
Step 1: Calculate dish's new food cost percentage
Step 2: Get quotes from two alternative suppliers
Step 3: If food cost exceeds 35%: adjust menu price or modify recipe
Decision rule: Select the option that protects gross margin while maintaining quality
This approach represents one of the most common blind spots in kitchen management - operators know they need systems but struggle to identify which decisions warrant formal frameworks.
Storage systems that ensure you'll use them
Store frameworks where you can access them instantly during busy periods. Simple beats sophisticated here - you need quick retrieval under pressure.
- Digital options: Tools like KitchenNmbrs allow dish-specific notes and calculations
- Physical storage: Laminated sheets in your office or expo station
- Mobile access: Phone notes app for decisions made anywhere
The system doesn't matter - consistency does. Frameworks you can't find won't influence your decisions.
Testing and refining your frameworks
Follow your framework exactly the first time you encounter each scenario. Then evaluate: did this produce a good outcome? Adjust based on results.
💡 Evaluation example:
You increased steak price from €32 to €35 due to beef cost increases.
- One-month result: 20% drop in steak orders
- Analysis: Price jump was too aggressive
- Framework revision: For 15%+ cost increases, try portion reduction first
Frameworks evolve through real-world application. They're tools for better decisions, not rigid rules.
How do you create a decision guide? (step by step)
Choose your scenario
Pick a situation that occurs regularly and involves significant money. Think about price increases, food cost overruns, or staff problems. Focus on a maximum of 5-7 scenarios.
Write down the trigger
Define exactly when you use the guide. For example: 'If the food cost of a dish exceeds 35%' or 'If a supplier raises prices by more than 10%'.
List your options
Think of all possible actions you can take. Also note the pros and cons of each option. Make sure you have at least 3 different options to choose from.
Determine your decision criteria
Make clear how you choose between the options. For example: 'Choose the option that best protects your margin' or 'Prefer solutions that don't affect the guest experience'.
Test and refine
Use the guide the first time the scenario occurs. Evaluate afterwards whether it led to a good decision and adjust the guide if necessary based on your experience.
✨ Pro tip
Document only scenarios that cost you money at least twice per quarter. Test each framework for 30 days before creating the next one.
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 many decision frameworks should I create?
Start with 5-7 frameworks covering your most frequent, high-impact scenarios. More than that becomes unwieldy and you won't use them consistently. Focus on quality over quantity - better to have three excellent frameworks than ten mediocre ones.
What if following my framework leads to a poor decision?
That's valuable feedback, not failure. Analyze what went wrong and revise the framework accordingly. Each real-world application makes your frameworks more accurate and useful.
Should I create frameworks for my kitchen staff to use?
Absolutely, especially for decisions they'll make when you're not present. Think sold-out ingredients, equipment failures, or customer complaints. Staff frameworks should be simpler and more specific than owner-level decision guides.
Can I also create guides for my team?
Yes, especially for situations where your chef or manager needs to make decisions when you're not there. Think about what to do with sold-out ingredients or guest complaints.
Where should I keep my guides best?
In a place where you can find them quickly when you need them. A notes app on your phone, a folder in your office, or digitally in a system like KitchenNmbrs all work fine.
Should I create guides for exceptional situations?
No, focus on scenarios that occur regularly. For very exceptional situations, it's better to decide ad-hoc. Guides are most valuable for recurring situations.
📚 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 →