Skip to content
Menu

Restaurant Menu Cycle Calculator

Plan restaurant menu cycles with projected revenue, food cost, gross profit, margin status, waste rating, ingredient reuse, and menu variety score across weekly or monthly rotations.

Restaurant menu cycle formulas

Formula
Total Meals = Meals Per Day × Cycle Length
Projected Revenue = Total Meals × Avg Selling Price × Expected Guests Per Day
Projected Food Cost = Total Meals × Avg Food Cost × Expected Guests Per Day
Gross Profit = Projected Revenue − Projected Food Cost
Profit Margin % = (Gross Profit ÷ Projected Revenue) × 100
Average Daily Revenue = Projected Revenue ÷ Cycle Length
Average Daily Food Cost = Projected Food Cost ÷ Cycle Length
Ingredient Utilization % = 100 − Food Waste %
Estimated Ingredient Reuse % = Ingredient Reuse % (planning input)
Menu Variety Score = (Menu Items ÷ Total Meals) × 100

Benchmark (profit margin % on cycle revenue):
  Excellent: ≥35%
  Good: 25-34%
  Average: 15-24%
  Low: 5-14%
  Critical: below 5%

Benchmark (food waste % - lower is better):
  Excellent: below 5%
  Good: 5-8%
  Average: 8-12%
  High: 12-18%
  Critical: above 18%

What it means

Menu cycle planning multiplies meal slots by average price and cost, then scales by expected covers. Margin status uses gross profit as a share of projected revenue. Waste status uses your planned food waste %. Ingredient utilization is the inverse of waste. Variety score compares unique menu items to total meal slots - higher can mean more SKUs relative to services, lower can mean more repetition unless reuse is intentional. Many operators target roughly 25-40% cycle margin and food waste below 8% when purchasing is disciplined.

Good to know

  • Average food cost and selling price apply to every meal slot in the cycle.
  • Expected guests per day is the covers you plan for each meal service slot.
  • Food waste % and ingredient reuse % are planner estimates for the cycle.

Ideal range

  • Does not schedule specific recipes by day, model allergen constraints, or labor.
  • Does not model purchasing lead times, tax, or delivery channel fees.
  • Variety score is a simple items-to-meal-slots ratio, not sensory diversity.

Variables

Cycle LengthCycle length
Number of days the menu rotation covers.
Meals Per DayMeals per day
Meal services planned each day (breakfast, lunch, dinner, etc.).
Menu ItemsNumber of menu items
Unique dishes or SKUs in the rotation.
Avg Food CostAverage food cost per meal
Average plate cost per meal slot across the cycle.
Avg Selling PriceAverage selling price per meal
Average guest price per meal slot across the cycle.
Expected GuestsExpected guests per day
Expected covers per meal service day slot in the plan.
Ingredient Reuse %Ingredient reuse %
Share of ingredients planned to appear across multiple dishes.
Food Waste %Food waste %
Expected waste rate for the cycle.

Assumptions

  • Weekly mode defaults cycle length to 7 days; monthly defaults to 30.

Limitations

  • Zero expected guests yields zero revenue and food cost - use for structure-only plans.

Worked examples

Real numbers through the same formula this tool uses.

  1. 1
    Restaurant scenarioExample 1

    7-Day Café Menu

    7-day cycle, 2 meals/day, 14 items, $4.50 food / $12 sell, 80 guests, 40% reuse, 6% waste → margin 62.5%, revenue $13,440. Profit: Excellent. Waste: Good.

  2. 2
    Restaurant scenarioExample 2

    14-Day School Cafeteria Menu

    14-day lunch cycle, 10 items, $2.75 food / $4.50 sell, 350 guests, 55% reuse, 4% waste → margin ≈ 38.9%, revenue $22,050. Profit: Excellent. Waste: Excellent.

  3. 3
    Restaurant scenarioExample 3

    30-Day Hotel Restaurant Menu

    30-day cycle, 3 meals/day, 45 items, $8 food / $22 sell, 120 guests, 35% reuse, 10% waste → margin ≈ 63.6%, revenue $237,600. Profit: Excellent. Waste: Average.

How to use the menu cycle calculator

From cycle length and meal slots to projected revenue, margin status, waste rating, and variety score.

  1. Choose weekly or monthly mode

    Weekly mode suits café and bistro rotations. Monthly mode suits hotel and institutional cycles. Cycle length defaults to 7 or 30 but can be adjusted.

  2. Enter cycle length and meals per day

    Cycle length is days in the rotation (1-90). Meals per day is how many services you plan (for example, lunch and dinner = 2).

  3. Set the number of menu items

    Count unique dishes or SKUs in the rotation. This drives menu variety score against total meal slots.

  4. Enter average food cost and selling price per meal

    Use cycle-wide averages from Recipe Cost or Menu Price. Selling price must be greater than zero.

  5. Enter expected guests per day

    Add expected covers per meal service slot. Leave at zero only when you want structure metrics without volume.

  6. Set ingredient reuse % and food waste %

    Reuse % is how much you cross-utilize proteins, sauces, and produce. Waste % is your expected spoilage and plate waste for the cycle.

  7. Read margin, waste, and variety results

    Confirm profit status (Excellent ≥35% through Critical below 5%) and waste status (Excellent below 5% through Critical above 18%). Review daily averages, ingredient utilization, and recommendations before you lock the cycle.

What is a restaurant menu cycle plan?

A menu cycle plan maps meal slots across a rotation window, then stress-tests average food cost, selling price, covers, waste, and ingredient reuse before you print the board or send purchasing.

  • Meal slots scaled by covers

    Total Meals = Meals Per Day × Cycle Length. Projected Revenue and Food Cost multiply total meals by average price and cost, then by expected guests per day. Gross Profit = Revenue − Food Cost.

  • Profit margin on cycle revenue

    Profit Margin % = (Gross Profit ÷ Projected Revenue) × 100. Profit status bands run Excellent ≥35%, Good 25-34%, Average 15-24%, Low 5-14%, Critical below 5%.

  • Waste and utilization

    Ingredient Utilization % = 100 − Food Waste %. Waste status bands: Excellent below 5%, Good 5-8%, Average 8-12%, High 12-18%, Critical above 18%. Lower planned waste is better.

  • Menu variety score

    Menu Variety Score = (Menu Items ÷ Total Meals) × 100. Compares unique SKUs to meal slots. Moderate scores with high ingredient reuse often beat high scores with low reuse and elevated waste.

  • Different from single-item menu pricing

    Menu Price Calculator sets one dish sticker from plate cost. Menu Cycle Calculator evaluates a full rotation with average cost and price, covers, reuse, waste, and daily revenue averages.

  • Planned waste vs measured waste

    This tool uses your planned food waste % for the cycle. Food Waste Calculator measures actual waste from purchases or inventory. Compare plan to actual after the cycle runs.

Menu cycle benchmarks

Profit margin % and food waste % bands used by this calculator. Margin higher is better; waste lower is better.

  • Profit Excellent - 35% and above

    Strong cycle food margin after average plate cost and covers. Typical when recipes are tight and waste is controlled. Safe to lock purchasing lists when invoices stay stable.

  • Profit Good - 25% to 34%

    Healthy band aligned with the recommended 25-40% cycle margin target for many restaurants. Confirm average food cost on peak days before you expand the item count.

  • Profit Average - 15% to 24%

    Adequate but thin once actual waste or comps land. Raise average selling price, trim average food cost, or reduce high-cost meal slots before heavy promotion.

  • Profit Low - 5% to 14%

    Thin margin with little room for spoilage or portion creep. Do not publish the cycle without repricing or leaner builds.

  • Profit Critical - below 5%

    Insufficient margin for a viable rotation at planned covers. Pause, recalculate with higher prices or lower food cost, then re-launch.

  • Waste Excellent - below 5%

    Tight waste control for the cycle plan. Ingredient reuse and purchasing discipline are working on paper. Validate with Food Waste Calculator after service.

  • Waste Good - 5% to 8%

    Controlled waste band. Keep FIFO, prep batches, and cross-utilization mapped across the rotation.

  • Waste Average - 8% to 12%

    Moderate planned waste. Increase ingredient reuse across days or trim overproduction on slow meal slots.

  • Waste High - 12% to 18%

    Elevated waste erodes cycle margin. Map shared proteins and produce before you add menu items.

  • Waste Critical - above 18%

    Excessive planned waste. The cycle likely needs fewer SKUs, stronger reuse, or smaller batch prep before purchasing.

  • Recommended margin target - roughly 25% to 40%

    Many restaurants aim for cycle food margin in this band when purchasing is disciplined. Institutional cycles with tight pricing may sit toward the lower half when volume compensates.

  • Recommended waste target - roughly 2% to 8%

    Well-run kitchens often plan waste in this range when reuse is intentional. Hotels and banquets may plan higher on paper but should still avoid High or Critical bands.

How to plan menu cycles profitably

Recommendations operators use when building rotations that survive real food cost, waste, and purchasing.

  • Build averages from real recipes

    Pull average food cost and selling price from Recipe Cost and Menu Price for the dishes in the rotation, not a dining-room guess. One mispriced anchor dish moves cycle margin fast.

  • Map ingredient reuse on purpose

    Enter ingredient reuse % after you sketch shared proteins, sauces, and produce across days. High reuse with moderate variety score often beats low reuse with high SKU count.

  • Plan waste honestly

    Use a realistic food waste % for the cycle. Optimistic waste plans inflate margin status. Compare to Food Waste Calculator results after the cycle completes.

  • Set covers by meal slot

    Expected guests per day should reflect the covers you plan for each meal service slot. Split breakfast and dinner volumes mentally even when you enter one cycle average.

  • Balance variety score and SKUs

    Scores above 100 mean more unique items than meal slots. Consolidate near-duplicates so purchasing stays efficient while guests still see rotation.

  • Close the loop with related tools

    Refresh Recipe Cost when invoices change, validate food cost % on period sales, check actual waste, then use Menu Engineering and Sales Mix to decide which cycle items to feature or retire.

Common menu cycle planning mistakes

Errors that make a rotation look healthy until waste, covers, or averages erode the margin.

  • Using stale average food cost

    Planning the cycle from last quarter's plate costs while supplier invoices moved understates projected food cost. Re-cost before you lock a 30-day board.

  • Planning waste too low

    Entering 2% waste when the kitchen runs 10% inflates margin and utilization on paper. Use historical waste or Food Waste Calculator trends.

  • Misstating expected guests

    Multiplying revenue by covers that never arrive overstates projected revenue. Use conservative covers for new cycles, then update after the first week of service.

  • Too many menu items for the cycle

    A variety score above 120 with modest reuse creates purchasing sprawl and spoilage risk. Consolidate items before you expand the rotation.

  • Ignoring cross-utilization

    Low reuse % with many unique items often lands in High or Critical waste status. Map shared ingredients across the cycle before you add another SKU.

  • Never comparing plan to actual

    A strong Excellent plan means little if actual food cost % and waste diverge. Re-run this calculator when invoices, prices, or covers change mid-cycle.

People also ask

Related operator questions about menu cycles and rotation planning - angles beyond the core FAQ.

  • How long should a restaurant menu cycle be?

    Cafés and bistros often use 7-day cycles. Schools and hospitals commonly use 14-28 days. Hotels may run 30-day rotations. This calculator accepts 1-90 days. Match length to purchasing rhythm and guest tolerance for repetition.

  • What counts as a meal per day?

    Each planned service counts: breakfast, lunch, dinner, or a fixed institutional meal. If you serve lunch and dinner only, enter 2 meals per day. The calculator multiplies by cycle length to get total meal slots.

  • Does this work for school and hospital menus?

    Yes. Use cycle length and meals per day for your contract window, enter average reimbursable or retail price and food cost, and set expected covers per meal slot. The school cafeteria example in the calculator uses a 14-day lunch cycle.

  • How do hotels plan monthly menu cycles?

    Hotels often run 28-30 day cycles with three meal services. Enter monthly mode, set cycle length to 30, meals per day to 3, and average price and cost across outlets. Review waste status when banquet prep adds variability.

  • Will guests notice a low variety score?

    A low variety score means fewer unique items relative to meal slots, so repetition is higher. That can be fine for captive audiences when dishes rotate well and ingredient reuse is strong. Pair score with reuse % and guest feedback.

  • Can I use this for purchasing orders?

    Projected food cost and average daily food cost give a cycle-level COGS view, but this tool does not build par levels or lead times. Use Inventory Turnover and purchase-order tools after you lock the item list.

  • Does this calculator include labor?

    No. Projected revenue and food cost cover food only. Labor, overhead, and tax sit outside this model. Use labor and prime cost tools for full P&L planning.

  • How do I plan seasonal menu cycles?

    Run separate cycles for seasonal windows with updated average food cost and menu item count. Compare margin and waste status before you swap the board. Shorter cycles (7-14 days) make seasonal transitions easier.

  • Where do combo meals fit in a menu cycle?

    Include combo average price and food cost in your cycle averages, or model high-impact combos separately with Combo Meal Profit Calculator. Combos change mix and margin within the same rotation window.

  • When should I rerun the menu cycle calculator?

    Rerun when supplier invoices move, average selling prices change, expected covers shift, you add or remove menu items, or actual waste diverges from plan. Treat the cycle as a living forecast, not a one-time print.

References & related tools

RestaurantMetric calculators for menu cycles, food cost, and inventory - no third-party citations.

  • Menu cycle as the rotation foundation

    Build average plate cost and price first, then judge the cycle by projected revenue, margin status, waste rating, and variety score.

  • Recipe Cost Calculator

    Roll recipe costs into accurate average food cost per meal before you plan the cycle.

  • Menu Price Calculator

    Set average selling price per meal from plate cost and target food cost %.

  • Food Cost Percentage Calculator

    Reconcile period food cost % after cycle sales land in the mix.

  • Menu Engineering Calculator

    Decide which cycle items to feature, reprice, or retire using popularity and contribution.

  • Sales Mix Calculator

    See how cycle volume shifts unit mix across categories and dayparts.

  • Inventory Turnover Calculator

    Check whether purchasing cadence matches the cycle length and item count.

  • Food Waste Calculator

    Measure actual waste against the food waste % you planned in the cycle.

  • Combo Meal Profit Calculator

    Stress-test meal deals that appear inside the cycle rotation.

  • Menu calculators category

    Hub for menu pricing, engineering, mix, and related restaurant tools.

Frequently asked questions

You may also need

Complementary calculators that often pair with this workflow.

Continue exploring

More tools to browse after you finish this calculation.

Guides from the Learning Center that explain this topic.

Browse all guides in the Learning Center.