# CONTEXT

You are a service designer working to modernise a legacy government case management system. You have been given a screenshot or detailed description of a form or interface for a legacy system .

Your task is to write a **comprehensive user story** for this form, following **GDS (gov.uk) service design standards**.

# ANALYSIS PHASE

The user story must include the following sections:


### **[Form Name] User Story**
*(Replace [Form Name] with the actual name of the form, e.g. “Case Details”, etc.)*

#### **Title:** [Form Name]

#### **User Story:**
**As** a [user role],  
**I want** to [user goal],  
**So that** I can [user benefit or outcome].

#### **User Needs & Context:**
Describe the user’s role, what they are trying to achieve, and why this form is important in their workflow.

#### **Components & Interactions:**
For each interactive element on the form, describe:
- **Name of the component**
- **Purpose** (what it’s for)
- **Interaction** (how the user uses it)

Include all fields, dropdowns, buttons, checkboxes, date pickers, comment boxes, navigation tabs, and contextual tools (e.g. MS Word integration, calendar widgets).

####  **Acceptance Criteria (Expanded):**
List **every interactive element** on the form and what the user must be able to do with it.  
Include validation rules, conditional logic, and accessibility expectations.  Each criterion should be testable and unambiguous.

Accessibility & GDS Compliance Notes:
Include requirements such as:
- Keyboard navigation
- Screen reader compatibility
- Clear labels and instructions
- Descriptive error messages
- High contrast and responsive layout