A photography studio should identify the proof set, selected image references and confirmed editing instructions before preparing final delivery. Keep comments, requested revisions and approved selections separate. Record the authorised delivery version and remaining decisions, so staff can explain what the client selected and which changes were accepted without relying on scattered messages or filenames alone.
- Proof comments and confirmed selections are different.
- Image references need to survive editing and delivery.
- Record accepted revisions against the correct version.
Give proof sets and images stable references
Use a project identifier and proof-set version, with image references that remain understandable through editing. A client selecting image 12 needs a link to the particular set they reviewed. Reordering a gallery without retaining references can make the same number point to a different image.
Record which set was made available and the relevant delivery channel. Staff should distinguish a new proof set from a replacement of the same instructions. Keep the original reference when a corrected upload changes an image or its order.
Separate comments from confirmed selections
A client comment may express a question, preference or requested edit rather than a final selection. Use clear states and a responsible coordinator to confirm the intended set. Do not interpret every marked image as an authorised addition to the final deliverable.
Keep the studio’s agreed scope and responsible decisions linked to the selection record. Commercial and rights questions need the applicable agreements and qualified guidance where required. The workflow should preserve those decisions without inferring licence terms or entitlement from a gallery checkbox.
Track revision requests by image and version
An editing request needs image reference, proposed change and decision state. The editor should see the accepted instruction and any unresolved question. A vague project-level note such as improve colours may be insufficient when different images have different confirmed requirements.
If a later request changes the agreed instruction, preserve the earlier version and the authorised outcome. Staff can then distinguish accepted revision work from a suggestion still awaiting discussion. Avoid silently replacing the brief after editing has begun.
Illustrative scenario: a client selects from two proof sets
Imagine a client sends selections from an earlier gallery while a corrected set is also available. The coordinator maps the requested image references to their actual proof-set version and confirms the intended selection. The editor receives accepted instructions against those identified images.
Final delivery references the confirmed set and authorised editing outcome. This illustrative scenario explains creative handoffs; it does not determine copyright ownership, licence rights, contractual revision limits or the appropriate commercial decision for a particular studio booking.
Keep delivery and acknowledgement distinct
Delivery records what was provided, its version and channel. Client acknowledgement or unresolved feedback is another event. The studio should be able to find remaining questions without treating an uploaded final folder as proof that every selection and revision issue has been settled.
Apply appropriate access to galleries and supporting information under your process. Share only the intended deliverables and necessary context. A staff handoff should not expose unrelated client projects or private notes merely because they happen to sit in the same storage folder.
Evaluate a selection from an older set
Ask a demonstrator to publish a corrected proof set, receive an old-set selection and record a later editing request. The operator should identify the accepted images, instructions and delivery version without opening a private message history. Include one request that remains unconfirmed.
EasyManageX catalogue entries are illustrative. Confirm proof references, revision states and access boundaries with fictional images and project records. A focused pilot can establish reliable selection handoffs before the studio relies on broader delivery or client-portal automation.
Your working checklist
- Create project and proof-set version references.
- Retain stable image identifiers after reordering.
- Separate comments from confirmed selections.
- Link accepted edits to image and version.
- Record final delivery and acknowledgement separately.
- Test an old-set selection and unresolved revision.
Common questions
Can gallery favourites become final selections automatically?+
Use the studio’s confirmed selection process and agreed scope. A favourite can express interest without settling the intended deliverable. Preserve the proof-set reference and ask the responsible coordinator to record the authorised selection, so an informal mark does not silently change editing or delivery commitments.
How should old-gallery selections be handled?+
Identify the proof set and map the image references before issuing work. Preserve the original request and confirm the intended images under your process. Reordered or replaced galleries can make the same number ambiguous, so a stable image identifier is more reliable than position alone.
Does uploading a final folder close the project?+
Record delivery as an event and keep unresolved feedback or acknowledgement tasks visible according to the studio’s process. An upload establishes what was provided, not necessarily that every decision is complete. Preserve the delivered version and the responsible owner for remaining client questions.
Sources and further reading
These primary references explain relevant concepts. Our scenarios and working checklists are original, illustrative guidance.
- ERPNext documentation: Project
Further reading on project tasks and customer handoffs; relevant to photography selection, editing and delivery responsibilities.
Published by EasyManageX as practical, AI-assisted guidance. Examples are illustrative. Confirm software capabilities, licence terms and project-specific requirements before committing. Read our editorial policy.
