This restaurant new menu survey template captures structured guest feedback on new menu items across four parameters — taste, presentation, value for money, and portion size — alongside variety satisfaction, favorite dishes, menu NPS, and open-ended suggestions. Built for restaurant owners, head chefs, and F&B managers who need real guest data before making permanent menu decisions.
What Questions Are in This Restaurant New Menu Survey Template?
This restaurant new menu survey template includes 5 questions across 6 screens. Unlike a general restaurant feedback form, every question is specifically about the new menu — not the regular dining experience. Here’s what each one captures and why it matters for your menu decision:
- “How satisfied are you with the variety of options on the new menu?” (emotion rating scale, 5-point) — Variety perception before anything else. A new menu with 30 items that all feel similar scores lower on variety than a menu with 15 items that span different cuisines, dietary needs, and price points. Low scores here mean your menu breadth doesn’t match your customer base’s expectations — and the fix is assortment, not quantity.
- “How would you rate the new menu on the following parameters?” (emotion rating matrix: Taste, Presentation, Value for Money, Portion Size — 5-point each) — The diagnostic core. These four parameters are the ones that drive menu item success or failure. A dish that tastes great but looks mediocre won’t get photographed (killing social media reach). A dish with great presentation but poor value-for-money perception won’t get reordered. Track each parameter separately with survey reports and you’ll know exactly what to tell the kitchen.
- “What were your favorite dishes from the new menu?” (open-ended) — This identifies your winners. The dishes guests name are the ones that survive the menu cut. Pay attention to how they describe them — guests who praise flavor are responding to taste, guests who mention “great deal” are responding to portion-price ratio. The reason tells you what to protect when you refine the recipe. Feed responses through thematic analysis to cluster dish mentions by theme.
- “Based on your meal today, how likely are you to recommend our new menu to your friends & family?” (NPS 0-10) — Menu NPS. This is your word-of-mouth predictor for the new menu specifically. Promoters will bring friends to try it. Detractors will tell people not to bother. Compare this to your regular restaurant NPS — if the new menu NPS is lower, the menu change is hurting advocacy even if individual parameter scores look decent. That gap between “the food is fine” and “I’d tell people to come try it” is where menu decisions live.
- “Do you have any suggestions for the new menu that you would like to see in the future?” (open-ended) — Future menu R&D straight from your customers. These responses are your idea pipeline for the next menu revision. Track frequency — if 20 guests ask for “more vegan options” over a month, that’s a validated demand signal. Run through AI feedback analytics to auto-cluster suggestion themes across all responses.
When Should You Deploy This Restaurant New Menu Survey?
Timing a new menu survey isn’t the same as timing a general restaurant feedback form. The goal is capturing reactions during the window when the menu is still new enough to change:
- Soft launch period (first 2-4 weeks): Deploy the survey immediately when the new menu goes live. The first 2-4 weeks of data are the most valuable because guests are experiencing items for the first time — their reactions are unfiltered by habit. After a month, regulars adapt and stop noticing what changed.
- During the meal, not after: Deploy via tablet at the table while the guest is still eating or immediately after the last course. Post-visit email for menu-specific feedback gets lower quality responses because guests forget which specific dishes they had and how they felt about each one.
- Run for a defined testing period. Don’t leave the restaurant new menu survey template running forever. Set a 4-6 week testing window, collect enough data (100+ responses minimum for statistical relevance), make your menu decisions, then switch back to your regular restaurant feedback form.
- Use a control period. Collect 2-4 weeks of general satisfaction data BEFORE the menu change, then compare to the survey period. If your regular restaurant NPS was +45 and the new menu NPS (Q4) is +28, the menu is hurting advocacy — regardless of what individual taste scores say.
Pro tip: Don’t just survey once during the testing period. Survey in week 1 (initial reactions), week 3 (adjusted expectations), and week 6 (settled opinions). Scores often dip in week 1 (change aversion), stabilize in week 3, and reveal the real trend by week 6.
How to Analyze Restaurant New Menu Survey Results
Menu data analysis is different from ongoing satisfaction analysis. You’re making a binary decision — keep, modify, or remove each dish — and the data needs to support that:
- Build a parameter scorecard. Aggregate the four matrix dimensions from Q2 across the testing period: taste, presentation, value for money, portion size. The parameter with the lowest average score is your highest-priority fix. A menu scoring 4.5 on taste but 3.0 on value for money tells the kitchen they nailed the food and tells the owner the pricing needs work.
- Mine the favorites question for your anchors. The dishes mentioned most frequently in Q3 are your new anchors — protect those recipes during any refinement. If three dishes account for 70% of mentions, those are the ones that justify the new menu. Everything else is negotiable.
- Cross-reference NPS with parameter scores. Promoters who rate taste 5/5 but value 3/5 are telling you the food is great but overpriced. Detractors who rate everything below 3 are signaling the menu missed entirely. Segment Q2 matrix scores by NPS group to see which parameters drive advocacy vs. which ones drive detraction.
- Cross-reference with sales data. A dish that guests mention as a favorite but has low order volume has a discoverability problem on the menu — bad placement, confusing description. A dish with high order volume that nobody names as a favorite has a novelty problem — people try it once and don’t reorder. Both are fixable with different interventions.
- Track the variety question trend. If variety satisfaction (Q1) drops over the 6-week testing period, guests are discovering that the new menu is narrower than it initially appeared. If it rises, they’re finding more to like over time. The direction matters more than the absolute number.
Benchmarks for Restaurant New Menu Surveys
New menu launches are inherently volatile — scores fluctuate more than steady-state feedback. Here are the ranges to expect:
- Taste scores: Aim for 4.0+ out of 5 on average across new items. Consistent scores below 3.5 after 50+ ratings signal a recipe problem, not a preference problem. Dishes above 4.5 are your new anchors — protect those recipes.
- Value for money: The parameter that drops most during menu changes, especially if prices went up. A drop of 0.3-0.5 points from your baseline is normal during a transition. A drop of 1.0+ means your pricing moved faster than your quality perception. Compare against CSAT baseline from before the change.
- Portion size: The most subjective parameter. Lunch guests rate portions 0.5-1.0 points higher than dinner guests for the same dish size. Segment by meal period before making portion decisions.
- Menu NPS: Compare Q4 directly to your regular restaurant NPS. A new menu that scores +30 when your regular NPS is +45 is underperforming on advocacy even if parameter scores look solid. The NPS gap is your urgency signal.
Integrating Menu Survey Data With Your Restaurant Operations
Menu feedback data is most powerful when it connects to your operational systems:
- Connect to your POS. Push survey data alongside POS sales data via Google Sheets or API. When you can see “the new pasta scored 4.6 on taste and had 120 orders this week” in one view, menu decisions become obvious.
- Route to the right team. Taste and portion feedback goes directly to the head chef. Presentation feedback goes to the plating team. Value-for-money feedback goes to the owner or F&B director who sets pricing. Use Slack integration to push feedback themes to the right channel.
- Build a feedback-informed menu cycle. Instead of changing menus based on gut feel, establish a cycle: launch new items → survey for 4-6 weeks → analyze → refine or remove → launch the next round. CX automation can trigger the restaurant new menu survey template automatically during your testing windows.
- Use AI for open-ended analysis. Two open-ended questions (Q3 favorites and Q5 suggestions) generate a lot of text. Run them through AI feedback analytics to auto-cluster dish mentions, praise themes, and suggestion categories. Reading 200 individual comments is slow. Seeing “48 mentions of ‘love the pasta,’ 32 mentions of ‘more vegan options,’ 27 mentions of ‘the burger’” is immediately useful.
Automating Your New Menu Survey Workflow
Menu testing is a recurring operational cycle, not a one-time project. Automate it:
- Set up a survey schedule tied to your menu calendar. Every menu change triggers a 4-6 week survey deployment. Deploy via kiosk at tables or SMS post-visit for guests who paid by card.
- Auto-generate weekly parameter scorecards. Use automated reports to produce a weekly summary: each parameter’s average score (taste, presentation, value, portion), volume of favorite dish mentions, NPS distribution, and trend vs. previous week. The chef gets this Monday morning — no manual data pulling.
- Trigger follow-up for strong opinions. Guests who write detailed favorites or suggestions in Q3 and Q5 are high-signal respondents. Set up alerts for responses with more than 20 words in the open-ended fields — those are the detailed opinions worth reading individually.
- Compare testing periods across menu cycles. After 3-4 menu changes, you’ll have trend data on how your customer base responds to change in general. Some restaurants see higher engagement during menu launches (novelty seekers). Others see dips (habit-driven customers). Understanding your pattern shapes how aggressively you change menus.
Related Restaurant Survey Templates
This restaurant new menu survey template is for testing menu changes. For ongoing restaurant feedback, use these:
Restaurant New Menu Survey Template FAQ
-
How do you survey customers about a new menu?
Deploy a menu-specific survey during the first 4-6 weeks of the new menu launch. Use a tablet at the table during or right after the meal for the highest quality responses. Include parameter ratings (taste, presentation, value, portion size), an open-ended question for favorite dishes, menu NPS, and a suggestions question. Collect 100+ responses before making permanent menu decisions.
-
What questions should a restaurant new menu survey template include?
Five questions cover the essentials: variety satisfaction, parameter-level ratings for taste, presentation, value for money, and portion size (as a rating matrix), a favorites question to identify your anchor dishes, NPS to measure word-of-mouth potential, and an open-ended suggestions question for future menu R&D. This template covers all five areas across 6 screens.
-
When should restaurants collect new menu feedback?
Start on day one of the new menu launch and run for 4-6 weeks. Survey at three intervals: week 1 (initial reactions — often skewed by change aversion), week 3 (adjusted expectations), and week 6 (settled opinions). Scores that dip in week 1 and recover by week 3 indicate normal adjustment. Scores that keep dropping through week 6 signal a real problem.
-
How many responses do I need for reliable new menu data?
At least 100 total responses to draw reliable conclusions about the menu overall. For individual dish decisions based on the favorites question, you want to see the same dish mentioned by 15+ guests before treating it as a confirmed anchor. If a dish gets zero mentions after 100 responses, it’s invisible to your customers — a placement or naming problem on the physical menu.
-
How do I compare the new menu against the old one?
Collect 2-4 weeks of general satisfaction data before the menu change as a baseline. Then compare your new menu NPS (Q4) against your regular restaurant NPS. If your baseline NPS was +45 and your new menu NPS is +28, the menu is hurting advocacy — even if taste scores look good. The baseline comparison turns opinions into evidence.
-
Can I use this survey for seasonal menu changes?
Yes — and you should. Seasonal menu rotations benefit from the same structured testing. Run the restaurant new menu survey template during each seasonal launch, compare parameter scores across seasons, and build a data-backed understanding of which seasonal items your customers actually want. After 2-3 cycles, you’ll know which dishes to bring back and which were one-season experiments.
-
How do multi-location restaurants test new menus?
Deploy the survey at all locations simultaneously and use location analytics to compare. A dish that scores 4.5 at one location and 3.2 at another has an execution problem, not a recipe problem. Location-level data also lets you pilot new dishes at select locations before a chain-wide rollout.