# Plan and requirements

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

## Scope and exclusions

Deliverables, boundaries, assumptions and work not included.

Not completed.

## Stages and dependencies

Output, contributor, approver, prerequisite, estimate and date status.

Not completed.

## Campaign coordination

Media placements, product release, required assets and readiness checks before each event.

Not completed.

## Integrations and data

System, owner, data fields, format, test access and failure behaviour; no secrets.

Not completed.

## Acceptance and changes

Testable criteria, who accepts the work, how to record a new request and review the estimate.

Not completed.

## Open decisions

Question, owner, clarification deadline and the impact of an unresolved answer.

Not completed.

## Related documents

- [Requirements template](https://keissmedia.com/resources/requirements/template.md)
- [Scope change: complete the record](https://keissmedia.com/resources/change/#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)