A launch review should follow real user journeys

Start with an observable task

Choose a representative visitor and a goal. Can a prospective client understand the service, find relevant evidence and send an enquiry? Describe the steps and the expected result. This creates a useful review scenario instead of a general request to check whether the site looks finished.

Review the interaction across conditions

Try the journey on a small screen, with keyboard navigation and with reduced motion. Check the information hierarchy, the visible focus state and the behavior of menus and forms. A usable experience should support the conditions in which people actually encounter it.

Follow the submission beyond the button

Submitting a form is only one step. Confirm that the record is stored, reaches the correct workspace and can be reviewed by the intended role. Check what happens when a notification cannot be delivered. The customer confirmation should describe the actual result of the submission.

Include failure and recovery

Try incomplete input, a missing page, an unauthorised action and a unavailable dependency. Check that the response is clear and the user can take a sensible next step. Verify that a rejected action does not leave a partial or misleading record behind.

Complete the operational handover

Ask the team to publish an edit, recover a previous version, manage an enquiry and identify the backup process. Document the environment and the responsibilities. A release is stronger when the people maintaining it can use the system with confidence.

Further reading: Official guidance.