KEISSMEDIAGet in touch
← All resources

Agree the work

Requirements and acceptance criteria

Agree what must work and how to check it.

Fill in the template ↓Download a blank template (.md)
When to use it
When a direction is chosen and the client and delivery team need to agree scope.
What you will have
Testable requirements, scope boundaries and an agreed review process.
When not to use it
An early experiment does not need a full specification. For a product, this worksheet may contribute to a PRD or technical specification; it does not automatically replace either.
View the worked example

The example is fictional. It demonstrates completion, not the outcome of an actual project.

Deliverables and exclusions

A Russian-language promotional website with three routes. No accounts, payments or visitor editing of routes.

User scenario

Someone with one free hour wants to choose a suitable walk and find its starting point.

Behaviour and states

Selecting a duration shows matching routes. No matches produces an explanation and a reset control. An external map opens only on request.

How to verify

Select 60 minutes: only routes of an hour or less remain. Complete the selection using a keyboard. Check no matches and reset. Save a test record and screenshots.

Devices and quality

Layouts and checks for phone and desktop. Visible focus and labels that do not rely on colour. Loading targets and the browser list remain to be agreed.

Review process

The delivery team checks the build, marketing reviews content and the client’s authorised reviewer approves it. A new language is a separate scope change.

Download example (.md)

Fill in the template

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

What is delivered at this stage and what is excluded?

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

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

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

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

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

Fields work in your browser. Your text is not sent to us or saved after the page closes. Download the document to continue later.

Sources and adaptation

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.

Version 1.0 · 15 October 2026