# Keiss Media: requirements and acceptance worksheet

Optional draft aid for a scoped digital project. Choose the sections the work needs; do not produce documents for their own sake.

## Goal and boundaries

Business goal, intended audience, deliverables, exclusions, dependencies and unresolved questions. Preserve the distinction between a business result to measure and a deliverable to accept.

## Participant journey

Entry point, core action, feedback, completion, repeat participation and sharing if required. Include empty, error and inaccessible-device states that matter to the assignment.

## Behaviour and content

For each feature state who uses it, what triggers it, expected behaviour, data involved and an acceptance example. Identify content owner and brand approvals.

## Integration requirements

Required systems, public API references where shareable, access owner, permitted data, failure behaviour and the person who validates feasibility. Do not paste tokens or credentials. An API description is not evidence that access has been granted.

## Quality requirements

Supported devices and browsers, accessibility, performance, security and privacy requirements appropriate to the project. A qualified specialist checks domain-specific requirements where needed.

## Acceptance

For each deliverable: criterion, test or review method, required evidence, reviewer, approval authority and unresolved dependencies. Distinguish a prototype review from production acceptance.

## Delivery and change

Milestones, review windows, responsibilities, effects of change, launch conditions and handover. Record who operates the project after launch. Estimates and deadlines remain proposals until agreed.