{
  "title": "Policy exception routing survey",
  "questions": [
    "Which exception category was unclear?",
    "What context did the decision owner need?",
    "What routing example would help?"
  ],
  "question_notes": [
    "Use this answer to locate the part of the experience that needs explanation. The example issue to investigate is: staff send exceptions to multiple unrelated teams.",
    "The context needed by the decision owner reveals why an unusual request cannot yet be assessed. Provide approved submission guidance, without encouraging policy bypass or treating a complete explanation as grounds for automatic approval.",
    "Turn the requested improvement into a testable next step. One illustrative action is: publish a clear exception contact route."
  ],
  "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 advise bypassing approved policy."
    },
    {
      "question": 3,
      "format": "Optional improvement suggestion",
      "reason": "Keep the suggested change separate from whether it has been tested. Publish a clear exception contact route."
    }
  ],
  "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."
}
