ZHILIAN CUBE | Delivery and Acceptance Checklist Template Purpose: a starting template for discussing scope, deliverables and acceptance. This is not evidence of an accepted project and does not replace the contract. Project: ________ Version: ________ Acceptance environment: ________ Contacts: ________ Date: ________ Agreed scope / contract appendix: ________ 1. Before work starts [ ] Agree goals, user roles, scope and exclusions. [ ] Identify implementation roles, materials, access and decision responsibilities. [ ] Agree milestones, fees, payment arrangements and change approval. [ ] Separate implementation fees from hosting, model, SMS and other third-party costs; identify procurement responsibility. [ ] Agree data location, access, external model use, retention and deletion. 2. Handover materials (mark items that apply; explain omissions) [ ] Custom source, version, dependencies and start-up instructions. [ ] Database schema or migrations and necessary anonymised samples. [ ] Deployment configuration, runtime requirements and backup/recovery instructions. [ ] API documentation, user guide and administrator handover notes. [ ] Usage and licence information for existing tools, open-source components and third-party services. [ ] Accounts and secrets transferred securely, outside this form and public source code. 3. Acceptance evidence (sample / expected result / actual result / evidence / conclusion) 1. Install, start and access key functions in the agreed environment using the documentation. 2. Complete the main workflows with mutually agreed samples. 3. Check role permissions, missing information, invalid inputs and human handover. 4. If external systems are in scope, validate real authorised interfaces and failure handling separately. 5. If efficiency measures are agreed, record baseline, sample size, period and a comparable retest. 6. If backup/recovery is agreed, perform and record a recovery check. 4. Outstanding issues Issue: ________ Impact: ________ Owner: ________ Target date: ________ Retest result: ________ Conclusion: accepted / accepted with mutually agreed outstanding items / retest required 5. Ongoing arrangements Support period: ________ Channels: ________ Response arrangements: ________ Bug-fix scope: ________ New requirements: ________ Source and ownership handover conditions: ________ Third-party renewals: ________ End-of-engagement handover, access and data handling: ________ Mutual confirmation record: ________