Questions to Ask in a Restaurant Survey
These are questions to ask in a restaurant survey, for an owner or manager writing a guest feedback form for a receipt link, a table card or a follow-up email. They follow the visit: the overall rating and whether the guest will return, then food, service, the room and the price, takeout and delivery, and a few about the guest to close. Each has a note on wording, the answer scale and what a good or a worrying result should lead you to do, and since no guest should be shown them all, the guide explains how to choose the eight or ten that fit one form.
Want questions from the whole vault instead? Try the random question generator.
The questions
Each question, and why to ask it
The visit
Overall, how would you rate your visit today?
Why ask it
This opens the form, on five labeled points from poor to excellent, so it is answered before any later question reminds the guest of a cold side dish. 'Today' ties it to one visit; in a follow-up email, swap in the date. The result to worry about is a pile of middle scores, from guests who had no reason to complain and no reason to return.
How likely are you to come back in the next month?
Why ask it
The time frame keeps it honest, since nearly everyone will 'come back sometime'. Fit it to your place: a lunch counter can ask about the next two weeks, a special-occasion room about the next celebration. Guests who rate the visit well and still answer 'unlikely' are telling you about price, distance or occasion, and a comment box underneath usually says which.
Would you recommend us to a friend who asked where to eat around here?
Why ask it
Picturing a real friend with a real question gets a truer answer than an abstract score. Yes, maybe and no are enough for a table card; switch to a 0 to 10 scale only if you mean to track the number for years and leave the wording alone. A run of 'maybe' describes a place that is fine and forgettable.
What was the best part of your visit?
Why ask it
The replies show what regulars would miss, so read them before you cut a dish or redo the room. Keep the box to a single line, because a large empty one looks like homework. When almost nobody mentions the thing you built the menu around, that is a finding too.
Was anything about your visit disappointing?
Why ask it
Asking outright gives people permission to mention the small thing they would never have raised at the table. Make it yes or no, with a text box that opens only on yes, so happy guests are through in one tap. Sort the replies by day and shift: three mentions of the same slow Saturday outweigh ten scattered gripes.
What was the occasion for your visit today?
Why ask it
A guest on a lunch break and a couple on an anniversary judge the same forty-minute meal very differently, and this tells you which of them answered. Give a short list to choose from: a quick meal, a meal with family or friends, a date, a work meal, a celebration, just drinks or coffee. It is not a score to chase. It is the key for reading the others.
Compared with your last visit, was this one better, about the same, or not as good?
Why ask it
Regulars come back for the meal they had last time, so 'not as good' from them is an early warning, often ahead of anything the sales figures show. Follow it with a box asking what changed. Newcomers need a fourth answer, 'this was my first visit', or they will guess.
Food
How would you rate the taste of your food?
Why ask it
Name taste outright. 'Food quality' lets one guest answer about flavor, another about freshness and a third about the size of the plate, and the score ends up meaning none of them. Use the same five points as the opening question, and read the results dish by dish once you know what each guest ordered.
Was your food at the right temperature when it reached your table?
Why ask it
Lukewarm plates often trace to the wait between the kitchen and the table more than to the cooking, so set the complaints against your busiest hours. Split the 'no' into hot food that was not hot enough and cold food that was not cold enough, because the two have different causes. If the complaints gather on one dish, look at how it is plated and held.
How would you rate the way your food looked on the plate?
Why ask it
A low score here usually arrives with a story in the comment box: a sauce that had run, a garnish left off, a plate that looked nothing like the photo. Scores that fall on busy nights and recover on quiet ones point to plates leaving the pass in a hurry. Leave it off the form at a counter or a food truck, where nobody came for the plating.
How fresh did your food seem?
Why ask it
'Not fresh' is too vague to act on until you know the item, so open a box on any low answer. The replies tend to gather on a few things: salad greens, bread, seafood, and fried food that sat under a heat lamp. One item named again and again is a question about how it is stored, prepped or held, not about the whole kitchen.
Was your order correct when it arrived?
Why ask it
It is a fact, so no scale is needed, only a box on 'no' for what was wrong. A wrong order starts in one of three places: how it was taken, how it was keyed in, or what left the kitchen. The comments say which, and each one has a different fix.
Was the portion size too small, about right, or too large?
Why ask it
Keep price out of the wording. Value has a question of its own further down, and a guest cannot answer both in one tap. 'Too large' sounds like praise and is partly a cost: if many guests say it, watch how much comes back on the plates. 'Too small' beside weak value scores is a pricing problem more than a kitchen one.
Which dishes did you order?
Why ask it
Knowing the order lets you break every food score down by dish, which is where a decent average hides one weak plate. Give a checklist of menu sections or best sellers, since a blank box here tends to get skipped. Leave the question out if the survey link carries the check number and your point-of-sale system can attach the order for you.
Did your dish match the way the menu described it?
Why ask it
A 'no' is often cured with a pen instead of a pan: the menu promised crispy, spicy or a generous side and the plate was something milder. Give 'mostly' as a middle answer, since few plates miss completely. Photos on your website or a delivery app are descriptions too, so look at them when this score dips.
How easy was it to find something on the menu you wanted to eat?
Why ask it
A test of the menu's range before anyone is asked to redesign it. Leave a box for anyone answering 'difficult', and expect the replies to fall into groups: vegetarians, people avoiding gluten, children, lighter eaters. One group repeating itself makes a case for a new dish. Scattered wishes do not.
Is there a dish or drink you wish we had on the menu?
Why ask it
Count the requests instead of weighing them one by one: a single guest asking for sushi at a burger place is a curiosity, and fifteen asking for a second vegetarian main course are a brief for the chef. Dishes you took off the menu will turn up here too, which is how you learn whether a cut was noticed. Keep it optional.
If you told us about an allergy or dietary need, how confident were you in how we handled it?
Why ask it
Asking about confidence catches the server who said 'I think it should be fine' as well as the plate that came out wrong. Most guests will choose 'I did not mention one' and move on. A low answer from anyone else goes to the kitchen and the floor that same day, and if the guest left contact details, call them.
How would you rate your drinks?
Why ask it
Coffee, cocktails and sodas reach the table by a different route than the food, so this score can sag while the kitchen's holds steady. Give guests who drank only water a 'did not order any' answer, and ask everyone else for a comment on a low rating: 'the coffee was lukewarm' and 'my drink took fifteen minutes' go to different people.
Service
How would you rate the service from the person who looked after your table?
Why ask it
The headline service score, on the same poor-to-excellent scale as the food. Word it for how you serve: 'the person who took your order' at a counter, 'our team' where several people share a table. If the survey can be traced to a server, decide before the first one goes out whether scores will count in anyone's review, and tell the staff either way.
How welcome did our staff make you feel?
Why ask it
Warmth gets its own question because a server can be friendly and slow, or quick and cold, and those call for different conversations. A low answer beside good marks for speed is usually about tone: a rushed greeting, a sigh at a substitution, a table that felt hurried out. Share the pattern with the whole team before singling anyone out.
How easy was it to book a table or get on the waitlist?
Why ask it
Keep in mind who cannot reply: anyone the booking page or an unanswered phone turned away never got a receipt. A few 'difficult' answers therefore stand for more people than they look like, and the quickest test is to try booking a table yourself from a phone. Walk-ins who were seated at once need an answer of their own.
Were you greeted soon after you came in?
Why ask it
A guest left standing at the door starts the meal already counting minutes. Yes or no is all it takes. Read the 'no' answers by hour, because they tend to land where the host is also running food or answering the phone.
How long did you wait for a table?
Why ask it
Use time ranges, not a rating: seated right away, under 10 minutes, 10 to 20, longer. For anyone who waited, add a follow-up asking whether the wait they were quoted turned out about right. A long wait quoted honestly is usually easier to forgive than a short one that ran over.
After you ordered, how did the wait for your food feel: short, about right, or too long?
Why ask it
Your kitchen tickets already hold the minutes, so the survey's job is how those minutes felt. 'Too long' on a ticket that ran to normal time usually means nobody told the table what was happening. The same kitchen can score well at dinner and badly at lunch, when guests are watching the clock.
How well did your server answer your questions about the menu?
Why ask it
Low marks here point toward tastings and pre-shift briefings more than attitude, since a server who has never eaten the special cannot describe it. Watch this one closely in the weeks after a menu change. Add 'I did not ask any' so the rest are not rating a conversation they never had.
After your food arrived, did someone come back to check on your table?
Why ask it
The check-back is the moment a cold plate gets replaced instead of written up online that night, which is why it earns a plain yes-or-no question to itself. A string of 'no' on busy evenings suggests the sections are too big for the staff on the floor.
How easy was it to get a staff member's attention when you needed something?
Why ask it
'Difficult' here nearly always has an object: a refill, the check, a missing fork. Ask for it in a comment. Before reading the result as one server's failing, look at how the floor was divided that shift and whether anyone was covering two sections.
When you were ready to leave, how quickly were you able to pay?
Why ask it
A slow check can undo a good hour, because the end of the meal is the part guests walk out with. Three answers will do: right away, after a short wait, it took too long. Where 'too long' turns up at lunch, see whether payment can be taken at the table or whether everyone is lining up for one terminal.
If you raised a problem during your visit, was it fixed before you left?
Why ask it
Give five answers: yes, partly, no, I had a problem but did not mention it, I had no problem. Count the fourth most carefully. Those guests left unhappy without giving you a chance, and a large share of them suggests staff are not asking, or are asking in a way that invites 'fine, thanks'.
Did anyone on our team make your visit better? Tell us who and how.
Why ask it
Optional, open, and the most pleasant reading on the form. Hand each mention to the person named, word for word, at the next pre-shift meeting. Do not add a matching box for naming someone who did badly: a complaint about a person belongs in a private comment that a manager follows up.
Room and price
How clean did you find your table and the area around it?
Why ask it
Guests take in the floor under the next table, the menus and the condiment bottles as much as their own place setting, which is why the question reaches past the table. Run the answers from not at all clean to very clean. Anything below the top two points earns a walk through the room at the hour it was reported.
How clean were the restrooms?
Why ask it
Guests tend to treat the restroom as a guess at the kitchen they cannot see, so a poor score here costs more than its share. Let anyone who never went in say so. Compare the rest by time of day, because a dip late in the evening usually means the checks stop when the rush starts.
Was the noise level too quiet, about right, or too loud?
Why ask it
A rating would not say which way to turn the dial, so ask for a direction. Set it beside the question about what brought the guest in: music that suits a Friday crowd is 'too loud' for a table trying to talk business. If 'too loud' wins on every kind of visit, start with the playlist volume before spending money on the room.
How would you rate each of these: seating comfort, lighting, room temperature?
Why ask it
Build a short grid with the same scale on every row. One score for 'atmosphere' gives you nothing to fix, while 'room temperature: poor' sends someone to the thermostat or to the table by the door. Comments that name a particular table are the valuable ones, so leave space for them.
Was it easy for everyone in your group to get in, get seated and move around?
Why ask it
On a 'no', open a box asking what got in the way. It turns up the step at the door, the tight path to the restroom, nowhere for a stroller, no high chair. What a building has to provide differs from place to place, so check your local rules; the survey's part is showing what guests ran into.
Was your meal good value for what it cost?
Why ask it
The word doing the work is 'value': a guest can find you expensive and worth it, or cheap and not. Give five answers running from poor to excellent. A low answer from guests who liked the food says the price outran something else, such as the service, the portion or the room.
Was there anything on your check you did not expect?
Why ask it
Service charges, automatic gratuity for large groups, card fees, a charge for bread or water and split-plate fees are the usual surprises, and a box on 'yes' will tell you which. What may be charged and how it has to be shown varies by place, so confirm the rules where you operate. Then make sure the menu says it before the check does.
Takeout
How did you place your order?
Why ask it
Its job is routing, so that dine-in guests never see the packaging questions and delivery customers are never asked about the restrooms. The list to choose from: with a server, at the counter, by phone, on our website or app, through a delivery service. On an online form it belongs near the top, whatever group it sits in here.
How easy or difficult was it to order from our website or app?
Why ask it
Only guests who ordered that way should see it. Follow anything below 'easy' with a box. The replies are specific: the menu would not load, an option was missing, the pickup time could not be changed. Together they make a repair list for whoever looks after the ordering page.
Was your pickup order ready at the time we gave you?
Why ask it
Late pickups suggest the quoted times are set for a quiet kitchen and never stretched when the dining room fills. Add 'I was not given a time' beside yes and no, and treat it as a finding of its own: someone taking orders is not quoting a time at all.
Was everything you ordered in the bag?
Why ask it
A dine-in guest with a missing side tells the server. A takeout guest finds out at home, with no way to fix it. Ask what was missing, and expect sauces, drinks and add-ons to lead the list; a second person checking the bag against the ticket at the handoff is the usual cure.
How well was your order packed?
Why ask it
Leaks, lids that popped, hot and cold items sharing a bag, and missing napkins or cutlery all land here, so pair the rating with a line for comments. One bad container can sit behind a month of complaints about a single dish. Read the comments item by item.
How was the food by the time you ate it?
Why ask it
Some dishes do not travel: fried things, dressed salads, anything that keeps cooking in its own steam. Ask which item suffered alongside the rating. A dish that scores well at the table and badly here needs different packaging or a place off the to-go menu.
If your order was delivered, did it arrive when you were told it would?
Why ask it
When an outside delivery service brings the food the delay may be out of your hands, yet the guest remembers the name on the bag. How complaints, refunds and late drivers are handled differs from one service to another, so ask your contact there how it works before promising a guest anything.
About you
How did you find out about our restaurant?
Why ask it
Whichever channel you pay for and nobody picks is the one to question. Give one choice from a list: walked or drove past, a friend or family member, a search or map app, a review site, social media, a delivery app, other. Show it to first-time guests only, since regulars rarely remember and will guess.
What made you pick us over other places to eat today?
Why ask it
If most guests say 'it was close', your competition is the sandwich shop next door and not the restaurant across town you measure yourself against. A dish named again and again is one to protect. Suggested answers: it was close, a particular dish, the price, someone suggested it, I come here often, an offer.
How often do you eat with us?
Why ask it
First visit, a few times a year, about once a month, a few times a month, weekly or more. Newcomers are reacting to a first impression and regulars to whether you are still what they liked, so a single average across both can mislead. Read the main scores for each group separately.
How many people were in your group?
Why ask it
Big tables stretch the kitchen and the server at once, so low scores from groups of five or more are about how large parties are handled and not about an ordinary night. Ranges are enough (1, 2, 3 to 4, 5 or more), with a checkbox for 'including children'. Drop the question if the check already records the number of guests.
Which meal was this: breakfast, lunch, dinner, or something in between?
Why ask it
Put brunch, happy hour and late night on the list if you serve them. Each shift is close to being its own restaurant, with other cooks, other servers and another manager. A score that is fine overall and poor at one meal hands a specific job to one person. With several locations, ask which one, or let the survey link carry it.
Do you live or work nearby, or were you visiting the area?
Why ask it
Locals are the repeat business, so a complaint from one of them is about every future visit. Visitors show how you look to someone with no history, and a room full of them means map listings and reviews matter more to you than a loyalty card would.
Would you like a manager to contact you about this visit?
Why ask it
Include it only if someone will reply within a day or two, because a request that goes unanswered is worse than no offer. Ask for a name and a phone number or email only on a yes, and keep the form anonymous otherwise. How long you may keep those details depends on the privacy rules where you operate, so find out what applies, and never treat this yes as permission to add someone to a mailing list.
Would you like to hear from us about new menus, events and offers?
Why ask it
Keep this apart from the question about a manager getting in touch, and leave the box empty until the guest checks it. Someone who agrees here is saying yes to marketing, which is a different thing from wanting a complaint answered. What a sign-up has to say and how consent has to be recorded differ by place, so check the rules where you operate before collecting an address.
Is there anything else about your visit you want us to know?
Why ask it
The closing box, optional and with no word limit. Expect praise for a person, a note about the parking lot, and now and then the real reason behind a low score at the top of the form. Have one named person read every entry each week.
How to build a restaurant survey guests will finish
Practical guidance for the conversation itself
Building the form
Choose eight to ten, not the whole page
A guest at the register, or in the car with a bag on the seat, will give you a couple of minutes at most. A short form that works for most places: the overall rating, coming back, taste, temperature, the service score, cleanliness, value, and one open box. Everything else on this page is a spare. Bring one or two in for a month when you have a reason, such as a new menu or a run of complaints about pickup, then take them out again.
Fit the form to where the guest meets it
A link or code on the receipt can run eight to ten questions and skip the ones that do not apply. A printed table card has no skip logic and is filled in with a server nearby, so hold it to four or five checkbox questions and give guests a box by the door to drop it in. A follow-up email to people who booked can go out the next morning, name the date of the visit, and run a little longer, because the guest is sitting down.
Let the check answer what it can
If the survey link carries the check number, your point-of-sale system already knows the date, the hour, the location, the dishes, the number of guests and often the server. Attach those and delete the matching questions. Each one you remove makes room for something only the guest can tell you.
Route dine-in and takeout guests apart
Place 'How did you place your order?' near the top of an online form and use it to branch. Someone who ate in the dining room should see nothing from the Takeout group, and someone who picked up a bag should skip the questions about the table, the restrooms and the noise. Where your survey tool cannot branch, run two short forms and print a different link on takeout receipts.
Give every question an owner
Before the form goes out, write a name beside each question: the chef for Food, the floor manager for Service, whoever runs online ordering for Takeout. A question nobody would act on is one to cut. The same list settles who phones the guest who asked for a call.
Wording and answer scales
Ask about one thing at a time
'Was your server friendly and fast?' cannot be answered by a guest whose server was charming and slow. Split it, or choose the half you would act on. The same trap hides in 'food and drinks', 'clean and comfortable' and 'price and portion'.
Facts get a yes or no, opinions get a scale
Whether the order was correct, whether someone checked on the table and whether the bag was complete are facts, and a five-point scale only blurs them. Taste, service and value are judgments and need the scale. For anything with a direction, such as noise, portion size or how long the food took, offer three choices with 'about right' in the middle.
Keep to one rating scale and label every point
Use the same five words, poor, fair, good, very good and excellent, for every 'how would you rate' question. A question that begins 'how clean' or 'how easy' needs words of its own, so give those five points too and keep the best answer on the same side of the page. Guests answer quickly, and a scale that reverses partway through the form collects mistakes. On a paper card print the words instead of a row of stars or faces, which different people read differently.
Offer a way out
'I did not use them', 'I did not order any' and 'this was my first visit' keep people from inventing an answer to get past a question. Without such an option, a guest who never saw the restroom gives it a three, and that three is noise in your average.
Do not point at the answer you want
'How delicious was your meal?' has already decided. So has a server who hands over the receipt and asks for a top score. Keep the wording flat, and tell staff they may mention the survey but never coach the answers.
Sending it and reading the results
Ask while the meal is fresh
A code on the receipt gets answered in the car or that evening, when the guest still remembers which plate was lukewarm. An email a week later gets a general impression. For takeout and delivery, send the link an hour or two after the handoff, since the food has to be eaten before anyone can rate it.
Thank everyone the same way
A small thank-you can lift the number of replies as long as it goes to everyone who finishes, whatever they said. A reward for a high score buys you high scores and nothing else. What you may offer, especially prize draws, can be regulated differently depending on where you are, so check before you print it on a receipt.
Break the scores down by shift, dish and day
A restaurant-wide average rarely sends anyone anywhere. The same number split by lunch and dinner, by weekday and weekend and by dish usually does: service is fine except on Sunday brunch, the food is fine except for one fried item on delivery. Go carefully when a group is small, because five replies are five stories and not yet a pattern.
Reply to unhappy guests quickly
Have low overall scores and every request for contact sent to a manager the day they arrive. A call or a note within a day or two, from someone who can say what was done about it, sometimes brings a guest back. Keep a simple log of what was promised and by whom.
Remember who fills these in
Delighted and annoyed guests are the readiest to answer, and many of the people in between never open the link. Read the results as a lead to follow, and check them against what you already hold: comps and voids, plates sent back, online reviews, repeat bookings. When the survey and the register disagree, look harder before changing anything.
Mistakes to avoid
Asking everything at once
A long form feels thorough and gets abandoned at the third screen, and the guests who do finish it are not typical of the room. If you cannot decide what to cut, rotate: keep five core questions fixed and swap the others month by month.
Letting scores land on one server without warning
If answers can be traced to a person and affect hours, sections or pay, staff will learn to steer who gets the survey. Say plainly how the results will be handled. How pay and reviews may be tied to feedback depends on your employment rules, so find out how it works where you are before you link them.
Making every question required
A guest who only wanted to tell you the soup was cold will close the form when it insists on an answer about parking. Require the overall rating at most. A skipped question costs you one data point, and a required one can cost you the whole reply.
Collecting answers and changing nothing
Guests who took two minutes and then saw the same wobbly table next month will not bother again. Fix one visible thing each round and say so, on the table card, the receipt or a sign by the door. Tell the staff first, with the comments that led to it.
Using the form in place of walking the floor
A survey reports a problem after the guest has gone home. A manager who stops at the table hears about it while the plate can still be replaced. Use the results to decide where to stand on a Saturday night and what to ask when you get there.
Steering only the happy guests to a review site
It is tempting to end the form with a link to your review page for anyone who scored you well and a private box for everyone else. Review sites set their own rules about asking for reviews, and some do not allow picking who gets asked, so read the rules of the one you use. If you invite reviews at all, show the same invitation to every guest.