← All resources

Keiss Media · Practical resources

Plan and requirements

Agree scope, responsibilities, dependencies and acceptance before production.

When to use it
When the concept and prototype are ready for production planning.
What you will have
A plan with deliverables, dependencies, owners and open decisions.
What to check
Dates and estimates need confirmation from the people responsible for delivery.
View the worked example

The example is fictional. It shows how to record questions and untested work.

Plan and requirements: the example drink learning example

All information is fictional. This is not a commission, an acceptance record, a verified result or a required service package.

Status

An illustrative plan with no agreed dates or fees.

Scope

A landing page, selection of one of three flavours, a game mechanic and a result screen. Physical prizes, accounts and sales are excluded by the example’s premise.

Dependencies

Packaging and copy → prototype → designs and rules → development → testing → launch decision. No calendar dates are assigned.

Campaign

Advertising should lead only to an accepted working release. Media placement and product release dates are unknown.

Integration

No external CRM integration is confirmed. The example does not collect participant identifiers or contact details. If integration is needed, its scope and estimate must be agreed separately.

Acceptance

Flavour selection works, valid moves follow the rules, the result is accessible, and the journey is checked on agreed devices. The complete criteria will be prepared with the requirements.

Change

Registration or a competition is a separate change requiring an estimate, owners and a review of the rules; it is not added silently.

Full workflow: https://keissmedia.com/resources/project-workflow/#plan

Download example (.md)

Fill in the template

If an answer is unknown, say so. You can leave fields open and record what needs clarification.

Project, version, status, author, date and reviewer.

Deliverables, boundaries, assumptions and work not included.

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

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

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

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

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

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 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 the example drink project.

Version 1.0 · 5 November 2026