The Website Handover Checklist Most Studios Skip (and You Should Demand)

Why Handover Matters More Than Launch

Launch day gets all the glory — the confetti, the "we're live!" post, the screenshot for the portfolio. But whether you're still happy with your site in six months has almost nothing to do with launch. It comes down to the handover.

I run this stage on every project we ship, and I've started thinking of it as the real deliverable. Because a beautiful site you can't access, can't edit, and can't fix isn't an asset. It's a liability with nice typography.

"A beautiful site you can't access, edit, or fix isn't an asset. It's a liability with nice typography."

The Handover Checklist

Five things should land in your hands before you call a project finished.

Full Access to Everything

You own the keys, you don't borrow them — the Framer project, your domain settings, your CMS, and every connected tool: analytics, forms, email. If any of it lives inside your developer's personal account, you don't truly own your site. This one's non-negotiable.

A Walkthrough, Not a Shrug

A live site is useless if you're scared to touch it. You should get a clear walkthrough — live or recorded — of the things you'll actually do: change text, swap an image, add a blog post, hit publish. You should leave able to make a basic edit without phoning anyone.

Documentation You'll Actually Open

Not a forty-page manual that dies in a folder. A short, human guide: how the components work, how to add a CMS entry, where the editable bits are, and the few things to leave alone. The goal is independence, not homework.

Proof the Technical Setup Is Done

This is the part you can't easily check yourself, which is exactly why it should come in writing: meta titles and descriptions per page, analytics installed and firing, forms tested end-to-end into the right inbox, sitemap submitted, redirects in place if you migrated, mobile and cross-browser checked. Hand it over as a ticked checklist — you shouldn't be taking it on faith.

A Pan for "What If Something Breaks?"

Because something will need to change — a new section, a price update, a fix. The handover should say plainly what's covered by any support window, what a future change costs, and how to reach the team. No mystery, no awkward "um, is this billable?" later.

What a Weak Handover Looks Like

The site goes live. You get a link. Maybe a cheerful "let me know if you need anything!" Then three weeks later you want to change one line of text and realize you have no access, no instructions, and no idea who to ask.

That's the exact moment a lot of people start quietly resenting a project they were thrilled about at launch. And it's completely avoidable.

"A good handover should leave you more capable, not more dependent."

The Three Questions to Ask Before You Sign Off

You don't need to memorize the whole checklist. Just ask three things before you call it done:

• Do I have full access to everything — project, domain, CMS, and tools?

• Can you show me how to make a basic edit myself?

• What happens when I need a change later — and what does it cost?

If the answers are clear and confident, you're in good hands. If they're vague, that tells you how the next six months are going to feel.

Let's Talk About Your Project

For us, handover is the finish line, not an afterthought — full access, a real walkthrough, and a site you can confidently run yourself. If your last project ended with a link and a shrug, let's do it properly this time. Book a free consultation, no pitch, no pressure.