What a weekly review should actually deliver
A weekly review is a decision process, not a reading of yesterday’s sales report. Its output is a short list of changes the team can implement and measure. Daily briefings handle today’s service; the weekly meeting identifies patterns across shifts. Mixing the two makes every discussion urgent and prevents deeper work.
Invite the people who can explain the numbers and change the process: the general manager, kitchen lead and relevant service or finance lead. A supplier delay does not require the whole restaurant team. Send the numbers before the meeting so time together is used for diagnosis. A sensible starting format is 45 minutes: five for previous commitments, ten for the scorecard, twenty for two material deviations and ten for decisions. This is a proposed agenda, not an industry standard.
Prepare a single view
Before the meeting, put sales, food cost, labour hours, guest feedback and unresolved issues in one place. Agree who owns each number and which period it covers. A missing number should become a task, not an estimate presented as fact.
Discuss deviations
Compare the result with your own plan and previous comparable periods. Separate a one-off event from a repeated issue. Ask which process could explain the change and what evidence would support that explanation.
Leave with an action list
Choose a small number of actions. Write down an owner, deadline and observable outcome for each. At the next review, begin with these commitments before adding new tasks.
Five numbers, with definitions
Start with net sales, guest or transaction count, average spend, food consumption and labour hours. Define average spend as comparable net sales divided by the corresponding count. Do not divide all sales by dine-in guests if those sales also include delivery. Decide whether discounts, refunds and taxes are included, and keep the definition stable.
For an operating estimate, food consumed equals opening inventory plus purchases minus closing inventory, adjusted consistently for transfers. Food cost percentage compares that consumption with food sales on the same basis. Purchases alone are not consumption: buying extra stock before a holiday can increase cash outflow without increasing that week’s usage. Labour hours and labour cost answer different questions. Keep both where reliable data exists; never invent a universal “healthy” percentage without knowing the service model.
Worked example: more sales, weaker economics
Consider an illustrative restaurant, not a client result. Food sales rise from THB 200,000 to THB 220,000. Food consumed rises from THB 60,000 to THB 74,800. Sales grew 10%, while the food-cost ratio moved from 30% to 34%. The four-point movement represents THB 8,800 compared with maintaining 30% at the new sales level.
That difference is a question to investigate, not proof of theft or waste. The menu mix may have changed, a delivery invoice may belong to another period, or inventory may be inaccurate. Inspect the highest-impact categories first. Then choose a bounded test: verify recipe yields for two dishes, reconcile three deliveries or repeat the count for high-value items. Record what would confirm or reject each explanation before assigning blame.
How to turn a finding into an action
“Reduce food cost” is an ambition. “By Thursday, the kitchen lead will weigh five portions of the two highest-variance dishes and compare them with the current recipes” is an action. Add a baseline, evidence and a review date. A short decision record can use six columns: issue, evidence, action, owner, deadline and verification.
Separate corrective work from experiments. Correcting an invoice error restores data quality; changing a portion is a commercial and quality decision that needs approval. At the next review, ask whether the action happened and whether the expected effect appeared. If the result did not move, revisit the explanation. Closing a task is not the same as solving the underlying problem.
Applying the review in Koh Samui and Thailand
For a restaurant in Koh Samui, Phuket or another destination market, annotate your own demand drivers: weather, local events, group bookings and changes in opening hours. Compare like with like. A full seven-day week and a week with two closed days should not be interpreted as equivalent trading periods. Avoid assuming that every Thai destination follows the same seasonal pattern.
Use the operating currency consistently and keep foreign-currency marketing figures separate. In a multilingual team, maintain one definition sheet with agreed translations for stock loss, refunds, covers and reservations. Local payroll, tax and licensing questions belong with qualified local advisers; the management meeting should record the operational implications and responsible follow-up, not improvise legal answers.
FAQ: what if the restaurant has no analyst?
Can a spreadsheet be enough? Yes, if the sources, definitions and owners are clear. Start with a small scorecard and reconcile it before automating. Software will not resolve inconsistent definitions on its own.
How many actions should the meeting produce? Use the team’s actual capacity. Two completed changes with evidence are more useful than twenty promises. Who checks the manager’s numbers? Assign an independent reconciliation for material items, such as sales against payment totals and purchases against receipts. The review becomes useful when the same definitions, decisions and checks survive a change of shift or manager.
Sources and scope
ISO: quality management and continual improvement ↗
Background on process-based management; the agenda and worked example above are editorial recommendations.