Website launch responsibility checklist

Assign an owner, evidence and a recovery decision to the checks that protect a website changeover.

Use this with the person responsible for deployment. A checked box is useful only when there is evidence behind it. The worksheet does not authorise a launch or replace the agreed approval process.

How to use it

Agree the launch scope, approver and recovery route before choosing the change window.
Record each test, its owner, result and unresolved dependency.
Repeat essential customer and email checks on the public site after an authorised launch.

A completed example

This example is fictional and illustrates decisions to record. It is not a client case study or a claim about results.

On a narrow screen, scroll across the table to read every column.

Stage and task	Illustrative owner	Evidence required	If it fails
Before: approve service and contact facts	Business owner	Approved page list and current contact details	Hold affected content for correction.
Before: test form receipt and confirmation	Developer and enquiry team	Harmless test reaches the right inbox; confirmation is accurate	Repair and retest before launch.
Changeover: preserve domain and mail settings	Authorised DNS administrator	Recorded before/after settings and a working recovery route	Stop and follow the agreed recovery plan.
After: verify old URLs and main journeys	Launch owner	Public checks of redirects, mobile navigation and enquiry delivery	Resolve customer-blocking failures or use agreed rollback.

Your worksheet

Edit the fields below, then copy or print your completed version. Edits stay in this tab and are not sent to AfterWorks or saved after you leave. The download is always the blank template. Keep passwords and personal customer information out.

Download blank worksheet

Editable website launch responsibility checklist

Website launch responsibility checklist

Complete one record per page, URL, task or supplier where appropriate.
Keep passwords and personal customer information out of this worksheet.

Project, scope and proposed change window:

Launch approver and explicit approval record:

Recovery owner and rollback trigger:

Task and stage: before / during / after:

Responsible person:

Dependency:

Expected result:

Observed result and evidence location:

Status: not started / blocked / passed / failed:

Issue and action owner:

Final approval or hold decision:

Public verification and follow-up date:

Completion checks
[ ] Content, links, images and essential customer journeys are reviewed.
[ ] Forms are checked end to end, not just for a success message.
[ ] Mobile, keyboard and error-recovery journeys are tested.
[ ] Domain, email, backups and recovery responsibilities are agreed.
[ ] Canonical, indexing and sitemap settings match the intended public site.
[ ] The owner explicitly authorises launch after reviewing unresolved issues.

Guidance: https://afterworks.space/resources/launch-checklist/

Website launch responsibility checklist

Complete one record per page, URL, task or supplier where appropriate.
Keep passwords and personal customer information out of this worksheet.

Project, scope and proposed change window:

Launch approver and explicit approval record:

Recovery owner and rollback trigger:

Task and stage: before / during / after:

Responsible person:

Dependency:

Expected result:

Observed result and evidence location:

Status: not started / blocked / passed / failed:

Issue and action owner:

Final approval or hold decision:

Public verification and follow-up date:


Completion checks
[ ] Content, links, images and essential customer journeys are reviewed.
[ ] Forms are checked end to end, not just for a success message.
[ ] Mobile, keyboard and error-recovery journeys are tested.
[ ] Domain, email, backups and recovery responsibilities are agreed.
[ ] Canonical, indexing and sitemap settings match the intended public site.
[ ] The owner explicitly authorises launch after reviewing unresolved issues.

Guidance: https://afterworks.space/resources/launch-checklist/

Before you call it complete

Content, links, images and essential customer journeys are reviewed.
Forms are checked end to end, not just for a success message.
Mobile, keyboard and error-recovery journeys are tested.
Domain, email, backups and recovery responsibilities are agreed.
Canonical, indexing and sitemap settings match the intended public site.
The owner explicitly authorises launch after reviewing unresolved issues.

Read the supporting guides

Explore the other planning worksheets or ask AfterWorks about your website.