Skip to content

Workli

Project Handover Checklist: Accounts, Files and Code

The last week of a freelance project is when small oversights become long-term headaches. A domain registered in the freelancer's name. An API key nobody rotated. A design file only one person can open. None of these are dramatic, but each one costs time later.

This is the handover checklist I use. It's written so either side can run it: the freelancer as a closing routine, the client as a final review.

Start with an inventory

Before transferring anything, list what exists. Open a document and fill in four columns: item, where it lives, who owns it now, who should own it.

Typical items:

  • Domains and DNS.
  • Hosting, servers, databases.
  • Code repositories.
  • App store and developer accounts.
  • Third-party services: email sending, payments, analytics, error tracking, storage.
  • Design files and asset libraries.
  • Documents, specs, recordings.
  • Paid licences: fonts, plugins, stock images, themes.

The inventory alone often reveals surprises. That's the point.

A few habits make the inventory more useful:

  • Start it early, ideally a week or two before the end date, not on the last day.
  • Add items as you remember them during the final milestones.
  • Mark anything with a renewal date coming up soon, such as a domain or a yearly licence.
  • Note which items the client has never logged into. Those are the ones most likely to cause trouble later.
  • Keep the finished inventory as part of the handover pack, so the next person working on the project can see where everything lives.

Accounts and access

Work through the list one account at a time.

  1. Transfer ownership of anything that should belong to the client. Domains, repos and app store listings are the usual ones.
  2. Remove the freelancer's access where they no longer need it, or reduce it to read-only if a support period is agreed.
  3. Rotate secrets the freelancer has seen: API keys, database passwords, admin passwords, deploy tokens.
  4. Check billing. Make sure no service is still charged to the freelancer's card, and none of the client's services are about to lapse.
  5. Confirm recovery options. Recovery emails and phone numbers should belong to the client.

Rotate secrets even when trust is complete. It's routine hygiene, not an accusation.

Files, design assets and code


  • Final files in the formats agreed (source plus exports).

  • Design files moved into the client's workspace, not just shared.

  • Fonts and stock assets listed with their licence terms.

  • Brand assets organised in one folder with clear names.

  • Old drafts either archived or clearly marked as superseded.

Code. Code handovers deserve extra care, especially when someone else will maintain it.


  • Repository owned by the client's account or organisation.

  • Main branch contains the final, deployed version.

  • README explains setup, environment variables (names only, not values), build and deploy.

  • Known issues and technical debt listed honestly.

  • Dependencies reasonably up to date, or the outdated ones noted.

  • Deployment works from the client's accounts without the freelancer.

  • Any scheduled jobs, webhooks or cron tasks documented.

A good test: could a new developer get the project running from the README alone? If not, the README needs another pass.

The handover call

A short call closes the loop.

  1. Walk through the inventory together.
  2. Demonstrate deployment or publishing from the client's side.
  3. Show where documentation lives.
  4. Agree on any support period: how long, what's included, how to ask.
  5. Confirm the final payment and the date ownership transfers.

Record the call if both sides agree. It becomes useful documentation.

After the handover

A few loose ends people forget:

  • Freelancer removes local copies of sensitive data, as agreed.
  • Client confirms in writing that the handover is complete.
  • Both sides note any portfolio permissions or NDA limits.
  • Final invoice is paid and receipted.

If the project was recorded as a contract on a marketplace, close it there as well so the record matches reality. On a platform like workli.tech, a completed contract becomes part of the freelancer's verified work history, so finishing it properly matters to them as much as the handover does to the client.

A clean handover is the last impression a freelancer leaves, and it's the first thing the client's next developer will notice. An hour of checklists at the end saves many hours of detective work later.

Writer

Workli

@workli

Working checklists for hiring freelancers, agreeing milestones and closing contracts cleanly.

Comments 0

Replies to this note, oldest first.

No replies yet. Found it useful? Say so below.

Write a reply

A moderator reads each reply before it goes up. A name will do; there is nothing to sign up for.

Plain text, up to 2,000 characters.

More from Workli