Scope and acceptance
Which tasks must work on release day, who will test them and who can accept delivery?
Evidence to request A scope with named owners, an acceptance test for each critical task and a way to price and approve changes.
What would your team need to see before it signs off a new service? Choose the questions that matter to your purchase and take them into the supplier meeting.
Use the evidence requests to record what the supplier can show and what still needs agreement in the statement of work.
Which tasks must work on release day, who will test them and who can accept delivery?
Evidence to request A scope with named owners, an acceptance test for each critical task and a way to price and approve changes.
What information moves through the service, where are copies and backups held, and who can access them?
Evidence to request A data-flow diagram naming hosting and third-party providers, access roles, retention periods and how a buyer can request export or deletion.
If an account is compromised or records are lost, who acts first and how would the service recover?
Evidence to request An incident contact, agreed notification steps and evidence of a restore test against the buyer’s recovery requirements.
Can someone complete the critical journey by keyboard or screen reader, including correcting a mistake?
Evidence to request An agreed accessibility target and test results for the actual journey, with devices, assistive technology, outstanding issues and retest owners.
Who receives a fault outside normal hours, how is its impact assessed and when can the buyer expect an update?
Evidence to request A support schedule naming hours, priorities, response targets, escalation contacts and the boundary between a defect and a paid change.
Which code, content and accounts would the buyer own or license, and what would a replacement supplier need?
Evidence to request A list of deliverables and licence terms that distinguishes bespoke work from third-party components, plus a plan for transferring source, domains, credentials and data.
Example for a booking system
Give a tester a sample booking and ask them to move it to a different day. Agree in advance what the learner and the training coordinator should each see.
Record the result of each step, the evidence and who will resolve any issue before sign-off.
Discuss your acceptance criteria