The week before launch, everyone finds something. ClientTweak brings every last-minute issue onto one review, prioritised and assigned, so you can see exactly what stands between you and launch day.
Stakeholders comment from a link with no account; your team signs in.
High priority for launch blockers, low for post-launch polish.
Assign each issue so it's fixed once, by the right person.
Review desktop, tablet and phone layouts before visitors do.
Use Browse mode to move through the site; comments are tracked per page.
Mark the review finished when everything that matters is resolved.
Add the staging URL and use Browse mode to move through the site as a visitor would. On each page, switch to Comment mode and pin anything that needs fixing: a broken layout, a typo, a wrong image. Comments are grouped by page in the list, so you can see where problems cluster.
Not everything raised in launch week needs to be fixed before launch. Set high priority on the issues that block go-live and low priority on polish that can wait. Assign each one, and use filters to focus the team on what matters today.
Switch the review to tablet and phone and check the pages most visitors will land on. Comments left at a width stay with that layout.
The best launch reviews are scheduled, not improvised. Decide who needs to sign off, which pages they're responsible for, and when their review is due. Share the staging site with each group a few days before launch, not the night before.
Agree what counts as a blocker. Typos on the homepage, broken forms and layout bugs at common widths usually are. A slightly long paragraph on an inner page usually isn't. Use priorities to make that split visible, and keep the low-priority items for the first week after launch.
On launch day, the comment list is your checklist. When every high-priority comment is resolved, finish the review and go live. Then turn off the review link, or regenerate it if you'll keep using the project.
Send the link to every stakeholder.
Flag blockers high and assign owners.
Resolve issues as fixes are deployed.
Finish the review when blockers are clear.
Content and copy, layout at every screen size, links and navigation, forms, images, page titles and metadata, and anything stakeholders need to sign off. See our website launch QA checklist for a full list.
Share a single review link where they can pin comments directly on the staging site, set a deadline, and triage everything in one list.
Yes, as long as ClientTweak can reach it by URL. Pages behind a login form or HTTP authentication aren't supported.
Yes. Set high priority on blockers and filter the comment list to focus on them.
Yes. Password-protect the review link, and turn it off after launch.
Yes. Keep the project and point it at the live site's pages, or create a new project for the production URL to collect post-launch feedback.
Typically the designer, the content owner, someone from the client or leadership who signs off, and whoever is responsible for QA. Each can review the same link.
Give reviewers at least a few working days. Starting the night before means there's no time to fix what they find.
Pin feedback on live websites, PDFs and images, and turn it into work your team can track.