Survey Questionnaire Design

Survey Questionnaire Design

This article outlines best practice for structuring survey questionnaires.

Surveys capture real guest experiences. Compared to a mystery visit questionnaire, the purpose of a survey is to measure sentiment rather than monitor service standards.

Well-designed survey questionnaires make it quick and easy for guests to complete, while still producing results that are clear, meaningful, and actionable for clients.

1. Structure the questionnaire with the guest's user experience in mind

Each section in the questionnaire creates a new page in Dynamic Survey. Questions should still follow the guest journey, but consider how many clicks the guest needs to make to navigate it and submit. Fewer clicks means a smoother completion experience.

For example:

  • Visit Details – order method/feedback category
  • Feedback – NPS and KPIs
  • Product Feedback – product rating questions
  • About You – demographic questions

A shorter survey is easier to drive engagement for. We recommend a survey should be around 10–12 questions.

2. Use clear rated questions

A survey should always measure NPS, followed by a few KPIs, e.g. service, cleanliness, speed, food and drink quality, and value for money.

  • NPS is a standard rating out of 10
  • KPIs are rated out of 5

When wording your question, consider what the rating key would be. For example:

"How satisfied were you with the following aspects of your visit?"
1 = very dissatisfied, 2 = dissatisfied, 3 = neither dissatisfied or satisfied, 4 = satisfied, 5 = very satisfied

3. Use the NPS influence question

The NPS influence question helps identify the main reason for a guest's score, whether this is a detractor, neutral or promoter score. The standard influence question to use:

"Great to hear, please select the main reason you’d recommend us." (logic for 9-10 scores)
"Thank you, please select the main reason you didn’t score us higher." (logic for 7-8 scores)
"Sorry to hear that, please select the main reason you wouldn’t recommend us so we can improve." (logic for 1-6 scores)
  1. Quality of food/drink
  2. Speed of service
  3. Team friendliness
  4. Team attentiveness
  5. Price of food/drink
  6. Cleanliness
  7. Atmosphere
  8. Payment process
  9. Other
The NPS influencer needs to have the analysis tag "NPS Influence". This ensures the data pulls into the NPS > NPS Influencers report in the Hub.

4. Use follow-on influencer questions for ratings 3 or below

As with the NPS influencer, follow-up influencer questions make reporting more valuable and provide clear insight into why guests are dissatisfied with an element of their visit. These should be single-choice, for example:
"Please tell us the main reason you were less than satisfied with the food quality?"
  • Taste
  • Temperature
  • Presentation
  • Freshness
  • Quality of ingredients
  • Portion size

All influencer questions need to have the analysis tag of "Influence Factor". This ensures the data pulls into the Feedback > Influences report in the Hub.

5. Use logic to control question visibility

Consider the order method and how this changes the guest journey. For example, a delivery order will not be able to answer questions on service or cleanliness.

Ensure you have the correct driving questions in place to manage this. For example:

"Please select your order method"
  • In restaurant
  • Via app
  • Click & collect
  • Delivery

This will also impact what answer options should appear on influence questions. For example, a click & collect order can rate their service, but not all key service points will be applicable if they rate 3 or below. Add logic at an answer option level if needed.

N.B. that not all driving questions need to be added to the questionnaire for surveys.

6. Use comment boxes strategically

Keeping the guest's user experience in mind, use comment boxes sparingly in surveys.

  • Always include a comment box on the NPS question, and make it forced.
  • Do not add comment boxes to other rated questions, as these add unnecessary length to the survey.
  • Where an influencer question has an "Other" option, use a forced comment box so the client can still gain insight.
  • You may want to use an "any other comments" text-only question on Product Feedback.

Quick Best Practice Checklist

When designing a survey questionnaire, ensure that:

  1. The structure minimises clicks and follows the guest journey
  2. The survey is kept to around 10-12 questions
  3. NPS and KPI questions use clear rated scales with defined rating keys
  4. An NPS influencer question is used for all ratings and tagged with "NPS Influence"
  5. Follow-on influencer questions are used for ratings of 3 or below and tagged with "Influence Factor"
  6. Logic controls visibility based on order method and prior answers
  7. Comment boxes are used strategically - forced on NPS, and on "Other" influencer options

    • Related Articles

    • Survey Setup in Dynamic Survey

      This article follows on from Survey Questionnaire Design and covers the practical steps for configuring a survey in Dynamic Survey Admin once the questionnaire itself has been created. Getting set up right matters as much as getting the questions ...
    • Mystery Visit Questionnaire Design

      This article outlines best practice for structuring mystery visit questionnaires. The goal of a mystery visit questionnaire is to measure whether specific service standards were delivered during a visit, rather than to collect general opinions. ...
    • Survey Updates

      1. In DS Admin, locate the survey e.g. pizzaexpressfeedback. 2. Copy the questionnaire from DS Admin, creating a Legacy Version. 3. On Admin, go through each section, add, remove or update questions as needed. 4. Check analysis tags are added on ...
    • Survey Branding

      Survey Branding is unique to each client and a ticket for Dev is required to add/update any branding to surveys. Please see fields below for information required on the ticket: Client and Client ID: Survey questionnaire: Survey link: Client logo: ...
    • Dynamic Survey Validator

      The validator triggers after every save. The severity of the error will be a different colour; red means this could be a breaking change, yellow means this could cause data loss, and blue is just for information. It will highlight the following ...