Most freelance projects do not end with a launch. They end with a quiet fade: the last deliverable goes out, the client stops replying, and three months later an email arrives asking where the source files are or how to change a headline. A proper handover prevents all of that. It is a short, structured document that says what was delivered, where everything lives, and what happens next.

The handover has six sections. First, a deliverables list: every file, page, or asset, with a link and a one-line description. Second, access: every account, login, and permission, transferred to the client and removed from your own access where appropriate. Third, documentation: how the work is organized, how to make common changes, and where the style decisions are recorded. Fourth, known issues: anything unfinished, any workaround, and anything the client should watch. Fifth, support terms: what is included after handover and what costs extra. Sixth, sign-off: a line for the client to confirm they have received everything.

For logins, never send passwords in plain email. Use a password manager share or a one-time secure link, and confirm the client has access before you delete your own copy. For design and code, hand over source files, not just exports: the editable design file, the repository, the build instructions. A client who only receives a PDF cannot maintain their own website, and they will come back to you for every small change, which is billable work you did not plan for.

Documentation does not need to be long. A single page usually covers it: where the files are, how to update the three things the client updates most, who to contact for hosting or domain issues, and the renewal dates for any subscription you set up on their behalf. Record a five-minute screen video walking through the deliverables if the project is complex. Clients watch videos; they rarely read manuals.

The handover is also your last chance to get paid and get a testimonial. Send the final invoice with the handover, not after it, and include a short testimonial request in the same message while the project is fresh in the client's mind. Ask one specific question, such as what result mattered most, instead of a generic request for feedback. Specific questions get specific answers, and specific answers win future work.

Build the handover into your project template so it is not a chore at the end of every engagement. A one-page checklist, filled in as the project progresses, takes ten minutes at the end instead of an afternoon of digging through old messages. Clients remember the ending more than the middle. A clean handover is what makes them call you first for the next project.

A one-page handover checklist keeps the process fast. The checklist reads: deliverables listed with links; logins transferred and confirmed; source files handed over; documentation page written; known issues listed; support terms stated; final invoice sent; testimonial requested; client sign-off received. Tick each item as the project closes, and save the completed checklist in the project folder. When the next client asks how you work, that checklist is your answer: organized, complete, and professional to the last day. Keep a copy of every signed handover for at least a year, because warranty questions and tax records both reach back further than memory does. A handover done well is also a quiet sales tool: it shows the next client, through the last client's experience, exactly how professionally you finish what you start.