A restaurant weekly report is a one-page operating review that turns seven days of sales, labor, food cost, cash, inventory and service data into a short list of management actions. The purpose is not to copy every number from the POS or accounting system. It is to show what changed, whether the change matters, what evidence explains it, who owns the correction and when the result will be checked again.
This guide gives you a practical weekly restaurant report template, the formulas behind the core KPIs, a review workflow and an action log you can use in a spreadsheet or management meeting. The examples are illustrative; your targets should come from your own budget, concept, menu, staffing model and prior periods.
What a Restaurant Weekly Report Should Do
A useful weekly report answers five questions in order:
- What happened? Sales, labor, food cost, cash, inventory and operating exceptions for the week.
- Compared with what? Budget, forecast, prior week, comparable prior period or an internal target.
- Why did it move? Evidence from invoices, schedules, waste logs, voids, counts, ticket times or other operating records.
- What action is required? A specific correction, not a vague note such as “watch food cost.”
- Who owns the follow-up? One named role or person, a due date and a repeat check.
This is different from a restaurant daily sales report, which is mainly a close-of-day control. It is also different from a manager logbook, which captures shift events and handover notes. The weekly report sits above both: it converts repeated daily signals into a management decision.
The Core Weekly KPI Formula Set
Keep the formula set small enough to review every week. Add more metrics only when they lead to a decision.
| Metric | Formula | Management use |
|---|---|---|
| Net sales variance | Actual net sales − planned net sales | Shows whether volume and mix landed above or below plan. |
| Sales variance % | (Actual − Plan) ÷ Plan × 100 | Normalizes the gap so weeks of different size can be compared. |
| Labor cost % | Total labor cost ÷ Net sales × 100 | Connects staffing cost to the sales actually produced. |
| Sales per labor hour | Net sales ÷ Labor hours | Separates scheduling productivity from wage-rate effects. |
| Food cost % | Food used ÷ Food sales × 100 | Tracks the relationship between food consumption and food revenue. |
| Food used | Beginning inventory + Purchases − Ending inventory | Provides the consumption figure behind food cost. |
| Prime cost % | (Cost of goods sold + Labor cost) ÷ Net sales × 100 | Combines the two major controllable cost groups. |
| Cash variance | Expected cash − Actual cash | Flags closing, deposit or payment-control exceptions. |
If your definitions differ from accounting definitions, write the definitions directly in the workbook. Consistency matters more than pretending one formula set fits every restaurant.
Choose the Right Comparison Column
A number without a reference point is only a number. For each KPI, choose one primary comparison:
- Budget when the question is financial performance against plan.
- Forecast when the operating plan changed after the original budget.
- Prior week when you are checking a short-term operating trend.
- Comparable prior period when seasonality or weekday mix matters.
- Internal target when a manager is working on a specific control goal.
Do not mix comparison bases within the same row without labeling them. A report that compares sales to budget, labor to last week and food cost to a historical average can still work, but the reference point must be visible so the reader knows what the variance means.
Weekly Report Triage: Which Variances Need Investigation?
Not every unfavorable number deserves the same attention. Use a simple triage system based on value, percentage and recurrence.
| Signal | Question | Action |
|---|---|---|
| High dollar impact | Is the absolute financial effect material to this restaurant? | Investigate even if the percentage looks small. |
| High percentage change | Did the metric move sharply relative to its normal base? | Check for denominator effects, coding errors and genuine operating change. |
| Repeated miss | Has the same issue appeared for multiple weeks? | Escalate from observation to corrective action. |
| One-time exception | Is there a documented event that explains it? | Record the evidence and watch for recurrence before redesigning the process. |
Set your own thresholds. A fixed “red if worse than X%” rule can be misleading because a small restaurant, a high-volume restaurant and a seasonal concept can face very different materiality. Use the report to surface the signal, then apply management judgment with evidence.
High-Risk Items to Review Before the Meeting
Some weekly variances deserve evidence before managers enter the review meeting. Pull the supporting records first:
- Food cost: beginning and ending inventory, purchases, credits, transfers, waste and unusual menu mix.
- Labor: scheduled hours, actual hours, overtime, training hours, call-outs and sales by daypart.
- Sales: covers, average check, channel mix, discounts, refunds, voids and closures.
- Cash: expected deposits, deposit confirmations, paid-outs, refunds and closing variances.
- Inventory: count differences, transfer records, receiving errors and high-value item movement.
- Service: repeated complaints, long-ticket exceptions, remakes and delivery accuracy issues.
This prevents the weekly meeting from turning into guesswork. For inventory differences specifically, use the evidence-first workflow in Restaurant Inventory Variance: Meaning, Formula, Causes and Fixes.
A One-Page Restaurant Weekly Report Template
Use one row per KPI and one action section below it. A spreadsheet can be as simple as the following structure.
| KPI | Actual | Plan/Reference | Variance | Cause code | Evidence |
|---|---|---|---|---|---|
| Net sales | |||||
| Labor cost % | |||||
| Sales/labor hour | |||||
| Food cost % | |||||
| Prime cost % | |||||
| Cash variance |
Action Log
| Issue | Corrective action | Owner | Due | Repeat check |
|---|---|---|---|---|
| Example: Friday labor over plan | Rebuild 5–8 p.m. station plan using actual sales curve | GM | Before next schedule | Next Friday |
Cause Codes Make the Report Searchable
If every manager writes a different explanation, you cannot see patterns. Use a short cause-code list and allow a note beside it. Example codes might include:
- SALES-VOLUME — sales volume below or above plan
- MIX — channel or menu mix changed
- STAFFING — scheduled coverage did not match demand
- OVERTIME — overtime or premium-pay effect
- PURCHASE-PRICE — supplier price movement
- WASTE — documented production or spoilage loss
- COUNT — inventory count or unit-entry issue
- TRANSFER — inter-location movement missing or late
- VOID-DISCOUNT — unusual refund, void or discount activity
- ONE-OFF — documented nonrecurring event
Cause codes are not proof. They are a classification layer. The evidence column should point to the schedule, invoice, count sheet, POS report or other record that supports the explanation.
Illustrative Weekly Review Example
Assume a restaurant reports net sales of $52,000 against a $55,000 plan. Labor cost is $15,600 and food used is $14,040 on food sales of $45,000.
- Sales variance = $52,000 − $55,000 = −$3,000.
- Sales variance % = −$3,000 ÷ $55,000 × 100 = −5.45%.
- Labor cost % = $15,600 ÷ $52,000 × 100 = 30.0%.
- Food cost % = $14,040 ÷ $45,000 × 100 = 31.2%.
Those percentages are not automatically good or bad. The manager compares them with the restaurant’s own plan and then checks evidence. If the sales miss came mainly from a weather-affected Monday while Friday and Saturday labor ran as scheduled, cutting weekend staffing may be the wrong response. If labor hours also stayed high during the weak Monday, the report points to a schedule-to-demand problem instead.
Weekly Review Workflow: 30 Minutes, Five Steps
- Lock the period. Use the same start/end dates across POS, payroll, inventory and purchasing data.
- Validate the inputs. Check for missing invoices, late transfers, incomplete counts and obvious POS coding errors before discussing performance.
- Rank the variances. Focus first on high-value, high-percentage or recurring misses.
- Assign one action per material issue. Write the action, owner, due date and repeat check.
- Close old actions. Do not keep adding new notes while last week’s corrective actions remain unresolved.
For labor-specific diagnosis, pair this report with sales per labor hour. For financial planning, compare the weekly result with your budget variance analysis and cash flow forecast.
Common Weekly Report Mistakes
- Too many KPIs: a 40-line dashboard can hide the three issues that actually need management attention.
- Changing definitions: using gross sales one week and net sales the next destroys comparability.
- Blaming before validating: a food-cost spike may come from count, transfer or invoice timing before it comes from operational loss.
- No owner: “review next week” is not an action.
- No repeat check: corrective action without a verification date cannot be closed.
- Using benchmarks as commands: external benchmarks can provide context, but staffing, food cost and margin decisions should reflect your own concept and economics.
Implementation Checklist
- ☐ Choose one fixed weekly reporting period.
- ☐ Define net sales, labor cost, food sales and food used in writing.
- ☐ Select 6–10 KPIs that lead to decisions.
- ☐ Give every KPI one visible comparison base.
- ☐ Add dollar variance and percentage variance where both are useful.
- ☐ Create a short cause-code list.
- ☐ Require evidence for material explanations.
- ☐ Add corrective action, owner, due date and repeat check.
- ☐ Review unresolved actions before adding new ones.
- ☐ Keep the one-page summary separate from supporting detail.
- ☐ Revisit the KPI set when the restaurant’s operating priorities change.
Restaurant Weekly Report FAQ
What should be included in a restaurant weekly report?
At minimum, include sales, labor, food cost or cost of goods, the most important cash or inventory exception, comparison values, variance, evidence, corrective action, owner and follow-up date. Add service or production metrics only when they support a current management priority.
Should I compare this week with last week or with budget?
Use the comparison that matches the decision. Budget is stronger for financial plan accountability; prior week is useful for short-term operating trends. Many restaurants keep one primary reference and one secondary trend column.
How many KPIs should a weekly restaurant dashboard have?
There is no universal number. Use the smallest set that covers the decisions managers are expected to make. If a metric is reviewed every week but never changes an action, consider removing it from the one-page summary.
Is food cost the same as actual-versus-theoretical food cost?
No. Food cost percentage measures actual food used relative to food sales. Actual-versus-theoretical analysis compares actual usage or cost with what recipes and sales mix suggest should have been used. For that deeper control, see Actual vs Theoretical Food Cost.
Should managers investigate every unfavorable variance?
No. Rank issues by financial value, percentage movement, recurrence and operating risk. Validate the data first, then investigate the material signals.
Can this template be used in Excel or Google Sheets?
Yes. The structure is platform-independent: one KPI table plus an action log. What matters is that formulas, definitions, periods and ownership stay consistent.
Before You Trust the Weekly Numbers: Data Validation Checks
A polished dashboard can still be wrong if the source data is incomplete. Before the weekly review starts, run a short validation pass. Confirm that the POS period matches the payroll period, every inventory count uses the same cutoff time, late invoices and supplier credits are posted to the correct week, and stock transfers are recorded on both sides. Review voids, discounts and refunds for obvious coding problems. If a metric depends on manual entry, compare the source total with the spreadsheet total before discussing the variance.
Use a visible status such as complete, estimated or pending correction for each input set. Managers should not make a permanent staffing, purchasing or pricing decision from a figure that is still provisional. If one important source is incomplete, record the issue and delay that part of the decision rather than filling the gap with an unexplained assumption.
How to Keep the Workbook Controlled Over Time
A weekly report becomes less useful when formulas, definitions and tabs drift. Keep one master template and protect formula cells where practical. Store the reporting week in a dedicated field instead of typing dates into headings. If a formula changes, note the effective week so old results are not silently recalculated under a new definition. Keep the one-page management summary separate from raw exports and supporting schedules so the decision view stays readable.
For restaurants with multiple managers, define who is allowed to change formulas, target references and cause-code lists. Everyone else can enter weekly data and action notes without changing the control logic. This reduces accidental formula damage and makes week-to-week comparisons more trustworthy.
Manager Takeaway
A weekly restaurant report is valuable only when it shortens the distance between a number and a management action. Keep the KPI set focused, define the formulas, compare each result with a clear reference, require evidence for material variances, and close every issue with an owner and a repeat check. Use the Restaurant Operator Lab tools and worksheets when you need to calculate or document the underlying numbers before the weekly review.