Website Pre-Launch Checklist: A Business Owner’s Guide to UAT

Phone, desktop display and checklist for a website pre-launch review

Before approving a website for launch, try completing real customer tasks on a phone and a computer. User acceptance testing, or UAT, helps you assess the result against the agreed scope rather than judging only the homepage design.

Turn project requirements into scenarios

Take the approved scope and turn each function into a task. For example, a customer needs to find a service, read its conditions and make an enquiry. Record the starting page, steps and expected outcome. Distinguish errors in agreed functions from new ideas; additional requests may need a separate scope review.

Check content that affects decisions

Verify company names, services, coverage areas, opening hours and contact details. If prices appear, the offer owner must confirm them. Open each PDF and check its version. Review metadata, page titles, images and relevant alternative text. For bilingual websites, read both versions and test switching languages on the same page.

Follow the complete enquiry journey

Use test data agreed by the project team. Check that labels, required fields and messages after an action make sense. If a button opens WhatsApp, the customer still has to send the message; opening an app does not prove receipt. Verify the receiving channel using the agreed test method without creating false leads in live operations.

Test phones, computers and keyboard controls

Use available devices to try menus, FAQs, buttons and important information. Look for clipped text, horizontal overflow and obscured buttons. Try Tab and Enter on the main journey. Record the device and browser so the provider can reproduce issues. This is a practical review, not certification that every device or accessibility requirement has been covered.

Make issues easy to reproduce

Keep one shared list with the URL, steps, expected result, actual result, screenshot and status. Flag issues blocking enquiries or payments as priorities for discussion. Avoid vague reports such as “the website is not right”. Retest after a fix, including nearby steps that may have been affected.

Approve the result and record outstanding work

Keep the reviewed checklist, agreed outstanding issues and the name of the person approving launch. Make post-launch responsibilities and dates clear. If you are planning a company website, discuss scope and the review process with alfatihstudio before development begins.

FAQ

No. UAT checks whether users can complete tasks and whether the result meets the agreed scope.

Yes. Try an available real phone as well as previews. Record the device and browser so the review limits are clear.

No. Distinguish problems in agreed functions from new content or functions that expand the scope.

Related articles