Menu

Handing a client website over properly: the checklist we run before we call a project done
📰

Handing a client website over properly: the checklist we run before we call a project done

DEV Community: github·Brightcode·4 days ago
#7yUwVsEK
#devtogithub#technology#devto#dev#client
Reading 0:00
15s threshold

By the Brightcode team, a small web development agency in Delhi NCR. Reviewed by Gaurav Khokkar, Founder.

Launch day feels like the end of a project. For the client, it's the start of owning something. If the handover is sloppy, they find out months later, usually when the domain is about to expire and the renewal email goes to a developer who left two jobs ago.

We take over a fair number of sites from other teams, and the problems we find are usually about who owns what, and rarely in the code. The domain sits in a freelancer's personal account. The only Google Search Console owner is an ex-employee. The .env file lives on one laptop.

So we treat handover as a deliverable with its own checklist, below.

1. Make a list of every account the site depends on

Before you transfer anything, write down every service the site touches.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.