Project Handoff Checklist: How to Deliver Work Professionally

The end of a project is the part clients remember. Weeks of careful work can be undone by a rushed handoff: a zip file with cryptic names, a missing font, a login nobody can find six months later. A calm, complete handoff does the opposite. It makes the client feel looked after and makes them far more likely to work with you again.

This checklist covers everything from the final quality check to the follow-up after delivery. It is written for freelancers and small agencies delivering design, web, content or marketing work, and you can adapt it to your own process.

What a good handoff achieves

A professional handoff should leave the client able to:

1. Find every final file quickly, now and a year from now.
2. Use the files correctly, in the right format for each purpose.
3. Own what they paid for, with rights and licenses clear.
4. Control every account and system involved, without depending on you.
5. Know what happens next: support, maintenance and how to reach you.

Keep these five outcomes in mind. Every item in the checklist serves one of them.

Step 1: Run the final checks

Before you package anything, confirm the work itself is finished.

Match deliverables to approvals

Go through the list of deliverables in your agreement and check each one against the approved version. If a file changed after approval, even slightly, make sure that change was agreed. The approval record should point to the exact version you are delivering.

Quality check

• Proofread all text, including alt text, metadata and small print.
• Check every link, button and form on web projects.
• Test on the devices and browsers named in the agreement.
• Check file exports open correctly on a machine other than your own.

Accessibility check

For web and digital work, accessibility is part of quality. The W3C's Web Content Accessibility Guidelines (WCAG) 2.2 are the current W3C Recommendation and a widely used reference (W3C). Even if your agreement did not set a formal conformance level, basic checks are worth doing before handoff:

• text has enough contrast against its background,
• images that carry meaning have useful alt text,
• every interactive element can be reached and used with a keyboard,
• headings follow a logical order,
• forms have visible labels.

If the agreement does require a specific level, document what you tested and how.

Step 2: Package the deliverables

Clients often open the handoff package months later, when they need one specific file. Organize for that moment.

Use a predictable folder structure

ClientName_ProjectName_2026-10/
  01_Final/
    Logo/
      SVG/
      PNG/
      PDF/
    Brand-guidelines/
  02_Source/
  03_Fonts-and-licenses/
  04_Documentation/
  README.pdf

Name files for humans

Use a consistent pattern such as client_asset_variant_size.ext, for example acme_logo_horizontal_dark.svg. Avoid words like "final" and "new" that mean nothing a month later.

Include the right formats

Think about where each asset will be used and include formats for each use: vector files for print and scaling, PNG or WebP for web use, PDF for documents and proofs. If the client's team uses specific tools, ask which formats they can open before you export.

Separate final from source

Put editable source files in their own folder (if your agreement includes them), so non-designers on the client's team are not confused by working files. If source files are not included, say so in the documentation.

For large packages, see our guide to sharing large files with clients.

Step 3: Make ownership and licenses clear

Clients need to know what they own and what they are licensed to use.

• Ownership of the work. Your agreement should state when rights transfer, often on final payment. In the US, work by an independent contractor is generally not a "work made for hire" unless it falls into specific categories and the parties sign a written agreement saying so; the U.S. Copyright Office explains this in Circular 30 (U.S. Copyright Office). Because the details matter, have a lawyer review how your contract handles ownership, and confirm the transfer in writing at handoff.
• Third-party licenses. List every font, stock image, icon set, plugin or template used, with the license holder and terms. Note which licenses are in the client's name and which they need to purchase themselves.
• Portfolio rights. If your agreement allows you to show the work, confirm any timing or confidentiality limits.

Step 4: Hand back accounts and access

This is the step most often rushed, and the one that causes the most trouble later.

Transfer, then remove

For each account or system you set up or used (domain registrar, hosting, CMS, analytics, social profiles, email marketing, app stores):

1. Confirm the client has owner-level access on their own login.
2. Transfer billing to the client if you were paying on their behalf.
3. Remove or downgrade your own access, as agreed.

Pay attention to how each service handles ownership. Google Search Console, for example, distinguishes verified owners, delegated owners and users, and notes that removing an owner does not remove their verification tokens, which should also be cleaned up (Google Search Console Help). Check each service's own documentation rather than assuming.

Handle passwords safely

Do not send credentials in the handover email. Where a shared password exists, transfer it through the service's own user management or a password manager's sharing feature, and suggest the client changes it afterwards. NIST's digital identity guidelines require services to support password managers because they make strong, unique passwords practical (NIST SP 800-63B); recommending one to your client is a useful parting tip.

Keep an access log

Your onboarding should have recorded every access you received. Use that list now and tick each item off as returned. Our guide to organizing client assets covers how to keep that list from the start.

Step 5: Write a short handover document

A one- to three-page README saves the client (and you) many future emails. Include:

• What's included: the folder structure and what is in each folder.
• How to use it: which file to use for which purpose ("use the horizontal logo on light backgrounds; the stacked version for square spaces").
• How to update it: for websites, how to edit pages, add posts and where settings live. A short screen recording works well alongside the document.
• Accounts: a list of systems and who now owns each one (no passwords).
• Licenses: the third-party license list from Step 3.
• Support: what is covered after delivery, for how long, and how to request help.

Step 6: Hold a short handoff meeting

For larger projects, a 30-minute call is worth it. Walk through the package, show how to use the main pieces, confirm access works for the client, and answer questions. Record the call (with permission) and add it to the documentation folder.

Step 7: Send the delivery message

The delivery message should be complete enough to stand alone.

Subject: Final delivery: Acme brand identity

Hi Priya,

The final brand identity package is ready. Here's what's included:

• Final logo files (SVG, PNG, PDF) in light, dark and one-color versions
• Brand guidelines PDF (v2, approved May 28)
• Source files and the font license details
• A README explaining which file to use where

Accounts: you are now the owner of the font license account; our access has been removed.

Support: we'll fix any issues with the delivered files free of charge until July 15.

Keeping files: please download and store a copy in your own systems. We'll keep a project archive for 12 months.

Thank you for the trust and the good collaboration.

Step 8: Close the loop

• Send the final invoice as agreed and confirm when it has been settled.
• Archive the project with your own notes: what went well, what to change.
• Follow up two to four weeks later to ask how things are going and whether they need anything.
• Ask for feedback on how the project ran. It improves your next handoff.

The complete project handoff checklist

Final checks

• Every deliverable matched to its approved version
• Proofreading, link and device checks done
• Accessibility basics checked (and documented if required)

Package

• Predictable folder structure
• Human-readable file names
• Right formats for each use
• Source files separated (or exclusion stated)

Ownership

• Rights transfer confirmed in writing
• Third-party licenses listed
• Portfolio rights confirmed

Access

• Client has owner access on every system
• Billing transferred
• Your access removed or downgraded
• No passwords sent by email

Documentation and delivery

• Handover document written
• Handoff meeting held (larger projects)
• Delivery message sent with support and retention terms

Close

• Final invoice sent
• Project archived with notes
• Follow-up scheduled

Making handoff easier from day one

The best handoffs are prepared throughout the project, not assembled in the last week. Keep files versioned, decisions recorded and access logged as you go. If your deliverables already live in one organized place, the handoff becomes a final tidy-up rather than a scramble.

That is the idea behind Clientwharf's file delivery: final files sit in the client's private portal with their version history, downloads use short-lived signed links, and the approval record for each deliverable can be exported as a PDF. Whatever you use, aim for a handoff the client can return to a year from now and still understand.