Photography
Make the photo delivery promise specific enough to keep
Editorial team · Reviewed
Delivery is easier to manage when the promise defines what arrives, when, and what the client can do with it. A gallery link by itself leaves many important questions unanswered.
A practical sequence
- Specify the included files, selection process and expected delivery window.
- Explain download permissions, any expiry and the support route.
- Separate gallery delivery from album design and physical-product fulfillment.
- Send an early update when the promised timing needs to change.
Work through an example
The package includes an edited gallery and an album design after the couple chooses favorites. The gallery can be delivered while the album remains open. The client sees two clear next steps instead of wondering whether the whole booking is finished.
Where judgement matters
Test the gallery as the recipient before sending it. Check the actual download policy, password behavior and mobile experience. A private preview that works for the photographer does not prove the couple has the intended access.
Make it usable
Open the working tool and replace its sample assumptions with your own. Adapt the structured template to record the resulting decisions and handoffs. Review the finished version with the person responsible before it becomes an instruction to someone else.
Work the decision
A practice case
An original fictional scenario. Numbers are illustrative inputs; this is not a customer result or a provider performance claim.
A studio promises a preview in seven days and a full gallery in six weeks. These are two deliverables with different review steps. A progress message saying editing underway may reassure the client but does not explain whether either date changed. Make the delivery promise specific enough to monitor and revise honestly.
| Decision | Why it matters |
|---|---|
| Define what each delivery includes. | A preview count, selection policy and final-gallery scope prevent different expectations from sharing one label. |
| Plan review and export before the deadline. | Color checks, filenames, access testing and download policy consume real time after editing. |
| Communicate a changed date before it passes. | A revised promise should include a concrete next update rather than an indefinite soon. |
Make one usable artifact
Create a delivery checklist with promised date, internal review date, responsible person, access test and the message the client will receive.
Then test the difficult case
The gallery uploads successfully but a client cannot download the allowed files. Keep delivery incomplete until the recipient’s actual access has been tested.
Use the linked tool or structured template below to record the result. Confirm it against the actual people, agreements and permissions before using it for an event.