Restaurant Prime Cost: Track It Weekly

Prime cost, the sum of food cost and labor cost expressed as a percentage of revenue, is the most actionable financial metric a restaurant operates around. Operators who calculate it once a month get a verdict on a period that is already over. Tracking it weekly turns the same number into something a manager can still act on.

What Prime Cost Actually Measures

Prime cost captures the two line items a restaurant manager can influence in real time: what goes into the kitchen and who works the floor. The formula is direct: add total cost of goods sold (COGS) to total labor cost (wages, payroll taxes, and benefits), then divide by total revenue for the same period.

A restaurant doing $25,000 in weekly sales, spending $9,000 on food and beverage, and $6,000 on labor, has a prime cost of $15,000 / $25,000, or 60%.

What prime cost excludes matters as much as what it includes. Rent, utilities, credit card processing fees, and equipment maintenance sit outside the calculation intentionally. Those costs are largely fixed or contractual. Prime cost isolates the two costs a manager can realistically move within a given week.

The Benchmark Trap

Restaurant industry consultants and trade publications commonly reference a prime cost corridor for full-service dining, often cited in the 55%-65% range. The National Restaurant Association consistently identifies food and labor as the two cost categories independent operators find hardest to manage, which is precisely why industry benchmarks cluster around those specific inputs.

The problem with a published benchmark is that it flattens meaningful variation. A high-volume pizza operation running a streamlined menu targets a fundamentally different prime cost than a tasting-menu restaurant with a full sommelier team. Even within a single restaurant, prime cost shifts across seasons, dayparts, and service formats.

A more useful benchmark is the restaurant's own performance history: what does prime cost look like during a well-run week, and what does it look like when something goes wrong?

Why Monthly Tracking Is Too Slow

Most independent operators calculate prime cost when the books close, once per month. By that point, the period it describes is three to five weeks in the past.

A single high-waste event, a stretch of unplanned overtime, or a food order delivered short and never credited by a supplier can bury itself inside a monthly average where it becomes invisible. The USDA Economic Research Service tracks commodity price volatility, and input prices, particularly for proteins and produce, can shift meaningfully within a single calendar month. Monthly reporting cannot separate a structural cost problem from a temporary spike in one category.

Weekly tracking does not require a full accounting close. It requires three data points that most operators already have access to: a COGS estimate from POS and inventory records, a labor figure from scheduling or payroll software, and the week's total revenue.

The Prime Cost Weekly Ledger

MyDashBorg calls this process the Prime Cost Weekly Ledger. It takes roughly 20 minutes per week and produces a consistent record that reveals patterns monthly totals hide.

Step 1 (COGS estimate): Take beginning inventory value, add invoiced purchases received during the week, subtract ending inventory. Divide by the week's gross sales. This is an approximation rather than a perpetual inventory audit, which is appropriate for weekly tracking purposes.

Step 2 (Labor cost): Pull actual hours worked from the scheduling or payroll system. Multiply by effective hourly rates. Add estimated payroll taxes and any benefits load. Divide by the week's gross sales.

Step 3 (Prime cost %): Add the two figures. Log the result alongside the week's cover count and average check for context.

Step 4 (Variance flag): Compare this week's prime cost against the restaurant's own rolling eight-week average. A spike of more than two to three percentage points in either food or labor, considered independently, is worth investigating before the next week closes.

The variance flag is the mechanism that makes weekly tracking worth the effort. It transforms a number into a question: was it food or labor that moved? Was it one night or the full week? Was it a volume issue, fewer covers with the same fixed labor, or an actual cost control failure?

A Concrete Scenario

Consider a 48-seat neighborhood bistro running a Thursday-through-Sunday dinner service and a midweek lunch. The operator tracked prime cost monthly and the numbers consistently landed in a range she considered acceptable. Monthly totals looked fine.

When the team moved to weekly tracking, a pattern emerged: every third week of the month, labor cost jumped four to six percentage points above the restaurant's own target. The cause was not a rate problem. The owner-operator took scheduled time off that week, and in her absence, the kitchen defaulted to longer prep hours and an extra front-of-house shift to cover the gap.

The fix was a written coverage protocol specifying who approved schedule additions during ownership travel. It cost nothing to implement. But it was only visible because the data had enough granularity to isolate which week caused the problem. Monthly averaging had made it look unremarkable.

When Prime Cost Spikes: What to Check First

When a variance flag appears, the order of investigation matters:

• Food cost spikes alone: Check for a missed supplier credit, a waste or spoilage event, or portion drift on a high-food-cost menu item.
• Labor cost spikes alone: Check schedule adherence, unplanned overtime, and whether cover count was lower than projected for those shifts.
• Both spike simultaneously: Usually a revenue shortfall inflating both percentages. Verify covers before assuming a cost control failure.
• Both trend upward across multiple consecutive weeks: Examine menu pricing against current ingredient costs. Persistent prime cost creep across both categories often points to a pricing problem, not an operations problem.

Treating a revenue shortfall as a cost discipline failure is one of the most common and costly misdiagnoses in independent restaurant management.

Weekly prime cost tracking does not require expensive software or a dedicated analyst. It requires a consistent process and the discipline to log three numbers every seven days. The pattern that emerges over eight to twelve weeks tells a more accurate story about a restaurant's financial health than any monthly report can.

Operators looking to move from ad-hoc spreadsheets to a structured weekly ledger can explore MyDashBorg's restaurant dashboard templates, built for operators who want consistent visibility without constructing their own system. Plans start at $15 per month and include AI-powered insights layered on top of the pre-built dashboard.