WEEKLY OPERATING REVIEW

A weekly restaurant review that ends with a decision

Published and reviewed 3 October 2026 · By Anurag Pandey

Sales went up, ingredients ran out and delivery orders arrived during a busy dinner. Which problem should you fix first? A useful weekly review connects those events instead of reading three unrelated dashboard totals. This guide shows the evidence to collect, the calculations to check and the action to test the following week.

1. Close the same week in every record

Choose an outlet and a repeatable boundary, such as Monday opening to Sunday closing. Count ingredients at that boundary and record deliveries received before it. Use the same period for POS sales, recipe usage and operating expenses. Keep settlement reconciliation separate because its eligibility dates can differ from the sales week.

• Sales: dine-in, takeaway and delivery totals, with voids, refunds and funded discounts identified. Keep a consistent basis that excludes pass-through amounts.
• Stock: physical opening and closing counts, supplier receipts, returns and transfers. Value quantities using a consistent costing method.
• Recipe usage: items sold × standard ingredient cost, with up-to-date recipes and yield. Include complimentary dishes in a separate explained category.
• Exceptions: waste, staff meals, remakes, missing dishes and complaints, recorded when they happened.
• Kitchen time: the busiest half-hour, station workload, queue length and actual ready times. A weekly order average cannot explain a Friday backlog.

If stock counts or purchasing records are incomplete, label the food-usage result incomplete. Do not make up the missing balance to create a tidy profit figure. The food-cost control sheet is a starting point for a clean inventory comparison.

2. Worked week: ₹2,40,000 sales, but only ₹12,000 after fixed costs

A fictional neighbourhood restaurant records ₹1,20,000 dine-in sales, ₹40,000 takeaway sales and ₹80,000 delivery sales. These figures exclude pass-through tax and are before the restaurant-funded discounts listed separately below. Total sales are ₹2,40,000. The kitchen serves all three channels.

The ₹58,000 other-variable total consists of packaging ₹10,000, platform services ₹20,000, funded discounts ₹6,000, incremental service labour/payment costs ₹12,000, refunds ₹4,000 and variable energy ₹6,000. The tax basis is assumed consistent with the revenue and expense treatment chosen for the example. These are invented amounts, not platform fee benchmarks.

Contribution = ₹2,40,000 − ₹80,000 − ₹58,000 = ₹1,02,000. Simplified operating result = ₹1,02,000 − ₹90,000 = ₹12,000.

Contribution is 42.5% of the chosen sales basis. The simplified operating result is 5% of sales before income tax and any items outside this example’s scope. It is not cash in the bank. Purchases may be unpaid, delivery settlement may be pending, and depreciation or other accruals may need separate treatment in the actual accounts. Read the contribution-margin explanation if these terms are new.

3. Try a different week without uploading your data

The initial figures reproduce the worked example. Change one input and recalculate to see its effect. Inventory figures are at cost; “other variable expenses” must exclude ingredients so they are not deducted twice. Known waste and staff meals explain usage variance; they are not extra deductions.

4. Explain ₹8,000 of extra ingredient usage before changing prices

Actual consumption ₹80,000 minus sold-dish recipe expectation ₹72,000 gives an ₹8,000 variance. The restaurant’s log records ₹5,000 discarded ingredients and ₹2,000 staff meals. These account for ₹7,000, leaving ₹1,000 unexplained. A variance is a question to investigate, not proof of theft.

Suppose ₹3,000 of the logged waste came from over-preparing a slow-selling side dish. The next test is a smaller first batch with a planned refill point, not a blanket reduction in portions. If the next comparable week avoids ₹1,500 of waste with unchanged sales and other costs, the model’s operating result would rise from ₹12,000 to ₹13,500. That is a conditional calculation; the test still has to demonstrate it.

Never extend a food’s safe holding time to improve the cost sheet. FSSAI provides catering hygiene requirements and inspection checklists; use them with trained supervision and your actual food-safety plan. The commercial review cannot establish that food is safe. FSSAI hygiene requirements · Official inspection checklists.

5. Check the peak cooking constraint before buying more advertising

In the example, dinner’s two-hour peak uses two equivalent cooking stations. That gives 2 × 120 = 240 station-minutes. The manager sets aside 48 minutes for the observed cleaning, changeover and disruption allowance. The remaining 192 usable station-minutes can handle 24 tickets at the measured current mix of eight station-minutes per ticket.

Usable station time = 240 − 48 = 192 minutes. Capacity = 192 ÷ 8 = 24 tickets. Demand of 30 tickets requires 240 minutes, exceeding usable time by 48 minutes.

The 20% allowance and eight-minute average are fictional measured assumptions, not industry standards. Station-minutes are work at the bottleneck, not the guest’s total wait. Different menus, equipment, batch cooking and simultaneous tasks can change this model. Re-measure when the mix changes.

Both contributions include their estimated order-variable costs before fixed expenses. The comparison explains why “more orders” can be the wrong peak-hour target. It does not mean dine-in is always better. Demand, customer commitments, service quality, batching, later repeat business and fulfilment terms still matter.

Try first: remove avoidable station delays, prepare ingredients safely before the peak, review availability and preparation times in the actual partner controls, and test promotions outside the constrained window where commercially appropriate. Adding a packer will not fix a cooking bottleneck unless packing is also blocking cooks. Do not accept orders you cannot safely fulfil or manipulate partner metrics.

6. Leave the review with one owner, one test and one review date

Keep a small action log. For this fictional restaurant, the first test is the side-dish batch plan because the waste is documented. The second is a peak station observation, not an immediate ad-budget increase. Keep supplier quality, food safety and the guest experience as non-negotiable constraints.

Also record what could invalidate the comparison: a holiday, a new menu, a supplier-price change, unusual weather, an equipment fault or a different number of open services. Do not claim a test worked because sales alone increased. Ask whether its additional contribution exceeded its additional cost and whether quality held.