# Requirements and acceptance criteria

Keiss Media · Version 1.0 · 15 October 2026

If an answer is unknown, say so. You do not need to complete every field before a first conversation.

## Deliverables and exclusions

[What is delivered at this stage and what is excluded?]

## User scenario

[Who wants to achieve what, and in which situation? Describe the goal rather than a button position.]

## Behaviour and states

[Trigger, expected result, errors and empty states. What data and integrations are needed?]

## How to verify

[For each deliverable, record the test action, expected behaviour and evidence. A launch date or sales growth is not a functional test.]

## Devices and quality

[Agree testable accessibility, device, performance, security and data requirements. Specialist requirements need specialist review.]

## Review process

[Who tests, who approves, where are issues recorded and how is a defect distinguished from new scope?]

## Sources and adaptation

- Agile delivery community, Government Digital Service: [Writing user stories](https://www.gov.uk/service-manual/agile-delivery/writing-user-stories). Open Government Licence v3.0.

Keiss Media’s existing worksheet was refined using GOV.UK guidance on user stories and acceptance criteria. Government-specific procedures and terminology were not carried over.

Contains public sector information licensed under the Open Government Licence v3.0.
https://www.nationalarchives.gov.uk/doc/open-government-licence/version/3/