A structured reflective journal for restaurant managers to record, review, and learn from operational, staffing, financial, and leadership decisions. Regular use builds stronger judgment, faster problem-solving, and measurable leadership growth over time.
Purpose & How To Use This Journal
Strong restaurant managers are not just reactive — they are reflective. This journal is designed to help you slow down after significant decisions, document your reasoning, and review outcomes honestly. Over time, your entries become a personal leadership database unique to your operation and management style.
Complete an entry whenever you make a decision that carries meaningful consequences for your team, guests, costs, or operations. You do not need to record every minor daily choice — focus on decisions where the outcome matters and where there is something to learn, regardless of whether it went well or not.
Aim to complete at least 2–4 entries per week. Consistency matters more than volume.
When To Complete An Entry
Use this journal for decisions across all areas of restaurant management, including but not limited to:
Category | Examples |
Staffing & HR | Hiring, firing, disciplinary action, shift changes, performance warnings, and promoting a team member |
Operations | Service flow changes, section adjustments, opening/closing procedure updates |
Financial | Cost-cutting measures, supplier negotiations, pricing changes, and compiling a table |
Menu | Launching or removing items, responding to food cost increases, and 86ing a dish mid-service |
Customer Experience | Handling complaints, service recovery, refund decisions, and managing a difficult guest |
Inventory & Purchasing | Emergency orders, changing suppliers, waste reduction decisions |
Marketing & Promotions | Running a special, responding to a negative review, launching a loyalty offer |
Health & Safety | Responding to a hygiene issue, managing an incident, and making equipment failure decisions |
Leadership & Culture | Addressing team conflict, delivering difficult feedback, and restructuring roles |
Decision Journal Entry
Entry Header
Field | Details |
Date | |
Manager Name | |
Restaurant / Location | |
Decision Title | Give it a short, descriptive name (e.g., "Reduced Monday evening staffing") |
Department | ☐ FOH ☐ BOH ☐ Bar ☐ Admin ☐ Events ☐ Entire Restaurant |
Decision Type | ☐ Urgent / Reactive ☐ Planned / Proactive |
Time Pressure | ☐ Decided in the moment ☐ Had hours to decide ☐ Had days to decide |
Who Was Involved | ☐ Decided alone ☐ Consulted team ☐ Consulted owner/senior management |
Section 1 — The Situation
Describe the situation that required a decision.
What was happening? What triggered the need to act? Include relevant context such as time of day, service period, staffing levels, guest volume, or any contributing factors that shaped the circumstances.
(Write freely — the more context here, the more useful this entry will be when reviewed later.)
Was this a recurring issue or a one-off situation?
☐ First time this has occurred ☐ Has happened before — not yet resolved ☐ Has happened before — previously resolved differently ☐ Expected/anticipated situation
Section 2 — The Decision Made
State the specific decision clearly and concisely.
Avoid vague language. Write it as if explaining to a colleague who was not present.
Who was informed of or affected by this decision?
Person / Role | How They Were Informed | Their Initial Response |
Section 3 — Reasoning Behind The Decision
Explain why this decision was made over other options.
Factor | Your Notes |
Information available at the time | |
Key risks identified | |
Time constraints or urgency | |
Financial implications considered | |
Team or guest impact considered | |
Gut instinct/experience factor | |
Relevant policies or standards applied. |
Confidence level at time of decision:
☐ Very confident ☐ Fairly confident ☐ Uncertain ☐ Had to decide without enough information
Section 4 — Alternatives Considered
What other options were available? Why were they not chosen?
Alternative Option | Why It Was Not Chosen |
In hindsight, were there options you did not consider at the time?
Section 5 — Expected Outcome
What did you expect to happen as a result of this decision?
Timeframe | Expected Result |
Immediate (same shift / same day) | |
Short-term (within 1–2 weeks) | |
Long-term (1 month or beyond) |
What were you most concerned might go wrong?
Section 6 — Actual Outcome
(Complete this section after sufficient time has passed — typically 1 to 4 weeks, depending on the nature of the decision.)
Date of Review: _______________
What actually happened?
How did the outcome compare to your expectations?
Area | Expected | Actual |
Guest impact | ||
Team response | ||
Financial result | ||
Operational impact | ||
Any unintended consequences |
Section 7 — Decision Effectiveness Rating
Rate the overall effectiveness of this decision:
Rating | Meaning | Circle Your Rating |
1 | Poor result — caused more problems than it solved | 1 |
2 | Below expectations — partial result, significant issues remained | 2 |
3 | Acceptable — achieved the minimum required outcome | 3 |
4 | Good result — achieved the intended outcome effectively | 4 |
5 | Excellent result — exceeded expectations, positive side effects | 5 |
Decision Rating: _____ / 5
Was the quality of the decision process sound, even if the outcome was disappointing?
☐ Yes — good process, outcome was outside my control ☐ Partially — process was rushed or incomplete ☐ No — the process and the outcome both need improvement
(Note: A well-reasoned decision can still produce a poor outcome due to factors beyond your control. Rating your process separately from the outcome builds more honest self-awareness.)
Section 8 — Lessons Learned
What did this experience teach you about managing your restaurant?
What did it teach you about your own decision-making or leadership style?
Did this decision reveal any systemic issues, gaps in your operation, or training needs?
☐ No systemic issue identified ☐ Yes — describe below:
Section 9 — What Would You Do Differently?
If faced with the same situation again, what would you change?
What I Would Change | Why |
Is there a standard procedure, checklist, or guideline that should be created as a result of this decision?
☐ No action needed ☐ Yes — describe below:
Section 10 — Follow-Up Actions Required
List any actions that must be taken as a direct result of this decision:
Action Required | Responsible Person | Due Date | Completed ☐ |
☐ | |||
☐ | |||
☐ | |||
☐ |
Monthly Reflection Section
Complete at the end of each month by reviewing all entries from the past 30 days.
Month: _______________
Year: _______________
Total entries completed this month: _______________
Reflection Question | Your Response |
What was my best decision this month, and why? | |
What was my worst decision this month, and what went wrong? | |
What recurring problems kept requiring decisions? | |
What does this pattern tell me about my operation? | |
Which decisions were most difficult, and why? | |
What leadership skill showed the most improvement? | |
What leadership skill still needs the most work? | |
What decision-making habit should I continue? | |
What decision-making habit should I stop or change? | |
What one thing will I do differently next month? |
Average decision rating this month: _____ / 5
Number of decisions rated 4 or 5: _____
Number of decisions rated 1 or 2: _____
Overall trend compared to last month: ☐ Improving ☐ Consistent ☐ Declining ☐ First month
Example Entry
Decision Title: Reduced server sections on Monday evenings
Department: FOH
Decision Type: Planned / Proactive
Time Pressure: Had days to decide
Situation: Monday evening covers had declined steadily over six consecutive weeks, averaging 30–40 guests between 6 pm and 9 pm. Despite low sales volume, we were running four full server sections with four staff on the floor. Labor cost on Mondays was consistently running above 38%, well above our 28% target.
Decision Made: Reduced Monday evening FOH from four sections to two, scheduling two servers instead of four from 5 pm onwards. One server is designated as support for both sections.
Reasoning: Sales data clearly supported the change. No single Monday in the past six weeks had exceeded 45 covers during the evening period. Continuing to staff at standard levels was not justified by revenue. Reducing sections would bring labor percentage in line with targets without affecting service quality at those cover numbers.
Alternatives Considered:
Alternative | Why Not Chosen |
Keep full staffing, offer early finishes | Unpredictable — staff may have stayed the full shift regardless |
Reduce to three sections | Still over-staffed relative to the cover count |
Close Mondays entirely | Premature — did not want to lose regular guests or reduce weekly revenue |
Expected Outcome: Labor cost reduction to approximately 26–28% on Mondays, with no deterioration in guest experience.
Actual Outcome: Labor cost dropped to 23.5% on the first Monday and averaged 25.8% across the following four weeks. Zero guest complaints related to service speed or attention. Two team members requested to be scheduled on other evenings instead, which was accommodated.
Rating: 5 / 5
Lesson Learned: Staffing decisions must follow sales data, not habit or historical scheduling patterns. Waiting six weeks before acting costs approximately R4,200 in unnecessary labor. Earlier monitoring of weekly trends would allow faster adjustments.
What I'd Do Differently: Set a trigger point — if covers drop below 45 for three consecutive Mondays, review staffing the following week rather than waiting for a longer pattern to emerge.
Why This Journal Builds Stronger Managers
Most managers make dozens of significant decisions every week. Without a record, those decisions and their outcomes disappear into the daily grind — and the same mistakes get repeated, often by different managers across the same operation.
After 6–12 months of consistent use, this journal gives you a personal database of:
What You Build | Why It Matters |
A record of successful decisions | Repeatable playbooks for common situations |
A record of failed or poor decisions | Honest accountability and pattern recognition |
Documented leadership growth | Evidence for performance reviews and career progression |
Common recurring challenges | Signals for systemic fixes, training, or process changes |
Cost-saving insights | Real data on what financial decisions worked and why |
Staffing lessons | A clearer picture of your team's strengths and gaps |
Customer service patterns | Faster, more confident responses to guest issues |
Many experienced hospitality operators and multi-unit managers credit structured reflective journaling as one of the most underused development tools available to restaurant leaders at every level of experience.
This journal is designed for restaurant managers, head chefs, floor managers, and hospitality operators worldwide. It is applicable across all restaurant formats, including full service, casual dining, fast casual, café, hotel F&B, and multi-unit operations.