A chain scorecard is useful when every outlet measures the same thing over the same period and the chain totals use the correct denominators. Different definitions or a simple average of outlet percentages can create a misleading chain figure even when every individual calculation is correct.
This guide sets out a small set of core metrics, the definitions they need, how to aggregate them, and how to turn differences into questions and actions. The outlets and figures are invented illustrations, not benchmarks or targets.
Start with a metric dictionary
Before collecting numbers, write down how each metric is defined, its source, its owner and the date the period's data is locked. Corrections after the lock are recorded as a new version, not overwritten.
Four core metrics are enough to start: net revenue, completed orders, food cost percentage and revenue per worked hour. Average order value follows from revenue and orders. Quality measures such as complaints or wait times can sit alongside as context without needing a formula.
Record the unit alongside the formula. Revenue per order is INR per completed order; food cost is a percentage of the agreed food-revenue scope; revenue per worked hour is INR per actual hour. A weekly denominator must not be divided into monthly revenue. Note source cut-off times and whether late corrections will restate the period or be shown separately.
- Net revenue: one agreed policy for tax, discounts and refunds, applied the same way in every outlet.
- Completed orders: one agreed definition of a completed order and of which period a refund belongs to. Choose a policy and apply it everywhere; there is no universal standard to copy.
- Food cost: food consumed, not total purchases, using the same valuation method and food-only revenue as the denominator. Count transfers between outlets once, in the direction they move; across the chain they net to zero.
- Worked hours: actual hours worked, not the planned roster and not paid leave, with a recorded policy for manager hours and central or shared staff. This is an aggregate figure, not a tool for monitoring individuals.
Worked example: two outlets and the chain
Take two illustrative food-only outlets over the same seven-day period, so there is no question about beverage revenue. Outlet A has net food revenue of INR 120,000, 600 completed orders, food consumed costing INR 36,000 and 400 worked hours. Outlet B has INR 80,000, 200 orders, INR 32,000 of food consumed and 200 worked hours.
The chain figures come from summing the underlying inputs, then dividing. Chain revenue is 200,000 and orders are 800, so the average order is 250. Food cost is 68,000 of 200,000, which is 34%. Revenue per worked hour is 200,000 divided by 600, about 333.33.
Averaging the outlet results instead gives 300 for average order, 35% for food cost and 350 for revenue per hour. All three are wrong, because the outlet denominators differ. Calculate each chain ratio from its summed numerator and summed denominator. A correctly weighted average can be equivalent, but a simple average of outlet ratios is not reliable.
| Illustrative, 7 days (INR) | Outlet A | Outlet B | Chain (from sums) | Simple average (wrong) |
|---|---|---|---|---|
| Net food revenue | 120,000 | 80,000 | 200,000 | - |
| Completed orders | 600 | 200 | 800 | - |
| Food consumed cost | 36,000 | 32,000 | 68,000 | - |
| Worked hours | 400 | 200 | 600 | - |
| Average order | 200 | 400 | 250 | 300 |
| Food cost % | 30% | 40% | 34% | 35% |
| Revenue per worked hour | 300 | 400 | 333.33 | 350 |
When a figure cannot be calculated
If a denominator is zero or negative, the ratio is not meaningful. Leave it blank with an explanation rather than showing zero. A true zero in a numerator, such as a genuinely recorded zero cost, is a valid result.
If any named outlet is missing a required input, the chain figure is incomplete. Do not present a total built from the outlets that did report as if it covered the whole chain. Mark it incomplete until every input is in.
Compare like with like
Before judging performance, check what else differs between outlets: trading days and closures, sales channels, menu and price changes and their timing, and how long each outlet has been open. Compare each outlet with its own baseline for the same kind of period, look at the trend, and note exceptions.
Read each metric for what it is. Outlet A's lower food cost does not prove it is more profitable. Outlet B's higher average order may come from its menu mix and does not prove its staff sell better. Revenue per worked hour is neither a profit measure nor a staff target. Do not cut staffing simply because the figure rose; review quality, wait times and controls separately. Cost allocation, write-offs and stock count cut-off can all explain differences before any operational cause does.
Keep the outlet list explicit when reporting a trend. A new outlet, a temporarily closed location or a missing submission changes what the chain includes. Show the all-outlet total and any separately defined comparable-outlet view with their own scope labels. Do not silently remove a difficult outlet to make the trend improve.
From difference to action
A scorecard should produce questions, not a ranking. Take outlet B's 40% food cost. Compare it first with B's own prior periods, not with a target taken from elsewhere. Then verify the data: was the stock count complete and taken at the right cut-off? Were transfers recorded in the right direction? Does the cost scope match the dictionary? Only once the data is confirmed should the review move to portioning, waste or supplier pricing. Do not jump to blaming theft or a supplier without evidence, and do not assume the review will find a single cause.
Record each issue in an action register with an owner, the evidence, one agreed action, a deadline and a follow-up check. The register, not the scorecard alone, is how anything changes.
At the follow-up, compare the action with its intended effect and check for side effects. A faster dispatch measure is incomplete if order errors increased; a lower food-cost percentage may reflect a price change rather than less waste. Record what the evidence supports and keep unresolved explanations open instead of claiming causation from one improved ratio.
Where the food cost principle comes from
Kitchen management teaching material calculates food cost for a period from opening stock plus purchases, less closing stock, with adjustments for items such as transfers and staff meals. That consumption principle is the one used here. The scorecard itself is an original management tool. It is not a formal accounting standard and it is not a hotel reporting framework.
Put it into practice
Your action checklist
Your progress saves in this browser. No sign-up needed.
0 of 8 complete
From reading to doing
Outlet performance scorecard and metric dictionary
The Outlet Scorecard worksheet has an input section with rows for two outlets plus blank rows, covering revenue, orders, food consumed cost and worked hours. It calculates average order, food cost percentage and revenue per hour, with an input status for each row. The chain ratios are calculated from summed inputs only when every named row is complete. Further sections hold the metric dictionary and the action register. There are no automatic traffic lights; set acceptable ranges in context.
Open the Outlet Scorecard tab in the launch workbook. Keep a copy for your own business.
Download the free workbook See what’s inside the toolkit →Sources & further reading
- Monthly Food Costs, in Basic Kitchen and Food Service Management (BC Cook Articulation Committee, BCcampus) ↗
BC Cook Articulation Committee, 2015, retrieved 7 November 2026. Supports the principle of food cost as opening stock plus purchases less closing stock, with adjustments. The scorecard and example are original.
Published by Keystonne Grow. Product links connect to the Keystonne ecosystem; check the linked product or service for its current scope.
