Hypothetical example
Put the decision in context.
A prototype includes useful error states but the build omits them. Compare the implemented interaction against the handover acceptance tasks.
Take these points into your brief.
Use this checklist to record what is agreed and what still needs confirmation.
- States and behaviour specification
- Developer acceptance tasks
- Implemented-experience review
For each item, keep the requirement, the supporting file or observation, and the person responsible for confirming it together.
Care, changes and ownership: your next step
Keep the final specification, supplier references and agreed responsibilities in an accessible handover record. Review the actual condition or operating problem before ordering a replacement or approving a change. If a component, location or requirement differs from the original, have that difference assessed. Retain dated changes so the next person responsible can understand the current state.
Sources and further reading
Source review: 11 September 2026. Confirm current requirements for your application. Platform features, eligibility and policies can change; check the requirements for your business and implementation.
