Every survey question needs a decision, an owner and a useful time window.
Before writing a question, write the decision it should inform. “How was your stay?” may produce a score, but it does not say whether reception, rooms, breakfast or management should respond. “How comfortable was your room last night?” has a clearer owner and can still lead to help while the guest is present.
The question also needs a time window. An in-stay pulse is for recovery now. A checkout check finds unresolved friction. A post-stay survey is better for patterns, value and return intent. Mixing all three jobs into one long form makes the survey slower for the guest and harder for the team to interpret.
Start with one of three short hotel survey templates.
The interactive workshop below contains a two-question in-stay pulse, a four-question checkout check and an eight-question post-stay review. Remove anything the hotel cannot use. A shorter relevant survey is more respectful than a comprehensive form built for somebody else’s property.
These are starting points, not universal standards. A resort, airport hotel, serviced apartment and small country inn have different facilities, arrival constraints and service owners. Keep the structure; change the questions only where the hotel can explain why.
Build the shortest survey that can change a decision.
Select a stay moment, remove questions your team cannot act on and copy the useful remainder. Nothing is submitted or stored.
Use this when the hotel can still improve the current stay. Keep the first question broad and reveal detail only when it changes the response.
2 questions selected
Use a short departure check to identify unresolved friction without turning reception into an interview.
4 questions selected
Use this set for experience learning. Keep optional service questions conditional so guests only see what applied to their stay.
8 questions selected
Twenty-five questions, grouped by the hotel decision they support.
Do not place all twenty-five questions in one survey. Choose one or two from the stay stages the guest actually experienced. Conditional logic should hide breakfast, spa, parking or accessibility questions when they do not apply.
Write neutrally. “How would you rate our excellent breakfast?” asks for agreement. “How would you rate the breakfast, if you used it?” leaves room for a genuine answer and a valid not-applicable choice.
| Decision area | Questions to choose from | Likely owner |
|---|---|---|
| Arrival | 01 How smooth was check-in? · 02 Did the team make you feel welcome? · 03 Was your room ready when promised? | Front office |
| Room experience | 04 Did the room match its booking description? · 05 How would you rate cleanliness? · 06 How comfortable was the room? · 07 Was it quiet enough? · 08 Did the room amenities meet the stated offer? | Rooms division |
| Service | 09 How helpful and courteous was the team? · 10 Was your request handled clearly? · 11 If you reported an issue, was it resolved? · 12 Were agreed accessibility arrangements ready? · 13 Was practical hotel information easy to find? | Guest services |
| Food, facilities and connection | 14 How would you rate breakfast? · 15 How would you rate dining, if used? · 16 How well did the facilities meet expectations? · 17 How reliable was the Wi-Fi? | Relevant department |
| Departure and value | 18 How smooth was checkout? · 19 Was the final bill understandable? · 20 How would you rate value for the price paid? · 21 Overall, how would you rate the stay? | Front office / management |
| Future and open response | 22 How likely are you to recommend the hotel? · 23 How likely are you to return? · 24 What was the highlight of your stay? · 25 What should we improve first? | Management / CRM |
Use a consistent scale, then ask for context only when it helps.
A five-point satisfaction scale is easy to understand and compare. A zero-to-ten recommendation question serves a different purpose and should not be silently converted into the five-point average. Yes-or-no questions suit factual checks; open text explains why, but asks for more effort and needs somebody to read it.
Conditional follow-up protects attention. A room-comfort score of one or two can reveal “What should the team look at first?” A score of four or five does not need the same recovery field. Always provide “not applicable” when a service may not have been used, otherwise non-use becomes a false neutral or negative score.
| Format | Use it for | Do not use it to claim |
|---|---|---|
| Five-point scale | Satisfaction with one defined experience | That a guest will recommend or return |
| Zero-to-ten recommendation | Recommendation intent with a stated scoring method | A complete explanation of the stay |
| Yes / no / not applicable | A factual check or whether a service was used | The strength of feeling behind the answer |
| Open text | Cause, context and the guest’s own priority | A clean trend without review and coding |
Low feedback should open a recovery path—not disappear into a dashboard.
Agree the threshold, owner and response time before inviting in-stay feedback. A low room-comfort score may need guest services immediately; a recurring note about confusing parking directions may belong in the next weekly operations review. Urgency comes from the guest situation, not the colour of a chart.
Keep private feedback and public reviews as separate choices. Asking every guest for an honest public review is different from steering only happy guests to a review site or hiding negative sentiment. UK CMA guidance addresses fake, concealed-incentive and misleading review practices; the safe operational principle is straightforward: never predetermine the sentiment you are willing to hear.
See how short surveys, conditional follow-up and named recovery ownership fit into one hotel-controlled workflow.
↗Collect less data, explain the purpose and make the form usable.
Anonymous feedback can remain anonymous. If a response is linked to a guest or stay so the hotel can follow up, define the purpose, lawful basis, access, retention and deletion process before collection. Do not ask for demographic or preference data merely because the survey tool offers the field.
A survey also has to work without perfect sight, dexterity or concentration. Use real labels, group related controls, explain required fields before they appear, provide a visible focus state and announce whether submission succeeded. The W3C forms guidance is a practical implementation baseline.
- State why the hotel is asking and whether the response is anonymous or linked to a stay.
- Mark optional questions as optional; do not force open-text explanations.
- Provide labels that remain visible instead of relying on placeholder text alone.
- Make each rating target large enough to use by touch and keyboard.
- Offer “not applicable” where a guest may not have used the service.
- Define who can read free text, especially where it may contain sensitive information.
- Confirm receipt without promising a response the hotel cannot deliver.
Review themes beside the operating change they produced.
A headline average cannot show what changed. Review question distribution, recurring themes, recovery status and time to ownership. Then keep the operating change beside the evidence: revised arrival instructions, a maintenance action, a room-standard check or a different breakfast handover.
Compare like with like. Keep question wording, scale and audience stable when measuring change. If the question or channel changes, mark the break in the series rather than presenting the before-and-after movement as if nothing else moved.
Connect experience signals to definitions, owners and review rhythms without hiding the source behind one average.
↗| Signal | Owner | Evidence of completion |
|---|---|---|
| One urgent in-stay issue | Named duty role | Guest contacted, action recorded, outcome checked |
| Repeated room or service theme | Department head | Cause reviewed and operating change assigned |
| Declining question distribution | Experience lead | Same question and cohort compared after the change |
| Unclear or unused question | Survey owner | Question rewritten, routed differently or removed |
Approve the survey before inviting a guest
A survey is ready when every answer has a purpose and the guest can participate honestly, accessibly and without unnecessary data collection.
checked
Frequently asked questions
Concise answers to the practical questions hotel teams ask when putting this guide into use.
01How many questions should a hotel guest satisfaction survey include?
Use the fewest questions that support a real decision. Two questions can be enough during a stay, four can work at checkout and a focused post-stay survey can use roughly six to eight. Do not send all twenty-five questions in this guide to every guest.
02When should a hotel send a guest survey?
Choose the moment according to the action. Use an in-stay pulse while the hotel can still recover the experience, a checkout check for unresolved friction and a post-stay survey for patterns, value and return intent.
03Should a hotel survey use a five-point scale or a zero-to-ten score?
A five-point scale is useful for satisfaction with a specific part of the stay. A zero-to-ten recommendation question serves a different purpose. Keep the wording and scale stable over time, and do not combine the two into one average.
04Can a hotel ask only satisfied guests to leave a public review?
No. That creates review gating and can produce a misleading picture. Keep private feedback and public-review invitations separate, invite eligible guests consistently and never suppress a public-review route because somebody reported a negative experience.
05Should hotel survey responses be anonymous or linked to a stay?
It depends on the purpose. Service recovery normally needs enough booking context for an authorised person to respond, while trend research may not. Tell the guest which approach applies and collect only the information needed for that purpose.
06What should happen after a guest gives negative feedback?
A defined threshold should create an owner, response time and next action. Urgent in-stay issues need a duty role; repeated themes need a department owner and an operating change. Record the outcome instead of treating the score itself as the completed task.
Current guidance behind this article
This guide combines primary guidance with practical hotel workflow analysis. Product capabilities and integrations should still be verified against the property’s systems, operating rules and current supplier documentation.
- J.D. Power2025 North America Hotel Guest Satisfaction Index Study
Hotel satisfaction research covering seven experience dimensions and the measured effect of an unresolved stay problem. The study is North American, so its figures are context rather than a UK benchmark.
- UK Competition and Markets AuthorityFake reviews guidance (CMA208)
Current UK guidance on genuine, incentivised, fake and misleading consumer reviews and the responsibilities of businesses that publish review information.
- Information Commissioner’s OfficeA guide to the data protection principles
UK guidance on purpose limitation, data minimisation, accuracy, storage limitation, security and accountability when personal data is collected or connected to a stay.
- W3C Web Accessibility InitiativeForms tutorial
Practical guidance for form labels, grouping, instructions, validation and notifications that make surveys easier to use with assistive technology.
