Define what is changing
Write a short release note describing the change and the pages or workflows it affects. Assign a person to review it. Test on a preview environment before changing the live website, especially when the release affects checkout, accounts or customer data.
Check the main journeys
Follow the paths a real visitor would take: find a service, read a project, switch language and make an enquiry. Submit a clearly labelled test enquiry and confirm that the intended recipient receives it. Check empty and invalid form inputs as well as a successful submission.
Review different screens and inputs
Inspect a narrow mobile layout and a desktop layout. Check long headings, menus, images and tables. Use a keyboard to reach links and controls, verify visible focus and ensure text remains readable when zoomed. Respect reduced-motion settings for decorative animation.
Prepare recovery
Keep a known working version and confirm how to restore it. Where data changes are involved, agree on backup and recovery responsibilities first. A source-code rollback does not automatically undo a database migration or restore lost information.
Verify the live result
After publication, repeat the critical journeys on the live site. Check error reporting, missing assets and the delivery of test enquiries. Record the release outcome and any follow-up work so the next update starts from a clear baseline.
Your checklist
- Preview reviewed
- Critical journeys tested
- Mobile and keyboard checks complete
- Recovery plan understood
- Live checks completed
YOUR NEXT STEP
Have a project in mind?
Tell us what you want to build or improve. We will help you define the scope and a practical next step.
Start your project hello@bombstart.com
