Website handoff checklist
A clean handoff turns a one-time project into a referral. Use this checklist when transferring a finished website to a client. It covers credentials, training, documentation, billing, and the support window.
Credentials & access
0 / 7Documentation
0 / 5Training
0 / 4Final review
0 / 5Billing & legal
0 / 4Post-launch support
0 / 5How to use this tool
- 1Complete each section before scheduling the handoff call.
- 2Tick items as you go. Progress saves automatically.
- 3Copy as markdown to send as a handoff document with your final invoice.
About this tool
Most "the website broke" panic emails after launch are not actually bugs, they are knowledge gaps. The client doesn't know how to update copy, where to find logins, or who to call. A structured handoff prevents 80% of those calls and sets you up to upsell maintenance.
Related tools
Bug report template generator
Fill in a few fields and copy a clean, ready-to-paste bug report in markdown. Built for product, dev, and QA teams.
Website pre-launch checklist
A 50+ item pre-launch checklist covering content, SEO, performance, accessibility, analytics, and legal. Save your progress in the browser.
Website QA checklist
Hands-on QA checklist for testing a website before sign-off. Cross-browser, responsive, forms, links, and content checks.
Website accessibility (WCAG) checklist
Practical WCAG 2.2 AA checklist for designers and developers. Color, keyboard, screen reader, forms, and content checks.
Frequently asked questions
How long should the post-launch support window be?
30 days is standard for marketing sites; 60–90 days for web apps. State the window clearly in your contract, along with what counts as a bug fix (free) vs a change request (billable).
What's the most common handoff mistake?
Leaving credentials in your own accounts. Domain, hosting, analytics, and CMS should all be owned by the client. If something happens to your business, the client should not lose access to their own site.
Should I include training?
Yes. At minimum a 30-minute live session plus a recording. Clients who feel confident editing their own site are happier, refer more, and are more likely to take a maintenance retainer.
How does this convert to a maintenance retainer?
Use the handoff to surface ongoing needs: security updates, plugin upgrades, content changes, monthly reporting. Quote a monthly figure that covers a few hours of work and a clear response window.
Reviewing work with your team?
Pin comments directly on a live website or design — no extension, no setup.