Keep the finding specific
Users cannot find reset instructions.
Mobility and public places · A focused questionnaire
Clarify community-room usage arrangements.
Opens product registration. Example questions are not imported automatically.
CHOOSE YOUR STARTING QUESTIONS
Keep only prompts your respondents can answer. All questions remain available below.
3 questions selected. Nothing is submitted.
A worked interpretation example
Illustrative scenario. These are not customer results.
Users cannot find reset instructions.
Provide room-specific reset photographs.
After testing this change—Provide room-specific reset photographs.—ask people who encountered the changed arrangement whether this original issue still occurred or did not occur: “Users cannot find reset instructions.” Invite a concrete explanation, including none or not applicable. Compare participant context and sample differences; a before-and-after survey alone does not establish causation.
Choose the response format
| Question | Suggested format | What to preserve |
|---|---|---|
| Which booking instruction was unclear? | Optional free text; none or not applicable accepted | Read for booking clarity. Keep the specific explanation in the respondent’s own words rather than converting it into an unexplained overall satisfaction score. |
| What setup information did you need? | Optional free text; none or not applicable accepted | Read for setup need. Keep the specific explanation in the respondent’s own words rather than converting it into an unexplained overall satisfaction score. |
| What handback rule was missing? | Optional free text; none or not applicable accepted | Read for handback clarity. Keep the specific explanation in the respondent’s own words rather than converting it into an unexplained overall satisfaction score. |
Make questions optional where appropriate. If you add a rating scale, label its endpoints, keep one idea per question, and retain a follow-up for reasons. These examples are not a validated measurement instrument.
Read the answers carefully
Operator must verify actual usage rules.
Users cannot find reset instructions. This is an illustrative pattern, not observed customer data. Operator must verify actual usage rules.
A useful starting point
Clarify community-room usage arrangements. These prompts examine booking clarity, setup need, handback clarity. Choose only questions your audience can answer. A missing detail can be answered with none; do not assume an issue occurred.
If nothing was unclear or difficult, say so. Skip questions about steps you did not experience; use not applicable where appropriate.
Read for booking clarity. Keep the specific explanation in the respondent’s own words rather than converting it into an unexplained overall satisfaction score.
Read for setup need. Keep the specific explanation in the respondent’s own words rather than converting it into an unexplained overall satisfaction score.
Read for handback clarity. Keep the specific explanation in the respondent’s own words rather than converting it into an unexplained overall satisfaction score.
If nothing was unclear or difficult, say so. Skip questions about steps you did not experience; use not applicable where appropriate. Which booking instruction was unclear? What setup information did you need? What handback rule was missing?
Download the questions as text ↓
Examples to adapt, rather than a validated research instrument.
From question to next step
Clarify community-room usage arrangements.
Ask after an adult respondent has encountered this specific situation. For draft-copy testing, show the actual material first; accept none or not applicable when the issue did not occur.
Provide room-specific reset photographs.
Before you send it
Would you agree that this entire experience was clear and easy?
Which booking instruction was unclear?
The first wording assumes a positive outcome and combines clarity with ease. The revised prompt asks about the concrete situation; respondents may report no difficulty.
Inside the product
The real SurveyTeams screenshot shows a separate labelled synthetic event survey. It demonstrates the manual builder, not this questionnaire already loaded and not the task described in the software being evaluated.
Creation and preview were exercised in the observed account. Distribution, results and other features are separate workflows and depend on account conditions.
Build with SurveyTeams
Use these examples to draft your questionnaire. Create a survey draft, add questions, and check the respondent preview in SurveyTeams. Additional features depend on your account and plan.
Opens product registration. Example questions are not imported automatically.
Learn about the product ↗Before you send it
Adult visitors, travelers and service operators who encountered the described information or arrangement. Ask only about the step each person actually encountered; voluntary responses are not automatically representative.
Read for booking clarity. Keep the specific explanation in the respondent’s own words rather than converting it into an unexplained overall satisfaction score. It supports this decision: Clarify community-room usage arrangements.
Read for setup need. Keep the specific explanation in the respondent’s own words rather than converting it into an unexplained overall satisfaction score.
Read for handback clarity. Keep the specific explanation in the respondent’s own words rather than converting it into an unexplained overall satisfaction score. Operator must verify actual usage rules.
Provide room-specific reset photographs. After testing this change—Provide room-specific reset photographs.—ask people who encountered the changed arrangement whether this original issue still occurred or did not occur: “Users cannot find reset instructions.” Invite a concrete explanation, including none or not applicable. Compare participant context and sample differences; a before-and-after survey alone does not establish causation.
The page offers text, CSV, JSON and Markdown downloads plus manual copying. Registration does not import the questionnaire. Use account-supported features and verify your own response-handling arrangements.
Continue exploring