Checklist progress is saved in this browser on this device.
Adapt the checks to the scale and risk of the release. For a small site, a short review may be enough; an application handling important data or transactions needs deeper testing and explicit operational owners. Google’s Site Reliability Engineering workbook is a useful reference for operational readiness.
Scope and product behavior
- Confirm the release scope, acceptance criteria, and approving owner.
- Test the main user journeys on supported browsers and device widths.
- Check empty, loading, error, offline, duplicate-submit, and permission states.
- Verify copy, links, contact paths, integrations, and any payment or booking flow.
- Confirm analytics and event collection match the agreed measurement plan.
Quality and access
- Review automated checks and resolve or document important failures.
- Test keyboard navigation, focus, labels, form errors, and reduced motion.
- Check page speed and image/font loading on representative network conditions.
- Confirm search metadata, redirects, and robots/indexing settings where relevant.
- Review logs and error reporting for exposed credentials or personal data.
Operations and recovery
- Confirm production configuration, secrets, domains, certificates, and permissions.
- Name the person who monitors the release and the person who can roll it back.
- Verify backups or recovery procedures for data that must be retained.
- Define what signals trigger a pause, rollback, or incident response.
- Prepare support notes and communicate known changes to affected users.
- Review the release outcome after launch and record follow-up work.
References
Every business and project is different. Treat this as general planning guidance, then confirm platform-specific, legal, tax, and security requirements with the appropriate provider or qualified professional.