# UX Content Brief

Define a user task, interface context, constraints, states, evidence, risks, terminology, and successful behavior before writing product copy.

## Usage note

Complete the brief with product, design, research, engineering, support, accessibility, and policy context. Copy cannot repair a flow whose available actions or system behavior do not serve the user.

## How to use this template

1. Define the user situation, task, prior state, consequence, and observable completion.
2. Map the full flow and all default, transitional, error, denied, and success states.
3. Collect product behavior, research, terminology, policy, and technical evidence.
4. Specify copy requirements, constraints, reviewers, accessibility, localization, and tests.
5. Approve the implemented content and monitor whether users understand and recover.

## Blank template

### User and task

- **Feature, surface, and release:** [Enter]
- **User and account state:** [Describe]
- **Prior event or entry point:** [Enter]
- **Primary task:** [One action or decision]
- **Motivation and concern:** [Evidence]
- **Permissions, plan, locale, device:** [Enter]
- **Consequence of error:** [Describe]
- **Successful end state:** [Observable behavior]

### Product and evidence

- **Product behavior source:** [Requirement/owner/version]
- **Research evidence:** [Finding/reference]
- **Support or analytics evidence:** [Enter]
- **Terms and definitions:** [Approved list]
- **Policy, privacy, legal, or safety requirement:** [Enter]
- **Technical constraints and variables:** [Enter]
- **Unknown questions:** [Question/owner/date]

### State content map

Duplicate for each state.

- **State and trigger:** [Default / Loading / Empty / Error / Denied / Success]
- **User question:** [What must they understand?]
- **Available actions:** [List]
- **Required message:** [Facts, condition, recovery]
- **Primary label or text:** [Draft]
- **Alternative route:** [Enter]
- **Owner and evidence:** [Enter]

### Quality and release

- **Voice and terminology:** [Enter]
- **Length and layout constraints:** [Enter]
- **Accessibility requirements:** [Enter]
- **Localization and variable notes:** [Enter]
- **Required reviewers:** [Product / Engineering / Privacy / Legal / Other]
- **Prototype test task:** [Enter]
- **Implemented QA:** [States/devices/assistive technology]
- **Success and recheck trigger:** [Define]