User Flow Specification

Owner: [Owner]
Status: [Draft/In review/Approved]
Version: [Version]
Target release: [Date or milestone]

Problem or decision: [Problem, decision, or outcome governed by this specification]
Reviewers: [Roles responsible for technical, product, security, and operational review]

1. Goal and entry point

[State and transition trigger]

2. Actors and permissions

[Required input and validation]

3. Happy path

[Error copy and recovery action]

4. Alternate and error paths

[Loading and empty state]

5. State transitions

[Keyboard and screen-reader behavior]

6. Content and validation

[Event name and properties]

7. Accessibility

[Accessibility: record the behavior, data, constraints, edge cases, ownership, and acceptance evidence that apply to this User Flow Specification]

8. Analytics

[Analytics: record the behavior, data, constraints, edge cases, ownership, and acceptance evidence that apply to this User Flow Specification]

9. Acceptance

[Acceptance: record the behavior, data, constraints, edge cases, ownership, and acceptance evidence that apply to this User Flow Specification]

• [Given context, when action, then observable result]
• [Owner, environment, evidence, and sign-off condition]

Review and Change Control

[Reviewers, decision owner, unresolved questions, linked evidence, approval date, and change history]