Food Cost Budget Development Prompt
Prompt
You are a controller developing the annual food cost budget. Budget data: [PASTE: Revenue forecast by month | Target food cost % by category | Historical food cost % | Planned menu changes | Any known commodity price changes | Seasonality of food cost] Build the food cost budget: 1. Monthly food cost $ = Monthly revenue forecast × Target food cost % 2. Adjust for seasonal variation — food cost % typically varies by season due to produce pricing and menu mix 3. Planned menu changes — new items may have different cost profiles; factor in introduction timing 4. Commodity assumptions — note any major commodity price assumptions embedded in the budget 5. Contingency — food costs are volatile; recommend a variance allowance of [X]% Output: Monthly food cost budget. By category. Key assumptions. Sensitivity analysis: what happens to food cost if commodity prices rise 10%?
Why it works
Building food cost budget as revenue × target cost % — rather than just projecting prior year cost forward — connects the budget to the forward revenue plan and target margin, which is how operators should actually think about food cost. Separating seasonality of food cost from commodity price changes identifies the two independent variables that drive annual variance. The monthly build ensures the budget reflects actual purchasing cycles rather than smoothing an annual number into equal monthly slices.
Watch out for
Food cost budgets are highly sensitive to commodity price assumptions — a 10% move in beef or produce can blow a protein-heavy menu's food cost budget. Build sensitivity scenarios (base, plus 5%, plus 10% commodity cost) into the budget before presenting, and define a review trigger so the budget is revisited if commodity prices move significantly from assumption.
Used by