Sharing files with clients: the delivery is part of the work

Delivery is part of the work. A client's last impression of a project is often the moment they try to open what you sent — and if that moment involves an account they do not have, a link that died, or an advert on the download page, it colours everything that came before it.

This is about the delivery itself: what the client experiences, and the small decisions that make it feel finished.

What the client should never have to do

• Create an account. The single most common friction. A client should click and download.
• Install anything. Including a desktop sync client, and including your favourite tool.
• Ask for access. A shared folder that requires approval turns delivery into a conversation.
• Work out what they received. Forty files named IMG_4471 is a puzzle, not a deliverable.
• Look at someone else's advertising on a page you sent them.

Name things for the person receiving them

Your naming scheme makes sense inside your project folder. It rarely survives the trip.

Name files as the client will file them: oakwood-brochure-v2-print.pdf, not OW_br_FINAL_v2_use-this-one.pdf. Include the client or project name, what it is, and the version. Skip "final" — it never is, and everybody knows it.

Version numbers beat dates for revisions, and dates beat nothing at all. If the client will circulate files internally, the name is the only context that travels with them.

Structure a delivery

For anything with more than a handful of files, send a folder with an obvious shape:

oakwood-brand-delivery/
  01-logos/
  02-social/
  03-print/
  read-me.txt

The read-me.txt takes two minutes and prevents most follow-up questions: what is in each folder, which format to use where, and who to contact. Clients forward it internally, and it does your explaining for you.

The message matters as much as the files

A bare link with no context looks like phishing, and increasingly gets treated as such. Three lines is enough:

• What this is, in the client's words rather than yours.
• When the link expires, stated as a date.
• What you need back — approval, notes, or nothing.

Saying the expiry out loud is the detail most people miss. "This link works until 4 October" turns a deadline into information rather than a surprise three weeks later.

Choose an expiry that fits the review

A week suits most approval rounds. A month suits a set of assets several people will work through at their own pace. Reserve permanent links for things you are genuinely publishing.

If a client comes back after expiry, resending takes seconds — and a link that expired is a much better outcome than one still live in an old email eighteen months from now, after the relationship has ended. More in how long a download link should last.

Know whether it landed

"Did you get it?" is a slightly awkward email that download counts make unnecessary. If the service mails the link for you, delivery and open receipts tell you the difference between a wrong address and a slow client — worth knowing before you chase.

One detail that matters when a delivery goes to several people: separate messages, not one with everybody in the To field. Two clients seeing each other's addresses is a small thing that looks careless, and occasionally worse.

Deliver in the right format

The most common misjudgement is sending the working file when the client needs the output, or the output when they need the working file. Ask once, at the start:

• Is anyone going to edit this? Send the source, untouched.
• Is it going to be looked at or placed? Send a clean export at the right resolution.
• Both? Send both, in separate folders, clearly labelled.

Guessing wrong costs a round trip and makes it look like you did not ask.

Keep your own record

Six months later, "what exactly did we send them in March?" is a real question, usually asked during a disagreement. A history of what went out, when, and how often it was downloaded answers it in seconds. Keep the record even after the files themselves are gone — the archive is the useful part.

The short version

Nothing to sign into, named for the client, structured with a read-me, a three-line message that states the expiry, separate messages per recipient, and a record you can look back at. None of it takes long, and it is the difference between a delivery that feels finished and one that generates three emails.

Related: how to send a whole folder, sending large video files to clients, and choosing a file transfer service.