Keep the finding specific
Users interpret an end date as excluding that day.
Product and software research / Survey guide
Product and software research · Practical survey guide
Date filter comprehension survey
Understand confusion about date ranges and time zones.
Opens product registration. Example questions are not imported automatically.
ILLUSTRATIVE QUESTIONNAIRE3 prompts
Try the first three questions here. Nothing is submitted or saved.
A worked interpretation example
From a comment to a practical next step.
Illustrative scenario. These are not customer results.
Choose an action to test
Explain range boundaries with an example.
Check the experience again
After trying the change, repeat “Which dates did you intend to include?” with people who experienced it. Check whether they still describe the original issue: users interpret an end date as excluding that day. Compare explanations and sample context, rather than claiming the change caused an improvement.
Choose the response format
Make room for the explanation.
| Question | Suggested format | What to preserve |
|---|---|---|
| Which dates did you intend to include? | Optional short text | Retain the specific point or condition described; avoid replacing it with an unexplained rating. |
| How did you interpret the end date? | Optional written explanation | Keep context that distinguishes different experiences. Do not assume every date field uses one time zone. |
| What time-zone information was missing? | Optional improvement suggestion | Keep the suggested change separate from whether it has been tested. Explain range boundaries with an example. |
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
Keep the conclusion within the evidence.
Do not assume every date field uses one time zone.
Users interpret an end date as excluding that day. This is a synthetic example, not a customer result. Do not assume every date field uses one time zone.
A useful starting point
Questions to understand the actual experience.
Understand confusion about date ranges and time zones. Use the prompts relevant to your audience and allow people to skip situations they did not encounter. Keep response handling consistent with what you explain in the invitation.
If nothing was unclear or difficult, say so. Skip questions about steps you did not experience; use not applicable where appropriate.
Which dates did you intend to include?
The intended dates identify the range users meant to request. Compare that intention with documented inclusion boundaries rather than assuming displayed labels establish completeness.
How did you interpret the end date?
End-date interpretation reveals whether a range includes the final day or uses another documented boundary. Explain actual date and timezone handling with a synthetic example, without inferring data completeness from interface wording.
What time-zone information was missing?
Missing time-zone information identifies an assumption users need explained when selecting a range. Distinguish the relevant field's actual zone from unverified reporting or display conventions.
If nothing was unclear or difficult, say so. Skip questions about steps you did not experience; use not applicable where appropriate. Which dates did you intend to include? How did you interpret the end date? What time-zone information was missing?
Download the questions as text ↓
Examples to adapt, rather than a validated research instrument.
From question to next step
Make the feedback useful.
Set the decision
Start with the decision: Understand confusion about date ranges and time zones.
Invite relevant voices
Invite people with relevant experience. Ask after someone has encountered the situation described in “Which dates did you intend to include?”, while they can still recall the details. For material testing, show the actual draft first; for planning, ask before the next relevant activity.
Choose an action
Explain range boundaries with an example.
Before you send it
Check what your wording assumes.
Would you agree that everything about date filter comprehension was clear and easy?
Which dates did you intend to include?
The first wording combines an assumed positive outcome with two different judgments. The revised prompt asks about a specific experience and permits an inconvenient or uncertain answer.
Build with SurveyTeams
Draft your own date filter comprehension questionnaire.
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.
Create your survey in SurveyTeams
Opens product registration. Example questions are not imported automatically.
Learn about the product ↗Before you send it
Questions, answered.
Who should receive this questionnaire?
Product users who attempted the described task. Ask only about steps each person encountered; do not treat a voluntary response sample as representative.
When should I ask these questions?
Ask after someone has encountered the situation described in “Which dates did you intend to include?”, while they can still recall the details. For material testing, show the actual draft first; for planning, ask before the next relevant activity.
What should I investigate in the answers?
Users interpret an end date as excluding that day. This is an illustrative pattern to look for, not a claim about your respondents. Do not assume every date field uses one time zone.
What would a practical follow-up look like?
Explain range boundaries with an example. After trying the change, repeat “Which dates did you intend to include?” with people who experienced it. Check whether they still describe the original issue: users interpret an end date as excluding that day. Compare explanations and sample context, rather than claiming the change caused an improvement.
How should I ask “How did you interpret the end date?”?
End-date interpretation reveals whether a range includes the final day or uses another documented boundary. Explain actual date and timezone handling with a synthetic example, without inferring data completeness from interface wording. Use an optional written explanation when predefined choices would hide relevant context.
Can I use the questions in SurveyTeams?
Copy the prompts or download TXT, CSV, JSON, or a Markdown worksheet, then adapt them in your own survey. The CTA opens registration; it does not import this example automatically. Verify available features in your account.
Continue exploring