Website Launch QA Kit digital product cover

Pagemage original / digital downloadv2.49.1

05 editable documentsOffline browser workbookOne-time no subscription

Website Launch QA Kit / Notion import + kit

Website launch checklist & QA test templates

Run a repeatable manual launch review and hand over a documented result.

Made for web designers preparing a client handover.

Price and availability

Catalog price: $24 USD

One-time purchase · No subscription

FilesZIP with five editable Markdown documents, an offline HTML workbook, a reading edition, and optional Notion import files (not a configured workspace). A five-document worked case follows one fictional project.
To useExtract the ZIP. Open the workbook in a current desktop browser; edit Markdown in a text editor. No account needed for the workbook or Markdown files. A Notion account is needed only for the optional import; set database properties and relations yourself.
LicenseUse for your own or client work; do not redistribute the original templates or tools. Full terms.
SupportProduct questions and corrections by email; no custom implementation or professional review. 14-day refund policy.

Read the free worksheet

Checking the live price and secure checkout…

Inside the download

See the actual offline workbook

These screens were captured from the current download with fictional project details. Open the extracted HTML workbook in a desktop browser and fill in its worksheets. The full kit includes four more documents and a fictional worked case.

Edit a worksheet. Add your project details and replace the remaining prompts with facts you have checked.
Export your work. Download readable Markdown, then save a JSON backup if you want to continue editing later. Check that each file reached your device.
Restore when you return. Choose that kit's JSON backup to resume the same editing session. Nothing is autosaved or sent to a cloud account.

Open any screenshot for a larger view.

First editable worksheet of Website Launch QA Kit with fictional project details entered — Actual first worksheet in edition 2.49.1, with fictional entries. Some prompts remain for the buyer to complete.

Offline workbook controls for Markdown export, JSON backup, and restore, showing a backup restored confirmation — Save and restore controls, captured in Freelance Quote Studio. The same controls are in all five featured workbooks.

The optional Notion pack contains Markdown and CSV import files, not a ready-made workspace. You set up properties and relations in Notion yourself; these screens show the offline workbook and calculator only.

The task

What you'll make

A release decision with recorded tests and a named person responsible for rollback.

Gather before you start

Preview site
Critical visitor tasks
Rollback access

Mark missing information so you can check it before using your work.

When to skip this kit

You need a native Excel, Canva, or Word template. This download contains Markdown documents and an offline HTML workbook, plus Notion import files you configure yourself.
You need autosave or cloud sync. Export Markdown or save a backup before closing the offline workbook.
You need someone to complete the work. These are worksheets to fill in yourself.

Read the first worksheet below to see whether its questions help with your task.

Included files

What's inside

01Launch test plan
02Buyer journey checks
03Accessibility review prompts
04Issue report
05Release and rollback checklist

Each document has instructions, questions, and space for your answers. The final document includes a common mistake to check for before using your work.

The worked case contains five completed documents, one for each worksheet. Follow the evidence, decisions, and corrections across the same fictional project. The case is included in the workbook, reading edition, Markdown example, and optional Notion import.

Your completion check

Link the release decision to reproducible task and recovery tests, resolve blocking failures, record accessibility coverage limits, and verify the deployed version and an owned rollback route.

Before you finish

Check this before you use it

A page looks correct while its form or payment journey fails.

Rehearse both success and failure paths using the actual intended flow.

Use the final worksheet to record what needs fixing and what you still need to check.

Free worksheet

Start with worksheet one

Free to inspect and copy

Launch test plan

Jump to a section

{{project}} / review owner {{business}} / approver {{contact}} / target {{deadline}}

Purpose: make a bounded release decision from reproducible evidence. A checked box is not a test result. Candidate version/build [ ]; staging address [ ]; production address [ ]; scope freeze date [ ]. Primary visitor task [ ]; completion evidence [ ]; consequence if broken [ ]. Pages, forms, payments, downloads, and external dependencies actually in scope [ ]. Mark absent features not applicable with a reason; do not imply a checkout was tested on an enquiry-only site.

Release gates agreed before testing G1 Primary task completes and the confirmation means what the copy promises. G2 Required-field, failed-request, unknown-outcome, retry, and fallback states are usable for the supported route. G3 Offer/contact information and applicable delivery behavior match the reviewed version. G4 Task-blocking barriers are resolved; accepted minor issues have an explicit owner and date. G5 The previous version and a tested recovery method are available to the release owner. Adapt these gates and define any additional requirements. Record unmet gates rather than lowering them after a failure.

Fixtures must be non-sensitive. Use an isolated test environment for injected failures; do not disrupt visitors or probe unrelated systems. Identify who can authorize production actions and any payment rehearsal before it occurs. Do not store credentials, payment details, full session links, or real enquiry text in shared evidence. Decision: proceed to production verification / hold / revise. Reason and evidence references [ ]; approver/date [ ]; untested scope and next owner [ ].

Your decision

Which broken journey would prevent a visitor completing their task? My answer: [ ] Source and date: [ ] Still to check: [ ] Next action, owner, and due date: [ ]

Before you start

Preview site: [Source or notes]
Critical visitor tasks: [Source or notes]
Rollback access: [Source or notes]

What you will make

A release decision with recorded tests and a named person responsible for rollback.

View plain worksheet text

{{project}} / review owner {{business}} / approver {{contact}} / target {{deadline}}

Purpose: make a bounded release decision from reproducible evidence. A checked box is not a test result.
Candidate version/build [ ]; staging address [ ]; production address [ ]; scope freeze date [ ].
Primary visitor task [ ]; completion evidence [ ]; consequence if broken [ ].
Pages, forms, payments, downloads, and external dependencies actually in scope [ ]. Mark absent features not applicable with a reason; do not imply a checkout was tested on an enquiry-only site.

Test environment matrix
ID | browser/version | operating system/version | viewport/zoom | real device or simulation | input/assistive tool | rationale
[Environment | exact versions | system | size | method | keyboard/screen reader where used | audience evidence]
State what is not tested and who accepts or investigates that gap. Emulation is not evidence of behavior on a real device.

Test record
ID | candidate/environment | starting state and fixture | action | expected observable result | actual result | pass/fail/blocked/not applicable | evidence | tester/time
[Case | version | precondition | reproducible steps | completion/failure state | observation | status | sanitized record | name/date]
Keep expected behavior separate from what happened. A blocked test stays blocked; a production test does not inherit a staging pass.

Release gates agreed before testing
G1 Primary task completes and the confirmation means what the copy promises.
G2 Required-field, failed-request, unknown-outcome, retry, and fallback states are usable for the supported route.
G3 Offer/contact information and applicable delivery behavior match the reviewed version.
G4 Task-blocking barriers are resolved; accepted minor issues have an explicit owner and date.
G5 The previous version and a tested recovery method are available to the release owner.
Adapt these gates and define any additional requirements. Record unmet gates rather than lowering them after a failure.

Fixtures must be non-sensitive. Use an isolated test environment for injected failures; do not disrupt visitors or probe unrelated systems. Identify who can authorize production actions and any payment rehearsal before it occurs. Do not store credentials, payment details, full session links, or real enquiry text in shared evidence.
Decision: proceed to production verification / hold / revise. Reason and evidence references [ ]; approver/date [ ]; untested scope and next owner [ ].

Your decision
Which broken journey would prevent a visitor completing their task?
My answer: [ ]
Source and date: [ ]
Still to check: [ ]
Next action, owner, and due date: [ ]

Before you start
- Preview site: [Source or notes]
- Critical visitor tasks: [Source or notes]
- Rollback access: [Source or notes]

What you will make
A release decision with recorded tests and a named person responsible for rollback.

This is the complete first worksheet from the current edition. The full kit adds the remaining four documents, a worked scenario, and the offline editing workbook, plus an optional Notion import ZIP with Markdown pages and CSV databases.

Worked example

See the worked-case summary

Fictional example included in edition 2.49.1.

Fictional case: Alder Advisory prepares release R12 of a five-page enquiry site. A simulated service failure reveals a false success message and cleared form inputs. Issue I01 blocks release. R13 preserves inputs and confirms receipt only after the defined success response; a lost-response case requires a safe duplicate check. The five completed documents connect test evidence, accessibility limitations, retesting, rollback readiness, and a conditional production release.

Before you choose

What should I have ready for this kit?

Bring preview site, critical visitor tasks, rollback access. Mark anything you still need to check.

How do I know the work is finished?

A release decision with recorded tests and a named person responsible for rollback. Check your answers against the original records and note anything unresolved before sharing your work.

What is in the Notion import pack?

The download includes an optional NOTION-IMPORT.zip with authored Markdown page templates and sample-filled CSV databases. Import the files in Notion, then set field types and any database relations yourself. Alongside those files, you receive editable Markdown documents and an offline HTML workbook. Set up the imported pages and tables yourself. These are not native Excel, Canva, or Word templates. Extract the whole ZIP before opening the HTML files. Mobile file managers may not run local scripts; the text files and reading edition remain available.

Will this do the work for me?

The kit supplies structure, questions, and examples. You provide the facts, make the decisions, and adapt the finished output. You are responsible for checking the finished work. Custom implementation and professional review are not included.

Included Notion import files · fictional preview data

Website Release and QA Desk

7 Notion page templates, 1 completed worked-case page and 3 sample-filled CSV databases. Extract the product download, then import NOTION-IMPORT.zip in Notion desktop or web.

04-Release-Test-Plan.md

# Release test plan · [release ID]
- Site, version, commit, and environment: [ ]
- Authorized owner and release decision maker: [ ]
- Scope and explicit exclusions: [ ]
- Backup, rollback method, and last test date: [ ]
- Test data is fictional or approved: [ ]

## Journeys
- Entry page to primary task and confirmation: [ ]
- Invalid, unavailable, and retryable states: [ ]
- Keyboard-only path, visible focus, and form labels: [ ]
- Narrow viewport and supported desktop browser: [ ]
- Redirects, canonical, contact/support, and policy links: [ ]
- Offline/download or payment-delivery path, if in scope: [ ]

## Exit decision
- Blocking issues and owners: [ ]
- Retests complete with evidence references: [ ]
- Remaining risk and accepted owner: [ ]
- Go / no-go, approver, date: [ ]

01-Release-Register · sample database

Release ID	Site or project	Environment	Release owner	Planned date	Scope reference	Backup or rollback reference	Decision owner	Status
REL-01	Sample community site	Staging	Release owner A	10/28/2026	Approved checklist / v1.3	Private deployment notes	Site owner	In rehearsal

What Notion setup requires

These are the field changes described in the included setup guide. Notion may initially import them as text.

Date: Planned date.
Select: Environment, Severity, Status.

Add any Release, Test, and Issue relations manually and verify the IDs. Keep credentials and private customer data out of the imported databases.

A new CSV import does not build relations, formulas, or rollups. Add any you need manually. Replace or delete the fictional sample rows before sharing.

Example rows are fictional. The import creates pages and databases; set property types and any relations inside Notion. You configure the tables after import.

Created by Pagemage with AI-assisted writing and development. Read how the content and tools are checked. Questions or corrections: hello@pagemage.tech. 14-day refund policy.