How-To & Tutorials
Freelance Client Handoff Checklist: Transfer Access Without the Lockout
Freelance Client Handoff Checklist: Transfer Access Without the Lockout

☰ Table of Contents
A freelance client handoff checklist is not just a folder of final files. It is the controlled transfer of ownership, access, decisions, and unfinished obligations, without leaving a client locked out or your own accounts exposed. The risky part often happens weeks after the project is “done,” when a password changes, a renewal lands, or nobody remembers who owns the domain.
This guide lays out a repeatable client project handoff for web, design, marketing, and automation work. It focuses on the handover details freelancers often miss: account ownership, least-privilege access, billing, and a clean offboarding trail. For client work more broadly, see our guide to a clear freelance revision policy.
Why Client Handoffs Break After “Done”
Most handoffs are treated as a delivery event: send the files, invoice the balance, archive the project. But a project may depend on accounts the client does not control yet, a paid plugin attached to the freelancer’s card, or an admin login shared over chat. Those dependencies work right up until the first change of staff, billing cycle, or password.
The goal is not to hand over every credential indiscriminately. It is to make the client able to operate what they bought, while removing your access only when the work and support agreement allow it. That distinction prevents two common failures: the client inherits a fragile setup, or you remain an unacknowledged administrator indefinitely.
Map Access Before You Touch Anything
Start with an inventory, not a password dump. List the systems used and record who owns each one, who pays, and what role the client currently has. Include domains, hosting, CMS, analytics, ad accounts, email platforms, repositories, cloud storage, design tools, and recurring integrations. A system can be “theirs” in practice but still be registered to your email address.

| Asset or account | Record before handoff | Safer transfer pattern |
|---|---|---|
| Domain and DNS | Registrar, registrant contact, renewal date, nameservers | Client-owned registrar account; invite named user or transfer ownership |
| Hosting and CMS | Account owner, billing party, admin roles, backups | Client account with individual admin; verify a recovery route |
| Analytics and ads | Property/account ID, current users, payment profile | Grant the client admin; avoid sharing a personal login |
| Code and design files | Repository or workspace, license, source-file location | Transfer project or invite client to their own workspace |
| Integrations and secrets | What connects, where credentials live, what breaks if rotated | Client-controlled secret store; rotate keys after verification |
Keep the inventory in a client-approved place and avoid putting live passwords in the checklist. Use each service’s invitation or ownership-transfer flow where possible. If a service only supports credentials, agree on a secure transfer method and ask the client to change the password after confirming access.
Choose the Right Handoff for Each Asset
“Transfer everything” sounds simple, but different assets have different ownership rules. A domain may need a registrant change; a software workspace may support an admin invitation; a source-code repository may need a transfer that preserves history. Use the platform’s documented ownership process instead of sending your own login.
- Client-owned from day one: Build inside the client’s accounts whenever practical. Invite your own named user, then remove or downgrade it after acceptance.
- Freelancer-owned but transferable: Confirm transfer eligibility, destination account, billing and any lock or waiting period before initiating it.
- Licensed or subscription asset: State what is included, what renews, and what stops if the client does not buy their own license. Do not imply that a personal subscription transfers automatically.
- Shared service account: Replace shared credentials with individual accounts and role-based access before closing the project.
For broader tool selection and workflow considerations, browse the How-To & Tutorials category. The right setup is usually the one the client can maintain without needing your personal account.
Build a Handoff That Can Be Repeated
A good client handoff document answers operational questions rather than narrating the whole project. Keep it short enough to use and specific enough to act on. Include:
- What was delivered: link to final files, source files, backups and documentation, with dates or version labels.
- Where it lives: storage location and the client-side owner who can restore access.
- How to do the routine task: the few steps the client will need, such as publishing a page or changing a campaign budget.
- Known limits: licenses, third-party dependencies, browser or device caveats, and work not included.
- Support boundary: the end date of included support, response expectations, and how new requests are scoped.

Do not bury the important information in a long screen recording. A short walkthrough can help, but pair it with written steps, account ownership, and a way to request access later. Store any video where the client controls retention and permissions.
Test the Exit, Not Just the Delivery
A client successfully opening a shared folder proves very little if the folder is still owned by your personal account. Test the handoff using a client-side user or have the client perform the key actions while you observe. Verify the access they need, then check that your own access can be removed without breaking the service.
| Test | Pass condition | Evidence to note |
|---|---|---|
| Ownership | Client appears as owner or designated administrator where appropriate | Account name and role, not a password |
| Recovery | Client controls recovery email, MFA and billing contacts | Client confirms each setting |
| Routine operation | Client can complete one representative task unaided | Task tested and date |
| Dependencies | Site or workflow still functions with freelancer access removed, if intended | Observed checks and exceptions |
| Backup and restore | Client can locate a current backup and knows the restore route | Backup location and last verified date |
Never remove your only working admin access before the client confirms their own access. Conversely, do not keep elevated access indefinitely “just in case.” Set a dated checkpoint to remove or reduce it, consistent with the contract and any agreed support period.
What to Keep, Transfer, and Remove
Keep the project record that supports your contract, invoice, and agreed business documentation. Transfer the deliverables and operating information the client purchased. Remove temporary accounts, test data, copied exports, and credentials that no longer serve a documented purpose, following the client agreement and any applicable retention duties.
For credentials, rotation is usually cleaner than passing around an old shared password. Create client-owned accounts or keys, test them, update integrations, then revoke the old credential and confirm the service still runs. Record the change without recording the secret itself.
A 30-Minute Client Closeout Checklist
For a small project, this sequence makes the final check manageable. Complex projects may need a longer security or legal review, but the order still helps:
- Minutes 0–5: reconcile deliverables against the scope and label final versions.
- Minutes 5–10: review the account inventory, owners, billing contacts, access roles and renewal dates.
- Minutes 10–18: invite or transfer the client’s named account, then have them confirm access and recovery control.
- Minutes 18–24: test one routine task, one backup location and any critical integration.
- Minutes 24–30: send the handoff document, list open items and support end date, then schedule any agreed access removal.
Send a concise written closeout afterward: what transferred, what remains open, what you will revoke and when, and who owns the next action. This gives both sides a reference if the project resurfaces months later.
FAQ
Should a freelancer create client accounts using their own email?
For systems the client will own and operate, use a client-controlled account whenever possible. If you need temporary setup access, invite your named account and plan its removal rather than making your personal email the permanent owner.
Is it safe to send passwords in a handoff document?
Generally, avoid placing passwords in ordinary documents or email. Prefer platform invitations and a reputable secure sharing method if a credential transfer is unavoidable, then have the client rotate it and enable multifactor authentication.
When should I remove my admin access?
After the client verifies their own access and the contract’s delivery or support conditions are met. Agree on a date, and first confirm that removing your role will not disable a needed integration or recovery path.
What if the client wants to keep using my software subscription?
Explain whether the license is transferable and what it costs or permits. Do not assume the subscription can be assigned to a client; check the vendor’s current terms and document the alternative if a client-owned plan is required.
What belongs in a website handoff?
At minimum: domain and hosting ownership, CMS roles, backups, source files, key integrations, renewal details, routine maintenance steps, and a clear list of items outside the project scope.
How do I close a project when a client stops responding?
Follow the notice, acceptance, payment, and retention terms in your agreement. Send a dated summary of the deliverables and access state through the agreed channel, avoid unilateral destructive changes, and get professional advice if ownership or payment is disputed.

