# User journey and prototype

Status: draft
Project: 
Version: 
Author and date: 
Reviewer: 

## User and goal

Who participates, what they need and why.

Not completed.

## Screens and transitions

Screen identifier, action and next screen; errors and return paths recorded separately.

Not completed.

## Stories and criteria

For each story: user, need, purpose and a testable result.

Not completed.

## Game rules

Controls, valid moves, scoring, limits, completion and replay.

Not completed.

## States and accessibility

Loading, offline, empty data and errors; keyboard operation, labels and distinctions that do not rely on colour alone.

Not completed.

## Prototype and questions

Link, version, review date and findings; unknowns and the person responsible for clarification.

Not completed.

## Related documents

- [Requirements and criteria: complete the worksheet](https://keissmedia.com/resources/requirements/#worksheet)

## Sources and adaptation

Keiss Media working guidance and learning examples. This route reuses the library’s existing brief, concept, requirements, scope-change, handover and hosting resources. Their sources and reuse terms are given on the respective pages. The new journey, planning and test-record templates connect those resources; they are not an official standard or a contract. User stories and acceptance criteria were checked against the GOV.UK Service Manual; the distinction between objectives and hypotheses follows 18F Methods. The examples were written for the fictional CHARGE project.

- [GOV.UK: user stories and acceptance criteria](https://www.gov.uk/service-manual/agile-delivery/writing-user-stories)
- [18F: design hypothesis](https://raw.githubusercontent.com/18F/methods/main/_methods/design-hypothesis.md)