Restaurant KPI Dashboard: 3 Numbers to Watch Every Week
Most restaurant owners can tell you last night’s sales number off the top of their head. Ask them their prime cost for the week and you’ll get a pause. Ask them their food cost percentage, and you might get a rough guess. Ask them their labor cost as a percentage of revenue, and a lot of operators have to dig. They have a good guess, and think they are fine, but can’t give you a firm answer.
That gap is where margin problems hide. Daily sales are easy to see. The numbers that actually tell you whether those sales are turning into profit are usually one step removed, and most KPI dashboards make this worse by burying the important metrics in a wall of data.
Three numbers cut through all of it. These are the three we put at the top of every restaurant P&L we review, and they’re worth checking every single week, not monthly, not at tax time, every week. If all three are in range, your operation has room. If any one is drifting, you have a problem that’s cheaper to fix now than it will be in 30 days.
Prime Cost Is the Number That Predicts Your P&L Before It Arrives
Prime cost is your cost of goods sold (COGS) plus total labor, expressed as a percentage of revenue.
The formula: (COGS + labor) divided by total revenue, multiplied by 100.
For a full-service restaurant, a healthy prime cost runs between 55% and 65% of revenue. Quick-service and counter-service operations sit a few points higher. We walk through the math and the per-concept ranges on our how to calculate restaurant prime cost page.
Prime cost matters most because it captures your two biggest and most controllable cost centers together. When prime cost is in range, your remaining costs (rent, utilities, insurance, marketing) have room to be covered with something left over. When prime cost climbs toward 65% or 70%, the math can get really tight, and the P&L will confirm the problem whether you tracked it weekly or not. Tracking it weekly just gives you the chance to respond before the month is gone.
The other reason prime cost is the right number to lead with: it’s a composite metric, which means a bad prime cost number tells you there’s a problem but not where. When prime cost is off-target, your next step is always to split it apart and look at food cost and labor cost separately. That’s the diagnostic sequence: start with prime cost, then follow it into whichever of the two components is pulling the number out of range.
Food Cost Percentage Shows Whether the Kitchen Is Operating the Way It Should
Food cost percentage is your cost of ingredients divided by food revenue. A full-service restaurant should generally run food cost in the high 20s to low 30s. If yours is consistently above that band and labor is in range, something is happening between receiving and the plate: over-portioning, unlogged waste (yes, this happens, and we have had clients suffer this problem with chefs hiding food waste), product rotation problems, or purchasing discipline issues.
Tracking food cost weekly rather than monthly is what makes it a useful management tool. A monthly food cost report tells you what happened. A weekly report tells you what is happening, and gives you time to investigate before the variance compounds.
We covered the most common hidden drivers of high food cost in our post on prime cost vs food cost. If that’s the piece of your prime cost that’s out of range, that article is a useful follow-read alongside this one.
One thing worth noting: food cost percentage is only meaningful if your inventory counts are accurate. A weekly food cost number built on a rough beginning-inventory guess will show you a number, but it won’t show you reality. Getting food cost right requires a consistent count process, every week, at the same time. Once food cost is dialed in as a weekly habit, labor cost is the natural next number to look at alongside it.
What Is a Good Labor Cost Percentage for a Restaurant?
Labor cost percentage is total labor (wages, payroll taxes, benefits) divided by revenue. We generally tell operators to aim for 25% to 35% of sales, with quick-service and casual concepts at the lower end of that and full-service sitting higher. When labor runs above the top of your concept’s range consistently, the investigation starts with scheduling: are you staffing based on projected covers, or defaulting to the same schedule every week regardless of what the reservation book says?
Labor cost is the most time-sensitive of the three numbers because it’s the one you can actually adjust within the week. Food cost is largely determined by purchasing decisions you already made. Labor cost reflects decisions you can still make: cutting a shift, adjusting floor coverage, rescheduling prep based on a slow night forecast.
Together, food cost and labor cost give prime cost its diagnostic value. When you know which one is pulling the prime cost number up, you know where to spend your management attention this week.
That leads to the practical question most operators ask next: how do you actually build a system that surfaces these numbers reliably every week?
How Do You Build a Weekly KPI Dashboard for Your Restaurant?
A weekly KPI dashboard doesn’t need to be complicated. For most independent operators, a simple tracking document with five inputs is enough: total revenue, COGS (purchases minus ending inventory), total labor cost, food cost percentage, and prime cost percentage. The math to calculate each takes a few minutes once your data is organized, and the output is a clear picture of whether the week was operationally sound.
The more common problem isn’t building the dashboard, it’s getting clean, timely data to populate it. Restaurant operators running through Xero have a meaningful advantage here because purchasing, inventory adjustments, and payroll can all flow into and through one system, which means COGS and labor cost can be pulled at any point in the week rather than reconstructed at month-end. The weekly cadence becomes sustainable when the data is already organized rather than scattered across separate software, paper counts, and payroll reports.
Once the dashboard is running, the goal isn’t to obsess over the numbers every day. It’s to build the habit of looking at all three together, once a week, as a unit. Prime cost gives you the headline. Food cost and labor cost tell you which chapter to read next.
When those three are running cleanly, you’re ready to add a secondary metric like covers per labor hour.
Should Restaurants Track Covers per Labor Hour as a KPI?
Covers per labor hour is one of the most useful secondary metrics for diagnosing labor cost problems, and most restaurants aren’t tracking it. The calculation is straightforward: total covers served divided by total labor hours worked during that service. There’s no single target worth quoting here, because the number swings hard on concept, average check size, and service model. What matters is your own baseline and whether it holds.
Where covers per labor hour becomes valuable is in comparing shifts and dayparts, and that detail lives in your POS and scheduling system, not in your books. If one daypart runs well below the others, that gap points directly to a scheduling conversation. Either that shift is overstaffed for its actual cover count, or the concept needs to reconsider whether that daypart justifies its current labor investment. The number by itself doesn’t tell you what to do, but it tells you exactly where to look.
Let’s look at an example. We’ve seen operators celebrate a 29% food cost on brunch while labor for that same daypart was running at 46%, which put brunch prime cost at 75%. The food cost alone said brunch was a win. Pairing it with daypart labor out of the POS said the opposite, and that’s where the conversation about covers per labor hour starts.
Your POS holds the shift-level detail, and Xero pulls the totals up so you can see the pattern across the whole business. Tools like Syft then build on those Xero totals, putting prime cost, labor cost percentage, and food cost trends in one view so you aren’t rebuilding the math each week. Seeing these numbers and trending over time is what turns a weekly KPI check from a chore into a real management tool. Which brings us to the final and most underrated part of the dashboard: how often you actually sit down with it.
How Often Should You Review Your Restaurant’s KPI Dashboard?
The answer is once a week, every week, without exception. The value of weekly KPIs isn’t in any single week’s numbers. It’s in the pattern. A prime cost that runs 62% for one week is probably noise. A prime cost that runs 62% for three weeks in a row is a structural problem, and the sooner you see the trend, the sooner you can respond to it.
The operators we see get the most out of their dashboards treat the weekly review the same way they treat the opening checklist: non-negotiable, same time, same format. Most set aside time on Monday morning to look at the prior week’s numbers before the current week gets moving. That cadence means any issues from the week before get caught before they compound into the week ahead.
Our restaurant accounting team helps independent operators build the reporting infrastructure to make these numbers visible every week, not just at tax time. If you’re making scheduling and purchasing decisions based on gut feel because the data isn’t organized enough to be useful, that’s exactly where we start.
Reach out to U-Nique Accounting and we’ll walk through what a weekly KPI setup would look like for your operation.
Until next time!
By MATT CIANCIARULO
