HIVE80lab — Ops notes

The Food Cost Percentage Tracker: The Friday Count That Tells You Where the Money Actually Goes

One page, ten minutes, every Friday: beginning inventory, purchases, ending inventory, food sales — one ratio that tells you whether a busy week made money or just moved it around. Food cost percentage is not paperwork; it is a leak detector. The count does not tell you what to cut. It tells you where to stand when you go looking.

Most independent restaurants run blind on food cost. The POS says sales were great, the bank account says the money never arrived, and the gap between those two facts is eating the business one over-portioned plate at a time. The tracker on this page closes that gap: a weekly ratio, a theoretical number from the recipes, and an investigation order for the weeks when the two disagree. It is the money-side twin of the refrigeration temperature log — the log keeps the stock alive, this one keeps the stock profitable.

1. The only math on the page

Food Cost % = COGS ÷ Food Sales × 100. That is the entire formula, and every argument about it is really an argument about the two inputs:

Targets by service style: 25–30% for fast casual and QSR, 28–32% for full service, higher if the menu is steak-heavy and lower if it is pasta-heavy — the number is a directional instrument, not a tax form. What matters is not hitting someone else’s number; it is knowing yours, weekly, and noticing the week it moves. A point of food cost on $41,000 of monthly food sales is $410 a month. Four points is the profit.

2. The sheet — ten minutes, every Friday

One count sheet, one row per storage area (walk-in, reach-ins, dry store, freezer), four columns:

(Beginning + purchases − ending) ÷ sales = this week’s percentage. Write it on the sheet next to last week’s. The trend line is worth more than any single week — one bad week is a delivery shortage or a catering write-off; three weeks drifting up is a leak, and the tracker’s job is to catch it in week two, not month four.

3. The gap — theoretical vs. actual

The actual percentage from the count answers what food really cost. The theoretical percentage answers what the food should have cost: every recipe’s plate cost × units sold, summed for the week. Most POS systems or recipe tools can hold the plate costs; if yours cannot, one spreadsheet with the top-twenty sellers covers 80% of the dollars.

The difference between the two — the gap — is the entire point of the exercise, because the gap has an address:

Notice what the gap does that a single percentage never can: it converts a feeling (“food costs seem high”) into a dollar figure with a timeframe. That figure is what makes the fix fund itself — a $30 scale that closes a $620/month portion leak has a payback measured in days, and the tracker is the document that proves it.

4. The investigation order — where to stand when the gap is wide

  1. The scale, first, always. Weigh the top five sellers during a normal service, against spec. Portion drift is the most common cause of a widening gap and the cheapest to fix — and it is almost never dramatic. An eighth of an ounce over, on the number-one seller, done a thousand times a month, is a line item.
  2. The waste sheet, second. One page taped above the bin for a week: item, amount, why (overprepped, dropped, returned, expired). Most kitchens discover their real waste rate the first week they measure it — and overproduction is a forecast problem, not a character problem.
  3. Receiving, third. Pull the week’s invoices against what the receiving check actually caught. Short weights, substitution at the same price, and the invoice paid for what the order said rather than what arrived all land silently in the count.
  4. Comps and voids, fourth. Unmanaged void codes and comps are food leaving without revenue arriving. If the POS lets anyone void anything, the count inherits every mistake and every favor.
  5. Theft, last — and expect to be wrong. Real theft exists, but it is the least common explanation on this list. Standing at the scale with the tracker in hand finds more money in an afternoon than a week of suspecting the staff, and it is the version of the conversation that keeps the team.

5. Worked example — the 40-seat restaurant’s Friday count

The same 40-seat restaurant that pulled the 43°F Tuesday read runs its first tracked month. The Friday count lands at 34.1% actual against 29.6% theoretical — a 4.5-point gap, $1,845 on the month’s $41,000 of food sales. The investigation order runs in one week:

Six weeks later the tracker reads 30.9% — not the theoretical 29.6%, and that is fine; the remaining 1.3 points are the honest cost of running a real kitchen. The tracker’s job was never zero. Its job was to make the leak visible while it was still a $30 scale problem instead of a $22,000 year.

5 traps (the ones that make the number lie)

Every page ships with a kit block — the paid tools behind the free advice:

Code HIVE-LAUNCH30 takes 30% off any kit at checkout.

Related: the gross margin pricing review is what a stable food cost licenses — once the ratio is honest, the pricing review decides which plates earn their shelf space; the price increase announcement is what you send when the count says inputs moved and the menu has to follow; the delivery receiving checklist is where purchases get verified before they ever reach the count; the refrigeration temperature log is the spoilage half of the same leak — warm stock is inventory cost you already paid for; the weekly ops review is where the Friday number gets read with the other vital signs instead of dying in a drawer; and the monthly close checklist is the month-end tie-out that keeps the weekly counts honest against the books.

Related: the par level & ordering guide is what acts on the count — the tracker finds the leak, the par sheet reorders to here instead of to vibes, and the two share the same Friday shelf walk.