Restaurant Feedback Form Template and Questions
Copy a short restaurant feedback form, choose the right questions, and route each guest response to the location team that can act on it.
A useful restaurant feedback form should take less than two minutes, identify the correct location, and give the team enough context to act. It should not feel like a market-research project at the end of dinner.
Start with the short template below. Add diagnostic questions only when somebody will use the answers.
Copy this short restaurant feedback form
1. Which location did you visit?
Pre-fill this from a location-specific QR code whenever possible.
2. When did you visit?
- Today
- Yesterday
- Choose another date
Optional: ask for the approximate time or order number when the team may need to investigate.
3. Overall, how was your experience?
Use a five-point scale with clear labels:
- Very poor
- Poor
- Okay
- Good
- Excellent
4. What would you like us to know?
Use one open text field:
Tell us what happened, what worked well, or what we should improve.
5. What was this mainly about?
- Food or drink
- Service
- Wait time
- Cleanliness
- Delivery or packaging
- Billing or payment
- Accessibility
- Something else
6. Would you like a reply?
- No, I only wanted to share feedback
- Yes, please contact me
Show name, email, or phone fields only when the guest asks for a reply. State who will receive the details and what they will be used for.
That is enough for the default flow. It gives the team a location, visit window, overall signal, issue theme, guest account, and permission to follow up.
Why this structure works
Each question has an operational purpose.
| Field | Decision it supports |
|---|---|
| Location | Which team owns the case |
| Visit date and time | Which shift, order, or service period to inspect |
| Overall score | How urgently the signal needs review |
| Guest comment | What actually happened |
| Theme | Which manager or department should receive it |
| Reply preference | Whether follow-up is expected |
| Contact detail | How the team can close the loop |
If a field does not change routing, investigation, analysis, or follow-up, consider removing it.
Make the location automatic
Do not begin with a dropdown containing 40 restaurant names if the QR code is already sitting inside one restaurant.
Create a separate QR code or short link for every location and carry the location ID into the form. Show the detected location at the top so the guest can correct it when necessary.
This small design choice:
- shortens the form;
- prevents feedback being assigned to the wrong outlet;
- makes location-level reporting more reliable;
- lets every case start with a clear owner.
Add diagnostic questions carefully
Use the short form for continuous feedback. Use a longer restaurant survey when the team has a specific question to answer.
Useful optional ratings include:
- food quality;
- friendliness;
- speed of service;
- order accuracy;
- cleanliness;
- value for money;
- delivery condition;
- likelihood to return.
Do not make all of them mandatory. A guest reporting a payment error should not have to rate six unrelated parts of the meal before reaching the comment box.
For a larger question bank, see restaurant survey questions.
Route feedback by meaning, not only by score
A low overall score needs attention, but certain words or themes may be more urgent than the rating suggests. The following is an example operating model, not a universal service standard.
| Signal | Example route | Example next step |
|---|---|---|
| Food safety or allergen concern | Duty manager and designated food-safety owner | Review immediately and preserve order details |
| Threat, harassment, or staff safety | Senior operations owner | Restrict access and escalate under company policy |
| Payment or billing issue | Location manager and finance owner | Verify receipt, order, and payment record |
| Delivery damage or missing item | Delivery or dispatch owner | Check packaging and handoff |
| Long wait or poor communication | Location manager | Review shift conditions and guest communication |
| Compliment naming a team member | Location manager | Recognize the employee |
| General suggestion | Normal feedback queue | Tag for recurring-theme review |
Use a named owner, due time, status, and internal note. An email alert alone does not create accountability.
A simple case workflow
Every response that needs action can follow the same sequence:
- New: the feedback has arrived.
- Triaged: the location and issue type are confirmed.
- Assigned: one person owns the next step.
- In progress: the team is investigating or following up.
- Resolved: the action and guest outcome are recorded.
- Learned: the issue is tagged for location or group analysis.
The guest-facing reply and the internal fix are related but different. A warm apology does not repair a recurring packaging fault. A repaired process does not remove the need to acknowledge the guest.
Where to place the feedback form
At the restaurant
- A small QR code on the receipt or billing folder
- A table card that does not compete with the menu
- A sign near collection or takeaway
- A link on the digital receipt
After the visit
- Reservation thank-you email
- Post-delivery SMS or WhatsApp
- Loyalty-app visit history
- Event follow-up email
On the website
- Contact or feedback page
- Location page
- Order-confirmation or support page
Use a direct invitation:
Tell the [Location] team about your visit. Share feedback privately or choose a public review option.
Do not label a long survey “quick” unless it is actually quick.
Keep public reviews transparent
Private feedback is valuable, but it should not become a filter that sends only high-scoring guests to Google. Offer the public review choice consistently instead of revealing it after a positive score.
Google says reviews must represent genuine experiences and prohibits incentives offered in exchange for reviews. Its official instructions explain how to create and share a review link or QR code.
Read the full restaurant Google review request playbook before joining the private and public flows.
Contact and consent copy
Keep consent specific and readable. For example:
If you request a reply, [Restaurant Group] will use the contact detail you provide to follow up on this feedback. See our privacy notice for how we store and delete this information.
Do not preselect marketing consent. A guest asking for help with a meal is not automatically subscribing to promotions.
Adapt retention, escalation, and privacy language to the laws and company policies that apply to your operation.
How to review the results
The dashboard should answer:
- How many feedback cases are open?
- Which ones are overdue?
- Which themes are increasing?
- Which locations resolve cases consistently?
- Which issues recur after being marked resolved?
- How many guests requested contact?
- Did the team record the action taken?
Avoid ranking locations only by average score. A small outlet with three responses and a flagship with 300 responses do not have equivalent evidence. Show response counts and time periods beside every comparison.
Frequently asked questions
How many questions should a restaurant feedback form have?
Use five or six short questions for the continuous form. Add more only for a defined research purpose. Completion and action quality matter more than collecting every possible metric.
Should contact details be required?
No. Let guests share feedback anonymously or without a reply. Ask for contact details only when follow-up is requested or when there is another clear, disclosed reason.
Should every low rating trigger an alert?
Not necessarily. Route by rating, theme, language, location, and operating risk. A food-safety concern can matter even when the guest selects a middling score.
Can the form ask guests to leave a Google review?
Yes, but do not use the private score to decide who receives the invitation. Keep the Google option neutral and available under a consistent rule.
What should happen after a guest submits the form?
Confirm receipt, show the expected follow-up channel, and create a case for anything that needs action. The internal record should include a location, owner, status, and next step.
Breeze turns location-specific guest feedback into an assigned, visible follow-up process. Explore the guest feedback platform.