Hypothetical example
Put the decision in context.
An app works online but loses progress after a connection failure. Include recovery behaviour and the agreed device range in acceptance.
Take these points into your brief.
Use this checklist to record what is agreed and what still needs confirmation.
- Agreed device and journey tests
- Permissions and recovery
- Applicable privacy and account-deletion checks
For each item, keep the requirement, the supporting file or observation, and the person responsible for confirming it together.
Check delivery: your next step
Use the approved specification as the acceptance reference and record observations, not just a general impression. Separate items accepted, items needing correction and items outside the agreed scope. Assign a responsible person and next action to unresolved work. Keep the final version and relevant evidence together so a later support request can identify what was actually delivered.
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.
