Don't lose knowledge when a freelancer leaves: a handover checklist

Freelance engagements end, and that is normal. The problem is when knowledge walks out the door with the freelancer: passwords nobody else has, systems nobody understands and decisions nobody wrote down. A good handover process prevents this and makes the next person productive quickly.

Plan for the handover from day one

The best handovers start at the beginning of the engagement:

• Everything lives in your accounts: code repositories, design files, cloud services, analytics and documents
• Documentation is part of the work, not an extra at the end
• Decisions are written down in tickets, pull requests or a decision log
• Credentials are stored in your password manager, never only on the freelancer's laptop

Include these expectations in your contract and onboarding. See onboarding remote freelancers.

What good documentation looks like

Documentation does not need to be long. It needs to answer the questions the next person will ask:

• What is this and why does it exist?
• How do I run it, build it or publish it?
• How is it structured? A short overview and a diagram if useful
• What are the known problems and risks?
• What would you do next?

The handover checklist

Work and files

• All code pushed to your repository, on the main branch or clearly labeled branches
• All design files, assets and source files in your shared drive
• Final versions of documents, with editable source files

Access and accounts

• List of every service the freelancer used, and which account it belongs to
• Credentials moved to your password manager
• Any accounts created in the freelancer's name transferred to your company
• Access removed or downgraded on the last day. See secure access for freelancers.

Knowledge

• A written handover document using the questions above
• A recorded walkthrough of the main systems or files, 30 to 60 minutes
• A list of open tasks, known bugs and ideas
• Contacts for vendors, tools and partners they worked with

Legal and finance

• Final invoice reviewed and paid
• Confirmation that intellectual property has been transferred under your contract. See protect your IP.

Overlap when you can

If a new freelancer or employee is taking over, arrange a short overlap: a few days or a couple of paid sessions where the outgoing freelancer explains the work and answers questions. It is one of the best investments you can make in continuity.

Keep the door open

End engagements on good terms. Pay promptly, thank them and ask whether they would be available for occasional questions at their normal rate. Many companies keep a former freelancer on a small retainer for a few months after a handover.

Frequently asked questions

How long should a handover take?

For most engagements, plan for one to five days of handover work, depending on how complex the systems are and how well they were documented along the way.

Should I pay for handover time?

Yes. Handover is real work, and paying for it makes it more likely to be done well. Include it in your contract and budget from the start.

What if a freelancer leaves suddenly?

This is why documentation, shared accounts and your own password manager matter from day one. If those are in place, a sudden departure is inconvenient rather than a crisis.

Build continuity into your team

HireCurated freelancers are vetted for communication and documentation habits, not just skills. Request a shortlist.