A practical client file handoff checklist

The handoff is often the last thing a client sees from a project, and it shapes how they remember the rest of it. A tidy, well-explained set of files feels finished. A folder of cryptic names, missing fonts and a link that has already expired creates a round of follow-up emails just when everyone wants to move on.

This checklist is written for freelancers and small teams who deliver files to clients: designers, small agencies, photographers and audio engineers. Adapt it to your work, then reuse it on every project.

1. Confirm what you owe

Start with the brief, proposal or contract, not with your export folder. List every deliverable you agreed to, including formats, sizes and any source files. It is much easier to notice a missing item on a list than in a folder.

• Are all agreed deliverables finished and approved?
• Do the formats match how the client will use them, such as web, print, social or broadcast?
• Did you agree to hand over editable source files, or only finished exports?

2. Name files so they make sense without you

Your client will search for these files months from now, probably without remembering the project’s details. Good names answer three questions: whose is it, what is it, and which version is it?

A simple pattern works for most projects: client-project-item-variant-date. For example, harbour-cafe-menu-print-a4-2026-10-06.pdf is self-explanatory, while menu_final_v3_REAL.pdf is not.

• Use dates in year-month-day order so files sort correctly.
• Stick to letters, numbers and hyphens. Some systems mangle spaces, accents and symbols.
• Remove words like “final” and “new”. They stop being true the moment a revision arrives.

3. Organise around how the client will use the files

Your working folders reflect how you made something. Delivery folders should reflect how the client will use it. A brand identity, for example, might be grouped as logos, colour and typography, templates, and source files, with each logo available in the handful of formats people actually need.

Keep the structure shallow. If a client has to open four nested folders to find a logo, they will email you instead. When a delivery holds only a few files, a flat list in a sensible order is often clearer than folders at all.

4. Add context

Files rarely explain themselves. A short note turns a pile of exports into a handoff. Include:

• what the delivery contains, in one sentence;
• which file to use for which purpose;
• anything not included, and why;
• licensing or usage notes for fonts, music or stock assets;
• when the download link expires;
• who to contact with questions.

Put the note where the files are. If the context lives only in an email, it gets separated from the files the first time someone forwards the link.

5. Run the final checks

Open every file you are about to send. Not a sample: every file. It is the only way to catch a blank page, a corrupted export or a video that stops halfway through.

• Each file opens and is the approved version.
• Image sizes, colour profiles and resolutions match the brief.
• Internal comments, hidden layers, tracked changes and private notes have been removed.
• Stray system files and drafts are not in the delivery folder.
• The total size looks plausible for what you are sending.

6. Send, then check as the recipient

Large deliveries belong in a download link rather than an email attachment. (If you need a refresher, read how to send large files without email attachments.) Before you send it, open the link in a private browser window and look at it the way your client will: title, note, file order, previews and total size.

Choose an expiry that gives the client a reasonable window, and say the date in your message. Afterwards, ask the client to confirm receipt. SentIt’s download count records requests that started, not completed transfers or page visits. A count alone cannot tell you whether the client saved every file successfully.

The reusable checklist

Copy this into your project template:

1. Every agreed deliverable is finished and approved.
2. Formats and sizes match how the client will use them.
3. Source files are included only if agreed.
4. File names follow one pattern: client, project, item, variant, date.
5. Folders, if any, are shallow and organised by use.
6. Working files, comments and hidden content are removed.
7. Every file has been opened and checked.
8. A short note explains contents, usage and contacts.
9. The link has an expiry date that is mentioned in the message.
10. The link has been opened as a recipient before sending.
11. Downloads have been confirmed, or a follow-up is scheduled.

Where SentIt fits

SentIt is built around this kind of handoff. A delivery has a title and an optional message that appear above the files. You can upload files or add them from Dropbox and Google Drive, put them in the order recipients will see them, and set when the link expires. Recipients get a clean page with previews where available and individual downloads, without creating an account. Download all offers a ZIP within the size and daily request limits; see current delivery limits. Anyone with the active link can access the files, so share it with care.

And if the client asks for one more change after you have sent the link, you can update the delivery without sending a new link.