# Digital project summary Status: draft Version: Date: Author: Reviewer: ## Project, version and status Name, author, date and reviewer; draft, awaiting approval or approved. Not completed. ## Facts, assumptions and questions For facts, give a source and date. For unknowns, record the question and owner. Not completed. ## Source material and brief Which business problem needs to be addressed? Record the output, document link, status and next decision. Not completed. ## Idea and concept Why does the proposed idea fit the task and the brand? Record the output, document link, status and next decision. Not completed. ## User journey and prototype What does a participant do, and how does the interface respond? Record the output, document link, status and next decision. Not completed. ## Plan and requirements What will be delivered, who is responsible, and what does launch depend on? Record the output, document link, status and next decision. Not completed. ## Development and testing What has actually been tested, and what still prevents launch? Record the output, document link, status and next decision. Not completed. ## Launch and handover Can the client operate the project after it is handed over? Record the output, document link, status and next decision. Not completed. ## Decisions and next actions Who is authorised to decide, what has been approved and what remains unresolved. Do not include secrets. Not completed. ## 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.