A new menu is one of the highest-stakes changes you can make, it touches revenue, cost, guest experience, and staff training all at once. The properties that get the most out of a launch don't just design a good menu, they benchmark it before launch, watch it closely in the first few weeks, and know exactly what "success" and "needs adjustment" look like in the data.
Phase 1: Pre-Launch Benchmarking
Before a single new item goes live, you need a clear baseline to compare against, otherwise you won't be able to tell whether the new menu is actually working.
-
Run a full Menu Engineering review of your current menu, filtered by category. Know exactly what you're keeping, reworking, or cutting, and why, based on Popularity and Profitability, not instinct.
→ See: "How Do I Use the Menu Engineering Feature Effectively?" - Record your baseline KPIs: Average Check (Food and Beverage), Food/Beverage Cost %, and Revenue by Item Category. These are the numbers you'll compare the new menu against.
- Set up new items in Recipes before launch, ingredients, quantities, and pricing, so cost and margin data starts flowing from day one instead of being backfilled later.
-
Apply menu design principles to the physical layout, decide prime placement in advance based on which new items you expect (or want) to perform best, rather than placing items arbitrarily and discovering the layout was working against you.
→ See: "How Do I Design My Menu for Maximum Profitability?" - Train staff specifically on the new items, not just what they are, but which ones you want actively upsold and why. A new menu only performs as well as your team's ability to talk about it confidently.
Phase 2: Launch Week
The first week is about watching closely, not waiting for a monthly review to tell you how it's going.
- Check Menu Engineering daily for the first week, specifically the new items. You're not expecting stable ratings yet, you're watching for early red flags, an item with zero sales, or a cost % wildly off from what you projected.
- Watch Average Check against your pre-launch baseline. A new menu should move this number, if it's flat or declining in the first week, that's worth investigating immediately rather than waiting to see if it "settles."
- Check Top Items Sold for your new items specifically, comparing Menu Price vs. Actual Price to confirm pricing is holding as designed, not already being discounted away.
Phase 3: Weeks 2-4
- Move to weekly Menu Engineering reviews, filtered to your new items, tracking whether early ratings are holding, improving, or slipping as the initial novelty wears off.
- Compare category-level Revenue and Cost trends against your pre-launch baseline, not just individual item performance, since a new menu can shift guest behavior across the whole category, not just the specific dishes you changed.
- Revisit menu design placement if an item is underperforming despite a good Menu Engineering profile. Sometimes the dish is right and the positioning is wrong, check this before assuming the item itself is the problem.
Phase 4: The Decision Point
By the end of the first month, you should have enough data to make a clear call on each new item:
- Keep as-is: Popularity and Profitability both holding at Satisfactory or better.
-
Adjust: strong Popularity but weak Profitability (or vice versa), a candidate for repricing, portion adjustment, or a recipe tweak rather than removal.
→ See: "How Do I Use WiseFins to Reduce Food & Beverage Costs?" for the ingredient-level drill-down process - Roll back: consistently weak on both axes with no clear fix, better to cut cleanly than let an underperforming item linger and quietly drag down the category.
Phase 5: Fold Into Your Regular Cadence
Once the launch has stabilized, bring the results into your next Monthly Business Review, both the wins worth highlighting and any items still being watched, so the launch becomes part of your ongoing rhythm rather than a one-off event that fades from view.
→ See: "How Do I Run an Effective Monthly F&B Business Review?"
Quick-Reference Checklist
- Pre-Launch → Full Menu Engineering review of current menu (keep/rework/cut)
- Pre-Launch → Baseline KPIs recorded (Average Check, Cost %, Revenue by Category)
- Pre-Launch → New items fully set up in Recipes before go-live
- Pre-Launch → Pricing sanity-checked via Recipe simulation
- Pre-Launch → Menu design placement decided intentionally
- Pre-Launch → Staff trained on new items and upsell priorities
- Launch Week → Daily Menu Engineering check on new items
- Launch Week → Average Check vs. baseline
- Launch Week → Menu Price vs. Actual Price (pricing holding, not discounted away)
- Weeks 2-4 → Weekly Menu Engineering review, new items
- Weeks 2-4 → Category-level trend vs. baseline
- Month 1 → Keep / Adjust / Roll back decision made per item
- Ongoing → Results folded into next Monthly Business Review
Comments
0 comments
Please sign in to leave a comment.