Client Photo Proofing and Approval Workflow

Give every proofing round one clear decision

A dependable proofing process connects one identified photograph, one requested decision and one recorded version. A gallery of attractive images is only the presentation layer. You also need to know who selected them, whether the selection is finished, what happens next and which files eventually satisfy the request.

Begin by defining the round. Are clients choosing photographs for retouching, confirming the treatment of finished portraits, selecting prints or approving an album layout? Those decisions can involve the same image, but they are not interchangeable. A favorite does not automatically approve a crop, retouch or printed product.

State who is expected to decide. A wedding couple may submit a joint album list while relatives make separate print choices. A commercial job may involve both the person photographed and a brand representative. Do not let one unlabeled favorites list become the accidental authority for every deliverable.

This article concerns the review and approval system itself. The post-production guide covers editing and output around it. The examples here are original hypothetical workflows; they do not describe a live Lightbox Pro gallery or an observed client project.

Review set v01Known image IDs and a defined question

Submitted choicesReviewer, purpose and completion recorded

Production snapshotSelected sources and accepted instructions

Retouch approvalWhich treatment is accepted?

Print choiceWhich image, crop, size and quantity?

Album approvalWhich layout and cover version?

Prepare a review set that is complete enough to choose from

Start with the photographer’s review, not every frame on the cards. Remove irrelevant tests and obvious mistakes from the proof set while retaining useful alternatives. For a choice between expressions, show enough context to make a real decision without presenting an exhausting burst as if every frame were equally different.

Group the set according to the task. For a wedding, parts of the day may help navigation. For headshots, separate people or departments. For print selection, a clear shortlist can be more useful than the full delivered job. Label groups in language the client understands rather than internal camera or processing terms.

Decide what stage of finish the proofs represent. A selection proof can precede detailed retouching, but explain that fact and what further work is included. If the client is reviewing color or skin treatment, the proof must show a sufficiently representative treatment; do not ask them to approve an appearance that has not yet been produced.

Keep an immutable record of the review set’s version and identities. If you replace photographs after a link is shared, you can invalidate notes that refer to their earlier order. Additions, replacements and removals deserve a new recorded set or an explicit update, not a quiet change beneath existing comments.

Keep filenames, review numbers and source identities connected

A display number is convenient for conversation, but it can change when the gallery is reordered. A camera filename can repeat across cards or cameras. A delivered filename may differ from both. Keep a mapping that can resolve a selection to one exact source and the intended rendered version.

For example, proof Harbour_P023 might map to Camera-B/Card-02/IMG_3418.CR2 and the rendered proof Harbour_P023_v01.jpg. The identifiers are an illustrative convention, not a required filename pattern. The useful property is that the client’s P023 cannot silently become a different photograph.

Scroll across to read all columns.

Do not rename proof files after selections arrive unless you preserve and verify the mapping. Likewise, avoid removing numbers from the final files without keeping a delivery cross-reference. A well-designed proofing experience should make later reconciliation easier, not conceal the underlying identity problem.

Choose hosted galleries or local proofs around the task

A hosted gallery can provide remote viewing, favorites and comments. A local viewing session can support a guided comparison on a controlled display. A numbered contact sheet can work well for a small review when paired with an exact response list. Each route needs an explicit way to finish and retain the decision.

Pixieset’s proofing documentation describes favorites, comments, notifications and exportable selection lists. These are documented capabilities of that hosted product, not evidence of a Lightbox Pro integration. If you use a gallery service, test the exact selection and export path available to your account.

Its Client Gallery setup guide also documents collection sets, privacy and download controls, and favorite lists with notes or selection limits. Use those settings deliberately. A shared collection, hidden gallery, password and download restriction answer different questions; enabling one does not establish all of them.

Scroll across to read all columns.

Do not choose a method solely because it minimizes your upload work. A client choosing among several near-identical expressions needs a different presentation from someone confirming five already finished portraits. Match the viewing detail and response mechanism to that decision.

Set access, downloads and watermarks before sharing

Review the set as a recipient before sending the link. Check whether unrelated jobs are visible, whether names or comments expose information to the wrong audience, and what a forwarded link permits. A privacy setting described in marketing is not a test of your particular collection.

Separate the ability to view, comment, select and download. If family members can view the wedding gallery but only the couple submits the album list, make that distinction explicit. If a commercial reviewer can approve an edit but not distribute originals, do not assume that hiding a download button communicates the entire agreement.

Use an access-controlled route appropriate to the material and the agreed audience. Keep account passwords and administrative access separate from client links. Where a service provides expiry or revocation, verify its current behavior rather than promising that a forwarded or downloaded copy can be recalled.

A watermark can identify a proof and discourage casual reuse, but it is not access control and cannot prevent a screen capture. Keep it from concealing the very expression, clothing or detail the client must judge. If unwatermarked detail is needed for a controlled retouching review, arrange that deliberately rather than sending the unrestricted master by default.

For color-sensitive approval, explain the limits of uncontrolled screens. A phone in bright sunlight and a maintained studio display are different viewing conditions. Use an appropriate physical proof or controlled review when the decision depends on print color or subtle detail. Do not promise that every remote screen will match the final product.

Write instructions that say what to do and what happens next

Keep the instructions short enough to use while looking at the photographs. Specify the purpose, selection method, number or range if applicable, deadline, completion action and where revision notes belong. Explain whether choices may still change after submission and what the photographer will do with them.

One hypothetical selection instruction might read: “Choose the portraits you want finished from review set v01. Use the image ID in any note. Submit the completed list when you are ready; saved favorites alone are treated as work in progress. We will confirm the received list before retouching.” Adapt the wording to the service’s actual behavior; do not invent a Finish button that the chosen tool lacks.

Give a concrete example of a useful note. “P023: soften the temporary mark near the glasses” is more actionable than “fix this one.” For a print request, ask for image ID, intended size, orientation and quantity. For an album, distinguish must-include photographs from optional alternatives.

Tell reviewers how to resolve uncertainty. They might keep an alternate, leave a question or request a guided comparison. Requiring a final choice when the proof is too small or an image is missing leads to unreliable approval, not a faster production process.

Keep deadlines tied to a real next step, such as the start of retouching or an intended print-order date. A missed deadline calls for clarification under the agreed workflow, not an automatic inference that every picture is approved. Record any revised date and whether production has already started.

Freeze a submitted list while preserving later revisions

Differentiate saved favorites from a completed submission. The precise signal depends on the service: a submitted list, a written confirmation or a reviewed local record. Check that you have the intended reviewer and list rather than simply the most recent activity notification.

Capture a production snapshot with the selected image identities, list purpose, notes, set version and completion time. Keep the original exported list or agreed response alongside your reconciled working record. A dashboard that continues changing should not be the only record of the selection you began to edit.

If a client revises a list after work begins, preserve both revisions and record the difference. A newly added frame, removed frame and changed retouching instruction have different production consequences. Confirm which revision is authoritative before replacing the working selection.

Do not merge multiple reviewers silently. The couple’s album list, a parent’s print list and a designer’s recommendations can overlap while serving separate purposes. Keep them named and reconcile conflicts deliberately. A large union of favorites is not necessarily the list any person intended to approve.

Reconcile the list with exact local photographs

Importing or copying a filename list is only the start of reconciliation. Compare expected and matched counts, inspect unmatched entries and check repeated stems. A list can appear complete while resolving one client ID to the wrong camera file.

1. Preserve the received record. Keep the original list or response as evidence.
2. Resolve each client-visible ID. Use the proof-set mapping, not a current gallery position.
3. Check ambiguity. Investigate duplicate filenames, changed renderings and selections from an earlier set.
4. Create a named working snapshot. State purpose and revision so later work does not depend on a temporary highlight.
5. Reconcile count and content. Confirm both the number selected and representative identities, including any exception.
6. Acknowledge what was received. Summarize unresolved questions before treating them as production instructions.

Lightbox Pro’s reviewed build 62 provides manual ratings, labels, sets and filename search. It does not establish a hosted-gallery list importer or automatic matching of Pixieset selections. Do not assume that pasting a service’s exported CSV into a search box will create a correct native selection.

For a small job, a deliberate manual reconciliation may be practical. For repeated high-volume work, select a supported integration or process whose identity handling you have actually validated. Keep that tool’s capability separate from Lightbox Pro’s intended future client-choice return.

Separate image choices from retouching and product approvals

An image-selection round decides which photographs move forward. A retouching round decides whether a particular treatment is acceptable. A print or album round adds physical product choices and layout. Make those approvals explicit so a yes to one cannot accidentally authorize another.

For a portrait revision, connect the note to a specific rendered version. If the client asks for less skin smoothing, confirm the scope and produce a new proof rather than overwriting the old evidence. The natural retouching guide explains how to retain an editable, restrained treatment.

For album work, selected photographs still need crop, sequence, layout and cover review. A favorite image used as a small supporting frame is not the same decision as placing it across a full opening. Keep the accepted design version and selected product together, as described in the album production workflow.

When a request is ambiguous, ask for the intended result rather than guessing from a vague adjective. “Warmer” might refer to overall color, a particular face or the feeling of an image. A sample reference and a targeted question can resolve the difference before the entire set is reprocessed.

Worked example: a multi-person portrait commission

Consider a hypothetical twelve-person team assignment. Each person chooses one portrait, while a brand lead approves the consistent treatment and the website crop. The photographer creates one review group per person and records the same stable image IDs in the local job mapping.

One person submits P023, another saves several favorites without confirming a final choice, and the brand lead requests a different background treatment for the website set. Treat these as three different states. Only the first is a completed individual selection; the second needs clarification, and the third affects treatment rather than choosing another exposure.

Freeze the completed choices as selection revision one, with unresolved people clearly marked. Make a small representative treatment proof for brand review before applying the background request to the full team. Once the treatment is accepted, finish the agreed photographs and produce the required website crops.

Before delivery, verify that each output maps to the intended person and accepted source. A correct count of twelve files would not reveal an accidentally duplicated portrait or someone’s unconfirmed favorite. Record the accepted treatment and crop version alongside the final list.

If someone later changes their choice, retain the previous delivery record and create a replacement revision. Confirm whether the change affects the public website, print material or both. This approach adds a small amount of recordkeeping while preventing a much larger ambiguity about what was approved.

A wedding job can use the same record structure with different decisions. The couple’s selected frame P023 might be intended for an album and a parent’s wall print. Preserve those as two product requests. The album crop may emphasize an expression, while the wall print needs more surrounding space; accepting one rendering should not silently replace the other. Confirm the required crop and product before ordering.

When two people submit conflicting instructions, pause the affected item and identify the agreed decision-maker. Do not infer authority from who clicked most recently or selected the most photographs. Keep unaffected production moving where the workflow allows, and mark the held item clearly so it cannot be included accidentally in a supposedly complete batch. Once resolved, retain the final instruction together with the superseded request and its outcome.

Release the checked output and retain the approval record

Inspect the actual final files after rendering and after passing through the delivery route. Confirm names, dimensions, crop, intended treatment and available downloads. Test a representative recipient experience using a safe separate destination so the check cannot overwrite your masters.

Retain the final image list, accepted proof or layout, resolved revision notes and delivered version. Keep exceptions visible: an image awaiting retouching, a print size not yet confirmed or a reviewer who has not completed the round. A completed gallery upload is not the same as completed client approval.

Close or archive the review according to the agreed process and service behavior. If access will expire, communicate that while keeping your own production records. Do not rely on an indefinitely available online link as the only evidence of accepted work.

Lightbox Pro’s long-term vision includes private client galleries and print/album choices returning into the catalog. The reviewed build does not contain that finished hosted service, synchronization or delivery workflow. The website’s client approval demonstration is illustrative. Use established proofing tools today and keep the identity mapping that makes a future or external integration trustworthy.