Client sign-off checklist for a website launch.

The last days before a launch are when small things get missed: an old phone number in the footer, a contact form that sends to the developer, a page still saying "Lorem ipsum" three clicks deep. A checklist you go through with the client protects both of you. They know what they are approving, and you have a clear record of what was approved.

Split the list into what you check and what the client checks. You know the technical side; they know their business, their prices and their phone number.

What the client should check

Content and facts

• Company name, address, phone number and email are correct everywhere, including the footer and contact page.
• Opening hours, prices and product or service descriptions are current.
• Names and job titles of people are spelled correctly.
• No placeholder text or placeholder images are left.
• Every page they expect is there, and nothing is there that should not be.

Tone and images

• The wording sounds like them.
• They have the rights to use every photo, logo and illustration.
• People shown in photos have agreed to appear.

Their own test

• They have looked at every page on their own phone and computer.
• They have filled in the contact form and received the message where they expect it.
• They have tried any booking, payment or sign-up process from start to finish.

What you should check

Functionality

• All forms send to the right address, with a confirmation for the visitor.
• All links work, including links to social profiles, documents and maps.
• The 404 page exists and helps people find their way.
• Third-party embeds (maps, videos, booking widgets) load correctly.

Mobile and browsers

• Every page works on small phones, tablets and large screens.
• Menus, buttons and forms are easy to use with a finger.
• The site looks right in the major browsers.

Search and sharing basics

• Every page has its own title and description.
• Search engines are allowed on the live site (and blocked on staging).
• Redirects are in place from old addresses, if the site replaces an existing one.
• Social sharing images and the browser icon (favicon) are set.

Performance and security

• Images are compressed and sized for the web.
• The site uses HTTPS everywhere, with no mixed-content warnings.
• Plugins, themes and the platform are up to date, with backups set up.

Legal and privacy

• A privacy policy is present and describes what the site actually collects.
• A cookie notice is in place if the site uses cookies that need consent.
• Any legally required company information for their country is shown.

These are not legal advice; your client is responsible for their own legal content, and may need to check it with a professional.

Access and handover

• The client has the logins they need (domain, hosting, CMS, analytics) and they are in the client's name where possible.
• Analytics and any tracking are set up and tested.
• The client knows how to make simple edits, or who to ask.

Go through it together

Send the client's half of the list a few days before the launch date, not on the day. Then book a short call to go through anything still open. Agree on what blocks the launch (a wrong phone number, a broken form) and what can be fixed in the first week after it (a photo that could be better). Without that distinction, every small wish becomes a reason to wait, and the launch date slips.

The sign-off itself

When both lists are done, ask for a written sign-off. It can be short. It should include:

• The website address and the date.
• The pages or features being approved.
• A sentence such as: "I have reviewed the website and confirm it is ready to go live. Further changes after launch will be handled as new requests."
• The client's name, and their reply or signature.

A reply to an email works. So does a status recorded on each page. The important thing is that it is written and easy to find.

After launch

Agree what happens next before you go live: a short period for fixing bugs at no cost, how new requests are handled, and whether there is a maintenance plan. Then do a final check on the live address, because things can change between staging and production (see collecting feedback on a staging site).

Where Tweakpin fits

Tweakpin keeps the final review on the page itself. Your client goes through the site, pins a note on anything that is not right, and you answer under it. When a page is ready, the client approves it, and everyone who opens the page sees that it is approved. The list of pages shows what is approved and what is still waiting, so the sign-off conversation starts from a clear picture rather than a long email thread. It complements a written sign-off; it does not replace your contract.