How a Restaurant Group Cut Prime Cost 5 Points With Weekly Reporting

How a Restaurant Group Cut Prime Cost 5 Points With Weekly Reporting

In the restaurant business, by the time you see a bad week on a monthly P&L, you've already had three more like it.

This is a restaurant prime cost case study — an illustrative composite, not a real client file — that shows what changes when reporting cadence matches the speed at which a kitchen actually moves. The numbers are constructed for teaching. The pattern is one most multi-unit operators recognize once they see it.

The short version: a three-location restaurant group was running on monthly reports closed two weeks after month-end. By that point, problems were 45 days old and unrecoverable. Switching to weekly prime-cost reporting by location surfaced a labor overrun at one location that no one had been able to see. Schedule changes and food waste tracking trimmed five points off prime cost across the group. On $6M in annual revenue, the recovered margin funded the buildout of a fourth location.

The setup behind this restaurant prime cost case study

Call the group Five Tables. Three full-service restaurants in a metro market — a flagship, a sister location across town, and a third that had opened eighteen months earlier. Combined trailing revenue around $6.0M. Mostly dinner service with a strong weekend brunch program. Targeted prime cost (food cost plus labor cost as a percentage of net sales) of 60%.

The actual prime cost across the group had been creeping up. The most recent monthly report showed 64.5% — four and a half points above target.

The owner could feel it. The bank balance felt tight. Distributions had slowed. But the monthly reports closed on the 14th of the following month, which meant the May data didn't land until June 14 — by which time June was half over and any bad weeks in May were impossible to course-correct.

The flagship was profitable. The second location was profitable. The third location was where the slippage was concentrated, but no one knew exactly which days, shifts, or cost lines were responsible.

Why monthly reporting was already too slow

Restaurant operations move at the speed of a shift, not the speed of a tax return.

A bad scheduling decision on a slow Tuesday adds $400 to labor cost. A spoilage incident on the produce delivery loses $250 of food cost. A protein price spike adds $0.80 per cover. Each of these is a Tuesday-shaped event. None of them survive aggregation into a single monthly number.

By the time a monthly P&L reports a four-point prime cost overrun across all three locations, the operator can see the symptom and has no view into the causes. The conversation with each manager defaults to generalities — "watch your labor" — because the data won't support anything more specific.

The Five Tables operator needed a cadence that let her see the problem inside the week it happened, not 45 days after.

What Lemoti built

The engagement opened with a target deliverable: a weekly prime cost report by location, with the prior week closed and reviewed every Tuesday.

To get there, three things had to change.

• Daily sales and labor capture. The POS system already produced daily sales by location and daypart. The scheduling and timekeeping system produced daily labor hours and dollars. The two were wired into a daily data pull so the week's running labor-to-sales ratio was visible at any moment.
• Weekly food cost via short-cycle inventory. Full physical inventory at month-end was still the audit-grade number. For weekly reporting, a streamlined cycle count on the top 20 SKUs (by dollar volume) was conducted every Monday morning, with food usage calculated as starting inventory plus purchases minus ending inventory. Approximate for the week, accurate enough for decisions.
• Tuesday review meeting. A 30-minute call every Tuesday with all three managers. Each location presented its prior-week prime cost, the breakdown into food and labor, and any explanations for variances above 1.5 points from target.

The new cadence was operating by week three of the engagement. The first weekly report was ugly. The second was already cleaner. By week six, the operators were managing in real time.

What the weekly view revealed

The slippage at Location 3 wasn't food cost. It was labor — specifically, a structural over-staffing on weekday lunch and early-dinner shifts that hadn't been re-evaluated since the location opened.

The location was running an additional server and an additional line cook on Tuesday and Wednesday dinners that the volume didn't justify. Each shift was adding about $320 of unnecessary labor. Across the two days for the year, that was roughly $33,000 of avoidable labor cost — about 0.6 points of prime cost on its own, before the cumulative pressure on the manager to "make budget" pushed other decisions.

The food cost at Location 3 was also creeping up, but it wasn't waste at the receiving end. It was over-prepping for the slow shifts, producing batch waste that hit the dumpster at the end of each night. The kitchen team adjusted prep par levels for Tuesday-Wednesday based on the actual demand curve and recovered another half-point.

The flagship had a different issue. Food cost was on target but trending up because protein prices had moved 8% across two months and the menu pricing hadn't kept up. A modest price adjustment on three signature dishes recovered roughly 0.4 points without measurable customer pushback.

The second location was within target on both lines and was used as the benchmark for the other two.

What changed at two quarters in

Prime cost across the group dropped from 64.5% to 59.6% over two quarters of weekly reporting — a five-point reduction without changing the menu, service standards, or staff count materially.

On $6M of annual revenue, five points of prime cost is $300,000 of recovered margin. After re-investing some of that into a modest cost-of-living wage increase for the front-of-house staff (which had also been part of the labor turnover problem), the net contribution to operating cash was roughly $230,000 annually.

Six months into the new cadence, the owner committed to a fourth location's buildout — funded primarily from the recovered margin rather than additional debt or partners. The reporting discipline had created the operating headroom that made the next location feasible.

What this restaurant prime cost case study shows

Restaurants don't lose margin in big chunks. They lose it in shifts and small decisions that compound across weeks. A monthly P&L can confirm that something went wrong. A weekly prime cost report can prevent it.

The data exists in every modern POS and scheduling system. What's missing in most multi-unit operations is the discipline to pull it together every Tuesday and the meeting where someone with the authority to change scheduling and prep par levels reviews it with the managers.

That's not analytics. That's operating cadence.

Find a CPA who runs the weekly cadence

If your monthly reports tell you what your prime cost was two weeks ago and your managers run their shifts off feel, the gap is in the cadence, not the team.

Lemoti works with multi-location restaurant and hospitality operators on weekly prime cost reporting, daily sales-and-labor capture, and the management cadence that turns operating data into operating decisions. Read their Sam's List reviews and book an intro call before another quarter of monthly-only reporting runs the prime cost line into the wrong neighborhood.