Meal Satisfaction Survey Template
Run this short post-meal survey when you want clear, fixable feedback on a specific dining experience. Keep it under 3 minutes, collect it right after the meal, and track results by location, daypart, and channel so you can spot patterns fast. You will leave with a simple scorecard, a short list of top issues, and an owner/date plan to fix them.
Trusted by 5000+ Brands
When to Run a Meal Satisfaction Survey (3 best moments)
Use this when you want fast, specific feedback tied to one meal.
Do this first: pick your collection moment and add a channel + location field.
You'll get: a same-day view of what to fix in food, service, or effort.
Immediate post-meal QR feedback (0-2 hours)
Place a QR on the receipt, table tent, tray liner, or pickup counter. Measure overall CSAT plus food quality (taste/temperature) and accuracy. Capture segments: channel (dine-in/takeout/delivery), daypart, location.
After a change (menu, recipe, supplier, labeling)
Run a short pulse for 3-7 days after you change something guests will notice. Measure the changed item first (taste, portion, labeling clarity) plus overall CSAT. Capture segments: menu item/version, location, daypart.
After catering or service recovery (confirm the fix)
Send a follow-up after an event or a resolved complaint. Measure effort (how easy it was) and whether the problem was fully resolved. Capture segments: event type, delivery/setup, location.
Deployment Playbook + How to Customize by Dining Context
Use this when you want a survey your team can run without guessing what to ask.
Do this first: keep a short core (6-10 questions) and use one consistent scale.
You'll get: clean scores you can trend, plus comments that point to specific fixes.
- Start with a short core: Ask overall satisfaction (CSAT), then food quality (taste/temperature), accuracy (including dietary requests), speed/convenience, service, and 1-2 open-ended follow-up questions ("What should we improve next time?" and "What should we keep doing?").
- Use one rating scale across items: Stick to a 5-point scale for food/service/speed so you can compare drivers. Follow rating scale best practices (clear labels, one idea per question, consistent direction).
- Add optional modules only when you will act: Add Environment (cleanliness, noise, seating), Value/fees (portion for price, add-on fees), Delivery handoff (packaging, arrival time), or Catering professionalism (setup, communication). Skip modules you will not review weekly.
- Customize by context (Keep / Add / Remove):
Restaurant — Keep: taste/temperature, friendliness, speed, accuracy. Add: wait time and cleanliness if those are frequent complaints. Remove: long demographics fields.
Cafeteria or meal program — Keep: temperature, variety, portion, speed. Add: queue length and availability (sold-out items). Remove: detailed server questions if service is self-serve.
Hospital or senior living — Keep: taste, temperature, choice/variety, and help with special requests. Research on healthcare and aged care food service commonly tracks these drivers, including taste, temperature, variety, and service support (see foodservice satisfaction domains in aged care and a systematic review of healthcare food service satisfaction measurement). Add: confidence in labeling and whether requests were handled correctly. Remove: any question asking for medical details. - Place the QR where the decision happens: Put it on the check presenter, receipt, tray liner, or pickup shelf sign. Use a short prompt like "Tell us about today" and avoid offering a long form link.
- Protect response rate without annoying guests: Make it one scan, mobile-first, and under 3 minutes. Send 1 reminder max for SMS/email, and keep wording neutral (no guilt). Follow a simple survey design checklist for clarity and burden control (see the Best Practices in Survey Design Checklist).
Next: decide which optional module you will review in your weekly ops meeting.
CSAT vs CES vs (Optional) Loyalty: What to Measure for Meals
Use this when you want one metric that tells you what to fix after a meal.
Do this first: pick CSAT as your core, then add CES only where friction is common.
You'll get: a score you can trend, plus a clear action tied to each metric.
| Metric | Best use | Recommended question wording | Scale | Pros / cons | What actions it drives |
|---|---|---|---|---|---|
| CSAT (Satisfaction) | Track meal quality and the overall dining experience. | "Overall, how satisfied were you with your meal today?" | 5-point (Very dissatisfied to Very satisfied). Use Likert scale options for meal ratings for driver items. | Pros: Easy to explain and trend by menu item and location. Cons: Tells you what is wrong, not why (you still need drivers). | If CSAT drops, check drivers (taste/temp, accuracy, speed, service) and fix the lowest one first. |
| CES (Effort) | Find friction in ordering, pickup, delivery, and problem resolution. | "How easy was it to get what you needed today?" or "How easy was it to resolve your issue?" | 5-point (Very difficult to Very easy). | Pros: Points to process problems your team can change fast. Cons: Less useful if guests rarely face steps or issues. | If CES is low, map the steps (order, pay, pickup/handoff, fixes) and remove the top 1 bottleneck. |
| Loyalty (NPS-style, optional) | Gauge likelihood to recommend when you can act on the drivers. | "How likely are you to recommend us to a friend or colleague?" | 0-10 (Not at all likely to Extremely likely). | Pros: Simple headline number for leadership. Cons: Easy to over-index on; does not tell you what to fix without drivers. | If loyalty is low, use comments + driver items to pick 1-2 fixes (often speed, accuracy, or value perception). |
Start with your own baseline by location and channel. If you want outside context, scan ACSI trend reporting for quick-service restaurant satisfaction, full-service restaurant satisfaction, or food delivery satisfaction.
Next: pick your scoring rule (top-box % or average) and keep it consistent.
How to Read Results, Segment, and Close the Loop
Use this when you want survey results to turn into menu and service fixes.
Do this first: decide your CSAT scoring rule and your low-score routing rule.
You'll get: a short fix list with owners and dates, plus a re-check cadence.
- Score CSAT and flag low resultsDo this: report CSAT as either average (1-5) or top-box (% 4-5). Watch for: locations/dayparts that miss your internal starter target (adjust after you have a baseline), for example under 4.0/5 average or under 75% top-box. Output: a weekly scorecard with red/yellow/green by location.
- Use driver items to diagnose the causeDo this: rank drivers (taste/temperature, accuracy, speed, service, value) by lowest score and biggest volume. Watch for: one driver that drops across many menu items (often speed) vs one menu item that tanks one driver (often taste or temperature). Output: the top 2 drivers to fix first.
- Segment only by fields you can act onDo this: slice results by location, menu item, daypart, and channel (dine-in/takeout/delivery/catering). Add: a yes/no field for "Did you request a dietary accommodation?" so you can compare that experience. Output: a short list of where the problem happens (not just that it happens).
- Turn findings into an action list with owners and datesDo this: write 1 action per issue in a tracker ("Fix: fries arrive cold at lunch", Owner: kitchen manager, Due: Friday). Watch for: vague actions like "improve service". Output: a "Top 3 fixes" panel you can review each week.
- Close the loop on low scores with a simple routing ruleDo this: route low overall scores using an internal starter rule (adjust after baseline), for example any overall CSAT under 3/5 goes to the shift lead the same day. Route repeat issues using your internal definition of "chronic" (adjust after baseline), for example the same menu item or location showing low scores for 2+ consecutive weeks, to the kitchen manager and log a fix date. Keep contact capture optional and minimal, and follow privacy and optional contact collection so guests know how you will use it.
Do this: put your CSAT scorecard at the top, a driver breakdown in the middle, and a "Top 3 fixes" tracker at the bottom (issue, owner, due date, status). Output: a single page you can use in pre-shift and weekly ops reviews.
Next: re-run the same survey after each fix so you can see if it worked.
Frequently Asked Questions
How long should a meal satisfaction survey be?
Keep the core survey under about 3 minutes, which is usually 6-10 questions. Add optional modules (delivery, environment, catering) only when you will review and act on them. Short surveys work better for post-meal QR collection because guests are already done eating.
When should I send the survey after the meal?
For dine-in and cafeterias, collect feedback at the point of experience with a QR on the table, tray, or receipt and aim for replies within 0-2 hours. For delivery, send SMS/email shortly after the order is marked delivered. For catering, send within 24 hours so details are still fresh.
Should I use CSAT, CES, or an NPS-style question for meals?
Track CSAT every time because it tells you if the meal met expectations. Add CES when ordering, pickup, delivery, or problem resolution is a frequent complaint; if CES drops, remove the top friction point. Use an NPS-style loyalty question only as an optional headline number, and only if you will act on the driver items behind it.
What questions should I ask about dietary needs and allergens without collecting sensitive data?
Ask experience-focused questions like "Was it easy to find options that fit your needs?" and "How confident did you feel in the labeling or staff guidance?" Avoid asking for medical details or specific diagnoses. If you collect contact info for follow-up, state why you are asking and how fast you will respond.
How do I analyze meal survey results so they lead to changes?
Segment first by what you can fix: location, menu item, daypart, and channel. Prioritize issues that are both frequent and low-scoring, then assign an owner and due date for each fix. Re-measure after changes using the same questions so you can see if scores move.
Should the survey be anonymous?
Default to anonymous if your goal is higher participation and cleaner trend data. Add optional contact capture only when you have a real service-recovery process and you will follow up fast. Always tell guests how you will use their contact details and do not make it required.
Related Survey Templates
FREE TO START -- NO CREDIT CARD REQUIRED