Hypothetical website pilot acceptance worksheet Adapt these checks to the agreed scope. The roles and requirements are hypothetical, not a record of completed work. Record the tested version, environment, date, tester and result alongside each check, with evidence and linked issues. 1. Decision or check: Confirm the pilot scope Example owner: Agency account lead with developer Evidence or question to record: Are the homepage, service layout, case-study layout, editing fields and enquiry route agreed? Record online booking and customer login as excluded in this example. 2. Decision or check: Confirm editing and case-study creation Example owner: Developer with authorised editor Evidence or question to record: Can the editor change, preview and publish service content, then create a case study that appears in its listing and at its own address? 3. Decision or check: Test enquiries and invalid submissions Example owner: Developer Evidence or question to record: Record receipt for every routing option. Check required fields and invalid email handling, including field-specific messages and retention of valid entered values. 4. Decision or check: Test permissions and delivery failure Example owner: Developer Evidence or question to record: Confirm signed-out visitors and non-editors cannot save changes, including through direct requests. Record the agreed delivery failure, visitor message and responsible person's notification. 5. Decision or check: Review design and content Example owner: Agency design lead and client content owner Evidence or question to record: Record review against approved design and copy on the agreed browser and device set. Link any issues. 6. Decision or check: Complete project-specific checks Example owner: Developer Evidence or question to record: Add the agreed accessibility, performance and security acceptance checks. Record the result for every address on the redirect list. 7. Decision or check: Resolve open items and accept delivery Example owner: Named agency approver, after required client approval Evidence or question to record: Identify blockers, accepted deferrals and scope changes. Each deferred issue needs its impact, responsible person and agreed resolution date. 8. Decision or check: Authorise public launch Example owner: Named client approver through the agency Evidence or question to record: Record launch permission. Who decides if a critical live check fails? What is the rollback or recovery action, including handling of affected live data? 9. Decision or check: Check the live site Example owner: Developer Evidence or question to record: Repeat the agreed public-site checks, including the enquiry route and important addresses. Record the launch result and remaining actions. 10. Decision or check: Confirm handover Example owner: Named agency or client owner with agreed support supplier Evidence or question to record: Confirm access to agreed files and accounts, deployment instructions and editing guidance. Include acceptance results and open items. Agree who handles faults and changes from handover. Source: https://kyln.digital/insights/agency-website-acceptance-checklist