Theoretical vs Actual Food Cost Variance Weekly Review

This template is used to review weekly food cost performance by comparing theoretical cost to actual cost percent. It helps operators spot variance, identify the ingredients driving it, and assign actions when the difference exceeds the defined threshold. It is best for teams that already track recipes, purchasing, and inventory closely enough to calculate both values.

The template is designed for weekly recurrence, which is usually frequent enough to catch waste, theft, portion drift, and purchasing issues before they compound. Weekly cadence also gives managers enough data to see patterns without waiting for month-end close. If your operation has very high volume or fast-moving menu changes, you may still keep the weekly review and add a midweek spot check.

A kitchen manager, GM, controller, or ops lead typically owns the review, with the DRI depending on how your team splits purchasing, inventory, and menu execution. The person running it should be able to verify recipe standards, check invoices, and assign blocking or non-blocking follow-up tasks. If the review surfaces a compliance or food safety issue, it should be escalated to the appropriate manager immediately.

A meaningful variance is any difference above the threshold your team defines for the location, menu mix, and sales volume. The template is built to support a normal threshold review, not to force every small fluctuation into a critical issue. Many teams treat small swings as non-blocking and reserve critical priority for issues that affect safety, compliance, or repeated loss patterns.

Common causes include portioning drift, recipe non-compliance, inventory count errors, vendor price changes, spoilage, waste, and unrecorded comps or voids. Ingredient-level drill-down helps separate a purchasing problem from an execution problem. Without that drill-down, teams often blame the wrong root cause and create follow-up tasks that do not fix the variance.

Yes. You can adjust the threshold, the ingredient drill-down fields, the sales period used for the theoretical calculation, and the action types assigned when variance is found. It works for single-unit restaurants, multi-unit groups, commissaries, and catering operations as long as the theoretical cost model matches how the menu is actually produced.

An ad-hoc spreadsheet review can identify variance, but it often loses accountability because follow-up actions are not assigned consistently and review history is hard to track. This template turns the process into a repeatable task with a clear recurrence, DRI, and verification step. That makes it easier to compare weeks, spot recurring issues, and confirm that corrective actions were completed.

This review usually depends on POS sales data, recipe costing, purchasing records, and inventory counts. Some teams also attach invoice exports, waste logs, or prep sheets to explain ingredient-level changes. The template itself does not require a specific system, but it works best when the underlying data is consistent and the same calculation method is used every week.

Document the event, mark the follow-up as non-blocking if it does not indicate a recurring control issue, and add a verification step so the team confirms the exception does not repeat. Examples include a vendor shortage, a menu test, or a temporary promo that changed mix. If the same exception appears more than once, it should be treated as a process issue rather than a one-off.