Client Delivery Packaging
Build a download package that names every file, states the usage terms, and stops at a size the client can actually receive.
Tools
Cloudinary, Bunny.net, imgix, SmugMug
Outcomes
Every delivery carries a version and a date • Usage terms travel with the files • Web-sized previews beside full resolution • Every send logged per client
Documentation
Instruction-ready detail below
What breaks
A delivery folder is zipped and sent with no note of which version it is or what the client may do with it, and a year later nobody can answer either question. Full-size files stall on the client connection, so the whole set gets resent.
What the workflow does
- Write a manifest naming every file with its version, size, and date.
- State the usage terms on the manifest and send them with the files, not separately.
- Make a web-sized copy of each file for email, proofing, and the web store.
- Keep the full-resolution set behind a link that expires after the agreed window.
- Log who received which version, and when.
What a human still approves
The account lead signs the terms, and the client confirms the file list before anything is sent. No delivery link goes out until a person has read the manifest and agreed the version.