Photo delivery workflow: from final edit to client download.
A good final delivery is simple, private and obviously finished. Prepare only the approved files, verify them, then give the client a clean place to download.
Confirm the selected set, export final files consistently, verify filename matches and file quality, publish a private final gallery and keep a clear project record after delivery.
1. Start from the confirmed selection
Before exporting finals, make sure you are working from the current approved set. This matters especially when a client has revised a selection. A final-delivery stage should not accidentally include images that were never confirmed.
2. Export with a consistent naming plan
Choose a naming convention that is useful to both photographer and client. If you keep the selected base filenames, matching remains straightforward. If you add prefixes or suffixes, do it consistently and keep the relationship to the selected originals understandable.
3. Verify the files before publishing
Open a representative sample, confirm dimensions and export settings, and make sure the expected file count matches the project. A delivery workflow is the last opportunity to catch a missing or mismatched final before the client sees it.
4. Publish a private final gallery
Make the delivery state visually clear and provide straightforward downloads. The client should not need to guess whether these are previews or finished files. Keep access private and use expiry or revocation controls according to the project.
5. Close the loop without losing the record
After delivery, retain enough project history to answer support questions. Knowing what was selected, what was delivered and when the client accessed or confirmed the delivery can be useful without turning the workflow into a full CRM.
What to avoid
- Exporting before checking the final selection
- Mixing previews and finals without clear labels
- Changing names inconsistently at the last stage
- Publishing a folder before verifying file count and output settings
- Deleting all project context immediately after sending the link
What to do next
Once the client has received the final files, close the project cleanly and keep only the project history and storage that your policy requires.
Related GaliVue product pages
Put the workflow into practice.
Use GaliVue’s Free Test to run one real project from preview sharing through client selection and final delivery.
See plans & start free