Restaurant food-cost review: a monthly menu process for owners

A food-cost review is most useful when it leads to a specific operational decision: revisit a recipe, change a portion guide, improve ordering, update a menu description, pause a dish, or leave a well-run item alone. It becomes less useful when the team tries to turn every menu decision into one percentage without checking the current recipe, waste, portioning, supplier variance, and guest response.

Use a monthly rhythm that matches the restaurant’s purchasing and menu-change cadence. The review should bring together the owner or manager, kitchen lead, purchasing contact, and person responsible for the menu. It is an internal operating review, not accounting, tax, or financial advice. Use qualified advisers for records, formal reporting, and decisions that require professional financial guidance.

Prepare a clean review pack

Start with information the team can explain. For each significant dish or category, gather the current menu price, recipe reference, recent ingredient cost observations, portion guide, availability notes, sales or order count where available, waste or return observations, and staff feedback. Do not assume a report is current if a supplier, recipe, or portion changed after its data period.

Limit the first review to a manageable set: high-volume dishes, high-cost ingredients, seasonal items, dishes with recurring availability issues, and items the team suspects are poorly understood. A focused review produces actions; a sheet covering every item with no discussion produces noise.

Review input	Question it supports	Check before use
Current recipe	What should go into the dish?	Last change date and owner
Purchase observation	What has changed in inputs?	Supplier, pack size, and date context
Portion guide	Is production matching the intended plate?	Kitchen test or spot check
Menu price	What is the current guest-facing amount?	Live menu and outlet scope
Guest and staff notes	Is the dish clear and workable in service?	Repeated pattern, not one anecdote

The contribution-margin framework in menu engineering with contribution margin can help a team structure questions, but it should never replace current operational judgement.

Compare the kitchen reality with the menu promise

Walk through the selected dishes with the kitchen lead. Is the recipe still the version on which the menu description and costing assumptions were based? Are staff using a consistent portion tool? Has a garnish become a regular substitution? Is a component now made differently because of an equipment, supplier, or prep change? These questions often reveal more than a spreadsheet alone.

Then open the live guest menu. Confirm the name, price, description, modifiers, and photo if present. A dish described as a generous shared plate may create an expectation that the current portion does not meet. A price change may have been published in one ordering channel but not another. The review should result in one current, explainable guest offer.

If a change is needed, use a named owner and a publish date. The workflow in restaurant menu change control can prevent the kitchen and digital menu from drifting apart while a decision is being implemented.

Decide among a small set of actions

Avoid treating every review as a price increase exercise. A dish may need a recipe clarification, better prep sequence, different purchasing practice, simpler garnish, improved description, or a pause while the team learns more. Make the decision based on the evidence available and record the assumption so it can be revisited.

Observation	Possible next action	Follow-up check
Ingredient variation is material	Review supplier, pack, or menu scope with purchasing	Recheck after the next purchase cycle
Portions differ by station	Refresh a visual portion guide and observe service	Spot check at busy and quiet periods
Guests ask what the item includes	Rewrite the first-line description	Ask staff whether questions fall afterward
Item is frequently unavailable	Adjust purchasing, availability state, or menu placement	Test the live menu before next service
Item slows the pass	Simplify prep or test a different service window	Review peak-hour station flow

Do not conceal an issue with misleading descriptions or unannounced substitutions. An honest availability note and a staff explanation protect trust while the team fixes the underlying process.

Add service and waste observations

Food cost is connected to the way a dish moves through service. Ask runners and floor staff which items return unfinished, which descriptions prompt repeated questions, and which modifiers create errors. Ask the kitchen which items generate trimming, missed prep, or last-minute rework. These are not automatic reasons to remove a dish, but they identify where a menu decision may be creating avoidable waste or friction.

Keep the conversation specific. “Guests do not like it” is too broad to act on. “Guests regularly expect two sides because of the menu photo” gives the menu owner something testable. A small feedback loop can make the monthly review more grounded; build a useful restaurant guest-feedback loop offers a process for collecting that input without overreacting to every comment.

Use a monthly owner checklist

• Choose a manageable group of high-volume, high-cost, changed, or confusing dishes.
• Confirm recipes, portions, purchase context, and live menu details are current.
• Discuss service and waste observations with kitchen and floor leads.
• Record one action, owner, and due date for each selected issue.
• Update every guest-facing channel only after the operational decision is confirmed.
• Recheck the change in the next review rather than assuming it worked.
• Involve qualified advisers for accounting, tax, and formal financial questions.

A monthly review cannot remove uncertainty from a restaurant, but it can make decisions more deliberate. The value is in the connection between what the menu says, what the kitchen can repeat, and what the team learns from real service.