Restaurant Weekly Reports: Key Metrics Every Operator Should Track

Related Resources

A restaurant weekly report is a one-page operating snapshot that closes on the same weekday every week and reports five controllable numbers, sales, food cost, beverage cost, labor cost, and prime cost, next to the execution data behind them. Restaurant accountants call the same object a flash report. It exists to catch a cost problem while you can still fix it.

The version most operators build stops at cost. That is the gap this page closes. A weekly report that shows prime cost climbed two points but cannot show that temperature-log completion dropped to 71 percent tells you the number got worse without telling you why. Cost data and execution data belong on the same page.

Three Xenia articles cover neighboring ground, and it helps to know which one to open. This page owns the weekly cadence, prime cost as a weekly number, and the flash report. The dashboards article covers live monitoring. The reporting article covers the full report taxonomy.

• Restaurant dashboard examples for multi-unit operators, for live, always-on monitoring between weekly closes
• Restaurant reporting and analysis for multi-unit operators, for the full report taxonomy across cadences
• Restaurant task management that keeps execution consistent, for the assignment layer behind your action items
• How to improve restaurant operations, for the broader operational playbook
• Daily ops checklists that feed weekly reporting, the checklist hub that produces your execution data
• Multi-location shift report template, for the daily layer underneath the weekly roll-up

How to Structure a Restaurant Weekly Report Template

Structure it as one scorecard table plus five short sections, in this order: executive summary, financial performance, operations execution, maintenance, next week priorities. The scorecard goes first because it is the only part some readers will finish. Every metric on it carries a target, a prior-week number, a status, and an owner.

Copy this scorecard directly. It is the whole report in one screen.

| Metric | This Week | Target | Prior Week | Status | Owner |
|---|---|---|---|---|---|
| Net sales |  |  |  |  | GM |
| Food cost % |  | 28-32% |  |  | Kitchen manager |
| Beverage cost % |  |  |  |  | Bar manager |
| Labor cost % |  | 25-35% |  |  | GM |
| Prime cost % |  | 55-65% |  |  | GM |
| Sales per labor hour |  |  |  |  | GM |
| Overtime hours |  | 0 |  |  | GM |
| Checklist completion % |  | 95%+ |  |  | Shift leads |
| Temperature logs completed |  | 100% |  |  | Kitchen manager |
| Audit score |  |  |  |  | GM |
| Open work orders over 7 days |  | 0 |  |  | Facilities |

Prime cost and labor ranges above come from Restaurant Resource Group and Restaurant365. Use the finer cuts by service model, 28 to 35 percent labor for full service and 25 to 30 percent for quick service, once your concept has its own history to compare against.

Section 1: Executive Summary (one page)

• Week ending date
• Net sales, with variance to prior week and same week last year
• Prime cost percentage, with variance to target
• The one number that moved most, and why
• Three action items, each with an owner and a due date

Section 2: Financial Performance

• Net sales by day
• Sales by category: food, beverage, retail
• Covers and check average
• Discounts and comps
• Food cost percentage
• Beverage cost percentage
• Labor cost percentage and hours, scheduled vs. actual
• Overtime by position
• Sales per labor hour
• Prime cost percentage

Section 3: Operations Execution

• Opening and closing checklist completion
• Most-missed item
• Temperature-log completion
• Audit or self-inspection score, with repeat-finding count
• Training tasks completed
• Guest review volume, rating, and top complaint theme

Section 4: Maintenance

• New work orders
• Closed work orders
• Open over 7 days
• Equipment downtime hours
• Preventive maintenance completion
• Capital items to flag

Section 5: Next Week Priorities

• Maximum three priorities
• A named owner for each
• A due date for each
• The metric each priority is meant to move

Cap it at three. Data without a next step is a history document, not a management tool.

What format should the weekly report use?

The same five sections work as a spreadsheet with one tab per week, as a digital form the GM submits, or as an auto-generated PDF export. The incumbent formats operators already pass around are worth naming honestly: RestaurantOwner.com's weekly prime cost worksheets, RRG's weekly prime cost workbook, 7shifts' free Excel templates, Smartsheet's restaurant financial templates, and SafetyCulture's restaurant weekly report template.

Here is the honest problem with all of them, including the spreadsheet you already use. Somebody has to retype numbers that already exist in the POS, the payroll system, and the checklist app. That retyping is why the weekly report is the most commonly skipped management task in a multi-unit group.

If you already have a weekly report spreadsheet that works, you do not need to rebuild it. Upload it to Xenia's AI Template Agent and it comes back as a digital submission form with the same fields, so the GM fills it on a tablet and the operations half populates itself. Pair it with a restaurant operations checklist template to feed the execution section.

How to Use Weekly Reports to Improve Restaurant Operations

Use the report as the agenda for a 30-minute weekly management meeting, then convert every red cell into an assigned, dated task. The report is an input to a decision, not an artifact. If nothing gets assigned, the week produced a document instead of a change.

What does a 30-minute weekly management meeting look like?

Distribute the scorecard and the exceptions before the meeting, not during it. Then run it tight:

1. Minutes 0 to 10. Red and yellow items only. Skip everything on target.
2. Minutes 10 to 20. Decide the two or three open issues. Decide, do not discuss.
3. Minutes 20 to 25. Read back owners, deadlines, and the message the wider team needs.
4. Minutes 25 to 30. Update the decisions log so next week can grade this week.

Formats worth borrowing sit in RestaurantOwner.com's weekly management meeting guide and Toast's restaurant meeting agenda template. The closing-the-loop step is the part most groups skip. Each agreed action should become a task in the same system that produces next week's completion data, which means next week's report grades last week's decisions automatically. That is what restaurant task management is for.

What decisions does the weekly report actually drive?

Catching food cost drift early. Food cost climbs two points in a week and you investigate now. Ask about portioning. Pull the waste log. Check receiving records. Two points caught in week three is recoverable. Two points running for six weeks is a hole.

Connecting labor cost to revenue patterns. Thursday revenue down 18 percent against last year with labor hours nearly identical is a scheduling gap. You built for volume that did not show up. Next week's schedule should say so.

Finding training gaps in operational data. The same checklist item missed week after week at the same store is a training signal. You do not have to guess what to train.

Getting ahead of equipment failures. Preventive maintenance completion and aged work orders are the two lines that turn an emergency repair into a scheduled one. Work order metrics are where that trend lives.

Benchmarking locations against each other. If one of five locations runs food cost four points below the others on the same menu pricing, study that location.

How do multi-unit operators compare weekly performance across locations?

Standardize the metric definitions and the week-close day first, then rank locations instead of averaging them, and report exceptions only above the district level. Every competing article on this topic writes for a single restaurant. What changes at 10, 50, or 200 locations is the part nobody covers.

• One report, three audiences. The GM report is diagnostic. The district manager report is comparative. The owner report is exception-only. Same definitions, different cuts.
• Rank, do not average. A 12-location average prime cost of 61 percent can hide two units at 70 percent. Rank every location on the same three or four metrics and publish the ranking to all GMs. The ranking is the accountability mechanism. The number is only the input.
• Exception-only roll-up. Above the store level, surface red and yellow variances and repeat findings. Not every metric for every store.
• Scope the visibility. A GM sees their unit, a DM sees their district, a VP sees the region, and the metric definitions are identical at every level. Xenia's location hierarchy and scoped permissions handles this: a franchise DM logs in and sees their 10 units, corporate sees all 200, and nobody is emailing separate spreadsheets.
• One week-close day across every unit. Obvious, and constantly violated in groups that grew by acquisition.

Hierarchy-scoped reporting is the accepted multi-unit standard, not a Xenia invention. Crunchtime, which acquired Zenput, serves "850+ restaurant brands across 150,000+ locations" and frames hierarchy as the backbone of its platform used to assign, track, and measure work. The difference worth arguing about is where the execution data lives. If your audit scores, checklist completion, and work orders sit in the same system that produces the report, the weekly roll-up stops being an assembly job. Restaurant analytics and cross-location audit benchmarking are the two views DMs open first.

How Xenia Helps You Build and Automate Restaurant Weekly Reports

Xenia produces the operational half of the weekly report and turns its action items into assigned, dated tasks. Sales and labor dollars come from your POS and payroll system. Xenia supplies checklist completion, temperature-log compliance, audit scores, incidents, and work orders, which is the half that explains why the cost numbers moved.

That scoping is deliberate. Positioning any ops platform as a replacement for an accounting flash report would not survive contact with a controller. Positioning it as the system that answers "why did prime cost move" is both true and the part your spreadsheet cannot do.

Which parts of a weekly report can actually be automated?

Partly automated is the honest answer. Four sources feed the report and they automate unevenly.

| Source | What it feeds |
|---|---|
| POS | Net sales, covers, check average, sales by category, discounts, comps, daypart splits |
| Payroll and scheduling | Hours scheduled vs. actual, labor cost, overtime, sales per labor hour |
| Invoices and inventory counts | Purchases by category, beginning and ending inventory, food and beverage cost, variance |
| Operations platform | Checklist and task completion, temperature logs, audit scores, incidents, work orders |

POS and payroll numbers pull automatically. Inventory still needs a weekly physical count, and no software changes that. The operational section only automates if the frontline work is captured digitally in the first place. A weekly report is only as automatable as the least digital step feeding it, which is why groups running paper checklists retype the operations section every week and eventually stop producing it.

What Xenia produces for the weekly packet

• Template Submission Dashboard. Live status counters and submission summary tables, so checklist and form completion for the week is a query instead of a phone call.
• Task Summary and Employee Productivity dashboards. Task counters by status, an employee leaderboard, and charts filterable by date range, status, assignee, category, asset, and location. See frontline reporting and analytics.
• Work Order Summary. Every work order with advanced filters and PDF or Excel export. That is your maintenance section, already built.
• Checklist report exports. Detailed PDF reports of checklist completions, attachable to the packet.
• AI Summaries. Lengthy reports, audits, and tasks compressed into digestible summaries, including weekly performance summaries generated automatically. Practically, a DM opens something like "Store #142: 91% audit score this week, two open corrective actions on the line check, food safety trending stable, drive-thru cleanliness flagged twice." The headline arrives before the dashboard does.
• Analytical Agent. Ask a plain-language question across your operations data, "which 10 stores have the worst food safety scores this quarter," and get the answer with the underlying view. No pivot tables, no BI license. Both capabilities sit in Xenia's AI features.
• Dashboards built on issues, not completion percentages. The view shows which locations are trending toward food safety failures, which corrective actions are overdue, and which DMs need support, rather than only whether yesterday's tasks got done.

Xenia reports across 300+ multi-location brands and 12,000+ stores managed daily, holds a 4.9 out of 5 Capterra rating, and is SOC 2 Type I. What that buys you on report day is narrow and specific: the operations section is already populated, the maintenance section exports itself, and every action item from last week's meeting has a status.

Conclusion

A weekly report earns its place by changing a decision. If yours takes two hours to build, arrives Wednesday, and ends without an owner on any line, the format is the problem.

Start with five numbers: sales, food cost, beverage cost, labor cost, and prime cost. Close the week on the same day every week. Review it inside 48 hours. Put the execution data next to the cost data so you can see why the number moved. Cap the report at one page and end it with three priorities, three owners, and three dates.

Then hold the line on length. Under 15 minutes to review, or it stops getting read.

If you want the operations half of that report to build itself, Xenia connects daily ops to automatic weekly reporting. Checklists, temperature logs, audits, and work orders land in one system, and the weekly summary comes out the other side with owners attached. Book a demo and bring your current weekly report spreadsheet. The fastest way to see whether this works is to watch your own template become a digital form.

Common Mistakes in Restaurant Weekly Reports

The most common failure is a cost-only report with no owner attached to any red number. Most operators build their first template and never change it. These are the patterns that keep showing up.

No prime cost. Reporting food and labor separately lets each manager defend their own line while the combined number breaches 65 percent unnoticed.

A floating week-close day. It breaks every week-over-week and year-over-year comparison in the report, and makes location-to-location comparison meaningless.

Reporting three days late. Detail recall decays fast. By Thursday, nobody remembers what happened on Sunday, and the corrective window for next week's schedule and order guide has already closed.

Metrics without an owner or a date. A red cell with no name next to it is a note, not an action.

Tracking what is easy instead of what matters. Revenue is easy. Food cost variance is harder to calculate and more useful. Sales per labor hour takes work to pull and is worth it.

No comparison context. A number without a frame is meaningless. 32 percent labor is fine in some concepts and a crisis in others. Show the target, the prior week, and the same week last year.

One file for every audience. Owners do not read GM diagnostics. GMs cannot act on a portfolio average. Different roles need different views of the same numbers.

Report length creep. Under 15 minutes to review is the rule. If it takes longer, it is too long. The corollary: every metric you add has to displace one, or the report stops getting read.

No corrective action tracking. If week two shows the same problem as week one, something failed between the two documents. The report needs a way to prove last week's action items actually happened.

Chasing bad data instead of fixing the source. When a number looks wrong, trace it before you escalate it. The usual causes are an invoice not entered before week close, a physical count skipped, and a checklist completed on paper and never logged.

Manual reporting that takes too long. If building the report takes more than 45 minutes, you will skip it during busy weeks, and busy weeks are exactly when you need the data. For multi-unit groups, Xenia's multi-unit operations platform pulls the execution half automatically so you are not rebuilding the same spreadsheet every Sunday night.