A Clear Design File Delivery Checklist
Package a small design delivery with final exports, source-file labels, usage notes, and a concrete feedback request.
Woff field note
Published
Updated
3 min read
A client should not need to guess which image to publish or which file another designer can edit. A delivery package is easier to use when each file has a purpose and the instructions travel with it.
Separate source files from ready-to-use exports
Name the final exports clearly: campaign-square-final.png and campaign-story-final.png are more useful than export-12.png. Label editable source files separately and explain which application the client needs to open them.
Include dimensions, intended use, and any agreed font or image-license instructions. Explain the license requirements in your delivery note rather than suggesting that a file download grants rights you did not sell.
Use a delivery note the client can scan
Create a handoff room, then adapt this note. Remove any format that is not part of the actual delivery.
Design delivery — [campaign] — [version]
Final exports:
- [square filename]: [dimensions], social feed
- [story filename]: [dimensions], story placement
Editable source:
- [source filename]: opens in [application/version]
Usage notes:
- [font or asset licence instructions]
- [crop, colour, or placement constraints]
Review request: reply with the filename and the change.
Download deadline: [expiry shown in this room]Attach the package and check it finished
Use Photos for image previews and Files for the source package. Each file must be at most 50 MiB, and a batch can contain up to 20 files. The room and sender allowances also apply; see help.
Wait for the batch to publish before sharing the invitation. If a source archive is too large, put it in your existing storage service and include the agreed access link with a clear label.
Make feedback specific
Ask for a filename and a requested change. For a visual correction, a marked-up screenshot can show the exact area. A new annotated image preserves the original context and keeps the review focused.
The delivery note has one editing owner. Recipients can send feedback in the room, but the note is not a shared editing canvas or a formal design approval system.
Archive the accepted version yourself
Save the final source files and agreed feedback in your usual archive. Standard rooms expire after 48 hours without activity; Pro pilot rooms, where available, have fixed 7- or 30-day deadlines. Downloading a file creates a copy that later link revocation cannot remove.
Check pricing before expecting a paid retention feature. The freelancer workflow shows how to do a small delivery with the current free tools.