RESTAURANT FEEDBACK TEMPLATE
Prepared by ScanPlz | Updated 14 October 2026
Guide: https://scanplz.com/guides/restaurant-feedback-form

Replace [Business name] and check the wording before sharing.
This is suggested wording for paper or a form tool. Match it to the fields
available in your setup; it is not a ScanPlz form import file.

INTRODUCTION
How was your visit to [Business name]?
Share feedback with our team so we can understand what worked and what needs
attention. You may leave out your name and contact details.

1. OVERALL EXPERIENCE
How would you rate your visit?
[ ] 1 Very poor  [ ] 2 Poor  [ ] 3 Okay  [ ] 4 Good  [ ] 5 Excellent

2. MAIN TOPIC
What is your feedback mainly about?
[ ] Food and drinks  [ ] Service  [ ] Cleanliness  [ ] Value  [ ] Something else

3. YOUR COMMENT
What went well, or what is one thing we could improve?
________________________________________________________________________
________________________________________________________________________

4. OPTIONAL FOLLOW-UP
If you would like a reply, leave your preferred contact detail and tell us
we may contact you about this feedback.
Name (optional): ________________________________________________________
Preferred email or phone (optional): ____________________________________
[ ] You may contact me about this feedback.

Thank you for sharing your experience. If you need help during your visit,
please speak to a member of staff.

TABLE-CARD WORDING
Share feedback about your visit to [Business name].
Scan to send a comment to our team. You may leave out your contact details.
[Place your business's tested feedback QR code here.]

STAFF CHECKLIST (keep this part for your team)
[ ] Check the code opens the intended business, branch and table/area.
[ ] Submit a test without personal details and confirm it is received.
[ ] Choose who checks responses during service and who covers their absence.
[ ] Record the issue, responsible person, next action and outcome.
[ ] Reply only when a guest requests contact and gives a usable contact detail.
[ ] Review repeated themes each week.
[ ] Invite honest public reviews equally; keep discounts separate from reviews.

For table-specific forms, use the context supplied by that code. For a paper
form, add a branch/table field only when it will help your team act.