WEBSITE LAUNCH REVIEW — BLANK WORKSHEET

BringPak Editorial Team | Published 15 October 2026

Use with your own team or any provider. Complete locally; downloading does not submit your answers.
Project / release reference: ____________________
Project type: Business website / Online store / Private customer portal
Review date: ____________________
Sign-off owner: ____________________

States: Not checked / Reviewed / Needs follow-up / Outside this scope
Record evidence for reviewed items and a reason for items outside scope. Use short references, not credentials or private customer records.
These self-recorded states are not an automated audit, launch approval, security certification or ranking score.

EVERY PROJECT

Agreed scope and sign-off owner
Name the pages and customer journeys being accepted, the person reviewing each area and what is deferred. A business owner may accept content while an operations lead reviews order handling. Record those decisions separately and agree who authorises the launch.
State: ____________________
Evidence reference / reason / next action: ____________________
Responsible person / follow-up date: ____________________

Domain, hosting and staff account ownership
Check who controls the domain, DNS, hosting, email and external provider accounts. Confirm the business can recover access and remove an old staff account. An invoice for development does not establish that these accounts are already in the intended owner's control.
State: ____________________
Evidence reference / reason / next action: ____________________
Responsible person / follow-up date: ____________________

Approved content and contact details
Review service descriptions, product information, prices where shown, permitted photos and contact details. Follow a phone or email link on an actual device. Remove example business details and confirm who approves later changes. Generated draft copy still needs review against the actual offering.
State: ____________________
Evidence reference / reason / next action: ____________________
Responsible person / follow-up date: ____________________

Mobile navigation and readable pages
Walk through navigation, long headings, the main action and any tables at a narrow phone width. Check text is readable, controls are usable and content does not disappear behind a sticky header. Repeat with images unavailable and a slower connection where practical.
State: ____________________
Evidence reference / reason / next action: ____________________
Responsible person / follow-up date: ____________________

Enquiry delivery and error handling
Use an agreed test enquiry and confirm the intended staff destination receives it with the correct service context. Check required fields, errors, duplicate clicks and the failure message when delivery is unavailable. An on-screen success message should correspond to the agreed receipt or storage outcome.
State: ____________________
Evidence reference / reason / next action: ____________________
Responsible person / follow-up date: ____________________

Keyboard navigation and form labels
Use Tab and Shift+Tab to follow links and controls, see the focus position and operate the main action. Check field labels, useful error text and image alternatives. Automated accessibility checks can help find issues, but record manual journey checks as well.
State: ____________________
Evidence reference / reason / next action: ____________________
Responsible person / follow-up date: ____________________

Public indexing and private access boundaries
For public pages intended for search, review successful responses, canonical URLs, index settings, sitemap entries and visible content without JavaScript. Keep private records behind access controls. Robots exclusions guide cooperative crawlers; they are not a replacement for authentication or customer permissions.
State: ____________________
Evidence reference / reason / next action: ____________________
Responsible person / follow-up date: ____________________

Existing URLs, redirects and missing pages
For a redesign, list useful old URLs and their relevant new destinations. Test permanent redirects, links and a genuinely missing page. Avoid redirecting every removed page to the homepage. If the site is new, mark old-URL migration outside scope with a reason while still checking navigation and missing-page behaviour.
State: ____________________
Evidence reference / reason / next action: ____________________
Responsible person / follow-up date: ____________________

Page titles and shared-link previews
Open representative pages directly and check that the page title, description, canonical and preview image describe that page. Check a shared link using the intended platform's available preview tools. A correct preview does not establish that a search engine has indexed the page.
State: ____________________
Evidence reference / reason / next action: ____________________
Responsible person / follow-up date: ____________________

Measurement and privacy choices
Agree which events mean a valid enquiry, booking or completed order and distinguish them from page views and clicks. Test that controls for applicable privacy choices are respected. Use labelled test activity where measurement is required, and avoid counting your team's tests as customer outcomes.
State: ____________________
Evidence reference / reason / next action: ____________________
Responsible person / follow-up date: ____________________

Recovery method and change ownership
Identify who can pause a change, restore a known deployment and recover the necessary records. Review the recovery method in a suitable environment, including access and the state it restores. Restoring code alone may not reverse a provider transaction or recover later data changes.
State: ____________________
Evidence reference / reason / next action: ____________________
Responsible person / follow-up date: ____________________

Staff handover and support arrangements
Ask the staff who will operate the site to complete their regular tasks. Confirm instructions, content editing, exports where agreed, renewals, support hours and the route for reporting an issue. Record outstanding work and the owner of each item rather than relying on a broad 'all done' message.
State: ____________________
Evidence reference / reason / next action: ____________________
Responsible person / follow-up date: ____________________

ONLINE STORES

Variants, stock and final order details
Test a representative product with its size, colour, quantity and price. Check unavailable combinations, the last unit and the final order summary. Identify the authoritative stock record and what happens when shop and website activity overlap.
State: ____________________
Evidence reference / reason / next action: ____________________
Responsible person / follow-up date: ____________________

Verified payment and COD states
Keep a COD order, an uploaded receipt and provider-verified payment distinct. Use the provider's permitted test process and review a failed or uncertain result before production. Confirm which verified event changes payment status and how staff handle a mismatch.
State: ____________________
Evidence reference / reason / next action: ____________________
Responsible person / follow-up date: ____________________

Dispatch, cancellation and returns
Follow the order reference through confirmation, packing, dispatch and a delivery exception. Check who can cancel, approve a return or change an address. Reconcile courier settlement separately from delivery where relevant. Use the business's approved policies and operating responsibilities.
State: ____________________
Evidence reference / reason / next action: ____________________
Responsible person / follow-up date: ____________________

Duplicate orders and integration failures
Repeat a synthetic order event and simulate an unavailable downstream service. Confirm one intended transaction, a usable staff notice and a review route. When a provider may have accepted an action before timing out, check the recorded result before creating another request.
State: ____________________
Evidence reference / reason / next action: ____________________
Responsible person / follow-up date: ____________________

PRIVATE PORTALS

Customer-to-record access boundaries
With synthetic customers A and B, check record pages, direct file addresses, search and export access. Changing a reference must not reveal another customer's information. Review staff permissions separately and record the agreed access rules; a visible login screen alone is insufficient evidence.
State: ____________________
Evidence reference / reason / next action: ____________________
Responsible person / follow-up date: ____________________

Document versions and approval history
Approve a specific synthetic document version, revise it and check which approval remains recorded. Agree whether the new version needs another review and who can publish it. Keep a draft, a published update and a customer approval as separate states.
State: ____________________
Evidence reference / reason / next action: ____________________
Responsible person / follow-up date: ____________________

Removed users and exported files
Remove a synthetic user's access and check the agreed sign-in, session and file-access behaviour. Decide which staff can export records, how a downloaded copy is handled and what can actually be revoked. Access removal cannot recall copies a permitted user already downloaded.
State: ____________________
Evidence reference / reason / next action: ____________________
Responsible person / follow-up date: ____________________

Existing record source and failed updates
Identify which system owns each displayed value and how stale or failed updates are shown. Check a repeated update, a missing record and an unavailable connection. Record how staff reconcile discrepancies and whether a migration is part of the launch scope.
State: ____________________
Evidence reference / reason / next action: ____________________
Responsible person / follow-up date: ____________________

DECISION AND HANDOVER
Outstanding work: ____________________
Agreed launch or follow-up decision: ____________________
Person recording the decision: ____________________
Recovery and support owner: ____________________

This original AI-assisted planning resource is published by BringPak, which offers development services. Use a scoped assessment for decisions requiring further technical review.

Guidance and interactive review: https://www.bringpak.com/resources/website-launch-checklist
Search moves: https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes
Accessibility first review: https://www.w3.org/WAI/test-evaluate/preliminary/
Authorization: https://cheatsheetseries.owasp.org/cheatsheets/Authorization_Cheat_Sheet.html