Comment cards and QR feedback forms: questions, placement and who reads them

A comment card or QR feedback form is a short in-stay survey a guest completes before checkout. Five questions, one visible placement, the guest's own language, a named reader every morning and one owner for every comment turn it into an operating tool rather than a box nobody opens.

The review appears three days after checkout, and the leaking shower was never reported to anyone. The card in the room asked one question, "How was your stay?", and the box was opened once a month. This article covers the design of hotel comment cards and QR feedback forms end to end: the questions, the placement, the languages, the daily reading routine and the rule that closes every comment. After reading, you can put a working form in front of guests this week.

Why ask during the stay instead of at checkout?#

Because a problem found at breakfast can still be fixed before the guest writes a public review, while a problem found at checkout can only be apologized for.

Define the window in your own hotel: from the moment the key is issued to the night before departure. Anything outside that window is a different process with different tools. In-stay feedback is operational, not reputational. It should route to housekeeping, maintenance or the kitchen within the hour, not into a monthly marketing report.

The checkout conversation is a separate instrument: three spoken questions at the desk, run by a person who can act. Do not merge the two, because a form at the desk competes with the conversation. If you want the spoken version, see the check-out conversation and its three questions.

The trade-off is real. A form catches problems mid-stay but gets fewer answers than a direct question from a receptionist. Run both and keep them distinct. Two rules protect the guest's patience: never ask the same question twice in one stay, because a guest who already told the front desk about the noise does not want to type it into a form the next morning; and decide in advance what counts as urgent. Safety, health, theft, money and staff conduct leave the normal queue entirely.

Which five questions belong on a hotel comment card?#

Five questions, each tied to a decision someone in the building can make that same day.

Start with one overall question on a five-point scale, with both ends labelled in words, so the number means something without a legend. Then one open field, short and specific: "What one thing would you change about your room?" is answerable; "Any comments?" is not.

Add three questions tied to departments that can act: room cleanliness, sleep quality (noise, bed, air), and breakfast or the bathroom, whichever your complaint log shows most often. Cut anything you cannot act on. "Value for money" invites a pricing argument nobody at the desk can settle, and it produces a score with no owner. Ask about the moment, not the brand: "How was your room when you returned this afternoon?" gives a usable answer; "How satisfied are you?" gives a mood.

Every field on the card is a promise that someone reads it. If a question has no reader, delete it before printing.

Where should the QR code go?#

Where the guest is standing still with a reason to think about the stay, not where the hotel has wall space.

Test every placement physically: scan it from the actual spot, in the actual light, on an older phone, with the hotel Wi-Fi and without it. The guest must be able to act without asking a staff member what the code is for, so print the destination in words next to the code.

Give each placement its own short link, so you learn where answers come from, not just how many arrive. Avoid codes on receipts and bills, where the guest is already leaving, and codes at eye height in corridors, where nobody stops. Paper still works where hands are free and staff are present: restaurant tables, the breakfast room, the front desk. Keep a pen beside the cards.

One code per context is enough. A room with three stickers on three surfaces reads as pressure, not hospitality.

Which languages does the form need?#

The languages your guests actually arrive in at your hotel, taken from your own registration data, not from a list of ten.

Rank the nationalities in your last twelve months of registrations and build the form in the top few plus English. That is a decision you can defend; a generic list is a guess. Machine translation is acceptable for the question text, but someone on the team must be able to read a free-text answer in each language you offer, or know who to ask.

Plan the translation of answers for the same day. A comment translated at month end has already missed its window. Test right-to-left layout for Arabic on a phone, not a laptop, and check that the scale still reads left to right or is clearly reversed.

A five-point scale does not mean the same thing in every market. Label both ends with words so the middle is not read as polite agreement. Do not claim every language. Say which ones the form offers and what happens to an answer written in another.

Who reads the answers, and when?#

A named person reads every answer every morning before the operations meeting, and a second person covers days off and holidays.

Fifteen minutes, same time, same person. The routine matters more than the tool: a form read on Fridays only is a weekly form. Reading is not replying. First sort each answer into fix now, fix this week, or log only, and only then decide who speaks to the guest.

The reader needs the authority to open a work order, not just the duty to report one. Otherwise the form creates a queue in front of another queue. Keep one log: date, room, department, comment, owner, action, closed date. One log, not four spreadsheets owned by four departments.

Set an alert rule: any comment about safety, illness, theft or a staff member's conduct goes to the manager within the hour, not the next morning. Once a week, count comments by department and by theme; once a month, read them next to your review scores, so the two pictures are compared, not kept apart. For the difference between these signals, see guest satisfaction metrics and how review scores differ from complaint rates.

How does a comment get closed?#

Every comment gets one owner, one action and a closing date, and the guest hears back before checkout if they are still in the house.

The department that can fix the problem owns the fix. Guest relations owns the follow-up, not the repair, and the two are recorded separately. While the guest is in-house, a short word at the desk or a note in the room is enough. After departure, the reply belongs to the complaint process, with its own fields and its own record; the fields a guest complaint record needs are a separate design question.

Close with evidence: a work-order number, a photo, or a line saying what changed. "Guest satisfied" with no contact behind it is not a closure. A comment that repeats is a process problem, not a guest problem. Group repeats monthly by department and by cause before assigning more training, using the method for finding the real cause in a complaint log.

Report the closure rate to the team weekly. A comment open for a month is a decision nobody made. Keep the guest's own words in the record, unedited, next to the action taken. Rewriting a comment in the log loses the detail that made it useful.

What about privacy on a feedback form?#

A feedback form collects personal data from the first field, so treat it as personal data from the first field.

Ask only what you will use. A room number is enough to route an answer; a name and a phone number are only needed if you intend to reply. Offer an anonymous option and state plainly what it costs: no reply is possible, and the guest should know that before writing.

Put one sentence on the form saying what happens to the answer, who reads it and how long it is kept. Free text can contain health details or other sensitive information. Do not copy it into public channels, marketing material or staff group chats.

Confirm retention periods and consent wording with your legal adviser. The general duty sits in KVKK (kişisel verilerin korunması kanunu, Türkiye's personal data protection law); the specifics depend on your own case. Never publish a guest's comment or photo without written permission, even a positive one.

What to do next#

Choose the five questions, name the person who reads them every morning, and put one code in one tested place this week. Run it for a month, then read the log rather than the count: if comments are closing with an owner and a date, the form is working; if they are not, the problem is the routine, not the card.