Your Final Files Shouldn’t Need a Rescue Party: Build a Handover Folder That Works
Photo: Biswarup Ganguly, CC BY-SA 4.0, via Wikimedia Commons
The final handover is where a lot of freelance goodwill goes to die. You send a ZIP called final_files_v7.zip, the client asks for the logo in a different format three weeks later, and you spend an evening hunting through old exports. A better folder structure will not make you a better designer, but it will make you look like a studio that has its act together, and it will save your sanity.
What the handover folder is actually for
It is not just a dump of files. It is a user manual for the project. A good handover folder answers the obvious questions before anyone has to ask them: what is in here, what is approved, what is editable, which fonts are used, what the licences allow, and how the client should use the assets.
That matters most when you are a solo creative. The client is not comparing you to a huge agency with a studio manager and an account team. They are comparing you to the last freelancer who sent a confusing folder and then went quiet. A clear handover makes you look reassuringly professional without requiring a single extra meeting.
The template
Use this as a starting point. Rename the project and date, then delete anything that does not apply.
ProjectName_Handover_2026-11-08/
├── 00_START_HERE/
│ ├── READ_ME_FIRST.pdf
│ └── Asset_Index.xlsx
├── 01_Final_Deliverables/
│ ├── Logo/
│ │ ├── [SVG](https://en.wikipedia.org/wiki/SVG)/
│ │ ├── PNG/
│ │ └── PDF/
│ ├── Print/
│ ├── Web/
│ └── Social/
├── 02_Editable_Files/
│ ├── Brand/
│ └── Layouts/
├── 03_Fonts_and_Licences/
│ ├── Font_Licence_Summary.pdf
│ └── [Only include font files if the licence allows]
├── 04_Exports_and_Specs/
│ ├── Colour_Profiles/
│ └── Print_Specs.pdf
└── 05_Archive_Note/
└── Project_Archive_Note.pdf
The exact names matter less than the logic. Start with orientation, then deliverables, then editable files, then fonts and licences, then specs, then the archive note.
Name things like a grown-up
Layer naming is where good intentions go to die. ‘Layer 47 copy’ tells nobody anything. Use a simple hierarchy that another designer could follow: Logo / Primary / Wordmark, Text / Headline / H1, Button / Primary / Default. If a layer is hidden or unused, delete it or move it to an ‘unused’ group rather than leaving a mystery.
File names should follow a pattern too. Pick something like Client_Project_Asset_Type_Version_Date and stick to it. Use ISO dates such as 2026-11-08 rather than 08.11.26, especially if the client works internationally. Use v01, v02 and v03 rather than final, final2, final_final and final_really.
Package fonts and licences without crossing a line
Do not send font files unless the licence allows it. This is the part that turns a tidy handover into a liability if you get it wrong. Include a Font Licence Summary instead: font name, foundry, licence type, what it covers, where the client can buy it, and whether files are included.
If the client needs editable files but does not have the font licence, either they buy the licence or you provide outlined versions. For web projects, include webfont files only if the licence permits it and the client has the right to use them. If in doubt, link to the foundry and explain the position clearly.
Export client-ready assets, not designer-ready clutter
Give the client what they asked for and a few sensible extras. A logo folder might include SVG for scalable use, PNG with transparency at a couple of sizes, and PDF for print. A print folder should include print-ready PDFs with the right bleed, crop marks and colour profile. A social folder should use platform names and dimensions rather than cryptic codes.
The Asset_Index.xlsx is the quiet hero here. List each file, what it is for, its format, dimensions and any notes. That one spreadsheet can stop a dozen ‘which file do I use for LinkedIn?’ emails.
The archive note that stops future-you from groaning
A short archive note is not busywork. It is a one-page memory aid for the next time the client returns, or the next time you need to update the work. Keep it to a page and include the useful facts:
Project: [name]. Client: [name]. Completed: [date]. Scope: [brief summary]. Master files: [location]. Deliverables: [list]. Software and versions: [details]. Fonts and licence status: [details]. Colour and print specs: [details]. Known limitations: [anything future-you needs]. Contact: [name and email].
Store the archive note with your project records, not just inside the ZIP. If the client loses the folder, you still have the useful context.
A simple handover ritual
- Duplicate the master project folder into a fresh handover folder.
- Remove junk, old versions and anything containing client personal data that does not belong in the final pack.
- Export the final assets into the right subfolders.
- Check fonts and licences, and write the Font Licence Summary.
- Write the README and the archive note.
- Zip the folder with a clear name, including the project and date.
- Send a short email that points to the three most important files or folders.
- File the archive note with your invoice and project records.
It takes an hour on a small job and maybe half a day on a bigger one. In return, you get fewer support requests, a more professional impression and a client who is far more likely to come back. Your final files should not need a rescue party. Build the folder once, use it every time, and get on with the next project.
