The Freelancer's Playbook for Client File Handoffs

When I started freelancing, every client handoff was an unbranded mess: 'Hey here's the latest version', followed by an 800 MB Dropbox link nobody knew what to do with. After a few embarrassing weeks I rebuilt my handoff flow. Now it takes 90 seconds and looks deliberately professional. Here's the version I still use today.

The principles

• →Every handoff is a discrete event — never 'just check my Drive folder'.
• →Expiry is a feature, not a bug. Old versions don't linger.
• →Filenames are signals — they tell the client what stage of the project we're in.
• →Every handoff includes a one-line context note. No silent drops.

Step 1 — Name the file like a professional

Replace 'final_v3_REAL_final.psd' with the format `ProjectName_DeliverableType_YYYY-MM-DD.ext`. Examples: 'Acme_Brand_Logo-Final_2026-02-01.zip', 'Acme_HomepageMockup_v2_2026-02-04.fig'. The client can sort their downloads folder chronologically and find anything you've sent.

Step 2 — Bundle related files in one transfer

If you're sending a Figma export, send the .fig file, a flattened PDF for context, and a one-page change log in the same transfer. The client gets a single 6-digit code instead of three. Multi-file transfers are SendMe's default — just drag in everything that belongs together.

Step 3 — Set the expiry based on review cadence

If you're expecting feedback within 24 hours, set 48-hour expiry (buffer for them to re-download). If it's a final deliverable they need to keep, set 7 days and remind them to save locally. Don't set anything past 7 days — by then you should have moved to the next version anyway.

Step 4 — Add a password for sensitive work

If the project is under NDA, embargoed (unreleased brand launches), or contains personal data (client photos), add a password. Share the code in your email and the password in a follow-up text. The cost is 10 seconds; the upside is a clean conscience.

Step 5 — Send the code with context

Don't just paste a link. Write a three-line email: what changed, what you'd like feedback on, and the code/URL. Example:

Hi Sarah — attached v2 of the homepage mockup. I've revised the hero section based on your notes from Monday. Code: 482931 — sendme.co.in/r/482931. Link expires Friday EOD. Looking forward to your thoughts.

Step 6 — Confirm receipt and close the loop

When the client confirms they got the file, you can mentally close that handoff. Don't keep checking. Don't worry that the link will expire — that's the point. Move on to the next chunk of work.

Bonus: a one-page deliverable index

At the end of long projects, send a final 'index' transfer: a ZIP containing every deliverable from the project, an index PDF that lists what's inside, and the dated change log. Set expiry to 7 days and tell the client this is their archive — they should download and save to their own storage. Then everything you've sent during the project can safely expire.

What this looks like in practice

A typical week for me, as a brand designer, involves three or four handoffs. Each one is a 90-second SendMe upload, a three-line email, and a confirmation reply. There's no version-control debate, no 'which folder was that in', no permanent storage rent. Clients consistently mention they like the deliberate, structured handoff — it makes me look more organised than I usually am.

The tools

I use SendMe for file transport, Notion for the project brief and notes, and a private Loom for screen-recorded walkthroughs. The whole stack costs under ₹2000/month and replaces what used to be three different SaaS subscriptions.