# Date filter comprehension survey

Understand confusion about date ranges and time zones.

If nothing was unclear or difficult, say so. Skip questions about steps you did not experience; use not applicable where appropriate.

## 1. Which dates did you intend to include?

Answer: ____________________

## 2. How did you interpret the end date?

Answer: ____________________

## 3. What time-zone information was missing?

Answer: ____________________

## Author notes / illustrative keys where applicable

1. The intended dates identify the range users meant to request. Compare that intention with documented inclusion boundaries rather than assuming displayed labels establish completeness.
2. 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.
3. 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.

Interpretation caution: Do not assume every date field uses one time zone.


## Illustrative finding and follow-up

Observation: Users interpret an end date as excluding that day.

Action to test: Explain range boundaries with an example.

Follow-up: 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.