The comment card on the table asked four questions and was collected by whoever cleared the plates. Most of them were blank, a few said the food was lovely, and once a month one of them said something that changed how the kitchen worked. The replacement is a QR code, and it collects a great deal more, which turns out to create a new problem rather than remove the old one.
A restaurant now hears from three separate groups of customers who had three unrelated experiences. Someone who sat at a table for two hours. Someone who collected a bag at the counter and ate at home twenty minutes later. Someone who never saw the restaurant at all because a delivery rider brought the food. Asking those three the same questions produces answers that cannot be compared and complaints that cannot be routed.
What follows is how to split that up, and what to do with the small number of submissions that need somebody in the next ten minutes rather than at the weekly meeting.
Three channels, three different forms
The temptation is one form with a first question asking which channel the customer used. It works, and it costs a step at the exact moment when the customer is deciding whether to bother. Where the code is printed already identifies the channel, so the question is redundant.
| Channel | Where the form lives | What only this channel can tell you | Who acts on it |
|---|---|---|---|
| Dine in | Table card, receipt, or the payment screen | Service, pace, noise, temperature of the room, cleanliness | Floor manager, same shift |
| Takeaway | Receipt and the bag sticker | Packaging, accuracy of the order, wait at the counter | Counter lead and kitchen |
| Delivery | Insert card in the bag | Arrival temperature, spillage, missing items, timing | Kitchen and whoever manages the platforms |
| After a complaint already made in person | A link sent in the follow up | Whether the fix actually landed | Owner or general manager |
Three short forms are less work than one long one, because each can drop the questions that make no sense for it. Nobody eating at home needs to rate the friendliness of the staff, and nobody who sat at a table has an opinion about the packaging.
The questions that separate the kitchen from the floor
A restaurant has two operations that fail in different ways, and a form that cannot tell them apart produces an average score that nobody can act on.
Four or five questions is the working length for dine in.
The food. One rating, and one open box under it. The open box matters more than the rating, because "the pasta was cold" and "the pasta was bland" go to different people. A cold plate is a timing and pass problem. A bland plate is a recipe or seasoning problem. The number alone hides which.
The service. One rating. This is where pace usually surfaces, which is the most common complaint in a full restaurant and the one guests are most likely to leave rather than raise at the time.
The wait. Either for a table or for food, depending on the format. Worth its own question because it is the single most reliable predictor of a low overall score, and because it is fixable by scheduling rather than by training.
One open question, asked narrowly. "What is the one thing that would have made this better" gets specific answers. "Any other comments" gets "everything was lovely, thanks" and an occasional essay.
The dish, if it can be asked cheaply. A short list of that day's menu, or a free text field. Without it, a run of complaints about one item is invisible inside a general drop in the food score.
Do not ask for a table number on a public form. Most guests do not know it, and the ones who do will guess. The timestamp and the service period locate the visit closely enough for almost every purpose.
Where the code goes, and what that changes
Placement decides who answers, which in turn decides what the data means.
A card on the table is read during the meal, so it collects the things that are true in the middle of a visit. It also collects complaints while the guest is still in the room, which is the only point at which anything can be rescued. That is worth more than the measurement.
A code on the receipt is read after paying, sometimes days later, which produces calmer and more complete answers about the whole visit. The response rate is lower.
A code on a payment screen or terminal gets the highest response rate of the three, and the shortest answers, because the customer is standing there waiting to leave. Keep that version to two questions at most.
There is also a difference in who answers. A table card is answered by the person who noticed something, which skews towards the guest who was unhappy and the guest who was delighted, with the middle staying silent. A receipt code reaches anyone who paid, which produces a flatter and more representative set of ratings. Neither is wrong, but a score collected one way should not be compared with a score collected the other way and read as a change in the restaurant.
A printed insert in a delivery bag is opened at home, at the moment the food comes out, which is why it is the only sensible way to ask about temperature and spillage. A code printed only on the outside of a bag that gets thrown away on the doorstep collects very little.
Delivery and takeaway, where the restaurant controls half the experience
The awkward part of delivery feedback is that a share of it is about something the kitchen cannot touch. The food left correct and hot, the rider took a long route, and the review lands on the restaurant.
Splitting the questions is what makes those submissions usable. Ask about the food separately from the arrival. Ask whether the order was complete, because missing items are the most common delivery complaint and they are a packing problem with a cheap fix. Ask roughly how long it took to arrive, not to measure the platform but to know whether a cold pizza was cold at the door or cold in the kitchen.
That split also gives the restaurant something to take to the platform, which is a conversation that goes better with a month of dated submissions than with an impression. Internally it separates three fixes that look identical from a score: change the container, change the packing check, or change how long the food sits on the shelf before collection.
Do not ignore the submissions that are purely about the rider. They are still the customer's experience of the meal, and the reply that acknowledges it costs two sentences.
The complaints that cannot wait for the weekly read
Almost everything a feedback form collects can be read once a week. Two categories cannot.
Anything mentioning an allergy or a reaction. This needs to reach a named manager immediately, be recorded with the time, the dish and the exact wording, and be answered by a person. It is also the clearest case for keeping the whole history of a submission in one place, because the follow up may matter months later.
Anything mentioning illness after a meal. The same urgency, plus a record of what was checked. Two unrelated reports in the same week about the same dish is the signal, and it is only visible if both were tagged rather than answered and closed in separate inboxes.
The mechanism for both is a threshold rule and an owner. Submissions containing certain words, or below a certain rating, go straight to one person by a channel that person actually watches. Everything else waits. Giving every response an owner and a state, so that anyone can see whether a serious one has been answered, is the part that makes the rule real rather than aspirational, and it is what response management is for once volume passes a few a week.
Feedback that names a member of staff
A public form will produce submissions naming individuals, in both directions, and neither is straightforward.
Praise is the easy half and still gets mishandled by being read silently. Named praise passed on in front of the team is one of the cheapest things a manager has available.
Complaints about a person need a slower path. A single submission is one side of one interaction, and acting on it as fact damages trust with the floor faster than almost anything else. Record it, tag it, and treat the pattern as the evidence rather than the incident. If three submissions across a month describe the same behaviour from the same shift, that is a conversation. One is a note.
That is also an argument for keeping the raw text rather than only a score. The wording is what distinguishes a guest who was rushed at a busy service from a guest who was treated badly, and a rating cannot hold that distinction.
Counting by service period, not by month
A monthly average across a restaurant is close to useless, because it mixes a quiet Tuesday lunch with a full Saturday night, and those are different operations with different staff.
The comparisons that produce decisions are narrower. By day part, which separates lunch from dinner. By day of week, which is where staffing errors show up. By shift, which is where training shows up. By dish, which is where the kitchen can act. By channel, since dine in and delivery scores moving in opposite directions is a common and informative pattern.
None of that needs a sophisticated tool. It needs a consistent tag set, a timestamp, and an export that carries the internal notes as well as the customer's answers. Enough restaurants discover at the point of analysis that their form tool exports only the raw questions that it is worth checking before the data is needed.
Volume is the other thing to be honest about. A single site collecting a handful of submissions a week does not have enough to read a trend at all, and treating a two point drop as a signal will send the kitchen chasing something that was three quiet Tuesdays. At that volume the right unit is the individual submission: read every one, answer the ones that need answering, and wait until a complaint appears three times before changing anything in the operation.
What to change first
Split the one form into a dine in version and a delivery version, and print the delivery one on a card that goes inside the bag rather than on the outside. Then set the threshold rule: anything mentioning an allergy, a reaction, or a rating at the bottom of the scale goes to one named person straight away, and everything else waits for a weekly read with tags applied. If the current form has no way to give a submission an owner and a state, that is the piece to replace, and a short look at a working setup will show whether it changes anything before any commitment is made.
Q1. What questions should a restaurant feedback form ask?
Four or five for dine in: a rating for the food with an open box under it, a rating for service, a question about the wait, one narrow open question asking for the single thing that would have improved the visit, and the dish if it can be asked cheaply. The open box under the food rating is the most valuable field, because it separates a timing problem from a recipe problem.
Q2. Where should the QR code for a restaurant feedback form go?
On the table if the aim is to catch problems while the guest is still present, on the receipt if the aim is a calmer account of the whole visit, and on a card inside the delivery bag for delivery orders. A code printed only on the outside of a bag collects very little, because the bag is usually discarded before anyone thinks about the food.
Q3. How should delivery feedback be handled when the platform delivered it?
Ask about the food and the arrival as separate questions, and include one about whether the order was complete. That separation shows whether a cold dish was cold at the door or cold in the kitchen, and it gives the restaurant dated evidence to raise with the platform. Submissions about the rider still deserve a reply, even when nothing in the kitchen caused them.
Q4. What should happen when a feedback form mentions an allergic reaction?
It should reach a named manager immediately rather than waiting for a weekly review, and the dish, the time and the exact wording should be recorded with the response. Reply as a person, not with a template. Keeping the whole history attached to that submission matters, because the follow up can continue for weeks.
Q5. Should a restaurant act on one complaint about a member of staff?
Record it, and treat the pattern rather than the incident as the evidence. One submission describes one side of one interaction, and acting on it as established fact costs more trust with the team than the complaint is worth. Several submissions across a month describing the same behaviour on the same shift is a different matter and is worth a conversation.