Photography Client Approval Workflow: Proofs, Selects, Revisions, and Final Files

A photography client approval workflow starts when the studio sends a controlled proof set with clear image identifiers, review instructions, a deadline, and a named approver. The client then submits confirmed selections and image-specific comments. Each revision returns for review as a new version, and only the exact version approved by the authorized reviewer should move into final quality review and delivery.

Sending a gallery does not create an approval process.

A client may open the proofs, mark several favorites, send separate comments by email, and ask an agency contact to review another version. The photographer may treat the favorites as final selects, while the retoucher works from a screenshot containing different filenames.

The files exist. The decisions do not line up.

StudioHero helps photography teams connect media records, project tasks, review notes, file status, QC work, and client delivery. Our photography studio management software gives producers, photographers, editors, and retouchers a shared record of what the client reviewed and what must happen next.

A working photography client approval workflow should answer the following:

1. Which proof set did the client receive?
2. Who reviewed it?
3. Who has authority to approve the work?
4. Which images became confirmed selects?
5. Which comments apply to each image?
6. Which revision is currently under review?
7. Which exact version received approval?
8. Which files can move to final delivery?

Define What Each Client Decision Means

Studios often use favorite, select, approved, and final as though they mean the same thing. They do not.

Favorite

The client likes an image or wants to consider it further. A favorite may become part of a shortlist, but it is not necessarily approved for retouching.

Select

The client has chosen the image to move into the next agreed production stage. That may mean retouching, cropping, color work, or final preparation.

Changes Requested

The client reviewed a specific version and identified work that must be completed before approval.

Approved

The authorized reviewer accepts the exact version under review and allows it to move into the next agreed stage.

A client can select an image without approving the retouched result. They can also like a proof without choosing it as part of the final set.

Your studio should define these terms before the first review begins.

Set the Approval Stages Before Sharing Proofs

Every photography project should move through named review stages.

A useful status structure may include:

1. Internal review
2. Proof set ready
3. Client review open
4. Selects received
5. Retouching in progress
6. Revision ready
7. Changes requested
8. Final approval pending
9. Approved
10. QC required
11. Ready for delivery
12. Delivered

Each status should tell the team what has happened and what action comes next.

“Proof set ready” means the studio has prepared the review files but has not sent them.

“Client review open” means the reviewer has received access and the studio is waiting for a decision.

“Changes requested” means the reviewed version has not passed.

“Approved” means the exact image or set can proceed under the agreed workflow.

A vague status such as client reviewing does not tell the team whether the client is choosing images, reviewing retouching, or approving delivery files.

Stage 1: Complete the Internal Selection

The client proof set should not contain every captured frame.

Before release, the photographer, editor, producer, or creative lead should review the shoot and remove files that should not move forward. These may include clear test frames, technical failures, unwanted duplicates, accidental captures, or images that do not meet the brief.

The studio should record:

1. Who completed the internal review
2. Which images passed
3. Which image identifiers entered the proof set
4. Who approved the proof set for release
5. Which files remained outside client review

This is an operating decision, not a lesson in artistic culling. The purpose is to prevent unsuitable files from entering the client approval process.

The related guide, How Photography Studios Organize RAW Files, Selects, and Final Deliverables, should own the wider file structure, naming, metadata, and archive process.

Stage 2: Prepare a Controlled Proof Set

The client proof set should contain only the images approved for review.

Include:

1. Clear image identifiers
2. The correct project or campaign name
3. The current review version
4. Simple review instructions
5. Selection limits where applicable
6. The review deadline
7. The name of the person expected to submit the decision
8. The action required from the client

Proofs are review files. They are not final deliverables.

The client should know whether they are choosing images, reviewing an edit, checking a crop, or approving a final set. Do not send a folder with no instruction beyond “Please review.”

A good review request states the decision required.

For example:

“Please choose the twelve images you want to move into retouching and add any image specific notes by Friday.”

That instruction leaves less room for conflicting interpretations.

Stage 3: Name the Authorized Approver

Commercial photography projects often involve several client contacts.

An art director may comment on composition. A marketing manager may review brand details. A product lead may check labels. An agency producer may manage the overall approval.

Your studio still needs one clear answer to this question:

Who can close the review?

Record:

1. Primary reviewer
2. Other permitted reviewers
3. Final approver
4. Review deadline
5. The decision each person can make
6. The contact responsible for resolving conflicting feedback

Comments and approval are different forms of participation.

Several people may leave notes, but only the named approver should move the project into final approved status. Without this rule, one client contact may approve a file while another requests further changes later.

Stage 4: Ask for One Specific Client Action

Do not ask the client what they think.

Ask them to perform the action required at the current stage.

That action may be:

1. Mark favorites
2. Build a shortlist
3. Submit confirmed selects
4. Add image specific comments
5. Approve a revision
6. Request changes
7. Approve the final set

The action must match the file status.

During proof review, the client may need to submit selects.

During revision review, the client must either approve the version or request another change.

During final review, the client must approve the exact version that will move into delivery.

Clear actions reduce vague feedback and prevent the team from guessing what the client intended.

Stage 5: Separate Favorites, Shortlists, and Confirmed Selects

A favorite is often an early preference.

A client may mark thirty images as favorites even though the project includes ten final retouched files. If the retoucher begins work on all thirty, the studio creates unnecessary work and may move outside the agreed scope.

Use separate states for:

1. Favorite
2. Shortlisted
3. Confirmed select
4. Rejected
5. Decision pending

Retouching should begin only when the required select set has been confirmed under the studio’s process.

A shortlist can help the client narrow options. It should not automatically become the retouching queue.

Stage 6: Record Every Select Against the Correct Image

Each selected image needs an identifier that remains consistent through proofing, retouching, revisions, approval, and delivery.

The selection record should include:

1. Image identifier
2. Selection status
3. Person selecting
4. Selection date
5. Intended use where relevant
6. Retouching requirement
7. Client comment
8. Required next action

Avoid descriptions such as “the close shot,” “the image with the blue shirt,” or “the third one on the second page.”

Those descriptions become unreliable when images move, galleries change order, or several similar frames appear together.

StudioHero’s media asset management software connects media with project records, metadata, QC information, supporting notes, movement history, and delivery activity.

Stage 7: Separate General Feedback From Image-Specific Feedback

Some feedback applies to the full set.

For example:

1. Use the approved crop ratio across the campaign.
2. Keep the color treatment consistent.
3. Match the supplied background reference.

Other feedback applies to one image.

For example:

1. Correct the product label.
2. Remove a visible mark.
3. Adjust the crop around the subject.
4. Use the alternate background version.

Record general feedback at the project or revision round level. Record image specific feedback against the individual image identifier.

Do not bury both inside one paragraph.

The retoucher needs to know which instruction applies to the full batch and which applies to one file.

Stage 8: Clarify Vague Comments Before Retouching Starts

Client comments such as “make it pop,” “it feels off,” or “can this look more premium” do not define a production task.

The producer or client contact should clarify:

1. Which image the comment applies to
2. What visual issue the client sees
3. Which reference should guide the change
4. Whether the request affects crop, color, background, product detail, or another attribute
5. Whether the comment changes the agreed scope

Starting work from unclear comments creates unnecessary revision rounds. The retoucher makes an interpretation, the client sees something different, and the project returns to the same unresolved question.

Clarification should happen before the task moves into production.

Stage 9: Turn Approved Comments Into Revision Tasks

Once the feedback is clear, convert each required change into assigned work.

The revision task should include:

1. Image identifier
2. Current version
3. Requested change
4. Assigned retoucher or editor
5. Due date
6. Review owner
7. Status
8. Open question where needed
9. Related client comment

StudioHero’s production management software connects project tasks, assignments, deadlines, files, and status updates. This gives the producer a clear view of what remains open instead of relying on comments scattered across several channels.

A client comment becomes useful only when the studio knows who must act on it and when the work is due.

Stage 10: Create a New Version for Every Revision Round

Do not overwrite the file the client reviewed.

Each revision should create a new version record with:

1. Source version
2. New version number
3. Revision round
4. Changes completed
5. Retoucher or editor
6. Completion date
7. Review status
8. Outstanding comments
9. Replaced version

The client should always know which version they are reviewing.

Names such as final, final new, latest final, and final approved create uncertainty. A numbered version and clear status are easier to trace.

Version 2 may be ready for client review.

Version 3 may contain the changes requested after that review.

Only one version should hold the approved status at a given stage.

Stage 11: Return Revised Files With a Clear Review Request

When the revised images are ready, tell the client:

1. Which revision round is available
2. Which files changed
3. Which comments were completed
4. Which questions remain open
5. What decision is required
6. When the response is due

Do not request final approval while unresolved comments remain.

A useful revision message might state:

“Revision 2 is ready for review. The crop, product label, and background comments have been completed. Please approve these files or add image-specific changes by Thursday.”

The client should not need to compare messages to understand what happened.

Stage 12: Track Every Revision Round

Even when the studio’s agreement controls the number of included revisions, the production record should still track each round.

Record:

1. Revision round number
2. Date feedback arrived
3. Reviewer
4. Comments received
5. Clarifications required
6. Changes completed
7. Date returned for review
8. Outstanding work
9. New requests added later

This history helps the producer distinguish an incomplete revision from a new request.

Suppose the client asks for a crop change during the first round, then asks for a different background after reviewing the completed crop. Those are separate requests and should not appear as one unclear revision note.

Stage 13: Request Approval for the Exact Version

Final approval must name the file or set under review.

Record:

1. Project
2. Image identifiers
3. Version numbers
4. Approver
5. Approval date
6. Approval status
7. Conditions
8. Permitted next action

“Looks good” may be positive feedback, but the studio should not treat it as final approval when formal signoff is required.

The approval should make the decision clear:

Approved for final delivery.

Approved for export creation.

Approved subject to one named correction.

Changes requested.

The status should reflect the actual decision, not the tone of the message.

Stage 14: Complete Final Quality Review

Client approval confirms that the reviewer accepts the creative result. The studio must still complete its own final QC before delivery.

Check:

1. Correct selected images
2. Correct approved versions
3. Requested changes completed
4. File naming
5. Required format
6. Dimensions
7. Resolution
8. Color profile
9. Crop
10. Output purpose
11. Required export versions
12. Delivery destination

The QC standard should follow the brief and the agreed output requirements.

A product photography file may need a different check from a campaign image or corporate headshot. Do not apply one technical specification to every project.

Record the QC result so the team knows the file passed before delivery.

Stage 15: Create the Final Files

The workflow should distinguish between the approved master and the delivery export.

Approved Master

The accepted high quality version retained by the studio.

Delivery Export

A file prepared for a specific client use, such as print, website, ecommerce, press, or social media.

One approved master may create several delivery exports.

Each export should remain connected to:

1. The approved master
2. The image identifier
3. The version
4. The intended use
5. The output specification
6. The QC status

Do not replace the approved master when creating smaller, compressed, or differently cropped versions.

Stage 16: Deliver Only Approved Versions

The final delivery record should include:

1. Client
2. Recipient
3. Project
4. Delivered image set
5. Image identifiers
6. Version numbers
7. File formats
8. Delivery date
9. Delivery location or method
10. Person completing the delivery
11. Client access or confirmation where recorded

The studio should be able to trace every delivered file back to the approved version.

If the client later asks which files were sent, the answer should not depend on searching an employee’s inbox.

Common Photography Approval Workflow Failures

Proofs Sent Without Instructions

The client receives the files but does not know whether to mark favorites, choose selects, leave comments, or approve the set.

Several Contacts Submit Conflicting Decisions

The studio receives comments from multiple people without knowing who can make the final decision.

Favorites Become Retouching Tasks Too Early

The team starts production before the client submits confirmed selects.

Feedback Arrives Through Several Channels

Comments appear in email, chat, screenshots, phone calls, and separate documents. Nobody has the complete set.

Vague Comments Move Into Production

The retoucher works from phrases that do not describe a specific change.

Previous Versions Get Overwritten

The studio cannot confirm what the client reviewed or what changed.

Informal Praise Becomes Approval

The team treats “looks good so far” as permission to deliver.

QC Happens After Delivery

The client receives incorrect filenames, formats, crops, or outdated versions.

A controlled process prevents these failures by naming the decision, reviewer, file, version, and next action at every stage.

Photography Client Approval Workflow

Workflow Stage	Client Action	Studio Record	Responsible Role	Stage Is Complete When
Internal selection	None	Approved proof image list	Photographer, editor, or producer	The proof set contains only approved review images
Proof preparation	None	Proof set, identifiers, instructions, deadline	Producer or project coordinator	The correct set is ready for release
Proof release	Receive access	Release date, reviewers, review status	Client contact	The authorized reviewer has received the set
Client review	Review proofs	Review activity and comments	Client reviewer	The required decision has been submitted
Favorite or shortlist	Mark preferences	Favorite or shortlist status	Client reviewer	Early preferences are recorded
Final selects	Confirm chosen images	Selection record and image identifiers	Authorized reviewer	The agreed number of selects is complete
Feedback review	Add comments	General and image specific feedback	Producer	Every comment is clear and assigned correctly
Revision task creation	None	Tasks, owners, due dates, source versions	Producer	The required work has been assigned
Revision production	None	New versions and completion notes	Retoucher or editor	The requested changes are complete
Revised review	Approve or request changes	Review version, comments, decision	Client reviewer	The client submits a clear response
Changes requested	Submit required edits	New revision tasks	Producer	Every request has an owner and due date
Final approval	Approve exact version	Approver, version, date, status	Authorized reviewer	The exact file or set receives approval
Quality review	None	QC result and correction status	Assigned reviewer	Every delivery requirement has passed
Delivery export	None	Export version and intended use	Editor or delivery coordinator	Exports match the approved master
Client delivery	Receive final files	Delivery date, recipient, files, versions	Producer or client contact	The approved files have been delivered and recorded

Photography Approval Status Template

Status	Meaning	Next Action
Internal review	The studio is deciding which images can enter client review	Complete the proof selection
Proof ready	The review set is prepared but not yet released	Send it to the named reviewer
Client review open	The client has access and a decision is pending	Wait for the required action
Selects received	The client has submitted confirmed image choices	Review and assign production work
Feedback clarification required	One or more comments cannot yet become tasks	Clarify the request
Retouching in progress	Approved work has been assigned	Complete the revision
Revision ready	A new version is ready for client review	Request approval or changes
Changes requested	The client has not approved the current version	Create the next revision tasks
Final approval pending	The studio is waiting for signoff on the exact final version	Request a clear decision
Approved	The named approver accepted the version	Start final QC and export work
QC required	Client approval is complete but studio checks remain	Complete final review
Ready for delivery	Approved files and exports passed QC	Deliver the recorded set
Delivered	The final files reached the client	Close the delivery task and retain the record

How StudioHero Supports Photography Client Approvals

StudioHero connects the records required to manage photography review and approval work.

Your team can use:

1. Media records linked to clients and projects
2. Searchable metadata
3. Supporting files and project notes
4. Production tasks
5. Assigned owners
6. Due dates
7. File version context
8. QC records
9. Corrective action notes
10. Media status
11. Delivery records
12. Approval history recorded within the project workflow

StudioHero does not replace your photo editing software. It gives the wider studio team a clear record of the file, review stage, responsible person, requested change, approval status, and final handoff.

Approval Must Name the File, Version, and Decision Maker

A photography approval workflow should make every client decision traceable.

Your team should know which proofs the client reviewed, which images became confirmed selects, what changes were requested, which version received approval, and which files moved into delivery.

A gallery alone cannot control those decisions.

StudioHero connects approvals with media records, project tasks, reviewers, revisions, QC work, and delivery history so your team can move images forward without guessing what the client meant.

Book a StudioHero demo to see how your studio can manage photography proofs, client selects, revision tasks, final approvals, QC, and delivery records in one system.