{
  "title": "Date filter comprehension survey",
  "questions": [
    "Which dates did you intend to include?",
    "How did you interpret the end date?",
    "What time-zone information was missing?"
  ],
  "question_notes": [
    "The intended dates identify the range users meant to request. Compare that intention with documented inclusion boundaries rather than assuming displayed labels establish completeness.",
    "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.",
    "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."
  ],
  "answer_guidance": [
    {
      "question": 1,
      "format": "Optional short text",
      "reason": "Retain the specific point or condition described; avoid replacing it with an unexplained rating."
    },
    {
      "question": 2,
      "format": "Optional written explanation",
      "reason": "Keep context that distinguishes different experiences. Do not assume every date field uses one time zone."
    },
    {
      "question": 3,
      "format": "Optional improvement suggestion",
      "reason": "Keep the suggested change separate from whether it has been tested. Explain range boundaries with an example."
    }
  ],
  "respondent_instruction": "If nothing was unclear or difficult, say so. Skip questions about steps you did not experience; use not applicable where appropriate.",
  "note": "Examples to adapt. Not a validated instrument."
}
