# ARRC Agency — Example QA & Acceptance Checklist

**SAMPLE CHECKLIST / NOT A TEST REPORT FOR A CUSTOMER PROJECT**

Project reference: [project] | Build / release ID: [version] | Test date: [date] | Reviewer: [name]

| Check | Applicable? | Result (Pass / Fail / Blocked) | Evidence / issue |
|---|---|---|---|
| Required user journeys mapped to agreed acceptance criteria | | | |
| Form required fields, validation, errors and safe retries | | | |
| Core business rules and unusual input values | | | |
| Navigation and keyboard-focus order | | | |
| Responsive layout at agreed viewport sizes | | | |
| Authorised access / role boundaries (if in scope) | | | |
| API status handling and network-failure states (if in scope) | | | |
| Data retention and backup checks (if in scope) | | | |
| Browser and device compatibility agreed in SOW | | | |
| Technical debt and known limitations disclosed | | | |
| Documentation, version and deployment configuration prepared | | | |
| Client UAT feedback recorded and resolved or accepted | | | |

A source/build/static check alone does not establish end-to-end production quality. Evidence should be recorded for the system under test.