Most restaurant owners make the same mistakes repeatedly while forgetting what actually worked. A decision log captures your successful choices so you can replicate wins instead of reinventing the wheel. Smart operators document their victories, not just their failures.
Why keep a decision log?
You make hundreds of micro-decisions daily. Which supplier gets your business? How many servers do you schedule for Friday night? Which appetizer replaces the slow-moving special? Most operators only remember disasters, not victories.
⚠️ Note:
Without tracking systems, you'll repeat costly mistakes while forgetting profitable decisions. This drains time, money, and energy.
What gets recorded in your decision log?
Focus on choices that directly impact your bottom line:
- Menu modifications: Which items did you add or cut? How did sales respond?
- Vendor selections: Why did you pick supplier Y? What were the outcomes?
- Labor scheduling: How many cooks did you schedule for Mother's Day? Was coverage adequate?
- Inventory decisions: How much seafood did you order for the festival weekend? Any waste?
- Pricing moves: Which menu items got price bumps? How did customers respond?
💡 Example:
Decision: Switched to new produce vendor
- Date: March 15, 2024
- Reason: 12% cost reduction from previous supplier
- Result after 6 weeks: Consistent quality, reliable delivery
- Savings: €420 monthly
Action: Lock in annual contract with this vendor
How do you structure your log?
Keep the format simple. Overcomplicate it and you'll abandon the system within weeks:
- Date: Exactly when was this decision made?
- Context: What challenge or opportunity triggered this?
- Action: What specific step did you take?
- Goal: What outcome were you targeting?
- Outcome: What actually occurred?
- Insight: What would you do differently next time?
💡 Example:
Context: Understaffed during Saturday dinner rush
- Action: Added extra line cook from 4:30 PM
- Goal: Cut ticket times, reduce kitchen stress
- Outcome: Average wait dropped from 38 to 22 minutes
- Cost: €75 additional labor
- Revenue: Served 15 more covers = €525 extra sales
Insight: Saturday prep cook always generates positive ROI
Digital vs. paper tracking?
Both approaches work, but digital offers clear advantages:
- Searchable records: Instantly locate similar past situations
- Mobile access: Review notes anywhere from your phone
- Permanent storage: Paper logs get lost or damaged
- Data integration: Connect with your POS or inventory systems
From years of working in professional kitchens, I've seen too many handwritten logs disappear during busy shifts. Tools like food cost calculators often include note-taking features that sync with your financial data.
Review schedule for your log?
Your log only creates value if you actually reference it:
- Weekly: Analyze decisions from the past seven days
- Pre-decision: Search for similar past scenarios before choosing
- Monthly: Identify recurring patterns and successful strategies
- Seasonal prep: Review how you handled last year's holiday rushes
💡 Example:
Reviewing last Valentine's Day preparation:
- Action: Created prix fixe menu at €48
- Outcome: 78% of diners selected it
- Revenue: 45% boost over typical Thursday
- Issue: Ran out of chocolate mousse by 8 PM
This year: Same menu structure, increase dessert par levels by 60%
Avoid these common mistakes
Don't fall into these traps while maintaining your decision log:
- Excessive detail: Keep entries brief and actionable, or you'll quit updating
- Failure-only focus: Document wins, not just disasters
- Missing metrics: Include specific numbers to measure success
- Vague context: Explain the reasoning behind each choice
- Never reviewing: An unused log provides zero value
How do you start a decision log? (step by step)
Choose your system
Decide whether you'll work digitally (app, notes app) or on paper. Digital is better for searching, paper for quick notes. Choose what fits your working style.
Create your template
Set up a fixed format: Date, Situation, Decision, Expectation, Result, Learning. Keep it simple, maximum 6 fields. Too complex and you won't stick with it.
Record your first decision
Start today with one decision you made. Fill in all fields, even if you don't know the result yet. You can add the result in a week or month.
Make it a routine
Schedule 15 minutes each week to add new decisions and update results from old ones. Link it to a fixed time, like Monday morning.
Use your log actively
For every major decision: first search your log to see if you did something similar before. What was the result then? What can you do differently or better this time?
✨ Pro tip
Track only your 4 most significant monthly decisions for the first 8 weeks. Once logging becomes automatic, expand your scope. A simple system you actually use beats a complex one that gets ignored.
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 maintaining a decision log actually require?
Roughly 15 minutes weekly. Spend 5 minutes logging new choices and 10 minutes updating results from previous decisions. You'll save hours by avoiding repeated mistakes.
Which decisions deserve logging versus which ones I should ignore?
Track choices affecting revenue, costs, or operations: vendor switches, menu updates, staffing levels, special event purchasing. Skip routine daily decisions like prep sequences or cleaning schedules.
How long should I wait before evaluating whether a decision worked?
Timing varies by decision type. Menu changes show results within 5-7 days, vendor switches need 3-4 weeks, staffing adjustments require 2-3 shifts. Set specific review dates for each entry.
What if a decision produces mixed results - partly good, partly problematic?
Document both outcomes separately. Example: new fish supplier delivers excellent quality but consistently arrives 2 hours late. This teaches you what to negotiate differently next time.
Should I track decisions made by my kitchen manager or other staff?
Absolutely, if they impact operations significantly. When your sous chef modifies a recipe or your FOH manager adjusts server sections, those choices affect your business. Build collective knowledge.
Can I integrate my decision log with existing restaurant management software?
Many systems support this integration. Apps with note-taking functions can link decisions directly to sales data, food costs, or labor reports. This immediately shows the financial impact of your choices.
📚 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 →