Feedback at the table, asked properly

The server clears the main course plates and asks the question every guest has heard a thousand times: "How was everything?" The guests smile and say "Lovely, thanks." Two days later, one of them posts a review saying the steak was overcooked and the service slow. The server had asked. The guest had answered. Neither had said anything real.

Feedback at the table is the most valuable feedback a venue can get, because it arrives while the guest is still there and the problem can still be fixed. But most venues waste it, by asking a question so familiar that it has become a pleasantry rather than a question. Guests answer politely, and the venue hears nothing.

This guide covers why the usual question gets nothing, the questions that get a real answer, when to ask, what to do with what you hear and how to record it so the whole team learns. Every venue and figure in it is an example.

"How was everything?" is not really a question. Guests hear it as a ritual, like "how are you?", and give the ritual answer. It is too broad to answer honestly, it is asked at a moment when the plate has already gone, and most guests do not want to make a fuss in front of their companions.

There is also a social pressure, and it matters, because customer satisfaction that is never voiced is never measured. Telling a friendly server that the food was disappointing feels rude, especially when the server seems to have done their best. So guests say it was lovely, and save the truth for later, or for a review.

The result is a venue that believes its guests are happy, right up to the moment the reviews say otherwise.

The fix is to ask a specific question. "How is the lamb?" is easier to answer honestly than "how is everything?". "Is the steak cooked how you like it?" invites a real answer. "Did the risotto have enough seasoning for you?" shows the server genuinely wants to know.

Specific questions tell the guest you are interested in the answer, not just going through the motions. They also make it easier for the guest to mention a problem, because you have asked about the very thing they might want to raise.

Each course needs its own question. With starters, ask about the dish the guest chose: "How are the scallops?" With mains, ask about cooking and seasoning: "Is the steak as you like it?" With desserts, ask simply whether they are enjoying it. With drinks, ask whether the wine is what they hoped.

Different questions at each course tell the guest you are paying attention to their meal, not reciting a script.

Timing matters as much as wording. Ask within the first two minutes of the food arriving, after the guest has tasted it. At that moment, a problem can still be fixed: a steak can be cooked a little more, a cold dish replaced, a missing sauce brought.

Asking after the plates are cleared is too late. The guest has eaten the disappointing dish, and the only thing left to offer is an apology. Early feedback at the table turns problems into recoveries.

Good servers watch before they ask. A guest pushing food around the plate, a full plate after ten minutes, a guest looking around for the server, a dish barely touched: each is feedback before a word is spoken.

When you see a sign, go to the table and ask specifically: "I noticed you haven't had much of the fish. Is it not quite right?" Guests who would never volunteer a complaint will often answer a question that shows you noticed.

Regulars are often the most honest source of feedback, because they know the venue well and want it to stay good. Ask them directly: "You've had the lamb a few times. Is it as good as it was?" or "Is there anything you miss from the old menu?"

Regulars notice changes that new guests cannot: a recipe that has changed, a portion that has shrunk, a server who has left. Their feedback is an early warning worth listening to.

Make it easy for the guest to be honest. Ask in a tone that invites a real answer, not a polite one. Lean in rather than standing over the table. Show you are ready to fix something, not to defend it.

Some servers find it helps to give the guest permission: "Be honest with me, is it how you hoped?" That small phrase tells the guest that criticism is welcome, and many will take the opening.

Complaints and feedback overlap, but they are not the same. A complaint is a guest telling you something went wrong and expecting it to be put right. Feedback is any information about the guest's experience, good or bad, which may or may not need action.

Treat both seriously, but differently. A complaint needs a response at once: an apology, a fix and a check that the fix worked. Feedback needs recording and, over time, acting on. Our guide to guest complaints: the first thing to say covers the complaint side.

When a guest raises a problem, the response in the first few seconds matters most. Stop, listen and do not interrupt. Thank them for telling you. Apologise for the experience, without arguing about whether it was really a problem. Then say what you will do, and do it quickly.

Service recovery done well can leave a guest happier than if nothing had gone wrong, because they have seen the venue care. Our guide to service recovery: putting a bad night right covers what to offer.

A problem raised at the table should reach the kitchen and the manager quickly. The kitchen needs to know if a dish was cooked wrongly or tasted off, so it can check other plates and fix the cause. The manager needs to know so they can visit the table if needed and decide on any gesture.

Make it a standard: every complaint at the table is passed to the manager straight away, and every food problem to the kitchen. Our guide to service standards written as actions, not values covers how to write standards like this.

Feedback at the table is not only about problems. When a guest says the lamb was the best they have had, pass it on to the kitchen. When they praise a server, tell the server and the manager. Good feedback is information too: it tells you what to keep doing.

It also builds morale. A kitchen that hears guests' praise, not only their complaints, works with more pride. A server who hears that a guest loved their recommendation recommends with more confidence.

Guests sometimes give feedback about a member of staff, good or bad. Praise should be passed on to the person straight away, and to the manager. Criticism should go to the manager, privately, and be handled fairly.

Never discuss a guest's criticism of a colleague in front of other guests or staff. Thank the guest, tell them you will look into it and do so after service.

Occasionally, a guest's complaint is unreasonable: a dish criticised for being exactly what the menu described, a demand for a free meal after eating every bite. Even then, listen and stay calm. Explain politely, offer what is fair and involve a manager if needed.

Record unreasonable complaints too. Most are one-off, but a pattern of similar complaints about the same dish may mean the menu description needs changing.

A manager visiting tables during service hears feedback that servers do not. Guests sometimes tell a manager what they would not tell their server, either because they do not want to get the server in trouble or because they feel the manager can do more.

Visit a few tables each service, briefly, with a specific question: "How did you find the new menu?" or "Is everything as you hoped tonight?" Keep it short, so it does not feel like an interruption.

The last good moment to ask is before the bill, when the meal is nearly over. A short, sincere question, "Was there anything tonight that wasn't quite right?", gives the guest one last chance to raise something while you can still do something about it.

A guest who mentions a problem before paying can be offered a gesture on the bill; one who mentions it after leaving can only be offered an apology by email, if you know who they are.

Some guests prefer to give feedback in writing rather than to a person. A short feedback form at the end of the meal, on a card, on the guest's phone or on a tablet handed over with the bill, lets them say what they would not say aloud.

Keep it short: an overall rating, a few specific ratings and one open box. Make it clear that the guest can stay anonymous if they wish. Our guide to survey questions that get answered honestly covers what to ask.

Families often give feedback about different things: whether the children's options suited the children, whether there was space for a pram, how quickly the children's food arrived. Ask parents directly, because they rarely volunteer it.

Small changes, such as bringing children's food first or offering crayons, can make a large difference to how a family remembers the visit, and whether they come back.

In a busy service, there is little time for long conversations, but a specific question still takes only a few seconds. "Is everything cooked how you like it?" asked while topping up water costs nothing and can catch a problem early.

If a guest has a lot to say and the floor is busy, listen briefly, deal with anything urgent and offer to come back, or ask the manager to visit the table.

Feedback heard at the table is lost unless it is recorded. A server who hears that the risotto was too salty, and tells nobody, has wasted the most useful feedback of the night.

Agree a simple way to record it: a note at the pass, a line in the shift report, a note on the guest's profile if they are a regular. Record good and bad, with the dish, the table and the time. Over a few weeks, patterns appear.

Share what you hear at the next pre-shift briefing: the praise, the complaints and the patterns. "Three tables said the risotto was too salty this week; the kitchen has adjusted the recipe." "A guest at table nine said Sam's wine recommendation made their evening."

Sharing feedback shows the team that it matters, and turns it into changes. A team that hears guests' feedback every day learns faster than one that only hears about reviews.

Asking for feedback is a skill, and it can be taught. Train servers to ask specific questions, to ask early, to watch for signs and to respond well when a guest raises a problem. Role-play helps: one server plays a guest with a mild complaint they are reluctant to mention, and the other practises drawing it out.

Make feedback at the table part of the service standards, with a clear routine: a specific question within two minutes of the food arriving, a check before the bill, and every complaint passed to the manager.

Some guests will never raise a problem at the table, however well they are asked. They prefer to leave quietly and decide not to return, or to write about it later.

For those guests, written feedback after the visit is the safety net. A short survey sent the next morning, with the option of staying anonymous, catches some of what the table missed. Our guide to guest feedback you can actually act on covers bringing the two together.

Thank every guest who gives feedback, good or bad. A guest who has taken the trouble to tell you something, especially something critical, has done you a favour. "Thank you for telling me, I'll make sure the kitchen knows" shows the feedback was welcome.

Guests who are thanked for feedback are more likely to give it again, and less likely to save it for a review.

Some venues leave a small card or a code on the table that guests can use to give feedback on their phone before they leave. It catches guests who would not say anything aloud but are happy to tap a rating.

Keep it short, make it optional and never use it as a replacement for asking in person. The card is a safety net, not a substitute for a server who cares about the answer.

Guests at the bar give feedback differently: they chat with the bartender, and feedback comes as part of the conversation. A good bartender listens for it and passes on what matters, such as a cocktail that disappointed or a snack guests keep asking for.

Bring bar feedback into the same record as the dining room's, so the whole venue's feedback can be seen together.

Some feedback cannot be acted on: a guest who wishes the venue were in a different neighbourhood, a request for a dish that does not fit the menu, a complaint about something outside your control. Thank the guest, record it and move on.

Recording it still has value. If many guests ask for the same thing, it may become something you can act on later.

An invented bistro's servers ask "how was everything?" as they clear plates. Guests always say it was lovely, yet the bistro's reviews mention overcooked steaks and slow service several times a month.

The bistro changes its routine. Servers ask a specific question about each main within two minutes of serving it, and a final question before the bill: "Was there anything tonight that wasn't quite right?" Every complaint goes to the manager, every food problem to the kitchen, and feedback is shared at the next briefing.

Within a month, servers are hearing about problems while they can still be fixed: a steak sent back to the grill, a cold side replaced. The reviews mentioning overcooked steaks stop, and the kitchen adjusts its timing on the grill after hearing the same comment four times in a week.

In servearound, guests can give written feedback at the table from the menu they open with the table's QR code, once their order is in: an overall rating, ratings for the food, the service and the ambience and a comment, with the choice of a reply or staying private. Staff can also hand the tablet to the guest from a booking and collect feedback there and then.

The feedback sits on the guest's profile alongside notes from the team, visit history and what they ordered, so the next booking is taken by someone who knows how the last visit went. The team sees every response, the average rating and which guests are happy to be contacted, and can send a follow-up email to those who asked for one. See Guest CRM and Order Fulfillment.

Guests hear it as a pleasantry and give a polite answer, especially when it is asked as the plates are cleared.

A specific question about the dish, such as "Is the steak cooked how you like it?", soon after the food arrives.

Within two minutes of the food arriving, and once more before the bill.

Listen, thank them, apologise, say what you will do and do it quickly, and tell the manager.

No. Complaints need a response at once; feedback needs recording and acting on over time.

Yes. It tells you what to keep doing, and it lifts the team's morale.

Offer written feedback, at the table or after the visit, with the option of staying anonymous.

Record it, share it at the briefing, look for patterns and act on the ones that repeat.

Feedback at the table is the most valuable feedback a venue can get, because problems can still be fixed. Stop asking "how was everything?" as plates are cleared. Ask a specific question within two minutes of the food arriving, watch for signs before you ask, make it easy for the guest to be honest and ask once more before the bill.

Respond to problems at once, pass every complaint to the manager and every food problem to the kitchen, record good and bad feedback, share it at the briefing, train servers to ask well and offer written feedback for the guests who will not say anything aloud.